← Back
Know Your Customer (KYC) required for Teams Phone porting requests
MC1191607 · build prod-20251231-200323
Category
planForChange
Severity
normal
Major change
True
Last modified
2025-12-02 23:58:07
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
Action by (AI)
2026-01-01 00:00:00
Services
Microsoft Teams
Tags
Feature update, Admin impact
Master tags
Security
Roadmap IDs

One-line summary

Teams Phone port-in requests will require KYC business info and documents via Teams Admin Center before submission, starting rollout in January 2026; existing numbers are unaffected.

Similar updates

More like this
MC1184994 (Updated) Microsoft Teams frontline BYOD onboarding wizard
...Teams on personal Android or iOS devices What will happen: A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs The wizard dynamically adjusts based on your organization’s security policies Supports MFA setup, with emphasis on Microsoft Authenticator push notifications This tool is optional and.
MC1085133 (Updated) Microsoft Teams: Rule-based enablement of Microsoft 365 third-party apps in the Teams admin center
(Updated) Microsoft Teams: Rule-based enablement of Microsoft 365 third-party apps in the Teams admin center Admins can soon manage Microsoft 365 certified SaaS app availability in Teams via new org-wide settings, with enhanced controls for security and customization. Updated December 3, 2025: We have updated the timeline. This feature will now.
MC1045221 (Updated) Microsoft Teams: New user setting to view incoming calls in a small window
(Updated) Microsoft Teams: New user setting to view incoming calls in a small window Teams will introduce a setting for incoming calls to appear in a small, resizable window, reducing disruptions; rollout starts mid-Jan 2026 and will be on by default. Updated November 17, 2025: We have updated the timeline. Users will ... This message applies to.
MC1183611 (Updated) Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF)
Thank y... [Introduction] To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone.
MC1162275 Product transitions to the cloud.microsoft domain – September 2025
Product transitions to the cloud.microsoft domain – September 2025 Microsoft Teams is now available at teams.cloud.microsoft; users will be redirected from the old domain in coming months to enhance security. Update links and ensure .cloud.microsoft is not blocked. [Introduction] To improve security and trust across Microsoft cloud services,.
MC1088732 Microsoft Teams: Important updates for Android-based Teams devices – Authentication changes coming soon
Microsoft Teams: Important updates for Android-based Teams devices – Authentication changes coming soon Teams Android devices must update to specified app versions for modern Entra ID authentication by Dec 31, 2025, or risk service disruption; enhanced security features will be enabled. If your organization does not manage one or more certified.

Details

Summary
Starting January 2026, Teams Phone porting requires a one-time Know Your Customer (KYC) process via Teams Admin Center. Admins must submit business info and documents for validation before port-in requests. Existing numbers are unaffected. This applies globally and includes all tenants, with role-based access control via Entra ID.

Body (from Message Center)

[Introduction]

We’re extending the Know Your Customer (KYC) requirements to the Teams Phone porting process in all markets. Teams administrators will need to submit general business information and supporting documents via Teams Admin Center before initiating a port-in request. This one-time process allows Microsoft to validate businesses and fulfill regulatory requirements, helping protect our phone services from misuse, such as spam calls and voice phishing (vishing).

If your organization has already completed the KYC onboarding (for example, when acquiring new telephone numbers), no further action is required. You will not need to complete the process again and can disregard this message. If you are unsure of the KYC status of your organization, please visit the Know Your Customer page in the Teams Admin Center to verify it and complete it if necessary.

[When this will happen:]

General Availability (Worldwide, GCC): We will begin rolling out early January 2026 and expect to complete by late January 2026.

[How this affects your organization:]

Who is affected: Teams administrators managing port-in requests for Teams Phone in all markets.

What will happen:

  • Teams administrators must complete a KYC process in the Teams Admin Center before submitting port-in requests.
  • Admins will be required to submit business information and supporting documentation.
  • The vetting process typically takes a few hours but may take up to two business days.
  • No port-in requests can be processed until the submitted information is validated.
  • Existing telephone numbers are not affected.
  • These requirements apply globally and are consistent across all Calling Plans markets.

[What you can do to prepare:]

  • Complete the KYC process in advance by visiting the Know Your Customer page in the Teams Admin Center.
  • Ensure your Teams administrators are ready to provide the following information:
    • Business email address
    • Company name
    • Tax ID, DUNS number, or Business Registration Number
    • Business address
    • A copy of the Business Registration, Registry Extract, or Articles of Incorporation
  • This process applies to all tenants, including those on free trials. No specific license tier is required to complete the KYC onboarding.
  • Learn more: Teams Phone Know Your Customer overview - Microsoft Teams | Microsoft Learn

[Compliance considerations:]

Question Explanation
Does the change store new customer data? The KYC onboarding process requires submission of business information and supporting documentation, which will be stored by Microsoft to fulfill regulatory requirements.

Does the change alter how existing customer data is processed? The process introduces new data collection and validation workflows that may interact with existing tenant metadata.
Does the change include an admin control and can it be controlled through Entra ID group membership? The KYC onboarding process is managed through the Teams Admin Center, which supports role-based access control via Entra ID group membership.

Raw JSON (for debugging)

Expand/collapse the full payload below.
Show/hide raw
{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": "2026-01-01T00:00:00Z",
    "ai_actions": [
      "Verify KYC status in Teams Admin Center",
      "Complete KYC onboarding if not done",
      "Prepare required business documentation"
    ],
    "ai_master_tags": [
      "Security"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "Teams Phone port-in requests will require KYC business info and documents via Teams Admin Center before submission, starting rollout in January 2026; existing numbers are unaffected.",
    "ai_topics": [
      "Teams"
    ],
    "category": "planForChange",
    "details_map": {
      "Summary": "Starting January 2026, Teams Phone porting requires a one-time Know Your Customer (KYC) process via Teams Admin Center. Admins must submit business info and documents for validation before port-in requests. Existing numbers are unaffected. This applies globally and includes all tenants, with role-based access control via Entra ID."
    },
    "id": "MC1191607",
    "importance": 5,
    "is_major_change": true,
    "last_modified": "2025-12-02T23:58:07Z",
    "ms_products": [
      "Teams"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "Microsoft Teams"
    ],
    "severity": "normal",
    "tags": [
      "Feature update",
      "Admin impact"
    ],
    "title": "Know Your Customer (KYC) required for Teams Phone porting requests"
  }
}