Microsoft Teams: Location-Based Routing update blocks OS default location for Operator Connect in India
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Microsoft asks admins to prevent or fix an issue. Read what it asks below and check the linked documentation; whether your tenant is affected is not known here.
- Microsoft's start date
- 22 Jun 2026
- Last changed by Microsoft
- 22 Jun 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedWhat and Why
We’ve updated Location-Based Routing (LBR) behavior for Operator Connect in India to ensure compliance with India toll bypass regulations. Microsoft Teams now blocks the use of a manually set Windows location (“OS default location”) for LBR-enforced users.
If a user’s location is derived from OS default settings instead of network-based detection, geo-coordinates are stripped and cannot be used for routing decisions. This helps prevent toll bypass and location spoofing.
This change reached General Availability on April 30, 2026. We acknowledge this change was not communicated in advance and are sharing this post to provide guidance.
Rollout Schedule
- This change has completed rollout (Worldwide and GCC).
Impact on Your Organization
Who is affected
- Tenants using Operator Connect in India with Location Based Routing enabled, especially:
Platforms/Services
- Microsoft Teams (desktop)
- Windows Location Services
- Operator Connect (India)
What will happen
- Teams will no longer accept manually set OS default location as a valid source for LBR enforcement
- When network-based location detection fails:
- Users may experience:
- Corporate environments may increase impact due to:
- Geo-coordinates are stripped
- LBR cannot validate user location
- PSTN calling may be disabled
- Intermittent dial pad or PSTN calling availability
- Calling working outside the corporate network but failing inside
- VPNs or proxies (including Zscaler configurations)
- Virtual machines or remote desktop environments
- Windows Location Services traffic routed through VPN instead of split tunneling
This behavior is by design. LBR in India requires verified network-based location detection for regulatory compliance.
Action Required / Recommendations
- Update VPN split-tunnel configurations to ensure Windows Location Services URLs are routed directly (not through VPN or proxy)
- Do not rely on manually set OS default location for LBR-enforced users
- Validate that network-based location detection is functioning correctly, especially for users reporting intermittent calling issues
- If users report a disabled dial pad:
- Verify whether their device is falling back to OS default location
- Check network routing configuration
Learn more: Plan Operator Connect for India | Microsoft Learn
Compliance considerations
| Consideration | Explanation |
|---|---|
| Does the change alter how existing customer data is processed, stored, or accessed? | The change modifies how location data is validated and processed by enforcing network-based detection and rejecting OS-derived location sources for LBR decisions. |
| Does the change modify, interrupt, or disable any Purview-related capabilities? | Calling functionality may be disabled when compliant location data is unavailable, which could indirectly impact user activity and communication patterns. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.