Merge pull request #250998 from MicrosoftDocs/alexbuckgit/docutune-autopr-20230912-031929-6910665-ignore-build

[BULK] - DocuTune: Fix stale and broken links (part 7)

Author: prmerger-automator[bot]

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

@@ -109,7 +109,7 @@ Check the authentication [scenarios](#scenario-description) in your applications
 
 - [Azure AD B2C custom policy overview](custom-policy-overview.md)
 
-- [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)
 
 - [SAAS Platform - Organization Application Onboarding Portal](https://app.archbee.com/doc/G_YZFq_VwvgMlmX-_efmX/8m90WVb2M6Yi0gCe7yor2)
 

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

@@ -16,7 +16,7 @@ ms.subservice: B2C
 
 # Tutorial for configuring HYPR with Azure Active Directory B2C
 
-In this tutorial, learn to configure Azure Active Directory B2C (Azure AD B2C) with [HYPR](https://get.hypr.com). When Azure AD B2C is the identity provider (IdP), you can integrate HYPR with customer applications for passwordless authentication. HYPR replaces passwords with public key encryptions that help prevent fraud, phishing, and credential reuse.
+In this tutorial, learn to configure Azure Active Directory B2C (Azure AD B2C) with [HYPR](https://www.hypr.com/). When Azure AD B2C is the identity provider (IdP), you can integrate HYPR with customer applications for passwordless authentication. HYPR replaces passwords with public key encryptions that help prevent fraud, phishing, and credential reuse.
 
 ## Prerequisites
 
@@ -26,9 +26,9 @@ 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
 - A HYPR cloud tenant
-  - Request a HYPR [custom demo](https://get.hypr.com/free-trial)
+  - Request a HYPR [custom demo](https://get.hypr.com/get-a-demo)
 - A user mobile device registered using the HYPR REST APIs, or the HYPR Device Manager in your HYPR tenant
-  - For example, see [HYPR SDK for Java Web](https://docs.hypr.com/integratinghypr/docs/hypr-java-web-sdk) 
+  - For example, see [HYPR SDK for Java Web](https://docs.hypr.com/integratinghypr/docs/sdk-java-web) 
 
 ## Scenario description
 

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

@@ -63,7 +63,7 @@ The following architecture diagram shows the implementation.
 
 ### Part 1 - Deploy the API
 
-Deploy the provided [API code](https://github.com/azure-ad-b2c/partner-integrations/tree/master/samples/IDology/Api) to an Azure service. The code can be published from Visual Studio, following these [instructions](/visualstudio/deployment/quickstart-deploy-to-azure).
+Deploy the provided [API code](https://github.com/azure-ad-b2c/partner-integrations/tree/master/samples/IDology/Api) to an Azure service. The code can be published from Visual Studio, following these [instructions](/visualstudio/deployment/quickstart-deploy-aspnet-web-app).
 
 You'll need the URL of the deployed service to configure Azure AD with the required settings.
 

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

@@ -59,7 +59,7 @@ Please clarify step 1 in the description below - we don't have steps in this tut
 
 1. After activation of your itsme partner account, you'll receive an email with a one-time link to the **client secret**.
 
-1. Follow the instructions at [itsme](https://business.itsme.be/en) to complete the configuration.
+1. Follow the instructions at [itsme](https://www.itsme-id.com/en-BE/business) to complete the configuration.
 
 ## Integrate with Azure AD B2C
 

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

@@ -31,7 +31,7 @@ To get started, you'll need:
   * If you don't have one, get an [Azure free account](https://azure.microsoft.com/free/)
 * An [Azure AD B2C tenant](./tutorial-create-tenant.md) linked to the Azure subscription
 * A Keyless cloud tenant
-  * Go to keyless.io to [Request a demo](https://keyless.io/go)
+  * Go to keyless.io to [Request a demo](https://keyless.io/demo-request)
 * The Keyless Authenticator app installed on a user device
 
 ## Scenario description

articles/active-directory-b2c/partner-ping-identity.md

@@ -16,7 +16,7 @@ ms.subservice: B2C
 
 # Tutorial: Configure Ping Identity with Azure Active Directory B2C for secure hybrid access
 
-In this tutorial, learn how to extend the capabilities of Azure Active Directory B2C (Azure AD B2C) with [PingAccess](https://www.pingidentity.com/en/software/pingaccess.html) and [PingFederate](https://www.pingidentity.com/en/software/pingfederate.html). PingAccess provides access to applications and APIs, and a policy engine for authorized user access. PingFederate is an enterprise federation server for user authentication and single sign-on, an authority that permits customers, employees, and partners to access applications from devices. Use them together to enable secure hybrid access (SHA).
+In this tutorial, learn how to extend the capabilities of Azure Active Directory B2C (Azure AD B2C) with [PingAccess](https://www.pingidentity.com/en/platform/capabilities/web-api-access/pingaccess.html) and [PingFederate](https://www.pingidentity.com/en/platform/capabilities/authentication-authority/pingfederate.html). PingAccess provides access to applications and APIs, and a policy engine for authorized user access. PingFederate is an enterprise federation server for user authentication and single sign-on, an authority that permits customers, employees, and partners to access applications from devices. Use them together to enable secure hybrid access (SHA).
 
 Many e-commerce sites and web applications exposed to the internet are deployed behind proxy systems, or a reverse-proxy system. These proxy systems pre-authenticate, enforce policy, and route traffic. Typical scenarios include protecting web applications from inbound web traffic and providing a uniform session management across distributed server deployments.
 
@@ -33,7 +33,7 @@ If you want to modernize an identity platform in such configurations, there migh
   - Drive the end-user experience consistency
   - Provide a single sign-in experience across applications
 
-In answer to these concerns, the approach in this tutorial is an Azure AD B2C, [PingAccess](https://www.pingidentity.com/en/software/pingaccess.html), and [PingFederate](https://www.pingidentity.com/en/software/pingfederate.html) integration.
+In answer to these concerns, the approach in this tutorial is an Azure AD B2C, [PingAccess](https://www.pingidentity.com/en/platform/capabilities/web-api-access/pingaccess.html), and [PingFederate](https://www.pingidentity.com/en/platform/capabilities/authentication-authority/pingfederate.html) integration.
 
 ## Shared environment
 

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

@@ -118,7 +118,7 @@ Learn more: [Application and service principal objects in Azure AD](../active-di
 
 1. Install the latest version of Microsoft Graph PowerShell Module on a Windows workstation or server.
 
-For more information, see [Microsoft Graph PowerShell documentation](/powershell/microsoftgraph).
+For more information, see [Microsoft Graph PowerShell documentation](/powershell/microsoftgraph/).
 
 2. Connect to the PowerShell module and execute the following commands:
 

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

@@ -16,7 +16,7 @@ ms.subservice: B2C
 
 # Tutorial to configure Azure Active Directory B2C with Strata
 
-In this tutorial, learn how to integrate Azure Active Directory B2C (Azure AD B2C) with Strata [Maverics Identity Orchestrator](https://www.strata.io/maverics-identity-orchestrator/), which helps protect on-premises applications. It connects to identity systems, migrates users and credentials, synchronizes policies and configurations, and abstracts authentication and session management. Use Strata to transition from legacy, to Azure AD B2C, without rewriting applications. 
+In this tutorial, learn how to integrate Azure Active Directory B2C (Azure AD B2C) with Strata [Maverics Identity Orchestrator](https://www.strata.io/), which helps protect on-premises applications. It connects to identity systems, migrates users and credentials, synchronizes policies and configurations, and abstracts authentication and session management. Use Strata to transition from legacy, to Azure AD B2C, without rewriting applications. 
 
 The solution has the following benefits:
 
@@ -34,7 +34,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 instance of [Azure Key Vault](https://azure.microsoft.com/services/key-vault/) to store secrets used by Maverics Identity Orchestrator. Connect to Azure AD B2C or other attribute providers such as a Lightweight Directory Access Protocol (LDAP) directory or database.
-- An instance of [Maverics Identity Orchestrator](https://www.strata.io/maverics-identity-orchestrator/) running in an Azure virtual machine (VM), or an on-premises server. To get software and documentation, go to strata.io [Contact Strata Identity](https://www.strata.io/contact/).
+- An instance of [Maverics Identity Orchestrator](https://www.strata.io/) running in an Azure virtual machine (VM), or an on-premises server. To get software and documentation, go to strata.io [Contact Strata Identity](https://www.strata.io/company/contact/).
 - An on-premises application to transition to Azure AD B2C
 
 ## Scenario description
@@ -62,7 +62,7 @@ The following architecture diagram shows the implementation.
 
 ## Maverics Identity Orchestrator
 
-To get software and documentation, go to strata.io [Contact Strata Identity](https://www.strata.io/contact/). Determine Orchestrator prerequisites. Install and configure.
+To get software and documentation, go to strata.io [Contact Strata Identity](https://www.strata.io/company/contact/). Determine Orchestrator prerequisites. Install and configure.
 
 ## Configure your Azure AD B2C tenant
 
@@ -104,7 +104,7 @@ You can run your Orchestrator instance on any server, whether on-premises or in
 ### Install Maverics Identity Orchestrator
 
 1. Obtain the latest Maverics RPM package. 
-2. Place the package on the system you'd like to install Maverics. If you're copying to a remote host, use SSH [scp](https://www.ssh.com/ssh/scp/).
+2. Place the package on the system you'd like to install Maverics. If you're copying to a remote host, use SSH [scp](https://www.ssh.com/academy/ssh/scp).
 3. Run the following command. Use your filename to replace `maverics.rpm`.
 
    `sudo rpm -Uvf maverics.rpm`