Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/active-directory-b2c/boolean-transformations.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 01/17/2022
+ms.date: 02/16/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -20,7 +20,7 @@ This article provides examples for using the boolean claims transformations of t
 
 ## AndClaims
 
-Computes an `And` operation of two boolean input claims, and sets the output claim with result of the operation.
+Computes an `And` operation of two boolean input claims, and sets the output claim with result of the operation. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean#andclaims) of this claims transformation.
 
 | Element  | TransformationClaimType  | Data Type  | Notes |
 |-------| ------------------------ | ---------- | ----- |
@@ -54,7 +54,7 @@ The following claims transformation demonstrates how to `And` two boolean claims
 
 ## AssertBooleanClaimIsEqualToValue
 
-Checks that boolean values of two claims are equal, and throws an exception if they are not.
+Checks that boolean values of two claims are equal, and throws an exception if they aren't. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean#assertbooleanclaimisequaltovalue) of this claims transformation.
 
 | Element | TransformationClaimType  | Data Type  | Notes |
 | ---- | ------------------------ | ---------- | ----- |
@@ -63,7 +63,7 @@ Checks that boolean values of two claims are equal, and throws an exception if t
 
 The **AssertBooleanClaimIsEqualToValue** claims transformation is always executed from a [validation technical profile](validation-technical-profile.md) that is called by a [self-asserted technical profile](self-asserted-technical-profile.md). The **UserMessageIfClaimsTransformationBooleanValueIsNotEqual** self-asserted technical profile metadata controls the error message that the technical profile presents to the user. The error messages can be [localized](localization-string-ids.md#claims-transformations-error-messages).
 
-![AssertStringClaimsAreEqual execution](./media/boolean-transformations/assert-execution.png)
+![Diagram shows how to use the AssertStringClaimsAreEqual claims transformation.](./media/boolean-transformations/assert-execution.png)
 
 ### Example of AssertBooleanClaimIsEqualToValue
 
@@ -122,7 +122,7 @@ The self-asserted technical profile calls the validation `Example-AssertBoolean`
 
 ## CompareBooleanClaimToValue
 
-Checks that boolean value of a claim is equal to `true` or `false`, and return the result of the compression.
+Checks that boolean value of a claim is equal to `true` or `false`, and return the result of the compression. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean#comparebooleanclaimtovalue) of this claims transformation.
 
 | Element | TransformationClaimType  | Data Type  | Notes |
 | ---- | ------------------------ | ---------- | ----- |
@@ -157,7 +157,7 @@ The following claims transformation demonstrates how to check the value of a boo
 
 ## NotClaims
 
-Computes a `Not` operation of the boolean input claim and sets the output claim with result of the operation.
+Computes a `Not` operation of the boolean input claim and sets the output claim with result of the operation. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean#notclaims) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -186,7 +186,7 @@ The following claims transformation demonstrates how to perform logical negation
 
 ## OrClaims
 
-Computes an `Or` of two boolean claims and sets the output claim with result of the operation.
+Computes an `Or` of two boolean claims and sets the output claim with result of the operation. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean#orclaims) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -218,4 +218,4 @@ The following claims transformation demonstrates how to `Or` two boolean claims.
 
 ## Next steps
 
-- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation) on the Azure AD B2C community GitHub repo
+- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/boolean) on the Azure AD B2C community GitHub repo

articles/active-directory-b2c/claim-resolver-overview.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 1/11/2022
+ms.date: 02/16/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -47,6 +47,8 @@ The following table lists the claim resolvers with information about the languag
 | {Culture:RegionName} | The two letter ISO code for the region. | US |
 | {Culture:RFC5646} | The RFC5646 language code. | en-US |
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#culture) of the culture claim resolvers.
+
 ## Policy
 
 The following table lists the claim resolvers with information about the policy used in the authorization request:
@@ -58,6 +60,7 @@ The following table lists the claim resolvers with information about the policy
 | {Policy:TenantObjectId} | The tenant object ID of the relying party policy. | 00000000-0000-0000-0000-000000000000 |
 | {Policy:TrustFrameworkTenantId} | The tenant ID of the trust framework. | your-tenant.onmicrosoft.com |
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#policy) of the policy claim resolvers.
 
 ## Context
 
@@ -73,6 +76,8 @@ The following table lists the contextual claim resolvers of the authorization re
 | {Context:IPAddress} | The user IP address. | 11.111.111.11 |
 | {Context:KMSI} | Indicates whether [Keep me signed in](session-behavior.md?pivots=b2c-custom-policy#enable-keep-me-signed-in-kmsi) checkbox is selected. |  true |
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#context) of the context claim resolvers.
+
 ## Claims 
 
 This section describes how to get a claim value as a claim resolver.
@@ -100,6 +105,8 @@ The following table lists the claim resolvers with information about the OpenID
 | {OIDC:Scope} |The `scope`  query string parameter. | openid |
 | {OIDC:Username}| The [resource owner password credentials flow](add-ropc-policy.md) user's username.| [email protected]|
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#openid-connect-relying-party-application) of the OpenID Connect claim resolvers.
+
 ## OAuth2 key-value parameters
 
 Any parameter name included as part of an OIDC or OAuth2 request can be mapped to a claim in the user journey. For example, the request from the application might include a query string parameter with a name of `app_session`, `loyalty_number`, or any custom query string.
@@ -127,6 +134,8 @@ The following table lists the claim resolvers  with information about the SAML a
 | {SAML:Subject} | The `Subject` from the NameId element of the SAML AuthN request.| 
 | {SAML:Binding} | The `ProtocolBinding` attribute value, from the `AuthnRequest` element of the SAML request. | urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST |
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#saml-service-provider) of the SAML claim resolvers.
+
 ## OAuth2 identity provider
 
 The following table lists the [OAuth2 identity provider](oauth2-technical-profile.md) claim resolvers:
@@ -157,7 +166,6 @@ To use the OAuth2 identity provider claim resolvers, set the output claim's `Par
 </ClaimsProvider>
 ```
 
-
 ## Using claim resolvers
 
 You can use claims resolvers with the following elements:
@@ -287,3 +295,7 @@ In a [Relying party](relyingparty.md) policy technical profile, you may want to
     </TechnicalProfile>
   </RelyingParty>
 ```
+
+## Next steps
+
+- Find more [claims resolvers samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver) on the Azure AD B2C community GitHub repo

articles/active-directory-b2c/claimsschema.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 03/05/2020
+ms.date: 02/16/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -238,6 +238,8 @@ The Identity Experience Framework renders the email address claim with email for
 
 Azure AD B2C supports a variety of user input types, such as a textbox, password, and dropdown list that can be used when manually entering claim data for the claim type. You must specify the **UserInputType** when you collect information from the user by using a [self-asserted technical profile](self-asserted-technical-profile.md) and [display controls](display-controls.md).
 
+Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims#user-input-types) of the user input type.
+
 The **UserInputType** element available user input types:
 
 | UserInputType | Supported ClaimType | Description |

articles/active-directory-b2c/date-transformations.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 1/17/2022
+ms.date: 02/16/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -20,7 +20,7 @@ This article provides examples for using the date claims transformations of the
 
 ## AssertDateTimeIsGreaterThan
 
-Asserts that one date is later than a second date. Determines whether the `rightOperand` is greater than the `leftOperand`. If yes, throws an exception.
+Asserts that one date is later than a second date. Determines whether the `rightOperand` is greater than the `leftOperand`. If yes, throws an exception. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#assertdatetimeisgreaterthan) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -32,7 +32,7 @@ Asserts that one date is later than a second date. Determines whether the `right
 
 The **AssertDateTimeIsGreaterThan** claims transformation is always executed from a [validation technical profile](validation-technical-profile.md) that is called by a [self-asserted technical profile](self-asserted-technical-profile.md). The **DateTimeGreaterThan** self-asserted technical profile metadata controls the error message that the technical profile presents to the user. The error messages can be [localized](localization-string-ids.md#claims-transformations-error-messages).
 
-![AssertStringClaimsAreEqual execution](./media/date-transformations/assert-execution.png)
+![Diagrams shows how to use the AssertStringClaimsAreEqual claims transformation.](./media/date-transformations/assert-execution.png)
 
 ### Example of AssertDateTimeIsGreaterThan
 
@@ -102,7 +102,7 @@ The self-asserted technical profile calls the validation `Example-AssertDates` t
 
 ## ConvertDateTimeToDateClaim
 
-Converts a `DateTime` claim type to a `Date` claim type. The claims transformation removes the time format from the date.
+Converts a `DateTime` claim type to a `Date` claim type. The claims transformation removes the time format from the date. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#convertdatetimetodateclaim) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -131,7 +131,7 @@ The following example demonstrates the conversion of the claim `systemDateTime`
 
 ## ConvertDateToDateTimeClaim
 
-Converts a `Date` claim type to a `DateTime` claim type. The claims transformation converts the time format and adds 12:00:00 AM to the date.
+Converts a `Date` claim type to a `DateTime` claim type. The claims transformation converts the time format and adds 12:00:00 AM to the date. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#convertdatetodatetimeclaim) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -160,7 +160,7 @@ The following example demonstrates the conversion of the claim `dateOfBirth` (da
 
 ## DateTimeComparison
 
-Compares two dates and determines whether the first date is later, earlier, or equal to another. The result is a new Boolean claim with a value of `true` or `false`.
+Compares two dates and determines whether the first date is later, earlier, or equal to another. The result is a new Boolean claim with a value of `true` or `false`. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#datetimecomparison) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -197,16 +197,16 @@ Use this claims transformation to determine if first date plus the `timeSpanInSe
   - **operator**: later than
   - **timeSpanInSeconds**: 7776000 (90 days)
 - Output claims:
-    - **result**: true
+  - **result**: true
 
 ## IsTermsOfUseConsentRequired
 
-Determine whether a `dateTime` claim type is earlier or greater than a specific date. The result is a new Boolean claim with a value of `true` or `false`.
+Determine whether a `dateTime` claim type is earlier or greater than a specific date. The result is a new Boolean claim with a value of `true` or `false`. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#istermsofuseconsentrequired) of this claims transformation.
 
 | Item | TransformationClaimType | Data type | Notes |
 | ---- | ----------------------- | --------- | ----- |
-| InputClaim | termsOfUseConsentDateTime | dateTime | The `dateTime` claim type to check whether it is earlier or later than the `termsOfUseTextUpdateDateTime` input parameter. Undefined value returns `true` result. |
-| InputParameter | termsOfUseTextUpdateDateTime | dateTime | The `dateTime` claim type to check whether it is earlier or later than the `termsOfUseConsentDateTime` input claim. The time part of the date is optional. |
+| InputClaim | termsOfUseConsentDateTime | dateTime | The `dateTime` claim type to check whether it's earlier or later than the `termsOfUseTextUpdateDateTime` input parameter. Undefined value returns `true` result. |
+| InputParameter | termsOfUseTextUpdateDateTime | dateTime | The `dateTime` claim type to check whether it's earlier or later than the `termsOfUseConsentDateTime` input claim. The time part of the date is optional. |
 | OutputClaim | result | boolean | The claim type that's produced after this claims transformation has been invoked. |
 
 Use this claims transformation to determine whether a `dateTime` claim type is earlier or greater than a specific date. For example, check whether a user has consented to the latest version of your terms of use (TOU) or terms of service. To check the last time a user consented, store the last time the user accepted the TOU in an [extension attribute](user-profile-attributes.md#extension-attributes). When your TOU wording changes, update the `termsOfUseTextUpdateDateTime` input parameter with the time of the change. Then, call this claims transformation to compare the dates. If the claims transformation returns `true`, the `termsOfUseConsentDateTime` value is earlier than the `termsOfUseTextUpdateDateTime` value, and you can ask the user to accept the updated TOU.
@@ -228,15 +228,15 @@ Use this claims transformation to determine whether a `dateTime` claim type is e
 ### IsTermsOfUseConsentRequired example
 
 - Input claims:
-    - **termsOfUseConsentDateTime**: 2020-03-09T09:15:00 
-- Input parameters: 
-    - **termsOfUseTextUpdateDateTime**: 2021-11-15 
-- Output claims: 
-    - **result**: true 
+  - **termsOfUseConsentDateTime**: 2020-03-09T09:15:00
+- Input parameters:
+  - **termsOfUseTextUpdateDateTime**: 2021-11-15
+- Output claims:
+  - **result**: true
 
 ## GetCurrentDateTime
 
-Get the current UTC date and time and add the value to a claim type.
+Get the current UTC date and time and add the value to a claim type. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date#getcurrentdatetime) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -259,4 +259,4 @@ The following example shows how to get the current data and time:
 
 ## Next steps
 
-- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation) on the Azure AD B2C community GitHub repo
+- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/date) on the Azure AD B2C community GitHub repo

articles/active-directory-b2c/general-transformations.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 01/17/2022
+ms.date: 02/16/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -20,7 +20,7 @@ This article provides examples for using general claims transformations of the A
 
 ## CopyClaim
 
-Copy value of a claim to another. Both claims must be from the same type.
+Copy value of a claim to another. Both claims must be from the same type. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/general#copyclaim) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -49,7 +49,7 @@ Use this claims transformation to copy a value from a string or numeric claim, t
 
 ## DoesClaimExist
 
-Checks if the input claim exists, and sets output claim to `true` or `false` accordingly.
+Checks if the input claim exists, and sets output claim to `true` or `false` accordingly. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/general#doesclaimexist) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -78,7 +78,7 @@ Use this claims transformation to check if a claim exists or contains any value.
 
 ## Hash
 
-Hash the provided plain text using the salt and a secret. The hashing algorithm used is SHA-256.
+Hash the provided plain text using the salt and a secret. The hashing algorithm used is SHA-256. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/general#hash) of this claims transformation.
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
@@ -115,4 +115,4 @@ The following example demonstrates how to hash an email address. The claims tran
 
 ## Next steps
 
-- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation) on the Azure AD B2C community GitHub repo
+- Find more [claims transformation samples](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/general) on the Azure AD B2C community GitHub repo