Microsoft’s EU Data Boundary
Microsoft has officially completed its EU Data Boundary for cloud services, pledging to store and process customer and personal data exclusively within the EU and EFTA.
Let’s take a closer look at what this really means.
On the surface, the commitment to store data within the EU sounds reassuring. Microsoft’s measures, including pseudonymization and encryption, aim to protect personal data in system-generated logs. Yet, the fine print reveals exceptions that could undermine these promises. Data from certain Azure services can still be transferred outside the EU if Microsoft deems it necessary for cybersecurity investigations. But who defines “necessary,” and what criteria guide these decisions?
But don’t get me wrong! This initiative marks a significant advancement in the quest for digital sovereignty and data protection, and it’s a step in the right direction for both businesses and consumers. For businesses utilizing Microsoft services, understanding how to configure for the EU Data Boundary is crucial:
1) Azure Users: Ensure that regional services are deployed in an EU Data Boundary region to be in-scope. For Professional Services Data, configure Azure Resource Manager accordingly.
2) Dynamics 365 & Power Platform: Provision your tenant in a Geo located in the EU Data Boundary to ensure compliance.
3) Microsoft 365: Customers signing up in EU or EFTA regions are in scope, but those with Multi-Geo Capabilities are excluded even if their tenant appears to be in the EU.
Is Microsoft’s EU Data Boundary a real step towards digital sovereignty?