MC1188995 – Product transitions to the cloud.microsoft domain – November 2025 (archived)

Product:

Microsoft 365 suite, Outlook, Teams, To-Do

Platform:

Developer, Online, World tenant

Status:

Change type:

Feature update, User impact, Admin impact

Links:

Details:

Summary:
Microsoft products like Outlook and To Do are transitioning to the cloud.microsoft domain by November 2025, with gradual automatic redirects and no required user action. Admins should update documentation, ensure network compatibility, and educate users. The new domain enhances security using Microsoft’s exclusive top-level domain.

Details:
[Introduction]
The cloud.microsoft domain was provisioned in early 2023 to provide a unified, trusted, and dedicated DNS domain space to host Microsoft's first-party authenticated SaaS products and experiences. This post is to inform you that the following Microsoft products and scenarios are now available at the cloud.microsoft domain, in parallel with the previous domains:
Microsoft Outlook (https://outlook.cloud.microsoft/)
Microsoft To Do (https://todo.cloud.microsoft/)
[When this will happen]
The services listed above are already available on cloud.microsoft, in parallel with their previous domains.
Outlook is currently rolling out under Targeted Release and will expand to Standard Release in the coming months.
Users will begin seeing Outlook redirect from its old domains to outlook.cloud.microsoft as part of this change.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-11-22

updated:
2025-11-22

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Domain Transition Impact
Users may experience confusion or disruption if they are not informed about the transition to the new cloud.microsoft domain, potentially leading to missed communications or inability to access services temporarily.
   - roles: End Users, IT Support
   - references: https://techcommunity.microsoft.com/t5/microsoft-365-blog/introducing-cloud-microsoft-a-unified-domain-for-microsoft-365/ba-p/3804961

Network Configuration Issues
If network configurations are not updated to allow access to the new cloud.microsoft domain, users may face connectivity issues, leading to interruptions in service availability.
   - roles: Network Administrators, End Users
   - references: https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges

Documentation and Training Gaps
Failure to update internal documentation and educate users about the new domain may result in confusion and increased support requests, impacting user experience and productivity.
   - roles: IT Administrators, End Users
   - references: https://devblogs.microsoft.com/microsoft365dev/action-required-ensure-your-microsoft-teams-apps-are-ready-for-upcoming-domain-changes/

Compatibility with In-House Applications
In-house Teams applications may not function correctly if they are not updated to support the new cloud.microsoft domain, leading to potential service disruptions for users.
   - roles: Developers, End Users
   - references: https://devblogs.microsoft.com/microsoft365dev/action-required-ensure-your-microsoft-teams-apps-are-ready-for-upcoming-domain-changes/

Security Perception
Users may be skeptical about the new domain due to the lack of familiarity with the .microsoft top-level domain, potentially leading to trust issues and reluctance to use the services.
   - roles: End Users, IT Security
   - references: https://support.microsoft.com/office/what-is-cloud-microsoft-7ba4c8b9-d062-4444-84a5-fca6c3006d2b

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

User Education and Training
With the transition to the cloud.microsoft domain, there is an opportunity to enhance user education regarding the benefits and security features of the new domain. This can improve user confidence and reduce potential confusion during the transition.
   - next-steps: Develop training materials and sessions that explain the new domain, its advantages, and how to navigate any changes. Schedule training sessions for all users, focusing on those who use Outlook and To Do regularly.
   - roles: IT Administrators, Training Coordinators, End Users
   - references: https://support.microsoft.com/office/what-is-cloud-microsoft-7ba4c8b9-d062-4444-84a5-fca6c3006d2b, https://techcommunity.microsoft.com/t5/microsoft-365-blog/introducing-cloud-microsoft-a-unified-domain-for-microsoft-365/ba-p/3804961

Documentation Update
Updating internal documentation to reflect the new cloud.microsoft domain is crucial. This ensures that all users have access to accurate information and resources, minimizing confusion and support requests.
   - next-steps: Audit existing documentation and assets for references to old URLs. Create a project plan to update all relevant documentation, including internal guides, FAQs, and support resources.
   - roles: IT Administrators, Technical Writers, Support Staff
   - references: https://devblogs.microsoft.com/microsoft365dev/action-required-ensure-your-microsoft-teams-apps-are-ready-for-upcoming-domain-changes/, https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges " target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges

Network Configuration Review
As the new domain may require different network configurations, this is an opportunity to review and optimize the organization's network settings to ensure seamless access to cloud.microsoft services without disruptions.
   - next-steps: Conduct a network assessment to identify any potential blocks or issues with the new domain. Ensure that all necessary firewall and proxy settings are updated to allow traffic to *.cloud.microsoft.
   - roles: Network Administrators, IT Security Officers, System Administrators
   - references: https://learn.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges, https://techcommunity.microsoft.com/t5/microsoft-365-blog/introducing-cloud-microsoft-a-unified-domain-for-microsoft-365/ba-p/3804961

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

Microsoft is making a change to some of its products, like Outlook and To Do, by moving them to a new domain called cloud.microsoft. Think of this like moving a store to a new location. The products are still the same, but they now have a new address. The new domain is designed to enhance security, much like moving to a gated community where there are extra measures to keep things safe.

For users, this change will be mostly seamless. When you try to visit the old address, you'll be automatically redirected to the new one, similar to how mail is forwarded to a new home address. You don't need to do anything special; the transition will happen in the background. However, you might notice that the new web addresses don't have the usual ".com" ending. Instead, they end with ".microsoft," which is a special domain that only Microsoft can use, adding an extra layer of security.

For those managing IT systems, like admins, there are a few things to check. It's important to update any internal documents or systems that reference the old web addresses to avoid confusion. Also, make sure that your network settings allow access to the new domain, much like ensuring your GPS is updated with the new address. If you're following Microsoft's standard network guidelines, this should already be in place.

In-house applications, particularly those integrated with Microsoft Teams, may need to be checked for compatibility with the new domain. This is similar to ensuring that all your appliances work after moving to a new house. Admins have the option to disable redirects if needed, using controls available in the Teams Admin portal.

Overall, while the move to cloud.microsoft is designed to be smooth and secure, a little preparation can help ensure everything continues to run smoothly.