'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Use Teams VoIP Across Two Microsoft 365 Tenants
Question details
The user wants to know if a single VoIP carrier can support Microsoft Teams Phone across separate educational and nonprofit Microsoft 365 tenants without merging the environments.
- Product
- Microsoft Teams Phone
- Device & OS
- not provided
- Scenario
- Planning to migrate an existing on-premises telephone system to Teams VoIP while keeping two independent M365 tenants for distinct organizational branches.
- Observed behavior
- The user needs to understand the impact of maintaining two distinct systems on user management, administration, licensing, and call routing.
Before proceeding, ensure you have global administrator access to both Microsoft 365 tenants and confirm with your VoIP provider that they support Direct Routing or Operator Connect for multiple independent tenant IDs.
Deploy a Single Carrier with Independent Tenant Configurations
You can use the same VoIP carrier for both tenants, but you must configure user management, licensing, and voice routing independently in each Microsoft 365 environment.
Using the same telephone carrier across an educational tenant and a nonprofit tenant is fully supported. However, because the tenants remain unmerged, the systems will not share a unified directory, administration center, or internal extension routing natively.
You will need to maintain separate administration for user creation, distribution lists, and SharePoint resources. Migrating an older system, such as a Nortel PBX, means you are effectively managing two separate PBX environments.
Contact your VoIP carrier to provision SIP trunks or Operator Connect numbers and explicitly assign the respective numbers to the two separate Microsoft 365 tenant IDs.
Log in to the Microsoft 365 Admin Center for the educational tenant, navigate to Billing > Licenses, and assign the required Teams Phone Standard licenses to your users.
Open the Teams Admin Center for the first tenant and independently configure your voice routing policies, dial plans, auto attendants, and call queues.
Log in to the Microsoft 365 Admin Center and Teams Admin Center for the nonprofit tenant, and repeat the entire licensing and voice routing configuration process to set up its separate environment.
Enhance Cross-Branch Collaboration with WPS Office
Managing multiple Microsoft 365 tenants can be administratively complex and costly. If you need a lightweight, cost-effective alternative for daily document creation across your nonprofit and educational branches, WPS Office provides robust tools and seamless compatibility with Microsoft formats.
- 1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen prompts to complete the installation.
- 3. Open and edit files seamlessly: Launch WPS Office and instantly open your existing Microsoft Office documents without format distortion.
Frequently Asked Questions
Can internal users call each other via extension across the two Microsoft 365 tenants?
No. Because the tenants are functionally separate, internal extension dialing is not natively supported between them. Calls between the educational and nonprofit tenants will route as standard external PSTN calls.
Do I need separate Teams Phone licenses for each tenant?
Yes. Licensing is strictly bound to individual Microsoft 365 tenants. You must purchase and assign Teams Phone Standard licenses separately in both the educational and nonprofit tenant admin centers.
What is the best way to migrate an existing on-premises PBX to this dual-tenant setup?
Migrating a legacy system (like Nortel) to two separate Teams VoIP tenants requires dividing your current user base, auto attendants, and call queues into two independent deployment plans. Work closely with your carrier to port existing numbers and distribute them to the correct Microsoft 365 tenants.
