Source note · Porting numbers to Microsoft Teams
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.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone - Calling Plans
- Subsystem
- port rejection
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Resolve Issues That Affect Port Orders - Microsoft Teams — Microsoft · tier 2 current vendor documentation · Errors related to fields in the Letter of Authorization (LOA) table; Errors related to your account table
Cite this note
APA
WarmTransfer. (2026, September 25). Porting numbers to Microsoft Teams: source note teams-number-porting-ts-rejection-fields. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-number-porting-ts-rejection-fields
BibTeX
@misc{warmtransfer-claim-teams-number-porting-ts-rejection-fields,
title = {Porting numbers to Microsoft Teams: source note teams-number-porting-ts-rejection-fields},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-number-porting-ts-rejection-fields},
note = {Source note teams-number-porting-ts-rejection-fields, checked 2026-09-25}
}