Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ez-backup

Author: halkazwini

articles/active-directory-b2c/media/partner-nok-nok/nok-nok-architecture-diagram.png

@@ -1,7 +1,7 @@
 ---
-title: Tutorial to configure Nok Nok Passport with Azure Active Directory B2C for passwordless FIDO2 authentication
+title: Tutorial to configure Nok Nok S3 Authentication Suite with Azure Active Directory B2C for FIDO passkey authentication
 titleSuffix: Azure AD B2C
-description: Configure Nok Nok Passport with Azure AD B2C to enable passwordless FIDO2 authentication
+description: Configure Nok Nok S3 Authentication Suite with Azure AD B2C to enable FIDO passkey authentication
 author: gargi-sinha
 manager: martinco
 ms.reviewer: kengaderdus
@@ -12,54 +12,56 @@ ms.date: 06/21/2024
 ms.author: gasinh
 ms.subservice: b2c
 
-# Customer intent: I'm a developer integrating Azure Active Directory B2C with a third-party authentication provider. I want to learn how to configure Nok Nok Passport as an identity provider (IdP) in Azure AD B2C. My goal is to enable passwordless FIDO authentication for my users.
+# Customer intent: I'm a developer integrating Azure AD B2C with a third-party authentication provider. I want to learn how to configure Nok Nok S3 Authentication Suite as an identity provider (IdP) in Azure AD B2C. My goal is to implement FIDO Passkey authentication for my users.
 ---
-# Tutorial: Configure Nok Nok Passport with Azure Active Directory B2C for passwordless FIDO2 authentication
+# Tutorial: Configure Nok Nok S3 Authentication Suite with Azure AD B2C for FIDO Passkey Authentication
 
-Learn to integrate the Nok Nok S3 Authentication Suite into your Azure Active Directory B2C (Azure AD B2C) tenant. The Nok Nok solutions enable FIDO certified multi-factor authentication such as FIDO UAF, FIDO U2F, WebAuthn, and FIDO2 for mobile and web applications. Nok Nok solutions improve security posture while balancing user the experience.
+Learn to integrate the Nok Nok S3 Authentication Suite into your Azure Active Directory (AD) B2C tenant. The Nok Nok solution enables FIDO-certified multifactor authentication such as FIDO UAF, FIDO U2F, WebAuthn, and FIDO2 for mobile and web applications. The Nok Nok solution strengthens your security while maintaining an optimal user experience.
 
-Go to noknok.com to learn more: [Nok Nok Labs, Inc.](https://noknok.com/)
+Learn more at [Nok Nok](https://noknok.com/)
 
 ## Prerequisites
 
 To get started, you need:
 
-* An Azure subscription
-  * If you don't have one, get a [Azure free account](https://azure.microsoft.com/free/)
-* An Azure AD B2C tenant linked to the Azure subscription
-  * [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md) 
-* Go to [noknok.com](https://noknok.com/).
-  * On the top menu, select **Demo**.
+* An Azure subscription. If you don't have one, get an [Azure free account](https://azure.microsoft.com/free/).
+* An Azure AD B2C tenant linked to the Azure subscription [Tutorial: Create an Azure AD B2C tenant](tutorial-create-tenant.md).
+* A Nok Nok Cloud evaluation tenant for FIDO registration and authentication.
 
 ## Scenario description
 
-To enable passwordless FIDO authentication for your users, enable Nok Nok as an identity provider (IdP) in your Azure AD B2C tenant. The Nok Nok solution integration includes the following components:
+To enable Passkey authentication for your users, enable Nok Nok as an identity provider (IdP) in your Azure AD B2C tenant. The Nok Nok integration includes the following components:
 
-* **Azure AD B2C** – authorization server that verifies user credentials
-* **Web and mobile applications** – mobile or web apps to protect with Nok Nok solutions and Azure AD B2C
-* **Nok Nok app SDK or Passport app** – authenticate Azure AD B2C enabled applications. 
-  * Go to the Apple App Store for [Nok Nok Passport](https://apps.apple.com/us/app/nok-nok-passport/id1050437340)
-  * Or, Google Play [Nok Nok Passport](https://play.google.com/store/apps/details?id=com.noknok.android.passport2&hl=en&gl=US)
+* **Azure AD B2C** – authorization server that verifies user credentials.
+* **Web and mobile applications** – mobile or web apps to protect with Nok Nok solutions and Azure AD B2C.
+* **Nok Nok Tutorial Web App** – application to register the passkey on your device.
+* **Nok Nok Sign in App** – application for authenticating Azure AD B2C applications using passkey.
 
-The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2C by using OpenID Connect (OIDC) for passwordless authentication.
 
-   ![Diagram of Nok Nok as IdP for Azure AD B2C using OpenID Connect (OIDC) for passwordless authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
+The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2C by using OpenID Connect (OIDC) for Passkey authentication.
+
+![Diagram of Nok Nok as IdP for Azure AD B2C using OpenID Connect (OIDC) for Passkey authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
+
+### Scenario 1: Passkey Registration
+1. The user navigates to the Nok Nok Tutorial Web App using the link provided by Nok Nok.
+2. The user enters their Azure AD B2C username and default tutorial app password.
+3. The user receives a prompt to register the passkey.
+4. The Nok Nok server validates the passkey credential and confirms successful passkey registration to the user.
+5. The passkey on the user's device is ready for authentication.
+
+### Scenario 2: Passkey Authentication
+1. The user selects the Sign in with Nok Nok Cloud button on the Azure AD B2C Sign in page.
+2. Azure AD B2C redirects the user to the Nok Nok Signin App.
+3. User authenticates with their passkey.
+4. The Nok Nok server validates the passkey assertion and sends an OIDC authentication response to Azure AD B2C.
+5. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
 
-1. At the sign-in page, select sign-in or sign-up and enters the username.
-2. Azure AD B2C redirects to the Nok Nok OIDC authentication provider.
-3. For mobile authentications, a QR code appears or push notification goes to the user device. For desktop sign-in, the user is redirected to the web app sign-in page for passwordless authentication.
-4. Scan the QR code with the Nok Nok app SDK or Passport app. Or, username is the sign-in page input.
-5. A prompt appears for authentication. Perform passwordless authentication: biometrics, device PIN, or any roaming authenticator.
-6. The authentication prompt appears on the web application.
-7. Perform passwordless authentication: biometrics, device PIN, or any roaming authenticator. 
-8. The Nok Nok server validates FIDO assertion and sends OIDC authentication response to Azure AD B2C.
-9. The user is granted or denied access.
 
 ## Get started with Nok Nok
 
-1. Go to noknok.com [Contact](https://noknok.com/contact/). 
-2. Fill out the form for a Nok Nok tenant. 
-3. An email arrives with tenant access information and links to documentation. 
+1. [Contact](https://noknok.com/contact/) Nok Nok.
+2. Fill out the form for a Nok Nok tenant.
+3. An email arrives with tenant access information and links to documentation.
 4. Use the Nok Nok integration documentation to complete the tenant OIDC configuration.
 
 ## Integrate with Azure AD B2C
@@ -70,8 +72,8 @@ Use the following instructions to add and configure an IdP, and then configure a
 
 For the following instructions, use the directory with the Azure AD B2C tenant. To add a new IdP:
 
-1. Sign in to the [Azure portal](https://portal.azure.com/#home) as at least B2C IEF Policy Administrator of the Azure AD B2C tenant.
-2. In the portal toolbar, select the **Directories + subscriptions**.
+1. Sign in to the [Azure portal](https://portal.azure.com/#home) as at least as the B2C IEF Policy Administrator of the Azure AD B2C tenant.
+2. In the portal toolbar, select **Directories + subscriptions**.
 3. On **Portal settings, Directories + subscriptions**, in the **Directory name** list, locate the Azure AD B2C directory.
 4. Select **Switch**.
 5. In the top-left corner of the Azure portal, select **All services**.
@@ -80,24 +82,21 @@ For the following instructions, use the directory with the Azure AD B2C tenant.
 8. Select **Identity providers**.
 9. Select **Add**.
 
-### Configure an Identity provider 
+### Configure an Identity provider
 
 To configure an IdP:
 
 1. Select **Identity provider type** > **OpenID Connect (Preview)**.
 2. For **Name**, enter the Nok Nok Authentication Provider, or another name.
-3. For **Metadata URL**, enter the hosted Nok Nok Authentication app URI, followed by the path such as `https://demo.noknok.com/mytenant/oidc/.well-known/openid-configuration`.
+3. For **Metadata URL**, enter the following URL after replacing the placeholder with the tenant ID provided by Nok Nok: `https://cloud.noknok.com/<tenant_id>/webapps/nnlfed/realms/<tenant_id>/.well-known/openid-configuration`.
 4. For **Client Secret**, use the Client Secret from Nok Nok.
 5. For **Client ID**, use the Client ID provided by Nok Nok.
-6. For **Scope**, use **OpenID profile email**.
+6. For **Scope**, use **openid**.
 7. For **Response type**, use **code**.
 8. For **Response mode**, use **form_post**.
-9. Select **OK**.
-10. Select **Map this identity provider’s claims**.
-11. For **UserID**, select **From subscription**.
-12. For **Display name**, select **From subscription**.
-13. For **Response mode**, select **From subscription**. 
-14. Select **Save**.
+9. For **User ID**, use **sub**.
+10. For **Display name**, use **sub**.
+11. Select **Save**.
 
 ### Create a user flow policy
 
@@ -106,31 +105,24 @@ For the following instructions, Nok Nok is a new OIDC IdP in the B2C identity pr
 1. In your Azure AD B2C tenant, under **Policies**, select **User flows**.
 2. Select **New**.
 3. Select **Sign up and sign in**.
-4. Select a **version**.
+4. Select a **Version**.
 5. Select **Create**.
 6. Enter a policy **Name**.
 7. In **Identity providers**, select the created Nok Nok IdP.
-8. You can add an email address. Azure won't redirect sign-in to Nok Nok; a screen appears with user options.
+8. Check **Email signup** under **Local accounts** to display an intermediate Azure AD B2C signin/signup page with a button that redirects the user to the Nok Nok Signin App.
 9. Leave the **Multi-factor Authentication** field.
-10. Select **Enforce conditional access policies**.
-11. Under **User attributes and token claims**, in the Collect attribute option, select **Email Address**. 
-12. Add user attributes for Microsoft Entra ID to collect, with claims that Azure AD B2C returns to the client application.
-13. Select **Create**.
-14. Select the new **User flow**.
-15. On the left panel, select **Application Claims**. 
-16. Under options, select the **email** checkbox
-17. Select **Save**.
+10. Click **Create** to save.
 
 ## Test the user flow
 
-1. Open the Azure AD B2C tenant. Under **Policies** select **Identity Experience Framework**.
+1. Open the Azure AD B2C tenant. Under **Policies**, select **Identity Experience Framework**.
 2. Select the created **SignUpSignIn**.
 3. Select **Run user flow**.
 4. For **Application**, select the registered app. The example is JWT.
-5. For **Reply URL**, select the redirect URL.
+5. For **Reply URL**, select the redirect URL of the application that you previously selected at the previous step.
 6. Select **Run user flow**.
-7. Perform a sign-up flow and create an account.
-8. After the user attribute is created, Nok Nok is called.
+7. Perform signin using the Azure AD B2C username and the passkey that you previously registered for the same user.
+8. Verify that you received the token after authentication.
 
 If the flow is incomplete, confirm the user is or isn't saved in the directory.
 

articles/active-directory-b2c/partner-nok-nok.md

@@ -293,14 +293,14 @@ If you are configuring the logger for a workspace, create a `Microsoft.ApiManage
 Use the following steps to enable Application Insights logging for an API. You can also enable Application Insights logging for all APIs.
 
 1. Navigate to your **Azure API Management service instance** in the **Azure portal**.
-1. Select **APIs** from the menu on the left.
-1. Click on your API, in this case **Demo Conference API**. If configured, select a version.
+1. Select **APIs** > **APIs** from the menu on the left.
+1. Select an API, such as **Swagger Petstore**. If configured, select a version.
 
    > [!TIP]
    > To enable logging for all APIs, select **All APIs**.
 1. Go to the **Settings** tab from the top bar.
 1. Scroll down to the **Diagnostics Logs** section.  
-    :::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-api-1.png" alt-text="App Insights logger":::
+    :::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-api-1.png" alt-text="Screenshot of Diagnostic Logs configuration in the portal.":::
 1. Check the **Enable** box.
 1. Select your attached logger in the **Destination** dropdown.
 1. Input **100** as **Sampling (%)** and select the **Always log errors** checkbox.

articles/api-management/api-management-howto-app-insights.md

@@ -1,11 +1,9 @@
 ---
-title: Add caching to improve performance in Azure API Management | Microsoft Docs
+title: Add caching to improve performance in Azure API Management
 description: Learn how to improve the latency, bandwidth consumption, and web service load for API Management service calls.
 author: dlepow
-manager: erikre
-ms.assetid: 740f6a27-8323-474d-ade2-828ae0c75e7a
 ms.service: azure-api-management
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 03/20/2024
 ms.author: danlep
 ---
@@ -42,52 +40,53 @@ To complete this tutorial:
 + [Create an Azure API Management instance](get-started-create-service-instance.md)
 + [Import and publish an API](import-and-publish.md)
 
-## <a name="caching-policies"> </a>Add the caching policies
+## Add the caching policies
 
-With caching policies shown in this example, the first request to the **GetSpeakers** operation returns a response from the backend service. This response is cached, keyed by the specified headers and query string parameters. Subsequent calls to the operation, with matching parameters, will have the cached response returned, until the cache duration interval has expired.
+With caching policies shown in this example, the first request to a test operation returns a response from the backend service. This response is cached, keyed by the specified headers and query string parameters. Subsequent calls to the operation, with matching parameters, will have the cached response returned, until the cache duration interval has expired.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Browse to your APIM instance.
-3. Select the **API** tab.
-4. Click **Demo Conference API** from your API list.
-5. Select **GetSpeakers**.
-6. On the top of the screen, select **Design** tab.
-7. In the **Inbound processing** section, click the **</>** icon.
+1. Browse to your API Management instance.
+1. Select **APIs** > **APIs** from the menu on the left.
+1. Select an API for which you want to configure caching.
+1. On the top of the screen, select **Design** tab.
+1. In the **Inbound processing** section, select the **</>** icon.
+    :::image type="content" source="media/api-management-howto-cache/code-editor.png" alt-text="Screenshot of the API Management policy editor in the portal.":::
 
-    ![code editor](media/api-management-howto-cache/code-editor.png)
+8. In the `inbound` element, add the following policy:
 
-8. In the **inbound** element, add the following policy:
-
-   ```
+   ```xml
    <cache-lookup vary-by-developer="false" vary-by-developer-groups="false">
        <vary-by-header>Accept</vary-by-header>
        <vary-by-header>Accept-Charset</vary-by-header>
        <vary-by-header>Authorization</vary-by-header>
    </cache-lookup>
    ```
 
-9. In the **outbound** element, add the following policy:
+9. In the `outbound` element, add the following policy:
 
-   ```
+   ```xml
    <cache-store duration="20" />
    ```
 
-    **Duration** specifies the expiration interval of the cached responses. In this example, the interval is **20** seconds.
+    In this policy, **duration** specifies the expiration interval of the cached responses. In this example, the interval is **20** seconds.
 
 > [!TIP]
 > If you are using an external cache, as described in [Use an external Azure Cache for Redis in Azure API Management](api-management-howto-cache-external.md), you may want to specify the `caching-type` attribute of the caching policies. See [API Management caching policies](api-management-policies.md#caching) for more details.
 
-## <a name="test-operation"> </a>Call an operation and test the caching
-To see the caching in action, call the operation from the developer portal.
+## Call an operation and test the caching
+To see the caching in action, call an operation from the portal.
 
-1. In the Azure portal, browse to your APIM instance.
-2. Select the **APIs** tab.
-3. Select the API to which you added caching policies.
-4. Select the **GetSpeakers** operation.
-5. Click the **Test** tab in the top right menu.
-6. Press **Send**.
+1. In the Azure portal, browse to your API Management instance.
+1. Select **APIs** > **APIs** from the menu on the left.
+1. Select the API to which you added caching policies.
+1. Select an operation to test.
+1. Select the **Test** tab in the top right menu.
+1. Select **Trace** two or three times in quick succession.
+1. Under **HTTP response**, select the **Trace** tab.
+1. Jump to the **Inbound** section and scroll to the `cache-lookup` policy. You should see a message similar to the one in the following screenshot, indicating a cache hit:
+    :::image type="content" source="media/api-management-howto-cache/test-api-cache-lookup.png" alt-text="Screenshot of cache-lookup when testing an API in the portal.":::
 
-## <a name="next-steps"> </a>Next steps
+## Related content
 * For more information about caching policies, see [Caching policies][Caching policies] in the [API Management policy reference][API Management policy reference].
 * For information on caching items by key using policy expressions, see [Custom caching in Azure API Management](api-management-sample-cache-by-key.md).
 * For more information about using external Azure Cache for Redis, see [Use an external Azure Cache for Redis in Azure API Management](api-management-howto-cache-external.md).
@@ -116,7 +115,4 @@ To see the caching in action, call the operation from the developer portal.
 
 [Create an API Management service instance]: get-started-create-service-instance.md
 
-[Configure an operation for caching]: #configure-caching
-[Review the caching policies]: #caching-policies
-[Call an operation and test the caching]: #test-operation
-[Next steps]: #next-steps
+