Microsoft Entra: Domain update for My Account and identity self-service experiences

Microsoft Entra is updating its self-service identity management domain from myaccount.microsoft.com to myaccount.cloud.microsoft, consolidating related sites for a unified experience. The change rolls out worldwide in late November 2026. Users need no action; administrators should ensure *.cloud.microsoft domains are allowed in network policies.

[What and why]

We're updating the domain used for Microsoft Entra identity and access management self-service experiences. As part of this change, myaccount.microsoft.com will move to myaccount.cloud.microsoft. Experiences currently hosted on separate domains will also be consolidated under the myaccount.cloud.microsoft domain.

The following experiences are included in this update:

• myaccount.microsoft.com
• myapps.microsoft.com
• myaccess.microsoft.com
• mystaff.microsoft.com

This change provides a more consistent and unified access point for identity and access management self-service experiences while supporting ongoing improvements to our service infrastructure.

[Rollout schedule]

• General Availability (Worldwide): Beginning in late November 2026 and expected to complete in late November 2026

[Impact on your organization]

Who is affected

• Users who access Microsoft Entra self-service identity and access management experiences
• Administrators who manage network, proxy, firewall, or endpoint allowlists

Platforms and services

• Microsoft Entra
• Web

What will happen

For users

• No action is required.
• Users accessing supported experiences will be automatically redirected to the new domain.
• Core functionality and existing workflows will remain unchanged.
• Over time, self-service identity and access management experiences will be available through a unified domain experience.

For administrators

• Most organizations are not expected to require configuration changes.
• Organizations that manage network, proxy, firewall, or endpoint allowlists should verify that required cloud.microsoft domains are accessible.
• Failure to allow required domains may result in users being unable to access these experiences after the rollout.

[Action required and recommendations]

Recommended actions for administrators

Before rollout begins:

• Review network, proxy, firewall, and endpoint policies that restrict access to Microsoft services.
• Verify that *.cloud.microsoft is included in required allowlists where applicable.
• Confirm that access to myaccount.cloud.microsoft is not blocked within your environment.
• Review internal documentation or user guidance that references the existing URLs and update as needed.

No action is required for users.

Learn more

• Unified cloud.microsoft domain for Microsoft 365 apps | Microsoft 365 for enterprise | Microsoft 365 | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.