MC1459136Microsoft 365 admin center: Usage reports migrating to new domains

What and why:

As part of Microsoft's domain consolidation initiative, Microsoft 365 admin center Usage reports will begin resolving new domains. Both the current and the new domains will remain active in parallel for a minimum of 30 days following this post, so Usage reports will continue to load on the current domains while you update your network configuration.

Redirection of the current domains to the new domains is not scheduled at this time. Any redirect will occur no earlier than September 17, 2026, subject to validation and approval, and we will announce the timing in a separate Message center post before it takes effect. The current domains will be retired at a later date following the redirect, and we will communicate that timing separately as well, so adding the new domains to your network configuration is required rather than optional. There is no change to the Usage reports experience, data, or permissions — this is a domain change only.

Rollout schedule:

• Worldwide: We will begin rolling out on mid-August 2026 and expect to complete by mid-August 2026.
• GCC: We will begin rolling out on mid-August 2026 and expect to complete by late August 2026.
• GCC High: We will begin rolling out on late August 2026 and expect to complete by late August 2026.
• DoD: We will begin rolling out on late August 2026 and expect to complete by early September 2026.

Impact on your organization:

Usage reports in the Microsoft 365 admin center will begin resolving to new domains, per cloud environment:

Enter the new domains exactly as shown when you update your network configuration.

If your organization uses firewall rules, proxy allowlists, or conditional access policies that reference the specific Usage reports domains listed above, Usage reports may fail to load once traffic moves to the new domains. The same applies if you use custom scripts or tooling with hardcoded endpoints. Because both domain sets remain active during the parallel period, this will not interrupt access before the redirect date is announced in a future post.

If you rely on poader Microsoft-managed to allow rules, service tags, or wildcard-based network configurations, you may need fewer changes or none, depending on your current network policy.

Action required / Recommendations:

Review your firewall, proxy, and conditional access configurations for references to the current Usage reports domains and add the corresponding new domains before your cloud environment rollout window closes.

• Check any custom scripts, automation, or integrations that call Usage reports at endpoints directly, and update hardcoded domains.
• Keep the current domains allowlisted alongside the new ones until the redirect timing is announced, so that access is maintained throughout the parallel period.
• Government and sovereign cloud tenants should validate the new domains against their network boundary and compliance requirements.
• If your network policy does not explicitly allowlist these domains, no action is required.

We will publish a reminder before the parallel period ends, and we will communicate via Message center if there are any additional changes to this rollout.