An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
To centralize log analysis across multiple Azure subscriptions you should use Azure Monitor with a centralized Log Analytics workspace and connect all subscriptions to it. The core design is to collect platform logs, activity logs, and resource diagnostics from each subscription into a single workspace, then control access using Azure RBAC.
First create a dedicated Log Analytics workspace in a central subscription that will act as the aggregation point. This workspace can receive logs from resources located in any subscription within the same Azure AD tenant. After creating the workspace, configure diagnostic settings on each subscription and on individual Azure resources such as virtual machines, App Services, SQL databases, storage accounts, and networking components so that their logs and metrics are sent to this central workspace.
For subscription-level visibility, enable Activity Log export by configuring diagnostic settings at the subscription level and selecting the central Log Analytics workspace as the destination. This ensures that administrative operations across all subscriptions are captured in one place.
For virtual machines, enable the Azure Monitor Agent and connect each VM to the centralized Log Analytics workspace using Data Collection Rules. The recommended approach is to create a Data Collection Rule that defines which event logs, performance counters, and syslogs should be collected, associate it with the target VMs across subscriptions, and specify the central workspace as the destination. Example using Azure CLI:
az monitor log-analytics workspace create \
--resource-group Central-RG \
--workspace-name Central-Logs \
--location eastus
az monitor data-collection rule create \
--resource-group Central-RG \
--name Central-DCR \
--location eastus
Then associate the DCR with VMs:
az monitor data-collection rule association create \
--name vm-dcr-association \
--rule Central-DCR \
--resource /subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.Compute/virtualMachines/<vm-name>
For PaaS services, configure Diagnostic Settings in each resource and choose the central Log Analytics workspace as the destination. This can also be automated with Azure Policy so that any new resource automatically sends logs to the workspace. A policy initiative can enforce that diagnostic settings are enabled and pointing to the central workspace, ensuring governance at scale.
To enable cross-subscription visibility, grant IT Operations the appropriate role such as Log Analytics Reader or Monitoring Reader at the workspace level. They do not need full access to every subscription if logs are centralized in the workspace.
For querying, use Kusto Query Language in the central workspace. Since all data resides in one workspace, cross-subscription queries are not required. If multiple workspaces are unavoidable, you can use cross-workspace queries such as:
workspace("workspace-id-1").SecurityEvent
| union workspace("workspace-id-2").SecurityEvent
For long-term retention and cost optimization, configure retention policies per table and optionally archive logs to Azure Storage. For security analytics, consider connecting the workspace to Microsoft Sentinel, which operates on top of Log Analytics and provides SIEM capabilities across all connected subscriptions.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin