POP/IMAP client authenticate fails if X-MS-Client-Application in the AD FS claim rule is set to Microsoft.Exchange.PopImap

PROBLEM

Consider the following scenario:

  • You're using Active Directory Federation Services (AD FS) for POP and IMAP client access authentication.

  • You have a claim rule to block access if the value of the X-MS-Client-Application claim type is not Microsoft.Exchange.PopImap.

These settings had previously worked as expected. However, you noticed recently that POP and IMAP clients fail to authenticate even though the correct user name and password is used.

Additionally, if you examine the AD FS access log, you may see entries that resemble the following:

[<Date><Time>] "POST /microsoftonline/ws-username HTTP/1.1" 403 ... "Microsoft.Exchange.Imap"
[<Date><Time>] "POST /microsoftonline/ws-username HTTP/1.1" 403 ... "Microsoft.Exchange.Pop"

CAUSE

A change was made recently in the service to separate POP and IMAP authentication. Instead of Microsoft.Exchange.PopImap, the value that's sent in theĀ X-MS-Client-ApplicationĀ header is Microsoft.Exchange.Imap or Microsoft.Exchange.Pop.

SOLUTION

In the existing claim rule, change the value of X-MS-Client-Application from Microsoft.Exchange.PopImap to Microsoft.Exchange.Imap and Microsoft.Exchange.Pop.

MORE INFORMATION

For more information, see the following resources:

Still need help? Go to Microsoft Community or the Azure Active Directory Forumswebsite.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×