Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 01:28 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams | New in Admin Center: Self-Serve Fixes for Porting Rejections

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 15 Aug 2025 early August 2025 → mid-August 2025, late August 2025
  • Seen 28 Jul 2025 late July 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated August 14, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a new self-service capability in the Teams Admin Center (TAC) that allows Teams Phone administrators to resolve and resubmit certain porting order rejections without needing to contact Microsoft support. This enhancement improves efficiency and reduces turnaround time for common porting issues, while preserving the existing support experience for more complex cases. When this will happen General Availability: We will begin rolling out in mid-August 2025 (previously early August)and expect to complete by late August 2025 (previously early August). How this will affect your organization This update streamlines the current porting experience in TAC without removing any existing features. Administrators will now be able to use the existing porting wizard not only to submit new porting orders but also to fix and resubmit certain rejected orders. When a porting order is rejected for a fixable reason—such as an incorrect ZIP code or missing PIN—administrators will: Receive an email notification. See a prompt on the order's detail page in TAC. Be guided through the porting wizard to correct and resubmit the order. This self-serve experience is designed to feel familiar and intuitive, minimizing disruption. Rejections that require partner coordination or are otherwise ineligible for self-service will continue to be handled by Microsoft support. This feature is: On by default Available to all tenants Accessible to Teams Phone administrators with appropriate permissions Admins can still contact Microsoft support if needed.  Steps to resolve a rejected porting order in Teams Admin Center To fix and resubmit a rejected porting order: a. Navigate to Teams Admin Center.  b. In the left navigation, expand the Voice drawer and select Phone numbers:   c. On the Phone numbers page, select the Order history tab. If an order requires customer attention, its status will show Customer action required. d. Click the name of the order to open its details: e. In the order details page, select Update to correct the issue and resubmit the order:   Steps to contact Microsoft support a. If your order status is Microsoft Support Engaged, it means that your order already has an associated support ticket. On the order details page, select the Contact service desk hyperlink and navigate to the associated ticket.  b. If your order status is Customer action required, you will need to create a new support ticket. Here are the steps: On the Order Details page, select the Action dropdown and select Get support. On the support home page, select Create ticket On the Create ticket page, fill in your Title, Description, Country. Ensure your Case Type is "Port in"and your Case Creation Reason is "Question about existing request" What you need to do to prepare Review the updated guidance on porting numbers to Teams: Submitting a port request | Microsoft Learn.  No additional configuration is required to enable this feature. Compliance considerations No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first
  1. Updated July 28,August 14, 2025: We have updated the timeline. Thank you for your patience. Introduction … When this will happen General Availability: We will begin rolling out in early August mid-August 2025 (previously late July) and early August)and expect to complete by earlylate August 2025. 2025 (previously early August). How this will affect your organization This update streamlines the current porting …

    • Tags Feature update, User impact → Updated message, Feature update, User impact

    Updated July 28, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a new self-service capability in the Teams Admin Center … When this will happen General Availability: We will begin rolling out in  early August 2025 (previously late July 2025July) and expect to complete by early August 2025. How this will affect …

  2. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 01:28 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current