Porting Phone Numbers to Microsoft Teams Phone: What to Know in 2026

Moving business calling into Microsoft Teams can reduce PBX complexity and give employees one place for chat, meetings, and phone calls. The porting process is straightforward when the licensing, carrier records, emergency locations, and cutover plan are prepared correctly.

What changed since Microsoft Business Voice

Microsoft 365 Business Voice has been replaced by the current Teams Phone portfolio. In 2026, organizations typically deploy Teams calling with one of these models: Microsoft Teams Phone with Microsoft Calling Plans, Operator Connect, Teams Phone Mobile where available, or Direct Routing with a Session Border Controller and carrier relationship. Number porting into Microsoft mainly applies when you are moving numbers to Microsoft Calling Plans. If you use Operator Connect, your selected operator usually manages the number migration. If you use Direct Routing, numbers often remain with your carrier and are routed into Teams through your SBC.

Choose the right Teams Phone connectivity model before you port

Before submitting a port order, confirm the target voice architecture. Microsoft Calling Plans are the simplest Microsoft-managed option in supported countries and regions. Operator Connect lets you choose a participating operator and manage much of the setup from the Teams admin center while the operator handles carrier-side services. Teams Phone Mobile integrates a mobile operator number with Teams in supported markets. Direct Routing is best when you need carrier flexibility, complex call routing, analog integrations, or coverage that is not available through Microsoft Calling Plans or Operator Connect. This decision affects who owns the number, who bills for calling, who handles porting, and how support is escalated.

Licensing and readiness checklist

Confirm licensing before the port date. Users need appropriate Microsoft Teams and Teams Phone licensing, such as Teams Phone Standard or a bundle that includes it, plus a calling connectivity option. Microsoft 365 E5 includes Teams Phone Standard, but calling capacity may still require a Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing. Review your subscriptions under the current Microsoft New Commerce Experience terms, including monthly or annual commitment choices. Also confirm that users exist in Microsoft Entra ID, Teams is enabled, service locations are set, emergency addresses are validated, and numbers are mapped to users, resource accounts, auto attendants, call queues, conferencing bridges, or voice applications.

Pre-port checklist

A clean port starts with accurate carrier information. Collect the current carrier name, billing account number, billing telephone number, service address, authorized contact, recent invoice, and Customer Service Record if available. Confirm whether a Letter of Authorization is required in your country or by your provider. Decide whether this is a full port or partial port, identify any numbers that support alarms, elevators, fax, door phones, modems, DSL, broadband, or other non-Teams services, and do not port those without a replacement plan. Remove account locks or port freezes only when you are ready, avoid placing disconnect orders, and keep the existing service active until porting and testing are complete.

How to submit a port request for Microsoft Calling Plans

For Microsoft Calling Plan numbers, use the Microsoft Teams admin center. The current experience is typically under Voice > Phone numbers, where you can start a port order and follow the guided workflow. Select the country or region, number type, and intended assignment. Enter the account details exactly as the losing carrier has them on file, including the billing telephone number in E.164 format, such as +14255551234. Upload any required documents, such as a Letter of Authorization, and submit the order. After submission, monitor the order history in the Teams admin center and watch for Microsoft or carrier requests for clarification.

Full ports, partial ports, and billing telephone numbers

A full port moves all numbers on an account from the existing provider. In that case, include the billing telephone number along with the other numbers being transferred. A partial port moves only some numbers on the account. In many partial-port scenarios, you should not include the billing telephone number unless it is one of the numbers being moved, because the remaining numbers still need an active account with the current provider. Rules can vary by country and carrier, so validate the port instructions before submission.

Supported numbers and regional availability

Number portability depends on country or region, number type, provider, and regulatory requirements. Geographic, non-geographic, toll, toll-free, and mobile numbers may be treated differently depending on the market. Toll-free numbers often require a separate order and may take longer. Numbers tied to broadband, DSL, alarm lines, fax services, or other data-dependent services require special planning because porting them can interrupt the underlying service. Fax is not a native Teams Phone workload, so keep a separate fax solution or modernize the process before porting fax-related numbers. Always check current Microsoft country and region availability and carrier guidance before promising a port date.

How long number porting takes

Porting timelines vary. Many standard ports are completed in days to a few weeks, but timing depends on the losing carrier, country, number type, order accuracy, documentation, holidays, and whether the order is manual, toll-free, complex, or international. The losing carrier must approve the request and provide a Firm Order Commitment date when applicable. Microsoft cannot force a losing carrier to approve inaccurate or unsupported requests. Avoid scheduling critical ports late on a Friday or immediately before a holiday unless you have a tested rollback and support plan.

Common reasons port orders are rejected

Most rejections come from mismatched account information. The carrier records may show a different company name, service address, billing telephone number, account number, authorized signer, or ZIP/postal code than the information in the port request. Other common issues include disconnected service, a port freeze, pending carrier orders, mixing numbers from different accounts, combining toll-free and standard numbers incorrectly, submitting unsupported number types, or including the billing telephone number in the wrong partial-port scenario. If an order fails, request the current invoice or Customer Service Record from the losing carrier, correct the data, and resubmit.

What to do on port day

Have an administrator available in the Teams admin center during the cutover window. Assign newly ported numbers to users, resource accounts, auto attendants, call queues, or other voice features as planned. Confirm calling policies, caller ID policies, emergency calling configuration, voicemail, call forwarding, and business-hours routing. Test inbound calls, outbound calls, voicemail, transfers, auto attendants, call queues, emergency calling where appropriate and legally permitted, and calls from mobile and external networks. Only cancel the old carrier service after the port is complete and production testing is successful.

When to get help

Porting is not just a carrier transaction. It touches licensing, Teams Phone design, identity, emergency calling, user adoption, call routing, and business continuity. A partner can help validate the right voice model, prepare carrier documentation, schedule the cutover, configure Teams Phone, and troubleshoot rejected orders before they delay the migration.

Key takeaways

• Use the current Teams Phone terminology: Business Voice has been replaced by Teams Phone licensing and voice connectivity options.
• Porting numbers into Microsoft is primarily for Microsoft Calling Plans; Operator Connect and Direct Routing use different carrier-management models.
• Accurate carrier records are the most important factor in avoiding port rejections.
• Keep existing phone service active until the port is complete and all inbound, outbound, emergency, and routing tests pass.
• Plan licensing, emergency addresses, user assignments, auto attendants, call queues, and post-port testing before choosing the cutover date.

Planning a move to Teams Phone? IT Partner can help assess your Microsoft 365 licensing, select the right calling model, prepare the porting plan, and configure Teams Phone for a smooth cutover.