# No account settings were returned from the Autodiscover response – Microsoft Exchange 2016 | Evotec Blog

blog

# No account settings were returned from the Autodiscover response – Microsoft Exchange 2016

16 Aug 2018en

![No account settings were returned from the Autodiscover response – Microsoft Exchange 2016](/wp-content/uploads/2018/08/img_5b75c854c651c.png)

Path

1. [Home](/)
2. [Blog](/blog/)
3. No account settings were returned from the Autodiscover response – Microsoft Exchange 2016

Explore this stream

[Back to Blog](/blog/)[All categories](/categories/)[All tags](/tags/)

**Categories**

[Exchange](/blog/?category=Exchange)[Office 365](/blog/?category=Office 365)[PowerShell](/blog/?category=PowerShell)

**Tags**

[exchange](/blog/?tag=exchange)[exchange 2013](/blog/?tag=exchange 2013)[exchange 2016](/blog/?tag=exchange 2016)[exchange on-premise](/blog/?tag=exchange on-premise)[exchange online](/blog/?tag=exchange online)[office 365](/blog/?tag=office 365)

**Browse**

[All categories](/categories/)[All tags](/tags/)

[View images (4)](#pf-content-image-1-0)

One user reported that after a name change she could no longer sign in to **Outlook**, even though **OWA** still worked fine. That detail matters because it points away from a total Exchange outage and toward a client-access or mailbox-level issue.

## First clue

Quick testing with the **[Microsoft Remote Connectivity Analyzer](https://testconnectivity.microsoft.com/)** confirmed there was a real Autodiscover problem for that user. Because she was the only person affected, it did not look like a global configuration issue.

[!\[Microsoft Remote Connectivity Analyzer validating Outlook autodiscover settings for the affected mailbox\](/wp-content/uploads/2018/08/img_5b75c854c651c.png)](/wp-content/uploads/2018/08/img_5b75c854c651c.png)

> Autodiscover settings for Outlook connectivity are being validated. The Microsoft Connectivity Analyzer wasn't able to validate Outlook Autodiscover settings. Additional Details No account settings were returned from the Autodiscover response. Elapsed Time: 0 ms.

[!\[Connectivity test result showing that no account settings were returned from the autodiscover response\](/wp-content/uploads/2018/08/img_5b75c8f68ce02.png)](/wp-content/uploads/2018/08/img_5b75c8f68ce02.png)

## What fixed it

Additional verification against the **Autodiscover** URL confirmed the symptom, but the actual cause showed up when checking the user's **Mailbox Features**.

[!\[Exchange mailbox features screen showing MAPI disabled for the affected user mailbox\](/wp-content/uploads/2018/08/img_5b75c9a101c31.png)](/wp-content/uploads/2018/08/img_5b75c9a101c31.png)

The problem was that **MAPI** had been disabled on the mailbox. Once it was enabled again, Outlook started working for the user.

I also wanted to make sure this was not going to surprise us again elsewhere, so I checked the rest of the environment with:

```
Get-CASMailbox -ResultSize Unlimited | Where { $_.MapiEnabled -eq $false }
```

[!\[PowerShell output checking Exchange mailboxes for users with MAPI disabled\](/wp-content/uploads/2018/08/img_5b75ca3a16460.png)](/wp-content/uploads/2018/08/img_5b75ca3a16460.png)

## Practical takeaway

If only one user is affected and OWA still works, look at mailbox-level client protocol settings before you spend hours on namespace or certificate troubleshooting.

## Current note

Microsoft still documents **MAPI** as a mailbox feature that can be enabled or disabled at the mailbox level in Exchange Server. So the lesson from this post still holds: a mailbox with `MAPIEnabled` set to `$false` can create very Outlook-specific failures that look bigger than they really are.

## Related Projects

Projects that align with this post's tags, categories, and content.

[All projects](/projects/)

Matching projects...

[Back to Blog](/blog)

[Newer post: PowerShellGallery – You are installing modules from an untrusted repository](/blog/powershellgallery-you-are-installing-modules-from-an-untrusted-repository/)[Older post: Microsoft Exchange Approval Assistant – Your message couldn’t be delivered because delivery to this address is restricted to authenticated senders](/blog/microsoft-exchange-approval-assistant-your-message-couldnt-be-delivered-because-delivery-to-this-address-is-restricted-to-authenticated-senders/)

## Related posts

- [Creating Visual Indicators for spoofed / external emails with PowerShell](/blog/creating-visual-indicators-for-spoofed-external-emails-with-powershell/)
- [Microsoft Exchange Approval Assistant – Your message couldn’t be delivered because delivery to this address is restricted to authenticated senders](/blog/microsoft-exchange-approval-assistant-your-message-couldnt-be-delivered-because-delivery-to-this-address-is-restricted-to-authenticated-senders/)
- [Office 365 – Adding email addresses based on Email Address Policy](/blog/office-365-adding-email-addresses-based-email-address-policy/)