Teams Phone number porting checklist
Published Aug 8, 2024
•
Updated May 1, 2026
Overview
Number porting (LNP) is calendar-driven paperwork plus technical validation. Miss a FOC date and you strand users between carriers.
Pre-port
- Gather CSR (Customer Service Record) from losing carrier; validate BTN and account PIN.
- List every TN (DID), toll-free, and analog line; flag fax and alarm circuits early—they may need alternate paths.
- Confirm E911 addresses per location in the Teams admin center match PSAP expectations.
Order hygiene
- Submit LOA with matching legal entity name; signatory matches authorized reps on file.
- Coordinate temporary forwarding if gap risk; never promise zero downtime on complex trunks.
Cutover window
- Freeze auto attendant and hunt group changes 48 hours pre-FOC unless emergency.
- Post-cut: place test inbound/outbound, 911 test per local policy (coordinate with PSAP where required), verify SBC cert chains healthy.
Documentation
Store carrier tickets, LOA PDFs, and FOC confirmations in the client compliance folder; note CSR snapshot date for audits.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
security-endpoint-protection
msp
+1
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
security-endpoint-protection
msp
+1
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...
security-endpoint-protection
msp
+1