Setting up a Survivable Branch Appliance for Teams Direct Routing
Verified 2026-09-30 · 64 sources · tier 2
For Teams voice administrators configuring branch PSTN survivability for Direct Routing..
A Survivable Branch Appliance (SBA) allows Microsoft Teams desktop clients and Teams Phones to maintain PSTN calling during an internet outage 5441. Direct Routing connects your PSTN operator through a certified Session Border Controller (SBC), which hosts or connects to the SBA software 5524.
Before you start
Direct Routing requires a Microsoft-certified SBC, PSTN trunks, users homed online, a public IP address, an SBC FQDN in a verified tenant domain with public DNS, and a publicly trusted TLS certificate 56. The SBA cmdlets in Teams PowerShell are intended exclusively for tenant administrators and SBC vendors and do not operate in a tenant without an SBA configuration 20.
SBA mode is supported on Teams Windows and macOS desktop clients running on physical machines and on Teams Phones; virtual machines and web clients are not supported 54. In offline mode, users can make and receive PSTN calls through the local SBA/SBC with media through the SBC, hold and resume PSTN calls, blind transfer, and forward calls to a single phone number or Teams user 38. Incoming calls to auto attendants or call queues can be redirected to a local agent or alternate numbers 37, and VoIP calls between users behind the same SBA remain supported 39. Switching tenants, Entra ID reverse number lookups, and location sharing on emergency calls are not supported in SBA mode 573435.
What changes by situation
Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.
Five questions. One permanent page you can send to your manager.
Step 1 Evaluate site fit
Yes: the SBC (and its PSTN trunk) is reachable from the site's LAN without the internet
Do
Verify that users can still connect to the SBC over the local intranet if WAN connectivity fails, because the SBA model assumes the local network and SBC access remain operational during a Microsoft cloud outage 41.
Verify
Confirm that the client device can route to the appliance address on the local network when the external internet route is disconnected 1.
Rollback
Suggested rollback: No configuration changes were made at this step.
No: the site reaches its SBC only over the link that would be down
Do
Do not deploy an SBA at this site: Microsoft frames the SBA architecture around branch users retaining local intranet connectivity to their SBC when cloud access is down 41. This is inferred: because the Teams client moves to the SBA only when the internet is disconnected while the device can still reach the SBA, a site lacking a locally reachable SBC cannot benefit from the appliance 1.
Verify
Suggested check: Document that the site lacks a local SBC path and exit the deployment process for this location.
Rollback
Suggested rollback: No configuration changes were made at this step.
Step 2 Configure media bypass on the SBC
Yes, media bypass is already enabled on this SBC
Do
Confirm that your SBC gateway already operates with media bypass enabled, as media bypass is required so branch clients exchange media directly with the SBC 58.
Verify
Ensure internal clients have network access to the public IP address of the SBC, using hairpinning on the NAT device if necessary to keep traffic internal 13.
Rollback
Suggested rollback: Maintain the existing media bypass setting.
No, the SBC currently runs without media bypass
Do
Enable media bypass on the Direct Routing gateway using Set-CsOnlinePSTNGateway with -MediaBypass $true 12. Ensure clients can reach the public IP address of the SBC from the internal network, using NAT hairpinning so traffic remains on enterprise network equipment 13. In normal operation, SIP signaling still flows via the Microsoft cloud while media flows directly to the SBC 14.
Verify
Confirm firewall configurations allow client UDP/SRTP ports 50000-50019 to reach the SBC's defined media ports 11.
Rollback
Run Set-CsOnlinePSTNGateway with -MediaBypass $false 12.
Step 3 Open required network ports
Do
Open ports 3443, 4444, and 8443 between Teams clients and the Microsoft SBA Server 19. Allow port 5061 (or the SBC's configured SIP port) between the SBA Server and the SBC 50. Allow outbound UDP port 123 from the SBA Server to an NTP server, and outbound port 443 to Microsoft 365 3036. Define Azure IP ranges and service tags for the public cloud according to Microsoft download id 56519 9. Enable TLS 1.2 on the operating system hosting the SBA VM 52.
Verify
Suggested check: Verify port reachability to the required client ports on the SBA from a local branch client subnet.
Rollback
Suggested rollback: Remove the newly created firewall rules and restore original network access lists.
Step 4 Register the SBA application in Microsoft Entra ID
Do
Register a single Microsoft Entra ID application to serve all SBAs in the tenant 40. Microsoft orders the setup sequence as: register the application, set implicit grant tokens, set API permissions, and create the client secret 5. Configure supported account types to accounts in this organizational directory only, set the Web redirect URI to https://login.microsoftonline.com/common/oauth2/nativeclient, and enable implicit grant for both access tokens and ID tokens 4. Add the Application API permission Skype and Teams Tenant Admin Access > application_access_custom_sba_appliance 3. Create a client secret, choosing any description and expiration, and copy the secret value immediately 51.
Verify
Confirm you have documented both the Application (client) ID from the application's Overview tab and the client secret value, which are required for the SBC-side SBA configuration 6.
Rollback
Suggested rollback: Delete the registered application from the identity provider portal.
Step 5 Provision the SBA object in Teams PowerShell
Do
Connect to Teams PowerShell, which is required because the Teams admin center does not support SBA configuration 59. Run New-CsTeamsSurvivableBranchAppliance with -Fqdn set to the appliance FQDN, an optional -Description, and an optional -Site parameter specifying the tenant network site 3149.
Verify
Run Get-CsTeamsSurvivableBranchAppliance to confirm the SBA appears in the tenant configuration with an Identity matching the supplied FQDN 2631.
Rollback
Remove the SBA object using Remove-CsTeamsSurvivableBranchAppliance -Identity <sba-fqdn> 47.
Step 6 Create the branch survivability policy
Do
Create the policy using New-CsTeamsSurvivableBranchAppliancePolicy -Identity <policy-name> -BranchApplianceFqdns "<sba-fqdn>", listing one or more SBA FQDNs 43. If the command fails immediately after provisioning the SBA, wait and retry, as newly added SBAs might take time before they can be referenced in policies 32. Subsequent adjustments to the appliance list use Set-CsTeamsSurvivableBranchAppliancePolicy with @{add="..."} or @{remove="..."} 42.
Verify
Run Get-CsTeamsSurvivableBranchAppliancePolicy -Identity <policy-name> to verify that the policy exists and lists the configured SBA FQDNs 2543.
Rollback
Delete the survivability policy by running Remove-CsTeamsSurvivableBranchAppliancePolicy -Identity <policy-name> 46.
Step 7 Assign the survivability policy
User by user
Do
Assign the policy to each user individually by running Grant-CsTeamsSurvivableBranchAppliancePolicy -PolicyName <policy-name> -Identity <user> 29. Pass the policy name without a leading Tag: scope prefix 45.
Verify
Check the user configuration with Get-CsOnlineUser, noting that it may take time before the assigned SBA appears in the cmdlet output 44.
Rollback
Remove the policy from the user by granting the $Null policy: Grant-CsTeamsSurvivableBranchAppliancePolicy -PolicyName $Null -Identity <user> 28.
To a group that contains the site's users
Do
Assign the policy to a group of site users using Grant-CsTeamsSurvivableBranchAppliancePolicy -Group <group-id> -PolicyName <policy-name>, passing an optional -Rank relative to other group assignments of this policy type 27. Pass the policy name without a leading Tag: prefix 45.
Verify
Verify group members using Get-CsOnlineUser, allowing time for the SBA policy assignment to appear 44.
Rollback
Suggested rollback: Remove the policy assignment from the group using the administration interface.
To every user in the tenant
Do
Apply the policy tenant-wide by running Grant-CsTeamsSurvivableBranchAppliancePolicy -Global -PolicyName <policy-name> 27. Pass the policy name without the Tag: prefix 45. Note that users must be able to reach the configured SBA locally when the internet is down 1.
Verify
Inspect arbitrary users using Get-CsOnlineUser, allowing time for the global policy assignment to reflect in tenant user objects 44.
Rollback
Suggested rollback: Reassign the global policy assignment to an empty or default state in the command-line interface.
Step 8 Install and configure the SBA on the SBC hardware
AudioCodes
Do
Obtain the SBA software from the vendor, either embedded in firmware or for separate VM or hardware hosting 24. Follow AudioCodes documentation for SBC-side configuration using the Application (client) ID and client secret 653.
Verify
Suggested check: Verify the appliance interface indicates that the local SBA service is active and registered.
Rollback
Suggested rollback: Remove the SBA service configuration from the device or stop the virtual appliance.
Ribbon
Do
Obtain the SBA software package from Ribbon, supplied embedded in firmware or as a separate installation 24. Follow Ribbon documentation to link the SBA to your tenant using the Application (client) ID and client secret 653.
Verify
Suggested check: Verify the management interface reports the SBA status as running.
Rollback
Suggested rollback: Disable the SBA service in the appliance management interface.
Oracle
Do
Deploy the SBA software provided for Oracle SBC platforms 24. Configure the appliance following Oracle vendor documentation using the Application (client) ID and client secret 653.
Verify
Suggested check: Check management logs to confirm that the SBA application successfully connects.
Rollback
Suggested rollback: Disable or de-provision the SBA component within the SBC configuration.
TE-SYSTEMS anynode
Do
Obtain the SBA software from the vendor, either embedded in firmware or distributed separately 24. Follow TE-SYSTEMS documentation to configure the SBA service with the Application (client) ID and client secret 653.
Verify
Suggested check: Verify the system service manager shows the SBA service running.
Rollback
Suggested rollback: Stop and disable the SBA service.
Step 9 Configure emergency voice routes for offline survivability
Do
Add a pattern to the users' regular voice routing policy that matches emergency dial strings without a leading + sign 57. Direct Routing normally uses emergency call routing policies 60, but in SBA mode, emergency call routing policies are not supported and emergency dial strings bypass normalization, causing emergency calls to fail unless matched by regular voice routes 57. Note that while emergency calls can be placed through the SBA, dynamic location information is not shared 57.
Verify
Suggested check: Review regular voice route regex patterns in the shell interface to confirm they route emergency numbers without a leading plus symbol.
Rollback
Suggested rollback: Remove the emergency dial patterns from the regular voice routing policies.
Step 10 Address Continuous Access Evaluation limits
The tenant does not use CAE tokens
Do
Maintain standard tenant token policies: in normal operations without Continuous Access Evaluation (CAE), the SBA accepts expired client authentication tokens for up to 7 days, provided the client has connected to the SBA within the prior 24 hours 61.
Verify
Suggested check: Verify that tenant conditional policies do not enforce Continuous Access Evaluation.
Rollback
Suggested rollback: No adjustments required.
CAE stays on; we accept the short SBA operating window
Do
Retain tenant CAE policies, noting that when a tenant uses Continuous Access Evaluation tokens, the SBA remains operational for only about 30 minutes after an internet disconnection 61.
Verify
Suggested check: Document the operational time limit in the site disaster recovery runbook.
Rollback
Suggested rollback: No configuration changes were made at this step.
We will disable CAE so the SBA can run longer
Do
Disable CAE to allow the SBA to function for up to 7 days during an outage 6116. Navigate to Microsoft Entra Conditional Access and configure the "Customize continuous access evaluation" session control to Disabled 17.
Verify
Suggested check: Confirm that the conditional policy disabling CAE applies to the target branch users.
Rollback
Set the "Customize continuous access evaluation" session control back to its prior state or remove the disabling Conditional Access policy 17.
Step 11 Validate failover and recovery
Do
This is inferred: validate failover by simulating a WAN outage on a physical desktop client that has connected to the SBA within the last 24 hours 611. Disconnect the internet uplink while preserving local LAN routing to the SBA, then place and receive test PSTN calls 1. The Teams client switches to the SBA automatically, allowing ongoing calls to continue without user action 8.
Verify
Confirm that the client displays the Appliance mode banner; this banner is the only UI indicator of SBA mode, and calling will not work without it 10. Verify that restarted desktop clients reconnect using cached authentication during the outage 15. After restoring internet connectivity, confirm the client falls back to normal mode once calls finish 23, and verify that the SBA uploads collected Call Data Records to update tenant call history 18.
Rollback
Suggested rollback: Reconnect WAN links and return the network to normal operational status.
Step 12 Hand over operational procedures
Do
Record the client secret expiration date in your administrative schedule 51. Update the operational runbook specifying that SBA issues must be reported to the SBC vendor's support organization, noting that an SBA is configured 48. Microsoft supports Direct Routing only with certified SBCs and expects the SBC vendor to investigate first 62.
Verify
Suggested check: Review runbook documentation to ensure the vendor support escalation path and client secret renewal reminders are established.
Rollback
Suggested rollback: No configuration changes were made at this step.
Applicability
Applies to: Microsoft Teams Phone, Microsoft Entra ID, and Microsoft Teams PowerShell module. Deployments: multi-tenant, direct-routing, dod, and gcc-high. Sources checked 2026-09-30. In GCC High and DoD government clouds, features such as Entra ID reverse number lookup and Shared Calling are not available 6364.
What remains uncertain
The step-by-step SBC-side installation menus and configuration procedures for AudioCodes, Ribbon, Oracle, and anynode are not covered by the sources below. Specific Ribbon hardware platform models and release numbers supporting the Direct Routing SBA are not covered by the sources below. Tenant-side PowerShell procedures to remove group and global branch survivability policy assignments are not covered by the sources below. Whether the Entra ID application permission requires administrative consent after creation is not covered by the sources below. SBA sizing recommendations, licensing costs, and how clients choose among multiple SBAs listed within a single policy are not covered by the sources below.
See also
Configures feature of
- Microsoft teams phone — SBA is a Direct Routing feature of Teams Phone; this guide reuses the registry claims microsoft-teams-phone-sba-prereqs; -sba-clients; -sba-emergency-limits; -sba-powershell-only and -sba-token-limits rather than re-recording them.
Sources
- 1The Teams client moves to the SBA only when two conditions hold: the user is assigned a branch survivability policy for an SBA that is up, and the internet is disconnected while the user's device can still reach the SBA.Survivable Branch Appliance for Direct Routing · How it works, 'The following conditions must be met' list · Checked 2026-09-30
- 2TE-SYSTEMS states that the SBA is an additional Windows application that ships automatically, as a service, with every Windows-based anynode deployment.Microsoft Teams SBA - anynode · Page body, SBA description paragraph · Checked 2026-09-30
- 3The SBA application's API permission is 'Skype and Teams Tenant Admin Access' > Application permissions > application_access_custom_sba_appliance.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, 'API permissions' bullet · Checked 2026-09-30
- 4The SBA application is registered with supported account types set to accounts in this organizational directory only, a Web redirect URI of https://login.microsoftonline.com/common/oauth2/nativeclient, and implicit grant enabled for both access tokens and ID tokens; its name is free choice.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, 'keep the following in mind' list · Checked 2026-09-30
- 5Microsoft orders the application registration as: register the application, set the implicit grant tokens, set the API permissions, create the client secret.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, closing numbered list · Checked 2026-09-30
- 6The SBA registration needs two values produced by the Entra application registration: the Application (client) ID, shown on the application's Overview tab, and a client secret.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, 'you need the following values' list · Checked 2026-09-30
- 7AudioCodes markets Direct Routing SBA products as a physical Mediant 800C SBA appliance and as a virtual appliance.Survivability Products (SBA) for Microsoft Teams · Product comparison table · Checked 2026-09-30
- 8During an internet outage the Teams client switches to the SBA automatically, ongoing calls continue without interruption, and the user does not need to take any action.Survivable Branch Appliance for Direct Routing · How it works, first paragraph · Checked 2026-09-30
- 9The SBA prerequisites require Azure IP Ranges and Service Tags for the Public Cloud to be defined following Microsoft's published download (download id 56519).Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 7 · Checked 2026-09-30
- 11For direct media between the Teams client and the SBC, the client uses UDP/SRTP ports 50000-50019 and must reach the media ports defined on the SBC.Plan for media bypass with Direct Routing · Requirements for direct media traffic (between the Teams client and the SBC), table · Checked 2026-09-30
- 12Media bypass is controlled per SBC with Set-CsOnlinePSTNGateway and its -MediaBypass parameter set to true or false.Plan for media bypass with Direct Routing · About media bypass with Direct Routing, second paragraph · Checked 2026-09-30
- 13For media bypass the Teams client must have access to the public IP address of the SBC even from an internal network, and hairpinning can be configured on the NAT device so that traffic never leaves the enterprise network equipment.Plan for media bypass with Direct Routing · Call flow if the user has direct access to the public IP address of the SBC; Requirements for direct media traffic, Note · Checked 2026-09-30
- 14With media bypass enabled in normal operation, SIP signaling still always flows via the Microsoft cloud; only media stays local.Plan for media bypass with Direct Routing · Call flow if the user has direct access to the public IP address of the SBC, third bullet · Checked 2026-09-30
- 15During an internet outage the Teams desktop client can reconnect to the SBA with locally cached authentication information even after a client restart or machine reboot, provided that information was cached before the outage and is still within the supported SBA authentication period.Survivable Branch Appliance for Direct Routing · Known issues and considerations > In SBA mode, second sub-bullet · Checked 2026-09-30
- 16For tenants using Continuous Access Evaluation tokens, Microsoft names disabling CAE for the tenant as an alternative to the roughly 30-minute SBA operating window.Survivable Branch Appliance for Direct Routing · Known issues and considerations, CAE bullet · Checked 2026-09-30
- 17Microsoft Entra's CAE setting now lives in Conditional Access: it is toggled when creating a Conditional Access policy through the 'Customize continuous access evaluation' session control, which can be set to Disabled.Continuous access evaluation in Microsoft Entra · Enable or disable CAE, first paragraph and Migration table · Checked 2026-09-30
- 18After connectivity returns, the SBA uploads the Call Data Records it collected to the cloud and call history is updated for review by the tenant administrator.Survivable Branch Appliance for Direct Routing · How it works, second paragraph · Checked 2026-09-30
- 19The Microsoft SBA Server communicates with the Teams client on ports 3443, 4444 and 8443, which must be allowed on the firewall.Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 3 · Checked 2026-09-30
- 20Microsoft's cmdlet reference says the SBA cmdlets are intended exclusively for tenant administrators and SBC vendors and are inoperative in a tenant that has no SBA configuration.New-CsTeamsSurvivableBranchAppliance (MicrosoftTeams) · Description · Checked 2026-09-30
- 21Microsoft lists the tenant-side SBA configuration as four steps: create the SBAs, create the Teams branch survivability policy, assign the policy to users, and register an application for the SBA with Microsoft Entra ID.Survivable Branch Appliance for Direct Routing · Configuration, numbered list · Checked 2026-09-30
- 22A failover test consistent with Microsoft's description is to cut the branch's internet path while leaving the client's LAN path to the SBA intact, confirm the SBA banner appears in a desktop client that connected to the SBA within the previous 24 hours, place and receive a PSTN call, then restore the internet and confirm the client returns to normal mode.inferredSurvivable Branch Appliance for Direct Routing · How it works (conditions, banner, offline functionality list); Known issues and considerations · Checked 2026-09-30
- 23Once the Teams client detects that the internet is back and any outgoing calls have finished, it falls back to normal operation mode and reconnects to other Teams services.Survivable Branch Appliance for Direct Routing · How it works, second paragraph · Checked 2026-09-30
- 24SBC vendors either embed the Microsoft-provided SBA code in their SBC firmware or distribute it separately so the SBA runs on a separate VM or hardware, and the customer obtains the latest firmware with the embedded SBA from the SBC vendor.Survivable Branch Appliance for Direct Routing · Prerequisites, first two paragraphs · Checked 2026-09-30
- 25Get-CsTeamsSurvivableBranchAppliancePolicy returns the SBA policies defined in the tenant, optionally narrowed by -Identity or by -Filter on a partial Identity match.Get-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams) · Synopsis; Syntax; Parameters > -Identity, -Filter · Checked 2026-09-30
- 26Get-CsTeamsSurvivableBranchAppliance returns the SBAs configured in the tenant, optionally narrowed by -Identity or by -Filter on a partial Identity match.Get-CsTeamsSurvivableBranchAppliance (MicrosoftTeams) · Synopsis; Syntax; Parameters > -Identity, -Filter · Checked 2026-09-30
- 27Grant-CsTeamsSurvivableBranchAppliancePolicy has three parameter sets: per user (-Identity), per group (-Group with an optional -Rank relative to other group assignments of the same policy type), and tenant-wide (-Global, which applies the policy to all users in the tenant).Grant-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams) · Syntax (Identity, GrantToTenant, GrantToGroup); Parameters > -Global, -Group, -Rank · Checked 2026-09-30
- 28A branch survivability policy is removed from a user by granting the $Null policy: Grant-CsTeamsSurvivableBranchAppliancePolicy -PolicyName $Null -Identity <user>.Survivable Branch Appliance for Direct Routing · Configuration > Assign a policy to a user, second example · Checked 2026-09-30
- 29A branch survivability policy is assigned to an individual user with Grant-CsTeamsSurvivableBranchAppliancePolicy -PolicyName <policy> -Identity <user>.Survivable Branch Appliance for Direct Routing · Configuration > Assign a policy to a user · Checked 2026-09-30
- 30The Microsoft SBA Server uses port 443 to communicate with Microsoft 365, and that port must be allowed on the firewall.Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 6 · Checked 2026-09-30
- 31An SBA object is created in the tenant with New-CsTeamsSurvivableBranchAppliance, for example with -Fqdn sba1.contoso.com and -Description, and the resulting Identity equals the FQDN.Survivable Branch Appliance for Direct Routing · Configuration > Create the SBAs, parameter table and example · Checked 2026-09-30
- 32After new Survivable Branch Appliances are added, it might take time before they can be used in Survivable Branch Appliance policies.Survivable Branch Appliance for Direct Routing · Known issues and considerations, penultimate bullet · Checked 2026-09-30
- 33A site whose users reach the PSTN SBC only across the same internet or WAN link that fails gains nothing from an SBA, because SBA mode depends on the client still reaching the SBA and on the SBA/SBC still reaching the PSTN locally during the outage.inferredSurvivable Branch Appliance for Direct Routing · Introduction, second paragraph; How it works, 'Network status check' bullet · Checked 2026-09-30
- 34In SBA mode other Teams users cannot be reached by reverse number lookup against Microsoft Entra ID contacts; a dialed number is still processed by the SBA and routed over the PSTN.Survivable Branch Appliance for Direct Routing · Known issues and considerations > unsupported user actions, last sub-bullet · Checked 2026-09-30
- 35In SBA mode a user cannot switch their Teams client to another tenant.Survivable Branch Appliance for Direct Routing · Known issues and considerations > unsupported user actions, first sub-bullet · Checked 2026-09-30
- 36The Microsoft SBA Server uses UDP port 123 to reach an NTP server, and that port must be allowed on the firewall.Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 5 · Checked 2026-09-30
- 37In offline mode an incoming PSTN call to a call queue or auto attendant number can be redirected to a local agent or to an alternative call queue or auto attendant number.Survivable Branch Appliance for Direct Routing · How it works, offline functionality list, items 7-8 · Checked 2026-09-30
- 38In offline mode the Teams client can make and receive PSTN calls through the local SBA/SBC with media through the SBC, hold and resume PSTN calls, blind transfer, and forward calls (always or when unanswered) to a single phone number or Teams user.Survivable Branch Appliance for Direct Routing · How it works, offline functionality list, items 1-6 · Checked 2026-09-30
- 39In offline mode two users registered behind the same SBA can place a VoIP call to each other that the SBA supports, and if a VoIP call cannot be initiated and the called party has a PSTN number a PSTN call is attempted instead.Survivable Branch Appliance for Direct Routing · How it works, offline functionality list, items 9-10 · Checked 2026-09-30
- 40Only one Microsoft Entra ID application needs to be registered for use by all the SBAs in a tenant; the registration lets the SBAs read required data from Microsoft 365.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, paragraphs 1 and 3 · Checked 2026-09-30
- 41Microsoft frames the SBA for the case where a branch temporarily cannot reach the Microsoft cloud through Direct Routing while the intranet inside the branch still works and users can still connect to the SBC that provides PSTN connectivity.Survivable Branch Appliance for Direct Routing · Introduction, second paragraph · Checked 2026-09-30
- 42SBAs are added to or removed from an existing policy with Set-CsTeamsSurvivableBranchAppliancePolicy using -BranchApplianceFqdns @{add="..."} or @{remove="..."}.Survivable Branch Appliance for Direct Routing · Configuration > Create the Teams Branch Survivability Policy, Set- example · Checked 2026-09-30
- 43A branch survivability policy is created with New-CsTeamsSurvivableBranchAppliancePolicy, taking an -Identity and -BranchApplianceFqdns, and one policy can contain one or more SBAs.Survivable Branch Appliance for Direct Routing · Configuration > Create the Teams Branch Survivability Policy · Checked 2026-09-30
- 44After a Survivable Branch Appliance policy is assigned to a user, it might take time before the SBA is shown in the output of Get-CsOnlineUser.Survivable Branch Appliance for Direct Routing · Known issues and considerations, last bullet · Checked 2026-09-30
- 45The -PolicyName passed to Grant-CsTeamsSurvivableBranchAppliancePolicy is the policy Identity without its scope prefix, that is without the leading 'Tag:'.Grant-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams) · Parameters > -PolicyName · Checked 2026-09-30
- 46Remove-CsTeamsSurvivableBranchAppliancePolicy removes an SBA policy from the tenant and takes a mandatory -Identity, the policy instance name.Remove-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams) · Synopsis; Syntax; Parameters > -Identity · Checked 2026-09-30
- 47Remove-CsTeamsSurvivableBranchAppliance removes an SBA from the tenant and takes a mandatory -Identity, the unique identifier of the SBA.Remove-CsTeamsSurvivableBranchAppliance (MicrosoftTeams) · Synopsis; Syntax; Parameters > -Identity · Checked 2026-09-30
- 48SBA issues are reported to the SBC vendor's support organization, and the report should state that a Survivable Branch Appliance is configured.Survivable Branch Appliance for Direct Routing · Report an issue · Checked 2026-09-30
- 49New-CsTeamsSurvivableBranchAppliance accepts an optional -Site parameter naming the TenantNetworkSite where the SBA is located and an optional free-text -Description.New-CsTeamsSurvivableBranchAppliance (MicrosoftTeams) · Parameters > -Site and -Description · Checked 2026-09-30
- 50The Microsoft SBA Server communicates with the SBC on port 5061, or whichever port is configured on the SBC, and that port must be allowed on the firewall.Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 4 · Checked 2026-09-30
- 51The client secret for the SBA application may use any description and expiration, and it should be copied immediately after it is created.Survivable Branch Appliance for Direct Routing · Configuration > Register an application for the SBA with Microsoft Entra ID, 'Client secret' bullets · Checked 2026-09-30
- 52TLS 1.2 must be enabled on the operating system of the SBA VM.Survivable Branch Appliance for Direct Routing · Prerequisites, bullet 2 · Checked 2026-09-30
- 53For step-by-step configuration of the SBC with the embedded SBA, Microsoft defers to SBC vendor documentation and links to four vendors: AudioCodes, Ribbon, Oracle and TE-Systems.Survivable Branch Appliance for Direct Routing · Session Border Controller configuration · Checked 2026-09-30
- 54SBA mode is supported on the Teams Windows and macOS desktop clients and on Teams Phones, and only on desktop clients running on a physical machine; VMs and web clients are not supported.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, sections 'Supported Teams clients' and 'How it works' · Checked 2026-09-24
- 55Direct Routing lets an organization use any PSTN operator by connecting it through a certified SBC that is procured, installed and managed by the customer, an integrator or a Direct-Routing-as-a-Service provider.PSTN connectivity options · PSTN connectivity options, bullet 'Direct Routing' · Checked 2026-09-24
- 56Direct Routing requires a Microsoft-certified SBC, PSTN trunks to it, users homed online, a public IP, an SBC FQDN in a verified tenant domain (not *.onmicrosoft.com) with public DNS, and a publicly trusted TLS certificate.Plan Direct Routing · Plan Direct Routing, section 'Infrastructure requirements' table and section 'SBC domain names' · Checked 2026-09-24
- 57In SBA mode, emergency calls can still be placed but location information is not shared, and SBA does not support emergency call routing policies; emergency dial strings bypass normalization, so they fail unless the regular voice routing policy has a matching pattern.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Known issues and considerations', 'In SBA mode, the following user actions aren't supported' · Checked 2026-09-24
- 58A Survivable Branch Appliance is Microsoft-supplied code distributed through SBC vendors, and it requires the SBC to be configured for media bypass so branch Teams clients can exchange media directly with the SBC.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Prerequisites' · Checked 2026-09-24
- 59SBA configuration (creating SBAs, creating and assigning the branch survivability policy, and registering an Entra ID application) is done only with Teams PowerShell; the Teams admin center does not yet support the feature.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Configuration' · Checked 2026-09-24
- 60Direct Routing requires specific emergency call routing policies, whereas with the other PSTN options the carrier handles much of the emergency call routing configuration.Plan and manage emergency calling · Plan and manage emergency calling, section 'Emergency call routing' · Checked 2026-09-24
- 61SBA accepts expired client authentication tokens for up to 7 days, cannot validate a client that has not connected to it in the last 24 hours, and stays operational for only about 30 minutes if the tenant uses Continuous Access Evaluation tokens.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Known issues and considerations' · Checked 2026-09-24
- 62Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, expects the SBC vendor to investigate first and escalate, and may decline support requests involving non-certified SBCs.Plan Direct Routing · Plan Direct Routing, sections 'Supported Session Border Controllers (SBCs)' and 'Support boundaries' · Checked 2026-09-24
- 63In GCC High and DoD clouds, Microsoft lists as not yet available: secondary ringer, voicemail and enhanced delegation call settings; transfer to voicemail mid-call; calling a number from the search bar; Entra ID reverse number lookup; Private Line and Multi-line; skip internal VoIP reverse number lookup; and Shared Calling.Teams Phone features · Teams Phone features, section 'Availability in GCC High and DoD clouds' · Checked 2026-09-24
Documents
Continuous access evaluation in Microsoft Entra
Get-CsTeamsSurvivableBranchAppliance (MicrosoftTeams)
Get-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams)
Grant-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams)
Microsoft Teams SBA - anynode
New-CsTeamsSurvivableBranchAppliance (MicrosoftTeams)
Plan and manage emergency calling
Plan Direct Routing
Plan for media bypass with Direct Routing
Plan for Shared Calling
PSTN connectivity options
Remove-CsTeamsSurvivableBranchAppliance (MicrosoftTeams)
Remove-CsTeamsSurvivableBranchAppliancePolicy (MicrosoftTeams)
Survivability Products (SBA) for Microsoft Teams
Survivable Branch Appliance for Direct Routing
Teams Phone features
Cite this page
APA
WarmTransfer. (2026, September 30). Setting up a Survivable Branch Appliance for Teams Direct Routing. WarmTransfer. https://warmtransfer.net/guides/teams-sba-setup
BibTeX
@misc{warmtransfer-teams-sba-setup,
title = {Setting up a Survivable Branch Appliance for Teams Direct Routing},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/guides/teams-sba-setup},
note = {Verified 2026-09-30}
}