Azure-docs: Inconsistent Documentation - Supported NameID Formats

Created on 6 Nov 2020 · 4Comments · Source: MicrosoftDocs/azure-docs

This page indicates that "Windows domain qualified name" is a valid NameID format. However other documentation indicates that "Windows domain qualified name" is not a valid NameID format.

Indeed when we created a new Application Registration from the Azure portal and tried sending a SAML authentication request from our app with the following element...

<samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName" AllowCreate="true"/>

...we received the following error message:

Timestamp: 2020-11-05T17:38:33Z
Message: AADSTS750161: Allowed SAML authentication request's NameIDPolicy formats are:
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress,
urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified,
urn:oasis:names:tc:SAML:2.0:nameid-format:persistent,
urn:oasis:names:tc:SAML:2.0:nameid-format:transient.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d362c1b5-1460-4de9-c53d-f0ec1ef07742
Version Independent ID: 9dc0a4df-81c8-13eb-720f-f589a3712e42
Content: Customize app SAML token claims - Microsoft identity platform
Content Source: articles/active-directory/develop/active-directory-saml-claims-customization.md
Service: active-directory
Sub-service: develop
GitHub Login: @kenwith
Microsoft Alias: kenwith

active-directorsvc assigned-to-author develosubsvc doc-bug triaged

Source

mattallscripts

👍1

Most helpful comment

@mattallscripts
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

JamesTran-MSFT on 6 Nov 2020

👍2

All 4 comments

@mattallscripts
Thanks for your feedback! We will investigate and update as appropriate.

JamesTran-MSFT on 6 Nov 2020

@mattallscripts
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

JamesTran-MSFT on 6 Nov 2020

👍2

Created a PR to get this article updated and inline with the newer article. @mattallscripts thank you for the catch and taking the time to provide feedback. I know it is a lot easier to just make a mental note and move on and that it takes time to log in and open and issue and improve the docs for the community. I really appreciate it. PR fix should be live shortly.