How to Assign and Manage Microsoft Teams Phone Numbers

Microsoft Teams Phone can replace or extend a traditional phone system by bringing PSTN calling into Teams. In 2026, number management depends on how your organization connects Teams to the phone network: Microsoft Calling Plans, Operator Connect, Teams Phone Mobile, or Direct Routing. This guide explains the current prerequisites and the admin steps for assigning, changing, and removing user phone numbers.

What Microsoft Teams Phone includes in 2026

Microsoft Teams Phone is Microsoft’s cloud calling platform for Teams. It provides PBX-style capabilities such as inbound and outbound calling, call transfer, voicemail, call queues, auto attendants, shared calling scenarios, and policy-based administration.

Teams Phone is not the same thing as a calling plan. Teams Phone provides the calling features; PSTN connectivity determines how calls reach the public telephone network. The main options are:

• Microsoft Calling Plans: Microsoft provides the phone numbers and PSTN calling minutes in supported countries and regions.
• Operator Connect: A participating telecom operator provides PSTN service and numbers directly through the Teams admin experience.
• Teams Phone Mobile: A participating mobile operator connects a user’s mobile number with Teams calling.
• Direct Routing: Your organization connects Teams to a certified session border controller and a telecom carrier of your choice.

The right option depends on country availability, existing carrier contracts, compliance requirements, number-porting needs, and whether you want Microsoft or a carrier to manage the PSTN service.

Licensing and prerequisites before assigning numbers

Before assigning phone numbers, confirm that each user has the correct licensing and configuration. In most deployments, a user needs:

• A Microsoft Teams license or entitlement. Depending on your region, tenant history, and purchase date, Teams may be included in a Microsoft 365 or Office 365 suite or may need to be purchased separately.
• A Teams Phone license, such as Teams Phone Standard, Teams Phone with Calling Plan, or a suite that includes Teams Phone, such as eligible E5 plans.
• A PSTN connectivity option: Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing.
• A valid usage location set for the user in Microsoft 365 admin center or Microsoft Entra admin center.
• A validated emergency address or emergency location where required.
• The correct number type. User numbers are for people; service numbers are typically used for auto attendants, call queues, conferencing, and resource accounts.

If you buy through CSP under the New Commerce Experience (NCE), review term length, cancellation windows, and seat-adjustment rules before purchasing large quantities of Teams Phone or Calling Plan licenses. Number porting and carrier migration timelines should also be planned before you cancel an existing phone service.

Admin roles and where number management happens

Most day-to-day Teams Phone administration is performed in the Teams admin center at https://admin.teams.microsoft.com. Depending on your organization’s role model, administrators commonly use roles such as Teams Administrator, Teams Communications Administrator, Teams Telephony Administrator, or equivalent scoped permissions.

Common locations in the Teams admin center include:

• Users > Manage users: review a user’s Teams configuration and assigned phone number.
• Voice > Phone numbers: view, acquire, assign, release, or manage available numbers, depending on the PSTN option.
• Locations > Emergency addresses: add and validate emergency addresses.
• Voice > Calling policies, Voice > Emergency policies, and Voice > Voice routing policies: configure calling behavior, emergency handling, and Direct Routing behavior.

The exact options you see can vary by license, country or region, PSTN connectivity method, and admin role.

How to get phone numbers for Teams Phone

The number-acquisition process depends on the PSTN connectivity model:

• Microsoft Calling Plans: In the Teams admin center, go to Voice > Phone numbers and use the option to get new numbers. Select the country or region, number type, quantity, area code or location details, and emergency address where required.
• Number porting: If users are keeping existing numbers, create a port order instead of requesting new numbers. Do not cancel the old carrier service until the port is complete.
• Operator Connect: Select and configure your operator in the Teams admin center. The operator provides or ports the numbers, and available numbers appear for assignment after operator provisioning.
• Teams Phone Mobile: The participating mobile operator controls the mobile number and provisioning process. Assignment and activation follow that operator’s workflow.
• Direct Routing: Numbers are typically provided by your telecom carrier and assigned through Teams policies and PowerShell rather than requested from Microsoft inventory.

Always distinguish user numbers from service numbers. If you are building auto attendants, call queues, or shared calling, you may need resource accounts, Teams Phone Resource Account licenses, and service numbers instead of standard user numbers.

How to assign a phone number to a user

Use this workflow for user numbers that are already available in your tenant or with your configured operator:

1. Confirm that the user exists in Microsoft Entra ID and has the correct Teams and Teams Phone licensing.
2. Confirm that the user’s usage location is set correctly.
3. Confirm that you have at least one validated emergency address or location if required for the user’s country or region.
4. Open the Teams admin center.
5. Go to Voice > Phone numbers.
6. Select an available user number.
7. Choose Edit or Assign, depending on the current interface.
8. In Assigned to, search for and select the user.
9. Select the emergency location if the number type and region require it.
10. Save or apply the change.

After assignment, the user’s number appears in Teams under Calls after provisioning completes. Changes are often visible quickly, but allow propagation time before troubleshooting. Users may need to restart Teams or sign out and back in if the calling interface does not update.

How to change a user’s Teams Phone number

To replace a user’s phone number:

1. In the Teams admin center, go to Users > Manage users.
2. Open the user and note the currently assigned phone number.
3. Go to Voice > Phone numbers.
4. Select the current number and remove the user assignment.
5. Select the new available user number.
6. Assign the new number to the same user.
7. Confirm or update the emergency location.
8. Save the change and allow time for Teams to update.

Before changing a number, consider the operational impact. Update published contact information, call-flow documentation, CRM records, emergency-location records, and any auto attendant or call queue references that may route to the user.

How to remove a phone number from a user

To remove a user number without immediately assigning a replacement:

1. In the Teams admin center, go to Users > Manage users.
2. Open the user and record the currently assigned number.
3. Go to Voice > Phone numbers.
4. Select the number assigned to that user.
5. Choose Edit.
6. Remove the user from Assigned to.
7. Save the change.

Removing a number prevents the user from receiving calls on that number and may affect outbound caller ID behavior depending on your policies. Keep track of whether the number should remain in inventory, be reassigned, released, or returned to the carrier. For ported or operator-managed numbers, confirm the correct release process before deleting or disconnecting service.

Emergency calling considerations

Emergency calling is a critical part of Teams Phone design and should not be treated as a checkbox. Requirements vary by country, region, carrier, and user type.

At minimum, validate emergency addresses and associate them with users or numbers where required. For larger or multi-site environments, consider dynamic emergency calling so Teams can determine a user’s dispatchable location based on network information such as trusted IP addresses, network sites, subnets, and Wi-Fi access points.

Also review emergency calling policies and emergency call routing policies. In some regions, laws or regulations may require accurate dispatchable location, emergency call notifications, direct emergency dialing behavior, or special handling for remote and hybrid workers. Validate your design with Microsoft documentation, your telecom provider, and legal or compliance stakeholders.

Bulk administration with PowerShell

The Teams admin center works well for small changes. For larger deployments, migrations, or audits, PowerShell is usually more efficient.

Common administrative tasks include exporting assigned numbers, assigning numbers in bulk, removing assignments, validating voice policies, and checking user provisioning state. Current Teams Phone number assignment is commonly managed with Microsoft Teams PowerShell cmdlets such as Get-CsPhoneNumberAssignment, Set-CsPhoneNumberAssignment, and Remove-CsPhoneNumberAssignment.

Use PowerShell carefully in production. Test with a small pilot group, keep a rollback file of previous assignments, and confirm emergency-location handling before bulk changes.

Do not forget call queues, auto attendants, and shared calling

User number assignment is only one part of a Teams Phone deployment. Many organizations also need central numbers for departments, reception, help desks, sales teams, and after-hours routing.

For these scenarios, review:

• Auto attendants for menu-based routing and business hours.
• Call queues for groups of agents.
• Resource accounts and service numbers.
• Caller ID policies.
• Shared calling for users who need PSTN calling but do not require a dedicated direct inward dial number.
• Voicemail, holidays, language settings, and overflow handling.

Designing these elements before porting numbers helps avoid call-flow disruption during migration.

Key takeaways

• Teams Phone provides the cloud PBX features; Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing provide PSTN connectivity.
• Users need the right Teams access, Teams Phone licensing, usage location, PSTN configuration, and emergency-location setup before number assignment.
• Number workflows differ depending on whether numbers come from Microsoft, an operator, a mobile provider, or Direct Routing.
• Use user numbers for people and service numbers with resource accounts for auto attendants, call queues, and shared calling scenarios.
• For larger deployments, use Teams PowerShell and a documented migration plan instead of making all changes manually.

Planning a Teams Phone rollout or cleaning up an existing configuration? IT Partner can help with Microsoft Teams Phone design, licensing under CSP/NCE, number porting, Operator Connect or Direct Routing planning, emergency calling configuration, and ongoing Microsoft 365 support.