Official documentation checked October 14, 2026.
A “region not supported” message in Copilot does not establish that an EU tenant must disable its data protections. Copilot supports EU organizational use, while particular features, models, clouds, and rollout stages can have different availability.
Do not change the tenant’s country, disable governance controls, or run Teams location commands to work around the message. Establish which service is displaying it first.
Identify the exact unsupported experience
Record the full message, time, app or URL, account type, tenant cloud, and the feature you selected. Distinguish a general Copilot sign-in error from a message appearing only when selecting a model, agent, or new capability.
Confirm that the signed-in account is the intended organizational account. If the same person has personal and work accounts, test in a fresh browser profile without importing confidential content. Note whether ordinary organizational Chat works and whether the problem is limited to one feature.
Check Microsoft’s current availability and language guidance and the feature’s own requirements. A service being available in a market does not guarantee every new capability is available to every account there.
Separate EU commitments from model-specific restrictions
Microsoft’s privacy documentation describes EU Data Boundary commitments for organizational Copilot with qualifications. It does not say the EU Data Boundary generally blocks Copilot until a tenant disables it.
Some model choices require a distinct review. For example, Microsoft’s current Anthropic configuration guidance describes defaults for EU/EFTA and UK customers, provider access controls, and residency exclusions. A model being disabled by policy may be intentional, not a defect.
If the issue is limited to such a model or feature, ask the administrator whether it is approved and supported. Do not enable an external provider solely to remove an error before the contractual and data-residency implications have been reviewed.
Run a safe administrator-led diagnostic
- Verify the user’s actual assigned entitlement and the requirements for the affected app or feature.
- Check relevant service-health notices and rollout messages for the tenant.
- Compare the same approved, nonsensitive task in a supported web or app experience. Record what succeeds and what fails.
- Have IT inspect the managed network path if the apparent connection region or proxy routing may be involved. Do not use a VPN to bypass market restrictions.
- Escalate a persistent discrepancy with the tenant cloud, feature, account context, exact message, and sanitized timestamps or request identifiers.
A comparison narrows the affected scope; it does not by itself prove a licensing, caching, or geography diagnosis. Avoid repeated license purchases, tenant migrations, or organization-wide policy changes without evidence.
Do not use emergency-location commands as a Copilot fix
Set-CsOnlineLisLocation is a Microsoft Teams command for modifying an emergency dispatch location. Its Location parameter describes a place such as a floor or office. It does not move the Microsoft 365 tenant, change Copilot processing geography, or disable the EU Data Boundary.
Do not run or adapt such commands to troubleshoot Copilot. If someone has already altered Teams emergency-location configuration following incorrect advice, notify the Teams administrator and verify the intended emergency-location records through the normal change process.
The desired outcome is access to an approved, supported feature with the organization’s protections intact. If a feature is unavailable under those conditions, retain the approved alternative and ask Microsoft or the service owner for the supported path rather than bypassing the restriction.