MC1462460 Medium
Microsoft Entra: Domain update for My Account and identity self-service experiences
Summary AI-generated
Microsoft Entra self-service experiences will move to myaccount.cloud.microsoft in late November 2026, unifying identity management domains for improved consistency.
Suggested actions AI-generated
- Review network, proxy, firewall, and endpoint policies for Microsoft services.
- Ensure *.cloud.microsoft is allowlisted.
- Confirm myaccount.cloud.microsoft access is not blocked.
- Update internal documentation or user guidance with new URLs.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1506728 Microsoft Entra: Changes to AgentIdentity.CreateAsManager permission for agent identities
- MC1191924 Microsoft Entra ID: Enhance protection of the authentication experience by blocking external script injection
- MC1392563 (Updated) OneDrive transitions to the cloud.microsoft domain
- MC1481309 Microsoft Entra ID: Enhance protection of the authentication experience by blocking external script injection
- MC1437671 (Updated) Microsoft Entra: Allow password change after secure sign-in with My Sign-Ins
- MC1303719 (Updated) Microsoft Entra: Upcoming changes to federatedTokenValidationPolicy default settings
Original post from Microsoft
[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
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
Additional details from Microsoft
- Summary
- 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.