Merge pull request #102087 from mmacy/release-b2c-prefix-removal-005

[b2c][seo] remove filename prefix 005

Author: tfosmark

.openpublishing.redirection.json

@@ -5446,6 +5446,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-custom-setup-twitter-idp.md",
+      "redirect_url": "/azure/active-directory-b2c/identity-provider-twitter-custom",
+      "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet.md",
+        "redirect_url": "/azure/active-directory-b2c/manage-user-accounts-graph-api",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-overview.md",
+        "redirect_url": "/azure/active-directory-b2c/overview",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-reference-oidc.md",
+        "redirect_url": "/azure/active-directory-b2c/openid-connect",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-reference-spa.md",
+        "redirect_url": "/azure/active-directory-b2c/implicit-flow-single-page-application",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-setup-goog-app.md",
+        "redirect_url": "/azure/active-directory-b2c/identity-provider-google",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-setup-twitter-app.md",
+        "redirect_url": "/azure/active-directory-b2c/identity-provider-twitter",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-setup-wechat-app.md",
+        "redirect_url": "/azure/active-directory-b2c/identity-provider-wechat",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-setup-weibo-app.md",
+        "redirect_url": "/azure/active-directory-b2c/identity-provider-weibo",
+        "redirect_document_id": true
+    },
+    {
+        "source_path": "articles/active-directory-b2c/active-directory-b2c-social-migration.md",
+        "redirect_url": "/azure/active-directory-b2c/migrate-social-identities",
+        "redirect_document_id": true
+    },
     {
       "source_path": "articles/active-directory-b2c/active-directory-b2c-custom-setup-goog-idp.md",
       "redirect_url": "/azure/active-directory-b2c/identity-provider-google-custom",
@@ -14911,7 +14961,7 @@
       "source_path": "articles/machine-learning/studio/algorithm-choice.md",
       "redirect_url": "/azure/machine-learning/how-to-select-algorithms",
       "redirect_document_id": false
-    },    
+    },
     {
       "source_path": "articles/machine-learning/machine-learning-algorithm-parameters-optimize.md",
       "redirect_url": "/azure/machine-learning/studio/algorithm-parameters-optimize",

articles/active-directory-b2c/TOC.yml

@@ -4,7 +4,7 @@
   items:
   - name: About Azure AD B2C
     expanded: true
-    href: active-directory-b2c-overview.md
+    href: overview.md
   - name: Technical and feature overview
     href: technical-overview.md
 - name: Quickstarts
@@ -55,11 +55,11 @@
       - name: OAuth2 protocol
         href: active-directory-b2c-reference-protocols.md
       - name: OpenID Connect protocol
-        href: active-directory-b2c-reference-oidc.md
+        href: openid-connect.md
       - name: Authorization Code grant flow
         href: authorization-code-flow.md
       - name: Implicit flow
-        href: active-directory-b2c-reference-spa.md
+        href: implicit-flow-single-page-application.md
       - name: Tokens
         href: active-directory-b2c-reference-tokens.md
       - name: Request access token
@@ -127,17 +127,17 @@
       - name: GitHub
         href: identity-provider-github.md
       - name: Google
-        href: active-directory-b2c-setup-goog-app.md
+        href: identity-provider-google.md
       - name: LinkedIn
         href: identity-provider-linkedin.md
       - name: QQ
         href: identity-provider-qq.md
       - name: Twitter
-        href: active-directory-b2c-setup-twitter-app.md
+        href: identity-provider-twitter.md
       - name: WeChat
-        href: active-directory-b2c-setup-wechat-app.md
+        href: identity-provider-wechat.md
       - name: Weibo
-        href: active-directory-b2c-setup-weibo-app.md
+        href: identity-provider-weibo.md
       - name: Generic identity provider
         href: identity-provider-generic-openid-connect.md
     - name: Tokens and session management
@@ -205,7 +205,7 @@
         - name: Microsoft Account
           href: identity-provider-microsoft-account-custom.md
         - name: Twitter
-          href: active-directory-b2c-custom-setup-twitter-idp.md
+          href: identity-provider-twitter-custom.md
       - name: SAML providers
         items:
         - name: ADFS
@@ -349,7 +349,7 @@
     - name: Export usage report
       href: active-directory-b2c-reference-usage-reporting-api.md
     - name: Account management
-      href: active-directory-b2c-devquickstarts-graph-dotnet.md
+      href: manage-user-accounts-graph-api.md
   - name: Audit logs
     href: active-directory-b2c-reference-audit-logs.md
   - name: Manage users - Azure portal
@@ -371,7 +371,7 @@
     - name: Migrate users
       href: active-directory-b2c-user-migration.md
     - name: Migrate users with external identities
-      href: active-directory-b2c-social-migration.md
+      href: migrate-social-identities.md
 - name: Reference
   items:
   - name: Identity Experience Framework release notes

articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md

@@ -254,4 +254,4 @@ Here's the JSON representation of the example activity event shown earlier in th
 
 ## Next steps
 
-You can automate other administration tasks, for example, [manage users with .NET](active-directory-b2c-devquickstarts-graph-dotnet.md).
+You can automate other administration tasks, for example, [manage users with .NET](manage-user-accounts-graph-api.md).

articles/active-directory-b2c/active-directory-b2c-reference-custom-attr.md

@@ -17,7 +17,7 @@ ms.subservice: B2C
 
  Every customer-facing application has unique requirements for the information that needs to be collected. Your Azure Active Directory B2C (Azure AD B2C) tenant comes with a built-in set of information stored in attributes, such as Given Name, Surname, City, and Postal Code. With Azure AD B2C, you can extend the set of attributes stored on each customer account.
 
- You can create custom attributes in the [Azure portal](https://portal.azure.com/) and use them in your sign-up user flows, sign-up or sign-in user flows, or profile editing user flows. You can also read and write these attributes by using the [Azure AD Graph API](active-directory-b2c-devquickstarts-graph-dotnet.md). Custom attributes in Azure AD B2C use [Azure AD Graph API Directory Schema Extensions](/previous-versions/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions).
+ You can create custom attributes in the [Azure portal](https://portal.azure.com/) and use them in your sign-up user flows, sign-up or sign-in user flows, or profile editing user flows. You can also read and write these attributes by using the [Azure AD Graph API](manage-user-accounts-graph-api.md). Custom attributes in Azure AD B2C use [Azure AD Graph API Directory Schema Extensions](/previous-versions/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions).
 
 > [!NOTE]
 > Support for newer [Microsoft Graph API](https://docs.microsoft.com/graph/overview?view=graph-rest-1.0) for querying Azure AD B2C tenant is still under development.

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

@@ -70,6 +70,6 @@ More information about the different types of tokens that are used in Azure AD B
 When you're ready to review some example requests, you can start with one of the following tutorials. Each corresponds to a particular authentication scenario. If you need help determining which flow is right for you, check out [the types of apps you can build by using Azure AD B2C](application-types.md).
 
 * [Build mobile and native applications by using OAuth 2.0](authorization-code-flow.md)
-* [Build web apps by using OpenID Connect](active-directory-b2c-reference-oidc.md)
-* [Build single-page apps using the OAuth 2.0 implicit flow](active-directory-b2c-reference-spa.md)
+* [Build web apps by using OpenID Connect](openid-connect.md)
+* [Build single-page apps using the OAuth 2.0 implicit flow](implicit-flow-single-page-application.md)
 

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

@@ -36,7 +36,7 @@ A [registered application](tutorial-register-applications.md) receives tokens an
 - `https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/oauth2/v2.0/authorize`
 - `https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/oauth2/v2.0/token`
 
-Security tokens that your application receives from Azure AD B2C can come from the `/authorize` or `/token` endpoints. When ID tokens are acquired from the `/authorize` endpoint, it's done using the [implicit flow](active-directory-b2c-reference-spa.md), which is often used for users signing in to JavaScript-based web applications. When ID tokens are acquired from the `/token` endpoint, it's done using the [authorization code flow](active-directory-b2c-reference-oidc.md#get-a-token), which keeps the token hidden from the browser.
+Security tokens that your application receives from Azure AD B2C can come from the `/authorize` or `/token` endpoints. When ID tokens are acquired from the `/authorize` endpoint, it's done using the [implicit flow](implicit-flow-single-page-application.md), which is often used for users signing in to JavaScript-based web applications. When ID tokens are acquired from the `/token` endpoint, it's done using the [authorization code flow](openid-connect.md#get-a-token), which keeps the token hidden from the browser.
 
 ## Claims
 

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

@@ -67,9 +67,9 @@ In a web application, each execution of a [policy](active-directory-b2c-referenc
 
 Validation of the `id_token` by using a public signing key that is received from Azure AD is sufficient to verify the identity of the user. This process also sets a session cookie that can be used to identify the user on subsequent page requests.
 
-To see this scenario in action, try one of the web application sign-in code samples in our [Getting started section](active-directory-b2c-overview.md).
+To see this scenario in action, try one of the web application sign-in code samples in our [Getting started section](overview.md).
 
-In addition to facilitating simple sign-in, a web server application might also need to access a back-end web service. In this case, the web application can perform a slightly different [OpenID Connect flow](active-directory-b2c-reference-oidc.md) and acquire tokens by using authorization codes and refresh tokens. This scenario is depicted in the following [Web APIs section](#web-apis).
+In addition to facilitating simple sign-in, a web server application might also need to access a back-end web service. In this case, the web application can perform a slightly different [OpenID Connect flow](openid-connect.md) and acquire tokens by using authorization codes and refresh tokens. This scenario is depicted in the following [Web APIs section](#web-apis).
 
 ## Web APIs
 
@@ -99,7 +99,7 @@ A web API can receive tokens from many types of clients, including web applicati
 
 To learn more about authorization codes, refresh tokens, and the steps for getting tokens, read about the [OAuth 2.0 protocol](authorization-code-flow.md).
 
-To learn how to secure a web API by using Azure AD B2C, check out the web API tutorials in our [Getting started section](active-directory-b2c-overview.md).
+To learn how to secure a web API by using Azure AD B2C, check out the web API tutorials in our [Getting started section](overview.md).
 
 ## Mobile and native applications
 

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

@@ -23,9 +23,9 @@ The OAuth 2.0 authorization code flow is described in [section 4.1 of the OAuth
 This article focuses on the **public clients** OAuth 2.0 authorization code flow. A public client is any client application that cannot be trusted to securely maintain the integrity of a secret password. This includes mobile apps, desktop applications, and essentially any application that runs on a device and needs to get access tokens.
 
 > [!NOTE]
-> To add identity management to a web app by using Azure AD B2C, use [OpenID Connect](active-directory-b2c-reference-oidc.md) instead of OAuth 2.0.
+> To add identity management to a web app by using Azure AD B2C, use [OpenID Connect](openid-connect.md) instead of OAuth 2.0.
 
-Azure AD B2C extends the standard OAuth 2.0 flows to do more than simple authentication and authorization. It introduces the [user flow](active-directory-b2c-reference-policies.md). With user flows, you can use OAuth 2.0 to add user experiences to your application, such as sign-up, sign-in, and profile management. Identity providers that use the OAuth 2.0 protocol include [Amazon](identity-provider-amazon.md), [Azure Active Directory](identity-provider-azure-ad-single-tenant.md), [Facebook](identity-provider-facebook.md), [GitHub](identity-provider-github.md), [Google](active-directory-b2c-setup-goog-app.md), and [LinkedIn](identity-provider-linkedin.md).
+Azure AD B2C extends the standard OAuth 2.0 flows to do more than simple authentication and authorization. It introduces the [user flow](active-directory-b2c-reference-policies.md). With user flows, you can use OAuth 2.0 to add user experiences to your application, such as sign-up, sign-in, and profile management. Identity providers that use the OAuth 2.0 protocol include [Amazon](identity-provider-amazon.md), [Azure Active Directory](identity-provider-azure-ad-single-tenant.md), [Facebook](identity-provider-facebook.md), [GitHub](identity-provider-github.md), [Google](identity-provider-google.md), and [LinkedIn](identity-provider-linkedin.md).
 
 To try the HTTP requests in this article:
 

articles/active-directory-b2c/custom-policy-custom-attributes.md

@@ -29,7 +29,7 @@ Your Azure AD B2C directory comes with a built-in set of attributes. Examples ar
 * An identity provider has a unique user identifier like **uniqueUserGUID** that must be saved.
 * A custom user journey needs to persist for a state of a user like **migrationStatus**.
 
-Azure AD B2C extends the set of attributes stored on each user account. You can also read and write these attributes by using the [Azure AD Graph API](active-directory-b2c-devquickstarts-graph-dotnet.md).
+Azure AD B2C extends the set of attributes stored on each user account. You can also read and write these attributes by using the [Azure AD Graph API](manage-user-accounts-graph-api.md).
 
 Extension properties extend the schema of the user objects in the directory. The terms *extension property*, *custom attribute*, and *custom claim* refer to the same thing in the context of this article. The name varies depending on the context, such as application, object, or policy.
 

articles/active-directory-b2c/faq.md

@@ -90,7 +90,7 @@ The Azure AD B2C password user flow for local accounts is based on the policy fo
 
 ### Can I use Azure AD Connect to migrate consumer identities that are stored on my on-premises Active Directory to Azure AD B2C?
 
-No, Azure AD Connect is not designed to work with Azure AD B2C. Consider using the [Azure AD Graph API](active-directory-b2c-devquickstarts-graph-dotnet.md) for user migration. See the [User migration guide](active-directory-b2c-user-migration.md) for details.
+No, Azure AD Connect is not designed to work with Azure AD B2C. Consider using the [Azure AD Graph API](manage-user-accounts-graph-api.md) for user migration. See the [User migration guide](active-directory-b2c-user-migration.md) for details.
 
 ### Can my app open up Azure AD B2C pages within an iFrame?