# Porting numbers to Microsoft Teams

Canonical: https://warmtransfer.net/knowledge/teams-number-porting

Last verified: 2026-09-25

For Calling Plans ports, the customer submits the port order to Microsoft, which coordinates fulfillment with the current carrier and becomes the service provider of record[^28]. When using other PSTN connectivity models, porting is conducted directly with the respective partner or carrier rather than with Microsoft as the gaining provider[^36][^13].

## Porting to Microsoft Calling Plans

To submit a port order in the Teams admin center, an administrator must hold the Teams Telephony Administrator, Teams Communications Administrator, or Teams Administrator role[^2]. The Teams admin center provides two port wizards: a classic All regions wizard and a new wizard for US and Canada numbers labelled US & Canada Preview, which Microsoft states is being developed for other Calling Plans regions[^54]. Within these wizards, numbers must be entered individually (10-digit or E.164 format in the US/Canada wizard, or E.164 in the classic wizard) or uploaded as a single-column CSV file headed PhoneNumber; number ranges are not supported[^32]. Port requests involving 1,000 or more numbers cannot use the admin center wizard and must instead be submitted manually through the Telephone Number Services (TNS) Service Desk[^21]. Microsoft also directs complex porting projects that span multiple providers, accounts or Billing Telephone Numbers (BTNs), number types, or service addresses to a manual Port in request[^8]. A manual Port in case opened in the Phone Number Service Center requires a signed Letter of Authorization (LOA), as Microsoft cannot process a request without one[^50]. Numbers that are ported or currently being ported to Microsoft are not counted against the tenant limits for acquiring Calling Plan phone numbers[^41].

The new US and Canada wizard groups submitted numbers by account, service provider, and type, processing only one group per port request while requiring separate requests for each additional group[^60]. More broadly, all numbers in a single port order must share the same service provider, account number, BTN, number type, and service address; any variation necessitates separate orders[^38]. Requests against the same account number are processed serially; if overlapping requests are submitted against one account, the losing provider processes only the first order and rejects the others[^46].

Port orders require a signed LOA, which can be executed either via e-signature (US and Canada)—where the authorized user receives an email and approval automatically submits the order—or offline by downloading, signing, and uploading the document[^25]. For US ports, Microsoft provides two distinct LOA forms: one for geographic user, voice app, and conferencing numbers, and one for toll-free numbers[^57]. Microsoft highly recommends including a recent invoice and the losing carrier's Customer Service Record (CSR) for US orders[^57]. In the US and Canada, the official document of record is the CSR and the Equipment Record, respectively, which customers should obtain from the current provider to ensure order details align[^11]. In the US and Canada wizard, if an edit to a validated order alters an already signed and uploaded LOA, the updated LOA must be downloaded, signed, and re-uploaded before resubmission[^24]. Country or region values cannot be edited in that wizard[^24].

## Eligible Number Types and Restrictions

Calling Plans support porting landline, mobile, VoIP, toll, toll-free, and service numbers[^15]. Mobile numbers can only be ported to Calling Plans in the United States, Puerto Rico, and Canada[^31]. Fax numbers may be ported, but they cannot be used for faxing and must be assigned to a user[^15]. A number's usage type (user or service) cannot be altered during the porting process; changes can only be made after the number has ported to Microsoft[^59]. In the US, geographic numbers can be ported as user, voice app, or audio conferencing numbers, whereas toll-free numbers can only be ported for voice apps or audio conferencing[^58].

Numbers that cannot be ported to Calling Plans include data-line numbers (DSL/broadband), Universal International Freephone Numbers (UIFN), numbers required to maintain active fax functionality, numbers from unsupported countries or regions, and UK nongeographic numbers, including the 0843, 0844, 0845, 0870, 0871, and 0872 ranges[^33]. Existing service must not be disconnected prior to the port, as inactive or disconnected numbers cannot be ported[^12]. Furthermore, attached services tied to the ported numbers, such as ISDN or broadband lines, are disconnected automatically upon port completion unless they are reassigned to retained numbers beforehand[^3].

## Timelines, Scheduling, and Preassignment

Microsoft acknowledges submitted port requests within 72 business hours[^9]. Regarding overall turnaround times, sources disagree: the Calling Plans overview indicates that orders typically take 7 to 14 days and up to 30 days depending on the current provider[^22], whereas the US country documentation states an approximate duration of 5 to 12 business days for US numbers[^56]. Mandatory minimum lead times are 5 days in the US and 10 days in Canada, with extra processing time expected for orders containing more than 200 numbers[^29]. Microsoft cites the losing carrier response SLA as 3 to 5 business days in the US and 5 to 7 business days in Canada[^26].

Target port dates cannot be set more than 30 calendar days in advance[^27]. Microsoft recommends scheduling a conservative target date at least 15 business days after submission, considering any date under 7 business days in the US or 10 business days in Canada to be aggressive[^10]. Target dates and times are requests only; the port completes on that date only if approved by the losing carrier[^49]. Approval is granted via a firm order commitment (FOC), and the losing provider releases the numbers to Microsoft on that FOC date, though in rare cases the losing carrier may override an issued FOC[^17]. For US orders, changes require at least 2 business days of notice, and cancellations require at least 1 business day of notice prior to the approved date[^55].

Daily scheduling windows depend on geography and number type:[^40]

| Region / Type | Allowed Porting Times | Scheduling Details |
| --- | --- | --- |
| US user numbers | 8am to 8pm US Eastern[^40] | Selectable target time within window[^40] |
| Canadian numbers (user and toll-free) | 11:30am Eastern[^40] | Earlier time requires special request to TNS Service Desk[^40] |
| US toll-free numbers | 11:30am Eastern[^40] | Earlier time requires special request to TNS Service Desk[^40] |

For numbers ported from an external carrier into Calling Plans, preassignment is supported if the target user or resource account has the appropriate Phone System or resource account license alongside a Calling Plan license, and the account's usage location matches the country of the number[^43]. Ported toll-free numbers also require a positive Communications Credits balance for preassignment[^43].

## Order Statuses, Rejections, and Troubleshooting

Microsoft identifies account details that fail to match carrier records—specifically the authorized person, address, account number, or BTN—as the primary cause of port rejections and delays[^30]. Other common rejection causes include active call control features (such as hunt groups or distinctive ring), pending disconnects or open service orders, mixing multiple providers or accounts in a single order, and frozen accounts[^39]. Sources disagree on how to handle the BTN: Microsoft's common mistakes list instructs administrators to verify that the BTN is included in the list of numbers being ported, whereas its partial-port guidance states that the BTN is excluded when it remains with the current provider[^6].

In the US and Canada wizard, an account PIN is mandatory for all mobile numbers and is distinct from a BTN Freeze PIN[^1]. Mismatched BTNs or account freezes cause immediate post-submission rejection[^5]. The authorized user cannot be updated while a port is in progress; changes must occur with the losing provider prior to porting, after which tenant administrators are treated by Microsoft as authorized users[^4].

When a carrier rejects a port request, it provides Microsoft only with a category-level reason rather than correct values, requiring the customer to obtain accurate information directly from the losing carrier[^44]. A rejection halts carrier processing and restarts the response SLA from the date the corrected order is resubmitted[^45]. Documented carrier errors include mismatched account numbers, authorized users, organization names, PINs, ZIP codes, service addresses, missing LOAs, and account freezes, which are resolved by aligning order fields with the CSR[^52].

Port orders display specific administrative statuses during processing:
- **Exception**: The current carrier rejected the order (typically due to inaccurate LOA details like PIN or ZIP code); Microsoft support corrects and resubmits the order[^47].
- **Customer action required**: The carrier rejected the order; administrators must select Update on the order details page, review the rejection error, correct it, and resubmit[^51].
- **Microsoft support engaged**: No customer action is needed because a support ticket is already active and Microsoft Support is handling the issue, such as resolving a submission error or managing an order that Microsoft must resubmit[^53].
- **Canceled**: The order is closed and numbers are not ported; subsequent requests cannot reuse prior validations or documentation[^7].

If issues arise following port completion, problems identified within 24 to 48 hours must be directed to the Phone Number Service Center, whereas issues noticed after 48 hours must be raised with Microsoft Support[^42].

## Migrations Across Teams PSTN Options

Moving existing numbers across different Teams PSTN architectures involves carrier-specific procedures:[^36][^13]

### Operator Connect
When migrating to Operator Connect, the porting process is conducted directly with the Operator Connect partner, governed by the organization's agreement with that operator[^36]. To transition numbers from Calling Plans to Operator Connect, the customer contacts the operator to execute the port; once complete, the operator uploads the numbers to the tenant, allowing the administrator to assign them via PowerShell or the Teams admin center[^37]. For Direct Routing numbers assigned online, the migration to Operator Connect is executed by the operator at an agreed date and time[^34]. For on-premises-assigned Direct Routing numbers in hybrid environments, the migration requires clearing the `LineURI` using `Set-CsUser` in Skype for Business Server PowerShell; because this causes a service outage during migration, the cutover must be coordinated with the operator[^35].

### Direct Routing
Porting numbers to a Direct Routing PSTN partner is executed directly through that partner, with Microsoft acting outside the gaining carrier transaction[^13]. Before Direct Routing numbers can be migrated to another Teams PSTN architecture, administrators must unassign the numbers and formally release them from Microsoft's inventory using `New-CsOnlineTelephoneNumberReleaseOrder` prior to the port event[^14].

### Moving Hybrid Numbers to Calling Plans
To transition hybrid numbers (originating from Direct Routing or Operator Connect) into Microsoft Calling Plans, administrators must contact the TNS Service Desk and identify the numbers as hybrid[^20]. In the US and Canada, preassignment is not allowed for these hybrid-to-Calling-Plans transfers, but Microsoft can preserve existing assignments; administrators must assign both a Calling Plan license and an emergency calling location to each number prior to port completion[^19]. Outside the US and Canada, hybrid numbers moved to Calling Plans cannot be preassigned and arrive in the tenant in an unassigned state[^18].

## See also
- See also [Microsoft Teams Calling Plans](https://warmtransfer.net/knowledge/teams-calling-plans).
- See also [Teams Operator Connect and Azure Communication routing](https://warmtransfer.net/knowledge/teams-operator-connect).
- See also [Teams Phone Direct Routing and SBC certification](https://warmtransfer.net/knowledge/teams-direct-routing).

## Applicability

Applies to: Microsoft Teams Phone - Calling Plans, Microsoft Teams Phone - Operator Connect, and Microsoft Teams Phone - Direct Routing. Deployments: hybrid and multi-tenant. Sources checked 2026-09-25.

## What remains uncertain
- Porting numbers away from Microsoft Calling Plans, including the port-out process and tenant PIN or account details, is not covered by the sources below.
- Operator-specific porting lead times and LOA formats for Operator Connect are not covered by the sources below.
- Porting and number handling procedures for Teams Phone Mobile are not covered by the sources below.
- UK Calling Plans porting lead times and LOA specifics from the UK country page are not covered by the sources below.
- The rollout timeline of the new port wizard to Calling Plans regions beyond the US and Canada is not covered by the sources below.
- Canada country page specifics, including LOA and Equipment Record submission details and specific lead times, are not covered by the sources below.
- Whether the manual port order submission page redirects to the port order overview is not covered by the sources below.
- Reconciling the two different port-order status vocabularies (Exception versus Customer action required) is not covered by the sources below.

## Sources

[^1]: The account PIN with the current provider is required for all mobile numbers being ported, and it is not the same thing as a BTN Freeze PIN. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Account information, account PIN bullet. Checked 2026-09-25.
[^2]: To submit a port order in the Teams admin center, the admin needs the Teams Telephony Administrator, Teams Communications Administrator or Teams Administrator role. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Prerequisites, step 3. Checked 2026-09-25.
[^3]: Other services tied to the ported numbers, such as ISDN or broadband, are automatically disconnected once the port completes, unless they are first moved to numbers that are not being ported. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > When to disconnect your existing phone lines, third bullet. Checked 2026-09-25.
[^4]: The authorized user cannot be changed during a port request; any change must be made with the current provider before the port. After the port completes, Microsoft treats the tenant admins as authorized users. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Account information, authorized user bullet. Checked 2026-09-25.
[^5]: If the Billing Telephone Number (BTN) does not match the current provider's records or the account has a freeze, the port request is rejected after submission. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Billing telephone number (BTN). Checked 2026-09-25.
[^6]: Microsoft's own guidance is inconsistent on the BTN. The Common mistakes list says to verify the BTN is included in the numbers being ported, while the partial-port guidance says the BTN is left out of the list when it stays with the current provider (disputed). Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Common mistakes, first bullet, fourth sub-bullet vs Full-port and partial-port orders, Note. Checked 2026-09-25.
[^7]: A Canceled port order is closed and the numbers are not ported. A new port order reuses none of the earlier validations or documents. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > table row Canceled. Checked 2026-09-25.
[^8]: Microsoft directs complex port projects that span multiple providers, accounts/BTNs, number types or service addresses to a manual Port in request. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > How many port requests do I need?, closing paragraph. Checked 2026-09-25.
[^9]: Microsoft acknowledges a submitted port request within 72 business hours. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Confirmation. Checked 2026-09-25.
[^10]: Microsoft recommends a conservative target port date at least 15 business days after submission for every port. It treats a date under 7 business days (US) or 10 business days (Canada) as aggressive. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Plan for port event date > Approach 1 and Approach 2. Checked 2026-09-25.
[^11]: The provider's official document of record is the Customer Service Record (CSR) in the United States and the Equipment Record in Canada. Customers should request it from the current provider to make the port order match. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Planning a number port event, opening paragraphs. Checked 2026-09-25.
[^12]: Do not disconnect service with the current provider before the port. Inactive or disconnected numbers cannot be ported. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > When to disconnect your existing phone lines. Checked 2026-09-25.
[^13]: With Direct Routing, porting existing numbers to the Direct Routing PSTN partner is done directly with that partner; Microsoft is not the gaining provider. Source: [Get Direct Routing phone numbers in your Teams tenant - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/get-phone-numbers-with-direct-routing), Introduction paragraphs 3-4. Checked 2026-09-25.
[^14]: Before Direct Routing numbers are ported to another Teams PSTN option, they must be unassigned and then released from Microsoft's number inventory with New-CsOnlineTelephoneNumberReleaseOrder before the port event. Source: [Get Direct Routing phone numbers in your Teams tenant - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/get-phone-numbers-with-direct-routing), Upload Direct Routing numbers to your tenant > Order history, Note. Checked 2026-09-25.
[^15]: Portable number types include landline, mobile, VoIP, toll, toll-free and service numbers. Fax numbers can be ported but cannot be used for faxing and must be assigned to a user. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > Numbers eligible for porting > You can transfer. Checked 2026-09-25.
[^16]: US rules require providers to complete a simple wireline-to-wireline or simple intermodal port within one business day, unless the new provider or the customer asks for a longer period. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(a). Checked 2026-09-25.
[^17]: The losing provider approves a port by issuing a firm order commitment (FOC) and releases the numbers to Microsoft on the FOC date. In rare cases the losing provider can override an FOC it has already sent. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), What happens after you submit a port order request > Approval. Checked 2026-09-25.
[^18]: Outside the US and Canada, Direct Routing or Operator Connect numbers moved into Calling Plans cannot be preassigned and arrive unassigned. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > table row Approved (FOCAccepted), Considerations column. Checked 2026-09-25.
[^19]: When Direct Routing or Operator Connect numbers in the US or Canada move into Calling Plans, preassignment is not allowed, but Microsoft can keep the existing assignment. A Calling Plan license and an emergency calling location must be assigned for each number before the port completes. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > table row Approved (FOCAccepted), Considerations column. Checked 2026-09-25.
[^20]: To move hybrid numbers (Direct Routing or Operator Connect) into Calling Plans, contact the TNS Service Desk and state that the numbers are hybrid. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Numbers eligible for porting > You can transfer, last bullet. Checked 2026-09-25.
[^21]: Port requests of 1,000 or more numbers cannot use the Teams admin center wizard. They must be submitted manually through the Telephone Number Services (TNS) Service Desk. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > Large port requests. Checked 2026-09-25.
[^22]: The Calling Plans overview says a port order typically takes 7-14 days from submission to completion, and up to 30 days depending on the current provider (disputed). Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Planning a number port event > Plan lead-time for port request processing. Checked 2026-09-25.
[^23]: Microsoft's US minimum lead time (five days) and recommended 15-business-day target date are well beyond the one-business-day regulatory interval for simple ports. The regulatory interval covers carrier-to-carrier completion after a valid request and does not set how far ahead Microsoft lets customers schedule (inferred). Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Plan lead-time for port request processing; Plan for port event date; compared with cornell-lii-47-cfr-52-35 (a). Checked 2026-09-25.
[^24]: If an edit to a validated order affects an LOA that has already been signed and uploaded, the updated LOA must be downloaded, signed and re-uploaded before the edit can be submitted. The country or region cannot be edited. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Authorize and submit, Edit Mode paragraph. Checked 2026-09-25.
[^25]: The Letter of Authorization (LOA) can be signed by e-signature, where the authorized user gets an email and approval auto-submits the order (recommended), or offline by downloading, signing and uploading it. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Authorize and submit; All regions tab > Complete your order. Checked 2026-09-25.
[^26]: Microsoft cites the losing provider's response SLA as 3-5 business days in the United States and 5-7 business days in Canada. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > What happens after you submit a port order request. Checked 2026-09-25.
[^27]: The target porting date cannot be more than 30 calendar days in the future. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Plan lead-time for port request processing, Note. Checked 2026-09-25.
[^28]: For Calling Plans ports, the customer submits the port order to Microsoft. Microsoft handles fulfillment with the current provider and becomes the service provider of record for the numbers. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Introduction (before Information required for a port request). Checked 2026-09-25.
[^29]: A minimum five-day lead time applies in the US and a minimum ten-day lead time in Canada, and requests of more than 200 numbers should expect extra time. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Planning a number port event > Plan lead-time for port request processing, bullets. Checked 2026-09-25.
[^30]: Microsoft names account information that does not exactly match the carrier's records (authorized person, address, account number, BTN) as the most common cause of port errors and delays. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > Common mistakes, first bullet. Checked 2026-09-25.
[^31]: Mobile numbers can be ported to Microsoft Calling Plans only in the United States, Puerto Rico and Canada. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Numbers eligible for porting, paragraph after the You can transfer list. Checked 2026-09-25.
[^32]: In the port wizard, numbers are entered individually (10-digit or E.164 in the new US/Canada wizard, E.164 in the classic wizard) or uploaded as a one-column CSV headed PhoneNumber; number ranges are not supported. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), New wizard tab > Phone numbers step 1; All regions tab > Get started. Checked 2026-09-25.
[^33]: Numbers that cannot be ported to Calling Plans include data-line numbers (DSL/broadband), Universal International Freephone Numbers (UIFN), numbers that must keep working for fax, and numbers from unsupported countries or regions. UK nongeographic numbers, including the 0843, 0844, 0845, 0870, 0871 and 0872 ranges, are also unsupported. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Numbers eligible for porting > You can't transfer, and UK Note. Checked 2026-09-25.
[^34]: For Direct Routing numbers assigned online, the move to Operator Connect is done by the operator on an agreed date and time. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing to Operator Connect > Step 1. Checked 2026-09-25.
[^35]: Moving on-premises-assigned Direct Routing numbers to Operator Connect requires clearing LineURI with Set-CsUser in Skype for Business Server PowerShell. The number is out of service during the migration, so it must be coordinated with the operator. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Move numbers from Direct Routing to Operator Connect > Step 1, Important note. Checked 2026-09-25.
[^36]: With Operator Connect, the customer ports existing numbers by working directly with the Operator Connect partner, because the phone number services agreement is between the organization and the operator. Source: [Get Operator Connect telephone numbers for your organization - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/get-phone-numbers-with-operator-connect), Introduction paragraphs 3-4. Checked 2026-09-25.
[^37]: To move numbers from Calling Plans to Operator Connect, contact the operator to port them. When the port order completes, the operator uploads the numbers to the tenant, and the admin then assigns them in the Teams admin center or with PowerShell. Source: [Configure Operator Connect - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-configure), Set up phone numbers > Move numbers from Calling Plans to Operator Connect. Checked 2026-09-25.
[^38]: All numbers in one port order must share the same service provider, account number, BTN, number type and service address. Any variation requires separate orders. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > How many port requests do I need?. Checked 2026-09-25.
[^39]: Other common port blockers Microsoft lists are: advanced call control features still enabled (such as call hunt or distinctive ring), open service orders or pending disconnects, numbers from different providers or accounts in one order, and a frozen account. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > Common mistakes, bullets 2-5. Checked 2026-09-25.
[^40]: US user numbers can be ported at any target time between 8am and 8pm US Eastern. Canadian numbers (user and toll-free) and US toll-free numbers are scheduled at 11:30am Eastern, and an earlier time requires a special request to the TNS Service Desk. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Plan for port event to process during business hours. Checked 2026-09-25.
[^41]: The Calling Plans limits on how many phone numbers a tenant can acquire do not count numbers that are ported or being ported to Microsoft. Source: [Get Microsoft Calling Plan telephone numbers for your organization](https://learn.microsoft.com/en-us/microsoftteams/manage-phone-numbers), How many telephone numbers can you get?, Important note above the table. Checked 2026-09-25.
[^42]: Problems with ported numbers noticed within 24-48 hours after the port completes go to the Phone Number Service Center; anything after 48 hours goes to Microsoft Support. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Report phone number issues. Checked 2026-09-25.
[^43]: For numbers ported from an external carrier into Calling Plans, preassignment is allowed if the user or resource account has the required Phone System or resource account license and a Calling Plan license, and its usage location matches the number's country. Toll-free numbers also need a positive Communications Credits balance. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > table row Approved (FOCAccepted), New number preassignment rules 1-4. Checked 2026-09-25.
[^44]: A rejecting provider gives Microsoft only a category-level reason, not the correct values. The customer must get corrected information from the losing provider directly. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), What happens after you submit a port order request > Rejection, Note. Checked 2026-09-25.
[^45]: Once a losing provider rejects a port, it stops processing until a corrected request is resubmitted, and the response SLA starts over from resubmission. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), What happens after you submit a port order request > Rejection. Checked 2026-09-25.
[^46]: Port requests against the same account number are processed one at a time. If overlapping requests are submitted for one account, the losing provider processes only the first and rejects the others. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Port request considerations > How port requests are processed. Checked 2026-09-25.
[^47]: The Exception port-order status means the carrier that currently owns the numbers rejected the order, typically because of incorrect LOA details such as the PIN or ZIP code; Microsoft support corrects and resubmits the order. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > table row Exception. Checked 2026-09-25.
[^48]: Microsoft's port-order documentation uses two status vocabularies: the troubleshooting article uses Customer action required and Microsoft support engaged, while the transfer article's status table uses Exception and Manual review. Which labels a tenant actually sees probably depends on the wizard version and has not been confirmed (inferred). Source: [Resolve Issues That Affect Port Orders - Microsoft Teams](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/issues-with-port-orders), Introduction bullets and status headings, compared with ms-learn-transfer-phone-numbers status table. Checked 2026-09-25.
[^49]: The target port date and time chosen at submission is a request only. The port happens on that date only if the losing provider approves it. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), What happens after you submit a port order request, second paragraph. Checked 2026-09-25.
[^50]: A manual Port in case in the Phone Number Service Center must include a signed LOA, because Microsoft cannot process a port request without one. Source: [Contact the Telephone Number Services team](https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/contact-tns-service-desk), Create a new case > Case type > Port in. Checked 2026-09-25.
[^51]: The status Customer action required means the carrier rejected the order. The admin selects Update on the port-order details page, sees the rejection error, fixes it and resubmits. Source: [Resolve Issues That Affect Port Orders - Microsoft Teams](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/issues-with-port-orders), Status: Customer action required. Checked 2026-09-25.
[^52]: Documented carrier rejection errors cover mismatched account number, authorized user, organization name, PIN, ZIP code or service address, a missing LOA, and a freeze on the numbers. Microsoft's fix for the field errors is to correct the field to match the CSR. Source: [Resolve Issues That Affect Port Orders - Microsoft Teams](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/issues-with-port-orders), Errors related to fields in the Letter of Authorization (LOA) table; Errors related to your account table. Checked 2026-09-25.
[^53]: The status Microsoft support engaged needs no customer action. Microsoft Support handles the order, for example when a carrier rejection must be resubmitted by Microsoft or a submission error occurred, and a support ticket already exists. Source: [Resolve Issues That Affect Port Orders - Microsoft Teams](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/issues-with-port-orders), Status: Microsoft support engaged; Request assistance for your port order. Checked 2026-09-25.
[^54]: The Teams admin center offers two port wizards: a new wizard for US and Canada numbers (labelled US & Canada Preview) and a classic All regions wizard; Microsoft says the new wizard is being developed for the other Calling Plans regions. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Porting wizard - All regions tab > Launch the port wizard. Checked 2026-09-25.
[^55]: For US ports, changes must be requested at least 2 business days, and cancellations at least 1 business day, before the approved porting date. Source: [Phone number management for the United States](https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-the-u-s), Porting Existing Numbers FAQ row Can I change or cancel my port order?. Checked 2026-09-25.
[^56]: The US country page gives an approximate porting time of 5 to 12 business days for US numbers (disputed). Source: [Phone number management for the United States](https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-the-u-s), Porting Existing Numbers to Microsoft Teams > FAQ row How long will it take for me to port my phone numbers. Checked 2026-09-25.
[^57]: For US ports, Microsoft publishes two separate LOA forms, one for geographic user, voice app and conferencing numbers and one for toll-free numbers. Microsoft highly recommends also supplying the CSR from the losing carrier and a recent invoice. Source: [Phone number management for the United States](https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-the-u-s), Porting Existing Numbers to Microsoft Teams > FAQ row What information and documents do I need. Checked 2026-09-25.
[^58]: In the US, geographic numbers can be ported as user, voice app or audio conferencing numbers, but toll-free numbers can be ported only for voice apps or audio conferencing, not as user numbers. Source: [Phone number management for the United States](https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-the-u-s), What number types can I port? table. Checked 2026-09-25.
[^59]: A number's usage type (user or service) cannot be converted during the port process, only after the number has been ported to Microsoft. Source: [What's a port order? - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview), Numbers eligible for porting, paragraph on user and service numbers. Checked 2026-09-25.
[^60]: The new US/Canada wizard groups the entered numbers by account, service provider and type, and processes only one group per port request; each additional group needs its own request. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Porting wizard - New (U.S. & Canada) tab > Phone numbers, step 2. Checked 2026-09-25.