Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Outlook keeps asking for a password with Microsoft 365: 'The connection to Microsoft Exchange is unavailable'

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Outlook shows a credentials box that returns every time, while Outlook displays "trying to connect...". If you cancel, Outlook says "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." Microsoft documents one cause for older Outlook: the Logon network security setting on the account is not Anonymous Authentication.

Microsoft says Outlook 2016 and recent builds of Outlook 2013 do not show that setting. For those, check three other things: whether the tenant's modern authentication switch for Outlook is on, whether the Outlook version is one Microsoft still supports for connecting, and whether the profile or the service is at fault.

What the error means

Microsoft's page, "Outlook continually prompts for your password when you try to connect to Microsoft 365", says that when you try to create an Outlook profile or connect to a Microsoft 365 mailbox, "you're continually prompted for credentials while the client displays a "trying to connect..." message." The page lists Outlook 2013, Outlook 2010, Office Outlook 2007 and Exchange Online as its scope.

Its cause: "the Logon network security setting on the Security tab of the Microsoft Exchange dialog box is set to a value other than Anonymous Authentication." It also says: "Microsoft Outlook 2016 and some recent builds of Outlook 2013 are not affected by this issue." Of those versions it says: "These versions have the Logon network security setting disabled or removed" from the account settings.

Two other pages set the background. Microsoft's modern authentication page says that when modern authentication is disabled in Exchange Online, Windows Outlook clients that support it "use basic authentication to connect to Exchange Online mailboxes." And the Basic authentication page states that Basic authentication "is now disabled in all tenants", including Outlook for Windows. A client that falls back to a method the service no longer accepts has nothing to offer except a prompt. Microsoft does not say in these words that this produces the loop, so test it rather than assume it.

The look of the prompt is a clue. Microsoft's modern authentication page says "the Basic Auth sign in dialog box and the Modern Auth dialog box look very different." Ask one affected user for a screenshot of the prompt and compare it with the sign-in window on a PC that connects correctly. If the two differ, the affected client may be using a different authentication method from the working one, and that difference is the first thing to explain.

The Basic authentication page also lists what was removed: Basic authentication in Exchange Online for Exchange ActiveSync, POP, IMAP, Remote PowerShell, Exchange Web Services, Offline Address Book, Autodiscover, Outlook for Windows and Outlook for Mac. It adds that the change "also prevents the use of app passwords with apps that don't support two-step verification." Microsoft does not say what a user sees when an old client still presents an app password, so treat a saved app password as no longer usable with those apps and test the client you have.

Likely causes

Cause What you see How to confirm
Logon network security not Anonymous Authentication (Outlook 2013 and earlier) Prompt loop, then "The connection to Microsoft Exchange is unavailable." Security tab in the account's More Settings shows another value
Modern authentication off for Outlook in the tenant (Microsoft does not state that this causes the loop; unconfirmed) Outlook 2013 or later may prompt and fail to sign in OAuth2ClientProfileEnabled is False. Microsoft says modern authentication has been on by default since August 2017, so False is a deliberate setting
Outlook version not supported for connecting Older Office installs fail or misbehave Version compared with Microsoft's connectivity table
Damaged profile or out-of-date software One PC only Microsoft: "Out-of-date software and corrupted Outlook profiles are two of the most common issues that can prevent you from sending and receiving email." Test on another PC
Service problem Many users at once Microsoft 365 Service health shows an Exchange Online issue

Prove the cause before changing anything

  1. Find the Outlook version on the affected PC. Compare it with Microsoft's table: Microsoft 365 Apps are "Supported as long as you’re using a supported version.", and "Support for connection to Microsoft 365 services with Office 2019 and Office 2016 ended on October 10, 2023." Support terms change, so check the current page.
  2. In Exchange Online PowerShell, read the tenant setting:
Get-OrganizationConfig | Format-Table Name,OAuth* -Auto

Record the OAuth2ClientProfileEnabled value.

  1. On an Outlook 2013 or earlier profile, open Control Panel, Mail, Show Profiles, choose the profile, Properties, E-mail Accounts, select the account, Change, More Settings, Security tab. Write down the Logon network security value. Do not edit the profile in the registry. Microsoft says modifying the Outlook profile by using the "Profiles" registry path "is not supported and may cause your Outlook profile to be in an unsupported state."
  2. If several people are affected together, check Service health in the Microsoft 365 admin center before touching any client.
  3. Run Microsoft's self-diagnostic, "Diag: Outlook keeps asking for my password", from Microsoft's password page. Microsoft's password page offers it for users of newer Outlook 2013 or Outlook 2016 on Exchange Online.

Fix

Logon network security (Outlook 2013 and earlier). Save first: the value you wrote down in step 3.

Disruptive step: exit Outlook, open the same dialog, set Logon network security to Anonymous Authentication, select OK, then Next, Finish and Close on each dialog. Impact: changes the authentication setting for that profile only. Back-out: set the list back to the value you wrote down.

Modern authentication off. Microsoft does not say that a False value causes the prompt loop, so run this only if step 2 showed False and the affected clients are Outlook 2013 or later. Microsoft's command enables modern authentication for Outlook 2013 or later.

Save first: the output of the Get-OrganizationConfig command above, which shows the current OAuth2ClientProfileEnabled value.

Disruptive step: the command below changes the whole tenant. Impact: Microsoft says Windows Outlook clients "are prompted to sign in again", the dialog looks different from the basic one, and a user with several accounts in one profile "might receive an error when they try to connect." Microsoft says the command "doesn't block or prevent Outlook 2013 or later clients from using basic authentication connections."

Set-OrganizationConfig -OAuth2ClientProfileEnabled $true

Back-out: run the same cmdlet with the value you saved from Get-OrganizationConfig, here -OAuth2ClientProfileEnabled $false. Be aware that with the setting at False, clients that use it may not be able to sign in, because Microsoft's deprecation page says basic authentication "is now disabled in all tenants". If sign-in fails afterwards, address the individual clients rather than relying on the setting. You can also reach this setting in the admin center under Settings, Org Settings, Modern Authentication.

Unsupported Outlook. Update to a supported version. Microsoft's connectivity page (dated 2026-09-28) says older Office versions "might still be able to connect to Microsoft 365 services, but that connectivity isn't supported." Support terms change, so check the current page.

Save first: on each PC to be updated, record the installed Outlook version and build (File, Office Account, About Outlook), and confirm the user's mail is held on the server, not only in a local data file.

Disruptive step: update Outlook to a supported version. Impact: it changes what the user sees, can change how profiles and add-ins behave, and applies to every user you update, so schedule it outside working hours and start with one PC. Back-out: there is no documented way back to an unsupported build; reinstalling the recorded version would put an unsupported client back, so keep the recorded version only as a record of what the PC had.

Profile or software problem. Microsoft's connection page suggests Windows Update and Microsoft's diagnostic "Run Tests: Outlook User Connectivity", which "requires a Microsoft 365 administrator account." Microsoft's connection page does not describe re-creating a profile, so treat it as a last step: keep the old profile until a new one is proven to work.

Save first: record the Windows and Outlook versions on that PC before running Windows Update.

Disruptive step: run Windows Update on the affected PC. Impact: Microsoft's page says it installs updates for Outlook and other desktop applications for Microsoft 365, and it can interrupt the user's work, so ask them to save open work first. Back-out: Microsoft's page gives none; test on one PC before others.

Confirm the fix

Start Outlook on the affected PC and watch for the "trying to connect..." message that Microsoft's password page describes. A working fix shows the mailbox connecting with no repeat prompt, and the credentials box does not return after a restart of Outlook. Send and receive one test message. If you changed the tenant setting, check one user on the oldest supported client and one on the newest.

Example (illustrative): rds01 hosts 40 users, all on one Outlook build. The tenant's modern authentication setting for Outlook was False. The administrator records the value, sets it to $true, and each user is asked to sign in again. If each sign-in takes about one minute, that is 40 minutes (40 x 1) of sign-in time spread across the group. Users with two mailboxes in one profile need extra attention, as Microsoft warns.

What to watch afterwards

  • Keep a list of Outlook versions in use and compare it with Microsoft's connectivity table at each quarter end.
  • After enabling modern authentication, watch for "Disconnected" reports from users with several accounts.
  • If conditional access or multifactor settings change later, retest Outlook on one account before applying to all.
  • Note the date the tenant setting was changed, so later faults can be placed before or after it.
  • Keep a record of which users have more than one account in their Outlook profile, since Microsoft names that case as one that can show a connection error after the change.

Risks and limits

These commands have not been run or lab-tested. Microsoft's password page covers Outlook 2013 and earlier. For current Outlook it points only to a self-diagnostic and does not list the causes of a prompt loop. Microsoft's pages on this fault do not describe remote desktop or hosted desktop sessions, so none of this is specific to them.

Do not reset or delete a user's profile, saved credentials or data files in the hope that the prompt will stop. An Outlook data file may hold mail that exists nowhere else, and deleting it cannot be undone. Do not turn off multifactor authentication for a mailbox to stop prompts.

Sources