{"id":17007,"date":"2026-06-23T08:01:47","date_gmt":"2026-06-22T23:01:47","guid":{"rendered":"https:\/\/m365jp.net\/?p=17007"},"modified":"2026-06-23T08:05:30","modified_gmt":"2026-06-22T23:05:30","slug":"mc1401300-microsoft-teams-location-based-routing-update-blocks-os-default-location-for-operator-connect-in-india","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2026-06-23-mc1401300-microsoft-teams-location-based-routing-update-blocks-os-default-location-for-operator-connect-in-india","title":{"rendered":"MC1401300 | Microsoft Teams: Location-Based Routing update blocks OS default location for Operator Connect in India"},"content":{"rendered":"<div class=\"postie-post\">\n<div>\n<hr>\n<table id=\"section\">\n<tbody>\n<tr>\n<th width=\"95%\">MC1401300 | Microsoft Teams: Location-Based Routing update blocks OS default location for Operator Connect in India<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n<hr>\n<table id=\"data\">\n<tbody>\n<tr>\n<th>Classification<\/th>\n<td>preventOrFixIssue<\/td>\n<\/tr>\n<tr>\n<th>Last Updated<\/th>\n<td>06\/22\/2026 22:55:20<\/td>\n<\/tr>\n<tr>\n<th>Start Time<\/th>\n<td>06\/22\/2026 22:55:16<\/td>\n<\/tr>\n<tr>\n<th>End Time<\/th>\n<td>12\/31\/2026 08:00:00<\/td>\n<\/tr>\n<tr>\n<th>Message Content<\/th>\n<td>\n<p><b>[What and Why:]<\/b><\/p>\n<p>  We\u2019ve updated <b>Location-Based Routing (LBR)<\/b> 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 (\u201cOS default location\u201d) for LBR-enforced   users.<\/p>\n<p>If a user\u2019s 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.<\/p>\n<p>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.<\/p>\n<p><b>[Rollout Schedule:]<\/b><\/p>\n<p>  <\/p>\n<ul>  <\/p>\n<li>This change has completed rollout (Worldwide and GCC).<\/li>\n<\/ul>\n<p><b>[Impact on Your Organization:]<\/b><\/p>\n<p><b>Who is affected:&nbsp;<\/b><\/p>\n<p>  <\/p>\n<ul>  <\/p>\n<li>Tenants using Operator Connect in India with Location Based Routing enabled, especially:<\/li>\n<ul>\n<li>Users on corporate networks or VPNs (especially Zscaler configurations)<\/li>\n<li>Users on virtual machines or remote desktop environments<\/li>\n<li>Environments where Windows Location Services URLs are routed through VPN or proxy instead of split tunneling<\/li>\n<\/ul>\n<\/ul>\n<p>  <\/p>\n<p><b>Platforms\/Services:<\/b><\/p>\n<ul>\n<li>Microsoft Teams (desktop)<\/li>\n<li>Windows Location Services<\/li>\n<li>Operator Connect (India)<\/li>\n<\/ul>\n<p><b>What will happen:<\/b><\/p>\n<ul>  <\/ul>\n<\/p>\n<ul>\n<li>Teams will no longer accept <b>manually set OS default location <\/b>as a valid source for LBR enforcement<\/li>\n<li>When network-based location detection fails:\n<ul>\n<li>Geo-coordinates are stripped<\/li>\n<li>LBR cannot validate user location<\/li>\n<li>PSTN calling may be disabled<\/li>\n<\/ul>\n<\/li>\n<li>Users may experience:\n<ul>\n<li>Intermittent dial pad or PSTN calling availability<\/li>\n<li>Calling working outside the corporate network but failing inside<\/li>\n<\/ul>\n<\/li>\n<li>Corporate environments may increase impact due to:\n<ul>\n<li>VPNs or proxies (including Zscaler configurations)<\/li>\n<li>Virtual machines or remote desktop environments<\/li>\n<li>Windows Location Services traffic routed through VPN instead of split tunneling<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>This behavior is <b>by design<\/b>. LBR in India requires verified <b>network-based location detection<\/b> for regulatory compliance.<\/p>\n<p>  <\/p>\n<p><b>[Action Required \/ Recommendations:]<\/b><\/p>\n<ul>\n<li>Update VPN split-tunnel configurations to ensure <b>Windows Location Services URLs are routed directly<\/b> (not through VPN or proxy)<\/li>\n<li>Do not rely on <b>manually set OS default location<\/b> for LBR-enforced users<\/li>\n<li>Validate that <b>network-based location detection is functioning correctly<\/b>, especially for users reporting intermittent calling issues<\/li>\n<li>If users report a disabled dial pad:\n<ul>\n<li>Verify whether their device is falling back to OS default location<\/li>\n<li>Check network routing configuration<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>  <\/p>\n<ul>\n<p>  <\/ul>\n<p><b>Learn more:<\/b>&nbsp;<a href=\"https:\/\/learn.microsoft.com\/microsoftteams\/operator-connect-india-plan\">Plan Operator Connect for India | Microsoft Learn<\/a><\/p>\n<p><b>[Compliance considerations:]<\/b><\/p>\n<table class=\"table table-bordered\">\n<tbody>\n<tr>\n<td><b>Consideration<\/b><\/td>\n<td><b>Explanation<\/b><\/td>\n<\/tr>\n<tr>\n<td>Does the change alter how existing customer data is processed, stored, or accessed?<\/td>\n<td>The change modifies how location data is validated and processed by enforcing network-based detection and rejecting OS-derived location sources for LBR decisions.<\/td>\n<\/tr>\n<tr>\n<td>Does the change modify, interrupt, or disable any Purview-related capabilities?<\/td>\n<td>Calling functionality may be disabled when compliant location data is unavailable, which could indirectly impact user activity and communication patterns.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>MC1401300 | Microsoft Teams: Location-Based Routing update blocks OS default location for Operator Connect in  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17007","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/17007","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=17007"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/17007\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=17007"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=17007"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=17007"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}