Source note · Avaya Aura to Teams Phone
Besides the SBC FQDN's domain being registered in the tenant, there must be a user in that domain with an E3 or E5 license assigned, otherwise pairing fails with a domain-not-configured error.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Direct Routing SBC pairing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Connect your Session Border Controller (SBC) to Direct Routing — Microsoft · tier 2 current vendor documentation · section 'Connect the SBC to the tenant', Considerations bullet 2
Cite this note
APA
WarmTransfer. (2026, September 30). Avaya Aura to Teams Phone: source note avaya-aura-to-teams-phone-sbc-domain-user. WarmTransfer. https://warmtransfer.net/knowledge/claims/avaya-aura-to-teams-phone-sbc-domain-user
BibTeX
@misc{warmtransfer-claim-avaya-aura-to-teams-phone-sbc-domain-user,
title = {Avaya Aura to Teams Phone: source note avaya-aura-to-teams-phone-sbc-domain-user},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/avaya-aura-to-teams-phone-sbc-domain-user},
note = {Source note avaya-aura-to-teams-phone-sbc-domain-user, checked 2026-09-30}
}