An organization has Azure resources deployed in both the United States and the European Union (EU). Legal compliance regulations require that all logs generated by EU resources remain stored within the EU, while US resource logs must reside in the US. Additionally, administrators must only access logs for their respective regions.
Which log routing and storage solution should you design to meet these requirements?
- ADeploy a single central Log Analytics workspace in the US, route all resource logs to it, and use Azure RBAC to restrict access based on the resource origin.
- BDeploy a single central Log Analytics workspace and use Azure Policy with a Deny effect to block resource logs from being routed across regional boundaries.
- Deploy one Log Analytics workspace in the US and a separate Log Analytics workspace in the EU, route the respective resource logs to each workspace, and manage access using Microsoft Entra ID groups.Answer
- DDeploy one Log Analytics workspace in the US and a separate Log Analytics workspace in the EU, route the respective logs to each, and assign log reader permissions directly to individual administrator user accounts.
Answer
Deploy one Log Analytics workspace in the US and a separate Log Analytics workspace in the EU, route the respective resource logs to each workspace, and manage access using Microsoft Entra ID groups.
The correct solution requires deploying separate Log Analytics workspaces in the US and the EU to satisfy the regional data residency requirements. Routing each region's resource logs to its local workspace keeps the data within the required boundaries. Managing workspace access via Microsoft Entra ID groups ensures secure, administrative segregation with minimal management overhead, aligning with Azure best practices.
Step-by-Step Solution
Key Concept
Data residency compliance and administrative isolation in Azure Monitor log routing design.
Estimated Time:1m 30s