Loading...

Microsoft Teams: PSTN calling blocked on Teams phone devices in India when emergency location is not configured

Microsoft Teams: PSTN calling blocked on Teams phone devices in India when emergency location is not configured

PSTN calling on Teams phone devices in India using Operator Connect is blocked if emergency locations are not configured, per telecom regulations. Admins must set emergency addresses and verify Location-Based Routing to restore calling. This change applies to Teams app version 1449+ and ensures regulatory compliance. What and Why To meet telecommunications regulations in India, Teams now requires an emergency location to be configured for Teams phone devices using PSTN calling with Operator Connect. This location helps verify that devices are operating within India. If a device cannot be validated, PSTN calling will be blocked to comply with regulatory restrictions on call routing. Rollout Schedule General Availability (India tenants using Operator Connect): Available now. Impact on Your Organization Who is affected Organizations with users in India using Microsoft Teams Phone with Operator Connect Devices running Teams app version 1449/1.0.94.2026088402 and later Admins responsible for configuring emergency locations and Location-Based Routing (LBR) policies Platforms/Services: Teams Phone devices (IP phones) What will happen PSTN calling behavior changes when emergency location is not configured: Outbound PSTN calls are blocked. Inbound PSTN calls may: Fail to connect, or Route to voicemail This behavior is enforced by design for regulatory compliance. No change occurs for users and devices with properly configured emergency locations. Action Required / Recommendations Action required by admins To restore PSTN calling functionality, complete the following: Configure emergency address/location for all Teams Phone users and devices in India. Verify Location-Based Routing (LBR) configuration, including: Network sites and subnets Emergency location associations Validate device compliance after configuration changes. Review your affected tenants. Communicate this requirement to your helpdesk and telephony admins. Update internal deployment documentation for Teams Phone in India. Learn more: Plan and configure Location-Based Routing for Operator Connect for India | Microsoft Teams | Microsoft Learn Compliance considerations Question Answer Does the change alter how existing customer data is processed, stored, or accessed? Yes. PSTN calling behavior depends on configured emergency location data to validate device location. Does the change include an admin control? Yes. Admins must configure emergency locations and LBR settings to enable PSTN calling. Message ID: MC1317835

The post Microsoft Teams: PSTN calling blocked on Teams phone devices in India when emergency location is not configured appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Microsoft Teams: PSTN calling blocked on Teams phone devices in India when emergency location is not configured

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Contact Center – Manage overnight shifts as a single continuous schedule

We are announcing the ability to manage overnight shifts as a single continuous schedule in Dynamics 365 Contact Center. This feature will rea...

9 hours ago

Manage who can upload advanced agents and plugins

Starting September 25, Microsoft 365 admins can control who uploads advanced Copilot agents and plugins, limiting access to specific users or ...

9 hours ago

Microsoft 365 Copilot: Insights Copilot Analytics cowork adoption impact

Microsoft 365 Copilot now includes Cowork adoption and impact insights in the Consumption dashboard and Viva Insights Advanced Insights. Avail...

9 hours ago

Writing Blocks in M365 Copilot

Microsoft 365 Copilot will introduce Writing blocks by mid-September 2026, enabling users to create and refine longer-form content like emails...

9 hours ago

Outlook: Change the organizer of meetings

Microsoft is introducing a feature to change the organizer of eligible Outlook meetings, allowing transfer of meeting ownership within an orga...

9 hours ago

Code Blocks in M365 Copilot

Microsoft 365 Copilot will support inline previews of code blocks, charts, and diagrams within conversations, eliminating the need for a separ...

9 hours ago

Microsoft SharePoint: PowerShell support for brand fonts deletion

Microsoft SharePoint will introduce the Remove-SPOFontFile PowerShell cmdlet by mid-October 2026, allowing admins to delete brand fonts across...

9 hours ago

[Outlook Mobile] Purview Data Loss Prevention support for Calendar Events

Outlook for iOS and Android will support Microsoft Purview Data Loss Prevention for calendar events, helping prevent sensitive data sharing in...

9 hours ago

[Outlook Mac] Purview Data Loss Prevention support for Calendar Events

Outlook for Mac will support Microsoft Purview Data Loss Prevention for calendar events, detecting sensitive info in meeting details to preven...

9 hours ago

[Outlook Mobile] Purview DLP Wait-on-Send Support

Outlook for iOS and Android will support Microsoft Purview DLP wait-on-send policies, allowing organizations to require and configure a wait t...

9 hours ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.