Merge pull request #102241 from mmacy/release-b2c-prefix-removal-007B

[b2c][seo] remove filename prefix 007

Author: v-shils

.openpublishing.redirection.json

@@ -5456,6 +5456,56 @@
         "redirect_url": "/azure/active-directory-b2c/custom-policy-multi-factor-authentication",
         "redirect_document_id": true
     },
+    {
+      "source_path": "articles/active-directory-b2c/active-directory-b2c-guide-troubleshooting-custom.md",
+      "redirect_url": "/azure/active-directory-b2c/troubleshoot-custom-policies",
+      "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-reference-threat-management.md",
+        "redirect_url": "/azure/active-directory-b2c/threat-management",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-reference-tokens.md",
+        "redirect_url": "/azure/active-directory-b2c/tokens-overview",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-troubleshoot-custom.md",
+        "redirect_url": "/azure/active-directory-b2c/troubleshoot-with-application-insights",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app-webapi.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-desktop-app-webapi",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-desktop-app",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-spa-webapi.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-single-page-app-webapi",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-spa.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-single-page-app",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-web-api.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-web-api-dotnet",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-tutorials-web-app.md",
+        "redirect_url": "/azure/active-directory-b2c/tutorial-web-app-dotnet",
+        "redirect_document_id": true
+    },
     {
       "source_path": "articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw-secure-basic.md",
       "redirect_url": "/azure/active-directory-b2c/secure-rest-api-dotnet-basic-auth",

articles/active-directory-b2c/TOC.yml

@@ -31,19 +31,19 @@
   - name: Authenticate users
     items:
     - name: ASP.NET
-      href: active-directory-b2c-tutorials-web-app.md
+      href: tutorial-web-app-dotnet.md
     - name: Desktop
-      href: active-directory-b2c-tutorials-desktop-app.md
+      href: tutorial-desktop-app.md
     - name: Single page
-      href: active-directory-b2c-tutorials-spa.md
+      href: tutorial-single-page-app.md
   - name: Grant API access
     items:
     - name: ASP.NET
-      href: active-directory-b2c-tutorials-web-api.md
+      href: tutorial-web-api-dotnet.md
     - name: Desktop
-      href: active-directory-b2c-tutorials-desktop-app-webapi.md
+      href: tutorial-desktop-app-webapi.md
     - name: Single page
-      href: active-directory-b2c-tutorials-spa-webapi.md
+      href: tutorial-single-page-app-webapi.md
 - name: Samples
   href: code-samples.md
 - name: Concepts
@@ -61,7 +61,7 @@
       - name: Implicit flow
         href: implicit-flow-single-page-application.md
       - name: Tokens
-        href: active-directory-b2c-reference-tokens.md
+        href: tokens-overview.md
       - name: Request access token
         href: access-tokens.md
   - name: User flow and policy
@@ -243,9 +243,11 @@
     - name: Troubleshooting
       items:
       - name: Collect logs using Application Insights
-        href: active-directory-b2c-troubleshoot-custom.md
+        href: troubleshoot-with-application-insights.md
+        displayName: troubleshooting
       - name: Policy validation
-        href: active-directory-b2c-guide-troubleshooting-custom.md
+        href: troubleshoot-custom-policies.md
+        displayName: troubleshooting
     - name: Usage analytics
       href: analytics-with-application-insights.md
     - name: Reference
@@ -387,7 +389,8 @@
   - name: Enable billing
     href: billing.md
   - name: Threat management
-    href: active-directory-b2c-reference-threat-management.md
+    href: threat-management.md
+    displayName: security
   - name: Extensions app
     href: extensions-app.md
   - name: User flow versions
@@ -414,4 +417,4 @@
     href: support-options.md
     displayName: technical
   - name: Videos
-    href: https://azure.microsoft.com/documentation/videos/index/?services=active-directory-b2c
+    href: https://azure.microsoft.com/documentation/videos/index/?services=active-directory-b2c

articles/active-directory-b2c/access-tokens.md

@@ -17,7 +17,7 @@ ms.subservice: B2C
 
 An *access token* contains claims that you can use in Azure Active Directory B2C (Azure AD B2C) to identify the granted permissions to your APIs. When calling a resource server, an access token must be present in the HTTP request. An access token is denoted as **access_token** in the responses from Azure AD B2C.
 
-This article shows you how to request an access token for a web application and web API. For more information about tokens in Azure AD B2C, see the [overview of tokens in Azure Active Directory B2C](active-directory-b2c-reference-tokens.md).
+This article shows you how to request an access token for a web application and web API. For more information about tokens in Azure AD B2C, see the [overview of tokens in Azure Active Directory B2C](tokens-overview.md).
 
 > [!NOTE]
 > **Web API chains (On-Behalf-Of) is not supported by Azure AD B2C.** - Many architectures include a web API that needs to call another downstream web API, both secured by Azure AD B2C. This scenario is common in clients that have a web API back end, which in turn calls a another service. This chained web API scenario can be supported by using the OAuth 2.0 JWT Bearer Credential grant, otherwise known as the On-Behalf-Of flow. However, the On-Behalf-Of flow is not currently implemented in Azure AD B2C.

articles/active-directory-b2c/active-directory-b2c-reference-policies.md

@@ -27,7 +27,7 @@ A user flow enables you to control behaviors in your applications by configuring
 - Customization of the user interface
 - Information that the application receives as claims in a token
 
-You can create many user flows of different types in your tenant and use them in your applications as needed. User flows can be reused across applications. This flexibility enables you to define and modify identity experiences with minimal or no changes to your code. Your application triggers a user flow by using a standard HTTP authentication request that includes a user flow parameter. A customized [token](active-directory-b2c-reference-tokens.md) is received as a response.
+You can create many user flows of different types in your tenant and use them in your applications as needed. User flows can be reused across applications. This flexibility enables you to define and modify identity experiences with minimal or no changes to your code. Your application triggers a user flow by using a standard HTTP authentication request that includes a user flow parameter. A customized [token](tokens-overview.md) is received as a response.
 
 The following examples show the "p" query string parameter that specifies the user flow to be used:
 

articles/active-directory-b2c/application-types.md

@@ -53,7 +53,7 @@ eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImtyaU1QZG1Cd...
 }
 ```
 
-Learn more about the types of tokens and claims available to an application in the [Azure AD B2C token reference](active-directory-b2c-reference-tokens.md).
+Learn more about the types of tokens and claims available to an application in the [Azure AD B2C token reference](tokens-overview.md).
 
 In a web application, each execution of a [policy](active-directory-b2c-reference-policies.md) takes these high-level steps:
 
@@ -83,7 +83,7 @@ Accept: application/json
 ...
 ```
 
-The web API can then use the token to verify the API caller's identity and to extract information about the caller from claims that are encoded in the token. Learn more about the types of tokens and claims available to an app in the [Azure AD B2C token reference](active-directory-b2c-reference-tokens.md).
+The web API can then use the token to verify the API caller's identity and to extract information about the caller from claims that are encoded in the token. Learn more about the types of tokens and claims available to an app in the [Azure AD B2C token reference](tokens-overview.md).
 
 A web API can receive tokens from many types of clients, including web applications, desktop and mobile applications, single page applications, server-side daemons, and other web APIs. Here's an example of the complete flow for a web application that calls a web API:
 

articles/active-directory-b2c/authorization-code-flow.md

@@ -136,7 +136,7 @@ A successful token response looks like this:
 | access_token |The signed JSON Web Token (JWT) that you requested. |
 | scope |The scopes that the token is valid for. You also can use scopes to cache tokens for later use. |
 | expires_in |The length of time that the token is valid (in seconds). |
-| refresh_token |An OAuth 2.0 refresh token. The app can use this token to acquire additional tokens after the current token expires. Refresh tokens are long-lived. You can use them to retain access to resources for extended periods of time. For more information, see the [Azure AD B2C token reference](active-directory-b2c-reference-tokens.md). |
+| refresh_token |An OAuth 2.0 refresh token. The app can use this token to acquire additional tokens after the current token expires. Refresh tokens are long-lived. You can use them to retain access to resources for extended periods of time. For more information, see the [Azure AD B2C token reference](tokens-overview.md). |
 
 Error responses look like this:
 
@@ -202,7 +202,7 @@ A successful token response looks like this:
 | access_token |The signed JWT that you requested. |
 | scope |The scopes that the token is valid for. You also can use the scopes to cache tokens for later use. |
 | expires_in |The length of time that the token is valid (in seconds). |
-| refresh_token |An OAuth 2.0 refresh token. The app can use this token to acquire additional tokens after the current token expires. Refresh tokens are long-lived, and can be used to retain access to resources for extended periods of time. For more information, see the [Azure AD B2C token reference](active-directory-b2c-reference-tokens.md). |
+| refresh_token |An OAuth 2.0 refresh token. The app can use this token to acquire additional tokens after the current token expires. Refresh tokens are long-lived, and can be used to retain access to resources for extended periods of time. For more information, see the [Azure AD B2C token reference](tokens-overview.md). |
 
 Error responses look like this:
 

articles/active-directory-b2c/configure-tokens.md

@@ -15,7 +15,7 @@ ms.subservice: B2C
 
 # Configure tokens in Azure Active Directory B2C
 
-In this article, you learn how to configure the [lifetime and compatibility of a token](active-directory-b2c-reference-tokens.md) in Azure Active Directory B2C (Azure AD B2C).
+In this article, you learn how to configure the [lifetime and compatibility of a token](tokens-overview.md) in Azure Active Directory B2C (Azure AD B2C).
 
 ## Prerequisites
 

articles/active-directory-b2c/faq.md

@@ -86,7 +86,7 @@ You can use the Azure AD Graph API to write your migration tool. See the [User m
 
 ### What password user flow is used for local accounts in Azure AD B2C?
 
-The Azure AD B2C password user flow for local accounts is based on the policy for Azure AD. Azure AD B2C's sign-up, sign-up or sign-in and password reset user flows use the "strong" password strength and don't expire any passwords. Read the [Azure AD password policy](/previous-versions/azure/jj943764(v=azure.100)) for more details. For information about account lockouts and passwords, see [Manages threats to resources and data in Azure Active Directory B2C](active-directory-b2c-reference-threat-management.md).
+The Azure AD B2C password user flow for local accounts is based on the policy for Azure AD. Azure AD B2C's sign-up, sign-up or sign-in and password reset user flows use the "strong" password strength and don't expire any passwords. Read the [Azure AD password policy](/previous-versions/azure/jj943764(v=azure.100)) for more details. For information about account lockouts and passwords, see [Manages threats to resources and data in Azure Active Directory B2C](threat-management.md).
 
 ### Can I use Azure AD Connect to migrate consumer identities that are stored on my on-premises Active Directory to Azure AD B2C?
 

articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant-custom.md

@@ -211,4 +211,4 @@ To test the multi-tenant sign-in capability, perform the last two steps using th
 
 When working with custom policies, you might sometimes need additional information when troubleshooting a policy during its development.
 
-To help diagnose issues, you can temporarily put the policy into "developer mode" and collect logs with Azure Application Insights. Find out how in [Azure Active Directory B2C: Collecting Logs](active-directory-b2c-troubleshoot-custom.md).
+To help diagnose issues, you can temporarily put the policy into "developer mode" and collect logs with Azure Application Insights. Find out how in [Azure Active Directory B2C: Collecting Logs](troubleshoot-with-application-insights.md).

articles/active-directory-b2c/identity-provider-azure-ad-single-tenant-custom.md

@@ -200,4 +200,4 @@ If the sign in process is successful, your browser is redirected to `https://jwt
 
 When working with custom policies, you might sometimes need additional information when troubleshooting a policy during its development.
 
-To help diagnose issues, you can temporarily put the policy into "developer mode" and collect logs with Azure Application Insights. Find out how in [Azure Active Directory B2C: Collecting Logs](active-directory-b2c-troubleshoot-custom.md).
+To help diagnose issues, you can temporarily put the policy into "developer mode" and collect logs with Azure Application Insights. Find out how in [Azure Active Directory B2C: Collecting Logs](troubleshoot-with-application-insights.md).