Microsoft Copilot
What is data residency control in Microsoft 365?
Data residency control in Microsoft 365 means knowing where each workspace and its data sit and checking that against the rule for that region. Multi-Geo places the data; oversight is an inventory by region and a check of the attributes that drive placement.
In short
- Residency rules are geographic, but the tenant changes with every new team, user move and guest.
- Microsoft 365 Multi-Geo places data; it does not tell you whether placement still matches your rule.
- The attributes that drive placement, such as a user country or preferred data location, must be filled and correct.
- Rencore does not move or store data by region; it gives visibility and policy oversight over where things sit.
Step by step
Five steps keep residency consistent by adding oversight around the native mechanism, not by replacing it.
-
Write the rule per region and data class
State which data must stay in which region, for example employee records in the EU, and which regions each subsidiary operates in. A rule specific enough to test is the basis for every later step.
-
Check the attributes that drive placement
Confirm that user country, department and preferred data location in Entra ID are filled and current, and that Multi-Geo is configured for the regions you need. An empty attribute silently places data by default.
Tip: Check a sample of leavers and movers first, because they are where attributes go stale.
-
Inventory workspaces, owners and guests by region
Build a view of which teams, sites and groups sit in which region, who owns them and which guests belong to them. This is the picture a residency rule is checked against.
-
Segment oversight by region
Scope what each regional admin sees and governs to their own region, so people responsible for a region see that region only. Virtual environments, filtered on the Entra ID country attribute, do this.
-
Check exceptions and keep the record
Flag workspaces whose owner or guests fall outside the rule, route each to its owner and record the decision. The record shows an auditor that residency was checked, not only configured.
What makes data residency controls so complex
A residency rule is simple to write: this data stays in this region. The tenant it must hold in is not simple. Users move countries, a workspace is created in one country for teams in several, guests join from outside the region, and group membership changes weekly. Each change can place data or access somewhere the rule did not intend.
Microsoft 365 Multi-Geo places data by the preferred data location set for a user or a group, and it relies on those settings being right for every user and group. Residency therefore turns into a data quality question. Without an inventory that shows where each workspace and its owner sit, the rule stays a policy on paper that nobody checks against reality.
Connectors in this How-to
Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.
Last updated 11 November 2026
