Understanding the Change to outlook.cloud.microsoft
If you find that your desktop Outlook application has started redirecting to outlook.cloud.microsoft instead of opening normally, you are likely seeing Microsoft’s transition of Outlook to a new cloud-based hosting platform. This domain is part of Microsoft’s broader consolidation of its cloud services under a unified infrastructure. For most users, this change is seamless and happens automatically through an update. However, some users experience issues where Outlook either fails to connect, opens a blank browser window, prompts for repeated sign-ins, or refuses to load at all.
The good news is that this is almost always a configuration or connectivity problem rather than a permanent failure of the application. Before attempting any fixes, it is important to understand that outlook.cloud.microsoft is a legitimate Microsoft domain. It is not a phishing site or an error. The problem occurs when your Outlook client, your browser, or your network is not handling the new endpoint correctly.
Check What Is Causing the Problem
The first step is to identify where the redirect is happening. In most cases, Outlook for Microsoft 365 (the classic version) and the new Outlook for Windows both rely on web-based authentication and, in the case of the new Outlook, a web-rendered interface. When Outlook tries to load the interface or authenticate, it may attempt to reach outlook.cloud.microsoft. If this fails, you may see a white screen, an error message, or a hanging process.
Possible causes include:
- An outdated version of Outlook or a pending update that has not completed correctly.
- Browser cache or cookies interfering with the authentication flow, even if you are not actively using a browser to open Outlook.
- Antivirus, firewall, or VPN software blocking the new domain.
- DNS issues on your network that prevent resolution of the domain.
- A corrupted Outlook profile or cached credentials.
Testing whether you can reach outlook.cloud.microsoft through a standalone web browser is a quick diagnostic step. Open your default browser and navigate directly to that URL. If the Outlook web app loads correctly, the issue is likely local to the desktop client. If it fails in the browser as well, the problem is likely network-related or a wider service issue.
Fixes to Try in Order
Because the causes vary, the most effective approach is to try fixes from simplest to most involved. You do not need to try every possible fix if an earlier step resolves the problem.
1. Update Outlook to the Latest Version
Microsoft regularly releases updates that address connectivity and authentication changes. If your Outlook version predates the domain transition, the client may not handle the redirect gracefully.
- Open Outlook.
- Go to File > Office Account (or Account, depending on your version).
- Click Update Options and then Update Now.
- Allow the update to complete and restart Outlook.
If Outlook will not open at all, you can manually download and install the latest update from the Microsoft support site for your specific Office version.
2. Clear Outlook Credentials from Windows Credential Manager
Stale credentials stored in Windows can cause authentication loops when the endpoint changes.
- Open the Control Panel and go to User Accounts > Credential Manager.
- Click Windows Credentials.
- Look for any entries related to Outlook, MicrosoftOffice, or Microsoft AAD (Azure Active Directory). Common names include
MicrosoftOffice16_Data:ADAL:...orMicrosoftOffice16_Data:MSOLogin:.... - Expand each relevant entry and click Remove.
- Restart Outlook. You will be prompted to sign in again.
This step does not delete your email data; it only clears cached authentication tokens.
3. Repair Outlook via Office Installation
If the application files themselves are damaged, a Quick Repair can restore them without affecting your data.
- Open Settings > Apps > Installed apps (or Apps & features).
- Locate your Microsoft Office or Microsoft 365 entry.
- Click the three dots and select Modify.
- Choose Quick Repair and follow the prompts.
If Quick Repair does not work, proceed with the Online Repair option, which requires an internet connection and takes longer but performs a full reinstallation.
4. Disable Add-ins Temporarily
Some third-party add-ins conflict with the new cloud authentication flow. Launch Outlook in safe mode to test.
- Press
Windows Key + R, typeoutlook.exe /safe, and press Enter. - If Outlook opens normally in safe mode, go to File > Options > Add-ins.
- At the bottom, select COM Add-ins from the Manage dropdown and click Go.
- Uncheck all add-ins, restart Outlook normally, and then re-enable add-ins one by one to identify the problematic one.
5. Check Browser Settings and Cache
Even if you use the desktop Outlook app, the new Outlook for Windows and the classic Outlook with certain features (like the To Do pane, calendar sharing, or add-ins) rely on web components rendered through a built-in browser view. That view uses your system’s default browser engine.
- Clear your browser cache and cookies, especially for Microsoft domains.
- Ensure your browser is up to date.
- If you use a third-party browser, try setting Microsoft Edge as the default browser temporarily to test whether the issue is browser-specific.
6. Flush DNS and Reset Network Settings
If the domain is not resolving correctly, your system will fail to connect.
- Open Command Prompt as Administrator.
- Type
ipconfig /flushdnsand press Enter. - Type
ipconfig /registerdnsand press Enter. - Type
netsh int ip resetand press Enter. - Restart your computer.
You can also try temporarily disabling your VPN or third-party firewall to confirm whether security software is blocking the connection to outlook.cloud.microsoft.
If the Problem Continues
If none of the steps above resolve the issue, the problem may be on Microsoft’s side or specific to your account. Check the Microsoft 365 Service Health dashboard (accessible through the admin center if you have an administrator account, or through the Microsoft 365 status page for general service incidents). A temporary outage affecting the outlook.cloud.microsoft endpoint would prevent all clients from connecting.
You can also create a new Outlook profile to rule out profile corruption:
- Open Control Panel and go to Mail (or Mail (Microsoft Outlook)).
- Click Show Profiles.
- Click Add, give the profile a new name, and configure your email account again.
- Set the new profile as the default and restart Outlook.
If the new profile works, you can delete the old profile after confirming your data is intact.
As a last resort, uninstall and reinstall Microsoft 365 or the Outlook application. Use the official Microsoft Support and Recovery Assistant tool, which can automate several of these steps and diagnose connectivity issues more deeply. That tool is available from Microsoft’s support site and is designed specifically for Office and Outlook problems.
Frequently Asked Questions
Is outlook.cloud.microsoft safe?
Yes. It is an official Microsoft domain used for hosting Outlook web components and authentication services. It is not a phishing site. If you are unsure, verify that the URL appears in your address bar as https://outlook.cloud.microsoft with a valid security certificate.
Will I lose my emails if I delete my Outlook profile?
No. Deleting or recreating an Outlook profile only removes the account configuration from the desktop client. Your emails, calendar entries, and contacts remain on the server. They will reappear once you add the account to a new profile.
Does switching to the new Outlook for Windows fix the issue?
Not necessarily. The new Outlook for Windows also relies on the outlook.cloud.microsoft endpoint. If the problem is network- or account-based, both versions may experience the same issue. However, the new Outlook is updated more frequently, so it may resolve some compatibility problems that the classic version has not yet patched.
Should I disable my antivirus permanently to make Outlook work?
No. Temporarily disabling it to test is reasonable, but you should re-enable it immediately. If your antivirus is blocking the domain, add outlook.cloud.microsoft to the trusted or allowed applications list in your security software instead of disabling protection entirely.
