Merge pull request #219518 from csmulligan/csm-exid-claims-mapping

[EXID] Content freshness update for claims-mapping (ADO-2074845)

Author: BCS2022

articles/active-directory/external-identities/claims-mapping.md

@@ -6,29 +6,29 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: conceptual
-ms.date: 04/06/2018
+ms.date: 11/24/2022
 
 ms.author: mimart
 author: msmimart
 manager: celestedg
 
 
-ms.collection: M365-identity-device-management
+ms.collection: engagement-fy23, M365-identity-device-management
 ---
 
 # B2B collaboration user claims mapping in Azure Active Directory
 
-Azure Active Directory (Azure AD) supports customizing the claims that are issued in the SAML token for B2B collaboration users. When a user authenticates to the application, Azure AD issues a SAML token to the app that contains information (or claims) about the user that uniquely identifies them. By default, this includes the user's user name, email address, first name, and last name.
+Azure Active Directory (Azure AD) supports customizing the claims that are issued in the SAML token for [B2B collaboration](what-is-b2b.md) users. When a user authenticates to the application, Azure AD issues a SAML token to the app that contains information (or claims) about the user that uniquely identifies them. By default, this claim includes the user's user name, email address, first name, and last name.
 
 In the [Azure portal](https://portal.azure.com), you can view or edit the claims that are sent in the SAML token to the application. To access the settings, select **Azure Active Directory** > **Enterprise applications** > the application that's configured for single sign-on > **Single sign-on**. See the SAML token settings in the **User Attributes** section.
 
-![Shows the SAML token attributes in the UI](media/claims-mapping/view-claims-in-saml-token.png)
+:::image type="content" source="media/claims-mapping/view-claims-in-saml-token-attributes.png" alt-text="Screenshot of the SAML token attributes in the UI.":::
 
 There are two possible reasons why you might need to edit the claims that are issued in the SAML token:
 
 1. The application requires a different set of claim URIs or claim values.
 
-2. The application requires the NameIdentifier claim to be something other than the user principal name (UPN) that's stored in Azure AD.
+2. The application requires the NameIdentifier claim to be something other than the user principal name [(UPN)](../hybrid/plan-connect-userprincipalname.md#what-is-userprincipalname) that's stored in Azure AD.
 
 For information about how to add and edit claims, see [Customizing claims issued in the SAML token for enterprise applications in Azure Active Directory](../develop/active-directory-saml-claims-customization.md).