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

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?