Merge pull request #246350 from kengaderdus/explain-idtyp

[CIAM]Update content related to idtyp optional claim

Author: prmerger-automator[bot]

articles/active-directory/external-identities/customers/how-to-web-app-node-sign-in-call-api-prepare-tenant.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: ciam
 ms.topic: how-to
-ms.date: 05/22/2023
+ms.date: 07/26/2023
 ms.custom: developer, devx-track-js
 ---
 
@@ -56,7 +56,7 @@ In this step, you create the web and the web API application registrations, and
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-app-role.md)]
 
-### Configure optional claims
+### Configure idtyp token claim
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-optional-claims-access.md)]
 

articles/active-directory/external-identities/customers/includes/register-app/add-optional-claims-access.md

@@ -3,11 +3,11 @@ author: kengaderdus
 ms.service: active-directory
 ms.subservice: ciam
 ms.topic: include
-ms.date: 03/30/2023
+ms.date: 07/26/2023
 ms.author: kengaderdus
 ---
 
-Tokens returned by Microsoft identity are kept smaller to ensure optimal performance by clients that request them. As a result, several claims are no longer present in the token by default and must be asked for specifically on a per-application basis. For this app, you include  **idtyp** optional claim. This claim is the most accurate way for an API to determine if a token is an app token or an app+user token. For example, the value of this claim is *app* when the token is an app-only token. 
+Tokens returned by Microsoft identity are kept smaller to ensure optimal performance by clients that request them. As a result, several claims are no longer present in the token by default and must be asked for specifically on a per-application basis. For this app, you include  **idtyp** optional claim to help the web API to determine if a token is an app token or an app+user token. Although a combination of **scp** and **roles** claims can used for the same purpose, the use of the **idtyp** claim is the easiest way to tell an app token and an app+user token apart. For example, the value of this claim is *app* when the token is an app-only token. 
 
 Use the following steps to configure **idtyp** optional claim: 
 

articles/active-directory/external-identities/customers/tutorial-daemon-dotnet-call-api-prepare-tenant.md

@@ -32,7 +32,7 @@ In this tutorial, you learn how to:
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-app-role.md)]
 
-## 3. Configure optional claims
+## 3. Configure idtyp token claim
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-optional-claims-access.md)]
 

articles/active-directory/external-identities/customers/tutorial-daemon-node-call-api-prepare-tenant.md

@@ -39,7 +39,7 @@ If you've already registered a client daemon application and a web API in the Mi
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-app-role.md)]
 
-## Configure optional claims
+## Configure idtyp token claim
 
 [!INCLUDE [active-directory-b2c-app-integration-add-user-flow](./includes/register-app/add-optional-claims-access.md)]