In Exchange Online backups there is a job that runs daily called a “live update”. This job is small in size (only a few KB) but it attempts to write to the library directly from the Index Server associated with the Exchange Online Client.
In my environment the Cloud Storage library is restricted to specific VNET’s for security. This VNET contains the Access Nodes and MediaAgents as we use Cloud Storage Accelerator to process the backups.
When the VNET restriction is in place this job fails as the Index Server which is not in the same VNET is unable to access the cloud library. If I remove the VNET restriction on the storage account the job runs without error.
Is there a way to find out where this job is initiated from so it can be massaged to write to storage via the MediaAgent rather than directly?
