Is there a roadmap or planned update to decouple Location-Based Routing (LBR) from the root OnlinePSTNGateway object in Microsoft Teams Direct Routing?

Question

Is there a roadmap or planned update to decouple Location-Based Routing (LBR) from the root OnlinePSTNGateway object in Microsoft Teams Direct Routing?

Jr. McClean 0

Currently, enabling LBR requires root gateway configuration (e.g., via -GatewaySiteLbrEnabled). For organizations utilizing modern multi-tenant partner architectures and derived trunking models (such as AudioCodes Live Pro/Express), the underlying global gateway configuration is managed entirely by the provider. Because administrators lack root modification rights over these shared gateway objects, they are unable to configure LBR or manage geographic routing through the Teams Admin Center (Voice > Direct Routing > SBCs).

Furthermore, enforcing LBR as a strict hardware-level switch creates major deployment hurdles by entirely blocking unmapped or remote workers in regions (like North America) where strict anti-toll-bypass compliance is not a legal mandate.

Proposed Solution

Decouple LBR from the Gateway Object: Shift LBR evaluation away from the root hardware gateway switch toggle to occur at the Voice Route, PSTN Usage, or Calling Policy layer.

Support Derived & Shared Trunks: Allow enterprises to manage geographic routing via distinct voice routes peered with gateways, bypassing the need for root gateway property access.

Regional Flexibility & Compliance: Enable flexible enforcement so enterprises can avoid unnecessary toll-bypass blocks in regions where they aren't legally mandated, while automatically locking LBR on for heavily regulated regions like India.

Will Microsoft be introducing policy-level or route-level LBR controls in future updates to accommodate multi-tenant and derived trunking models?

0 comments

2 answers

Your answer

Answer 1

Jr. McClean 0

Thank you for taking the time to clarify and for pointing me toward the feedback portal. I completely understand that community forums do not have visibility into unannounced roadmaps.

For anyone else running into this same hurdle with multi-tenant partner architectures (like AudioCodes Live) where tenant admins don't have root OnlinePSTNGateway rights, I previously logged this as a feature request here: Unlock LBR for Derived Trunks.
If anyone in the community has experience or tips on how to gain visibility for feedback items like this, or if there are specific partner channels or product groups that track these architectural gaps, I would genuinely appreciate any advice.

Thanks again for the guidance!

Helen Luu 3,555 Reputation points Independent Advisor

2026-10-15T15:34:23.9033333+00:00

Thank you so much for your quick action. I hope the Microsoft product team will consider your feedback and implement the suggested changes once they have completed their review.

Answer 2

Hello @Jr. McClean

At this time, I could not find any publicly announced roadmap or planned update regarding the decoupling of Location-Based Routing (LBR) from the OnlinePSTNGateway object in Microsoft Teams Direct Routing. Based on the information currently available, the existing LBR design still requires configuration at the PSTN gateway level.

I understand that this can be an important consideration, particularly in scenarios where the root PSTN gateway is managed by a service provider and is not directly under the tenant administrator's control.

To help bring visibility to this requirement, I strongly encourage you to submit your suggestion through the Microsoft Feedback Portal. The Microsoft development teams actively review customer feedback, and many enhancements have been implemented based on community input.

Since this is a user-to-user forum, my role is limited to providing guidance based on publicly available Microsoft information. I’m therefore unable to confirm any unannounced roadmap or future product changes.

I hope this information helps clarify the current situation regarding LBR and the OnlinePSTNGateway configuration. While I understand this may not provide the specific solution you were hoping for, submitting your requirement through the Microsoft Feedback Portal would be the appropriate way to bring this scenario to Microsoft's attention for consideration.

Please feel free to reach out if you have any further concerns.