A sister-city partnership raises EU-style expectations that certain personal data stay in an approved geography. Which Microsoft 365 trust topic addresses that concern?
Select an answer to reveal the explanation.
Short Explanation
Sister-city rules that care about geography are a data-residency conversation. Microsoft residency options help keep data at rest where policy requires—not a slide transition setting.
Full Explanation
Sister-city partnerships that raise EU-style expectations for keeping certain personal data in an approved geography are addressed by data residency support to help meet geographic regulatory expectations. Microsoft 365 trust topics include residency commitments about where customer data is stored at rest—precisely the concern when geography matters for citizen personal data shared across borders.
Planner emoji reactions, PowerPoint morph transitions, and Teams Together mode backgrounds are UX features and do not control data-at-rest geography for regulatory residency requirements in a municipal tenant.
Exam caveat: residency is about storage location; privacy laws may also require additional controls such as lawful basis documentation, DLP, and Priva workflows—residency alone may not satisfy every privacy obligation. Operational check: document which Microsoft 365 data residency offering applies to the city’s tenant region, confirm workloads holding sister-city personal data are in scope, and involve legal before expanding storage to another geography. In municipal Microsoft 365 fundamentals scenarios, always map the business need to the named capability, reject distractors that describe a different pillar, and verify the control in the admin portal before telling leadership the risk is closed.