Merge pull request #251193 from MicrosoftDocs/main

9/12/2023 PM Publish

Author: Taojunshen

articles/active-directory-b2c/custom-domain.md

@@ -67,7 +67,7 @@ Every new Azure AD B2C tenant comes with an initial domain name, <domainname&
 
 Follow these steps to add a custom domain to your Azure AD B2C tenant:
 
-1. [Add your custom domain name to Azure AD](../active-directory/fundamentals/add-custom-domain.md#add-your-custom-domain-name-to-azure-ad).
+1. [Add your custom domain name to Azure AD](../active-directory/fundamentals/add-custom-domain.md#add-your-custom-domain-name).
 
     > [!IMPORTANT]
     > For these steps, be sure to sign in to your **Azure AD B2C** tenant and select the **Azure Active Directory** service.

articles/active-directory-b2c/partner-akamai-secure-hybrid-access.md

@@ -40,7 +40,7 @@ To get started, you'll need:
 
 - An application that uses headers for authentication. In this sample, we'll use an application that displays headers [docker header-demo-app](https://hub.docker.com/r/mistermik/header-demo-app).
 
-- **OR** an OpenID Connect (OIDC) application. In this sample, we'll use an [ASP.NET MVC web app](../active-directory/develop/tutorial-v2-asp-webapp.md) that signs in users by using the Open Web Interface for .NET (OWIN) middleware and the Microsoft identity platform.
+- **OR** an OpenID Connect (OIDC) application. In this sample, we'll use an [ASP.NET MVC web app](../active-directory/develop/web-app-tutorial-01-register-application.md) that signs in users by using the Open Web Interface for .NET (OWIN) middleware and the Microsoft identity platform.
 
 ## Scenario description
 
@@ -398,7 +398,7 @@ Once the Application is deployed in a private environment and a connector is cap
 
 #### Option 2: OpenID Connect
 
-In this sample, we'll use a [ASP.NET MVC web app](../active-directory/develop/tutorial-v2-asp-webapp.md) that signs in users by using the Open Web Interface for .NET (OWIN) middleware and the Microsoft identity platform.
+In this sample, we'll use a [ASP.NET MVC web app](../active-directory/develop/web-app-tutorial-01-register-application.md) that signs in users by using the Open Web Interface for .NET (OWIN) middleware and the Microsoft identity platform.
 
 1. Configure the OIDC to SAML bridging in the **AZURE AD B2C SAML IdP** created with the previous steps.
 
@@ -422,7 +422,7 @@ In this sample, we'll use a [ASP.NET MVC web app](../active-directory/develop/tu
 
    [ ![Screenshot shows the akamai oidc app claim settings.](./media/partner-akamai-secure-hybrid-access/akamai-oidc-claims-settings.png)](./media/partner-akamai-secure-hybrid-access/akamai-oidc-claims-settings.png#lightbox)
 
-7. Replace startup class with the following code in the [ASP.NET MVC web app](../active-directory/develop/tutorial-v2-asp-webapp.md).
+7. Replace startup class with the following code in the [ASP.NET MVC web app](../active-directory/develop/web-app-tutorial-01-register-application.md).
 
    These few changes configure the Authorization code flow grant, the authorization code will be redeemed for tokens at the token endpoint for the application, and it introduces the Metadata Address to set the discovery endpoint for obtaining metadata from Akamai.
 

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

@@ -79,7 +79,7 @@ To learn more, go to techdocs.akamai.com for [What is a Property?](https://techd
 4. For **Property hostnames**, add a property hostname, your custom domain. For example, `login.domain.com`. 
 
   > [!IMPORTANT]
-  > Create or modify certificates with correct custom domain name settings. </br> Go to techdocs.akamai.com for [Configure HTTPS hostnames](https://learn.akamai.com/en-us/webhelp/property-manager/https-delivery-with-property-manager/GUID-9EE0EB6A-E62B-4F5F-9340-60CBD093A429.html). 
+  > Create or modify certificates with correct custom domain name settings. </br> Go to techdocs.akamai.com for [Configure HTTPS hostnames](https://techdocs.akamai.com/property-mgr/docs/serve-content-over-https). 
 
 #### Origin server property configuration settings
 
@@ -115,4 +115,3 @@ To ensure traffic to Azure AD B2C goes through the custom domain:
 
 * [Enable custom domains for Azure Active Directory B2C](./custom-domain.md?pivots=b2c-user-flow)
 * [Tutorial: Create user flows and custom policies in Azure AD B2C](./tutorial-create-user-flows.md?pivots=b2c-custom-policy&tabs=applications)
-

articles/active-directory-b2c/partner-arkose-labs.md

@@ -26,7 +26,7 @@ To get started, you'll need:
   - If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/)
 - [An Azure AD B2C tenant](tutorial-create-tenant.md) linked to your Azure subscription
 - An Arkose Labs account
-  - Go to arkoselabs.com to [request a demo](https://www.arkoselabs.com/book-a-demo/)
+  - Go to arkoselabs.com to [request a demo](https://www.arkoselabs.com/bot-management-demo/)
 
 ## Scenario description
 
@@ -54,9 +54,9 @@ The following diagram illustrates how the Arkose Labs platform integrates with A
 
 ## Request a demo from Arkose Labs
 
-1. Go to arkoselabs.com to [book a demo](https://www.arkoselabs.com/book-a-demo/).
+1. Go to arkoselabs.com to [book a demo](https://www.arkoselabs.com/bot-management-demo/).
 2. Create an account.
-3. Navigate to the [Arkose Portal](https://dashboard.arkoselabs.com/login) sign-in page.
+3. Navigate to the [Arkose Portal](https://portal.arkoselabs.com/) sign-in page.
 4. In the dashboard, navigate to site settings.
 5. Locate your public key and private key. You'll use this information later. 
 
@@ -102,7 +102,7 @@ The user flow is for sign-up and sign-in, or sign-up. The Arkose Labs user flow
 
 3. In Azure-Samples, modify [selfAsserted.html](https://github.com/Azure-Samples/active-directory-b2c-node-sign-up-user-flow-arkose/blob/main/Assets/selfAsserted.html) file so `<ARKOSE_PUBLIC_KEY>` matches the value you generated for the client-side validation.
 4. Host the HTML page on a Cross-Origin Resource Sharing (CORS) enabled web endpoint. 
-5. [Create a storage account](../storage/common/storage-account-create.md?tabs=azure-portal&toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
+5. [Create a storage account](../storage/common/storage-account-create.md?tabs=azure-portal&toc=/azure/storage/blobs/toc.json).
 6. [CORS support for Azure Storage](/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services).
 
     >[!NOTE]

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

@@ -17,7 +17,7 @@ zone_pivot_groups: b2c-policy-type
 
 # Configure Asignio with Azure Active Directory B2C for multifactor authentication
 
-Learn to integrate Azure Active Directory (Azure AD B2C) authentication with [Asignio](https://www.asignio.com/). With this integration, provide passwordless, soft biometric, and multifactor authentication experience to customers. Asignio uses patented Asignio Signature and live facial verification for user authentication. The changeable biometric signature helps to reduce passwords, fraud, phishing, and credential reuse through omni-channel authentication.
+Learn to integrate Azure Active Directory (Azure AD B2C) authentication with [Asignio](https://www.web.asignio.com/). With this integration, provide passwordless, soft biometric, and multifactor authentication experience to customers. Asignio uses patented Asignio Signature and live facial verification for user authentication. The changeable biometric signature helps to reduce passwords, fraud, phishing, and credential reuse through omni-channel authentication.
 
 ## Before you begin
 

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

@@ -17,7 +17,7 @@ zone_pivot_groups: b2c-policy-type
 
 # Configure Transmit Security with Azure Active Directory B2C for passwordless authentication
 
-In this tutorial, learn to integrate Azure Active Directory B2C (Azure AD B2C) authentication with [Transmit Security](https://www.transmitsecurity.com/bindid) BindID, a passwordless authentication solution. BindID uses strong Fast Identity Online (FIDO2) biometric authentication for reliable omni-channel authentication. The solution ensures a smooth sign in experience for customers across devices and channels, while reducing fraud, phishing, and credential reuse.
+In this tutorial, learn to integrate Azure Active Directory B2C (Azure AD B2C) authentication with [Transmit Security](https://transmitsecurity.com/solutions/password-mfa-replacement) BindID, a passwordless authentication solution. BindID uses strong Fast Identity Online (FIDO2) biometric authentication for reliable omni-channel authentication. The solution ensures a smooth sign in experience for customers across devices and channels, while reducing fraud, phishing, and credential reuse.
 
 ## Scenario description
 
@@ -41,7 +41,7 @@ To get started, you need:
 * An Azure AD B2C tenant linked to the Azure subscription
   * See, [Tutorial: Create an Azure Active Directory B2C tenant](./tutorial-create-tenant.md) 
 * A BindID tenant
-  * Go to transmitsecurity.com to [get started](https://www.transmitsecurity.com/developer?utm_signup=dev_hub#try)
+  * Go to transmitsecurity.com to [get started](https://developer.transmitsecurity.com/#try?utm_signup=dev_hub)
 * Register a web application in the Azure portal
   * [Tutorial: Register a web application in Azure Active Directory B2C](./tutorial-register-applications.md) 
 * Azure AD B2C custom policies

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

@@ -15,7 +15,7 @@ ms.subservice: B2C
 ---
 # Tutorial: Configure Cloudflare Web Application Firewall with Azure Active Directory B2C
 
-In this tutorial, you can learn how to configure the [Cloudflare Web Application Firewall (WAF)](https://www.cloudflare.com/waf/) solution for Azure Active Directory B2C (Azure AD B2C) tenant with custom domain. Use Cloudflare WAF to help protect organizations from malicious attacks that can exploit vulnerabilities such as SQL Injection, and cross-site scripting (XSS).
+In this tutorial, you can learn how to configure the [Cloudflare Web Application Firewall (WAF)](https://www.cloudflare.com/application-services/products/waf/) solution for Azure Active Directory B2C (Azure AD B2C) tenant with custom domain. Use Cloudflare WAF to help protect organizations from malicious attacks that can exploit vulnerabilities such as SQL Injection, and cross-site scripting (XSS).
 
 ## Prerequisites
 
@@ -42,7 +42,7 @@ After a custom domain for Azure AD B2C is configured using Azure Front Door, [te
 
 ## Create a Cloudflare account
 
-On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-up). To enable WAF, on [Application Services]([https://www.cloudflare.com/plans/](https://www.cloudflare.com/plans/#price-matrix) select **Pro**, which is required.
+On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-up). To enable WAF, on [Application Services](https://www.cloudflare.com/plans/#price-matrix), select **Pro**, which is required.
 
 ### Configure DNS
 
@@ -58,7 +58,7 @@ The settings appear in the following image.
 
 ### Configure the Web Application Firewall
 
-Go to your Cloudflare settings, and use the Cloudflare content to [configure the WAF](https://www.cloudflare.com/waf/) and learn about other security tools. 
+Go to your Cloudflare settings, and use the Cloudflare content to [configure the WAF](https://www.cloudflare.com/application-services/products/waf/) and learn about other security tools. 
 
 ### Configure firewall rule
 

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

@@ -17,7 +17,7 @@ ms.subservice: B2C
 
 In this tutorial, learn how to integrate Azure Active Directory B2C (Azure AD B2C) with Experian CrossCore, a service that verifies user identification. It does risk analysis based on information provided by the user during sign-up. CrossCore permits users to sign in, or not.
 
-Learn more about [Experian](https://www.experian.com/decision-analytics/account-opening-fraud/microsoft-integration) solutions, services, etc. 
+Learn more about [Experian](https://www.experian.com/business/products/crosscore) solutions, services, etc. 
 
 In this tutorial, you can use the following attributes in CrossCore risk analysis:
 
@@ -62,7 +62,7 @@ The following architecture diagram shows the implementation.
 
 ## Onboard with Experian
 
-1. Create an Experian account. To get started, go to [Experian](https://www.experian.com/decision-analytics/account-opening-fraud/microsoft-integration) and scroll to the bottom for the contact form.
+1. Create an Experian account. To get started, go to [Experian](https://www.experian.com/business/products/crosscore) and scroll to the bottom for the contact form.
 2. When an account is created, you receive information for API configuration. The following sections continue the process.
 
 ## Configure Azure AD B2C with Experian

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

@@ -19,7 +19,7 @@ Learn to integrate Azure Active Directory B2C (Azure AD B2C) with F5 BIG-IP Acce
 
 Deploy F5 BIG-IP Application Delivery Controller (ADC) as a secure gateway between private networks and the internet. There are features for application-level inspection and customizable access controls. If deployed as a reverse proxy, use the BIG-IP to enable secure hybrid access to business applications, with a federated identity access layer managed by APM.
 
-Go to f5.com resources and white papers for: [Easily Configure Secure Access to All Your Applications via Azure AD](https://www.f5.com/services/resources/white-papers/easily-configure-secure-access-to-all-your-applications-via-azure-active-directory)
+Go to f5.com resources and white papers for: [Easily Configure Secure Access to All Your Applications via Azure AD](https://www.f5.com/resources/white-papers/easily-configure-secure-access-to-all-your-applications-via-azure-active-directory)
 
 ## Prerequisites
 
@@ -35,7 +35,7 @@ To get started, you need:
   * F5 BIG-IP® Best bundle
   * F5 BIG-IP Access Policy Manager™  standalone license
   * F5 BIG-IP Access Policy Manager™ add-on license on a BIG-IP F5 BIG-IP® Local Traffic Manager™ (LTM)
-  * 90-day BIG-IP full feature [trial license](https://www.f5.com/trial/big-ip-trial.php)
+  * 90-day BIG-IP full feature [trial license](https://www.f5.com/trials)
 * A header-based web application or an IIS app for testing
   * See, [Set up an IIS app](/previous-versions/iis/6.0-sdk/ms525396(v=vs.90))
 * SSL certificate to publish services over HTTPS, or use default while testing
@@ -130,7 +130,7 @@ For BIG-IP configuration use Guided Configuration v.7/8. The workflow framework
 2. Go to **Access** > **Guided Configuration**. 
 3. The version appears in the top right-hand corner. 
 
-To upgrade the Guided Configuration, go to my.f5.com for [K85454683: Upgrade F5 BIG-IP Guided Configuration on the BIG-IP system](https://support.f5.com/csp/article/K85454683).
+To upgrade the Guided Configuration, go to my.f5.com for [K85454683: Upgrade F5 BIG-IP Guided Configuration on the BIG-IP system](https://my.f5.com/manage/s/article/K85454683).
 
 ### SSL profiles
 
@@ -348,7 +348,7 @@ To achieve SLO, enable your application sign out function to call the Azure AD B
 
 An alternative SLO process is to enable the BIG-IP to listen for the request, when selecting the applications **Sign out** button. Upon detecting the request, it calls to the Azure AD B2C sign out endpoint. This approach precludes making changes to the application. 
 
-To learn more BIG-IP iRules, go to support.f5.com for [K42052145: Configuring automatic session termination (logout) based on a URI-referenced file name](https://support.f5.com/csp/article/K42052145).
+To learn more BIG-IP iRules, go to support.f5.com for [K42052145: Configuring automatic session termination (logout) based on a URI-referenced file name](https://my.f5.com/manage/s/article/K42052145).
 
 > [!NOTE]
 > Regardless of approach, ensure the Azure AD B2C tenant knows the APM sign-out endpoint. 
@@ -450,4 +450,3 @@ The same access log provides detail.
   10. Select **Apply**.
 
 For more information, go to techdocs.f5.com for [OAuth client and resource server troubleshooting tips](https://techdocs.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-authentication-sso-13-0-0/37.html#GUID-774384BC-CF63-469D-A589-1595D0DDFBA2)
-

articles/active-directory-b2c/partner-grit-editor.md

@@ -17,7 +17,7 @@ ms.subservice: B2C
 
 # Edit Azure Active Directory B2C Identity Experience Framework (IEF) XML with Grit Visual IEF Editor
 
-[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/iefeditor), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
+[Grit Software Systems Visual Identity Experience Framework (IEF) Editor](https://www.gritiam.com/iefeditor.html), is a tool that saves time during Azure Active Directory B2C (Azure AD B2C) authentication deployment. It supports multiple languages without the need to write code. It also has a no code debugger for user journeys.
 
 Use the Visual IEF Editor to:
 
@@ -89,9 +89,8 @@ After the IEF is modified, download, and upload the files to Azure AD B2C to see
 
 For additional information, review the following articles:
 
-- [Tutorial: Create user flows and custom policies in Azure Active Directory B2C](custom-policy-get-started.md?tabs=applications)
+- [Tutorial: Create user flows and custom policies in Azure Active Directory B2C](./tutorial-create-user-flows.md?pivots=b2c-custom-policy&tabs=applications)
 
 - [IEF Editor](https://app.archbee.com/doc/uwPRnuvZNjyEaJ8odNOEC/WmcXf6fTZjAHpx7-rAlac) documentation
 
 - [Grit IAM B2B2C](partner-grit-iam.md)
-