Source record · tier 2 current vendor documentation

What's a port order? - Microsoft Teams

Publisher: Microsoft
URL: https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/port-order-overview
Published: 2026-05-28
Updated: unknown
Accessed: 2026-09-24
HTTP status: 200
License: Microsoft Learn content; CC BY 4.0 for docs text per MicrosoftDocs repos, verify before reuse; no-redistribution; short excerpts and locators only

Source notes citing this source

Microsoft recommends a conservative target port date at least 15 business days after submission for all ports, trading speed for predictability. in context
When porting hybrid numbers, meaning numbers moving from Direct Routing or Operator Connect to Calling Plans, Microsoft asks customers to contact the TNS service desk and flag the numbers as hybrid. in context
A port request of 1,000 numbers or more must bypass the Teams admin center porting wizard and be submitted manually through the Telephone Number Services service desk. in context
Microsoft says a Calling Plan port typically takes 7-14 days end to end and up to 30 days depending on the losing carrier; the US needs at least 5 days' lead time, Canada at least 10, and the target date cannot be more than 30 calendar days out. in context
Microsoft advises against disconnecting service with the current provider before porting is complete, because inactive or disconnected numbers cannot be ported. in context
Port requests against the same carrier account are processed one at a time; a second batch from the same account must wait until the first port completes, or the losing carrier rejects the overlapping requests. in context
Microsoft recommends a conservative target port date at least 15 business days after submission for all ports. in context
Microsoft identifies the Customer Service Record (CSR) as the US document of record for porting and the Equipment Record as the Canadian equivalent. in context
Microsoft advises not disconnecting service with the current provider before porting completes, because inactive or disconnected numbers cannot be ported. in context
An account freeze at the losing provider causes a Microsoft port order to be rejected, and Microsoft says removing a freeze can take one to three weeks. in context
Microsoft Calling Plan port requests of 1,000 or more numbers must bypass the Teams admin center wizard and be submitted manually through the Telephone Number Services (TNS) Service Desk. in context
For Microsoft Calling Plan ports, the minimum lead time is five days in the US and ten days in Canada, and target port dates cannot be more than 30 calendar days out. in context
Microsoft gives the losing service provider's response SLA as 3-5 business days in the United States and 5-7 business days in Canada. in context
Porting mobile numbers into Microsoft Calling Plans is available only in the United States, Puerto Rico and Canada. in context
A single Teams admin center port order requires every number to share the same service provider, account number, BTN, number type and service address. in context
For US user numbers on Microsoft Calling Plans, port times can be chosen between 8am and 8pm US Eastern; Canadian numbers and US toll-free numbers are scheduled at 11:30am Eastern. in context
Microsoft says port requests for the same account number are processed one at a time; overlapping requests on one account cause the losing provider to reject all but the first, or all of them. in context
Vendor lead times of five or more business days exceed the US regulatory porting intervals, most likely because they add vendor validation, LSR rejections and resubmissions, and customer date preferences on top of carrier execution. inferred in context
Microsoft advises turning off advanced call-control features such as call hunt or distinctive ring on the numbers with the current provider before porting to Teams. in context
Numbers dedicated to fax cannot keep faxing after a port to Teams, because Phone System and Calling Plan licences include no fax service; they can only be assigned to users. in context
Microsoft's port order process, where Microsoft becomes the service provider of record, applies to Teams Phone with Microsoft Calling Plans. in context
A single Teams port order can include only numbers that share the same service provider, account number, BTN, number type and service address; anything else needs separate orders. in context
Ports of 1,000 or more numbers to Teams Calling Plans must skip the Teams admin center wizard and be submitted manually to the Telephone Number Services service desk. in context
Microsoft says a Teams port typically takes 7 to 14 days and up to 30, needs at least 5 days' lead time in the US and 10 in Canada, and cannot target a date more than 30 calendar days out. in context
The losing provider processes port requests for the same account number one at a time; overlapping requests on one account are rejected, so batched ports must be sequential. in context
Microsoft recommends a conservative target port date at least 15 business days after submission over an aggressive date under 7 (US) or 10 (Canada) business days. in context
To move numbers from Direct Routing or Operator Connect into Calling Plans (hybrid numbers), customers contact the TNS Service Desk and flag the numbers as hybrid. in context
Data-line numbers (DSL/broadband), Universal International Freephone Numbers and numbers from unsupported countries cannot be ported, and fax numbers can be ported only for use as user numbers because Calling Plans provide no faxing. in context
Port requests of 1,000 numbers or more must bypass the Teams admin center wizard and be submitted manually through the Telephone Number Services (TNS) Service Desk. in context
A port order typically takes 7-14 days end to end and up to 30 days; the US needs a minimum 5-day lead time, Canada 10 days, and the target port date cannot be more than 30 calendar days out. in context
The losing carrier's response SLA to a port request is 3-5 business days in the United States and 5-7 business days in Canada, and it resets if a rejected request is resubmitted. in context
Porting mobile numbers into Microsoft Calling Plans is available only in the United States, Puerto Rico and Canada. in context
One wizard port order can carry many numbers only if they share the same service provider, account number, billing telephone number (BTN), number type and service address; otherwise separate orders are needed. in context
Port requests for the same carrier account number are processed one at a time; submitting overlapping requests for one account causes the losing carrier to reject all but the first (or all). in context
Microsoft does not currently support porting UK nongeographic numbers, including shared-cost 0843, 0844, 0845, 0870, 0871 and 0872 numbers, into Calling Plans. in context
Numbers can be ported to Microsoft Calling Plans in every country or region where Calling Plans are offered, and the Teams admin center porting wizard only shows those countries. in context
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. in context
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 in context
Microsoft directs complex port projects that span multiple providers, accounts/BTNs, number types or service addresses to a manual Port in request. in context
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. in context
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. in context
Do not disconnect service with the current provider before the port. Inactive or disconnected numbers cannot be ported. in context
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. in context
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. in context
To move hybrid numbers (Direct Routing or Operator Connect) into Calling Plans, contact the TNS Service Desk and state that the numbers are hybrid. in context
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. in context
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 in context
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 in context
Microsoft cites the losing provider's response SLA as 3-5 business days in the United States and 5-7 business days in Canada. in context
The target porting date cannot be more than 30 calendar days in the future. in context
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. in context
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. in context
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. in context
Mobile numbers can be ported to Microsoft Calling Plans only in the United States, Puerto Rico and Canada. in context
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. in context
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. in context
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. in context
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. in context
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. in context
Once a losing provider rejects a port, it stops processing until a corrected request is resubmitted, and the response SLA starts over from resubmission. in context
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. in context
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. in context
A number's usage type (user or service) cannot be converted during the port process, only after the number has been ported to Microsoft. in context

Cite this source record

APA

WarmTransfer. (2026, May 28). What's a port order? - Microsoft Teams. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-port-order-overview

BibTeX

@misc{warmtransfer-ms-learn-port-order-overview,
  title  = {What's a port order? - Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-port-order-overview},
  note   = {Microsoft, accessed 2026-09-24}
}