Skip to content

Commit 9df355b

Browse files
committed
[b2c][seo] remove filename prefix 005
1 parent 69a9a06 commit 9df355b

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+96
-46
lines changed

.openpublishing.redirection.json

Lines changed: 51 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5446,6 +5446,56 @@
54465446
"redirect_url": "/azure/active-directory-b2c/custom-policy-multi-factor-authentication",
54475447
"redirect_document_id": true
54485448
},
5449+
{
5450+
"source_path": "articles/active-directory-b2c/active-directory-b2c-custom-setup-twitter-idp.md",
5451+
"redirect_url": "/azure/active-directory-b2c/identity-provider-twitter-custom",
5452+
"redirect_document_id": true
5453+
},
5454+
{
5455+
"source_path": "articles/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet.md",
5456+
"redirect_url": "/azure/active-directory-b2c/manage-user-accounts-graph-api",
5457+
"redirect_document_id": true
5458+
},
5459+
{
5460+
"source_path": "articles/active-directory-b2c/active-directory-b2c-overview.md",
5461+
"redirect_url": "/azure/active-directory-b2c/overview",
5462+
"redirect_document_id": true
5463+
},
5464+
{
5465+
"source_path": "articles/active-directory-b2c/active-directory-b2c-reference-oidc.md",
5466+
"redirect_url": "/azure/active-directory-b2c/openid-connect",
5467+
"redirect_document_id": true
5468+
},
5469+
{
5470+
"source_path": "articles/active-directory-b2c/active-directory-b2c-reference-spa.md",
5471+
"redirect_url": "/azure/active-directory-b2c/implicit-flow-single-page-application",
5472+
"redirect_document_id": true
5473+
},
5474+
{
5475+
"source_path": "articles/active-directory-b2c/active-directory-b2c-setup-goog-app.md",
5476+
"redirect_url": "/azure/active-directory-b2c/identity-provider-google",
5477+
"redirect_document_id": true
5478+
},
5479+
{
5480+
"source_path": "articles/active-directory-b2c/active-directory-b2c-setup-twitter-app.md",
5481+
"redirect_url": "/azure/active-directory-b2c/identity-provider-twitter",
5482+
"redirect_document_id": true
5483+
},
5484+
{
5485+
"source_path": "articles/active-directory-b2c/active-directory-b2c-setup-wechat-app.md",
5486+
"redirect_url": "/azure/active-directory-b2c/identity-provider-wechat",
5487+
"redirect_document_id": true
5488+
},
5489+
{
5490+
"source_path": "articles/active-directory-b2c/active-directory-b2c-setup-weibo-app.md",
5491+
"redirect_url": "/azure/active-directory-b2c/identity-provider-weibo",
5492+
"redirect_document_id": true
5493+
},
5494+
{
5495+
"source_path": "articles/active-directory-b2c/active-directory-b2c-social-migration.md",
5496+
"redirect_url": "/azure/active-directory-b2c/migrate-social-identities",
5497+
"redirect_document_id": true
5498+
},
54495499
{
54505500
"source_path": "articles/active-directory-b2c/active-directory-b2c-custom-setup-goog-idp.md",
54515501
"redirect_url": "/azure/active-directory-b2c/identity-provider-google-custom",
@@ -14911,7 +14961,7 @@
1491114961
"source_path": "articles/machine-learning/studio/algorithm-choice.md",
1491214962
"redirect_url": "/azure/machine-learning/how-to-select-algorithms",
1491314963
"redirect_document_id": false
14914-
},
14964+
},
1491514965
{
1491614966
"source_path": "articles/machine-learning/machine-learning-algorithm-parameters-optimize.md",
1491714967
"redirect_url": "/azure/machine-learning/studio/algorithm-parameters-optimize",

articles/active-directory-b2c/TOC.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
items:
55
- name: About Azure AD B2C
66
expanded: true
7-
href: active-directory-b2c-overview.md
7+
href: overview.md
88
- name: Technical and feature overview
99
href: technical-overview.md
1010
- name: Quickstarts
@@ -55,11 +55,11 @@
5555
- name: OAuth2 protocol
5656
href: active-directory-b2c-reference-protocols.md
5757
- name: OpenID Connect protocol
58-
href: active-directory-b2c-reference-oidc.md
58+
href: openid-connect.md
5959
- name: Authorization Code grant flow
6060
href: authorization-code-flow.md
6161
- name: Implicit flow
62-
href: active-directory-b2c-reference-spa.md
62+
href: implicit-flow-single-page-application.md
6363
- name: Tokens
6464
href: active-directory-b2c-reference-tokens.md
6565
- name: Request access token
@@ -127,17 +127,17 @@
127127
- name: GitHub
128128
href: identity-provider-github.md
129129
- name: Google
130-
href: active-directory-b2c-setup-goog-app.md
130+
href: identity-provider-google.md
131131
- name: LinkedIn
132132
href: identity-provider-linkedin.md
133133
- name: QQ
134134
href: identity-provider-qq.md
135135
- name: Twitter
136-
href: active-directory-b2c-setup-twitter-app.md
136+
href: identity-provider-twitter.md
137137
- name: WeChat
138-
href: active-directory-b2c-setup-wechat-app.md
138+
href: identity-provider-wechat.md
139139
- name: Weibo
140-
href: active-directory-b2c-setup-weibo-app.md
140+
href: identity-provider-weibo.md
141141
- name: Generic identity provider
142142
href: identity-provider-generic-openid-connect.md
143143
- name: Tokens and session management
@@ -205,7 +205,7 @@
205205
- name: Microsoft Account
206206
href: identity-provider-microsoft-account-custom.md
207207
- name: Twitter
208-
href: active-directory-b2c-custom-setup-twitter-idp.md
208+
href: identity-provider-twitter-custom.md
209209
- name: SAML providers
210210
items:
211211
- name: ADFS
@@ -349,7 +349,7 @@
349349
- name: Export usage report
350350
href: active-directory-b2c-reference-usage-reporting-api.md
351351
- name: Account management
352-
href: active-directory-b2c-devquickstarts-graph-dotnet.md
352+
href: manage-user-accounts-graph-api.md
353353
- name: Audit logs
354354
href: active-directory-b2c-reference-audit-logs.md
355355
- name: Manage users - Azure portal
@@ -371,7 +371,7 @@
371371
- name: Migrate users
372372
href: active-directory-b2c-user-migration.md
373373
- name: Migrate users with external identities
374-
href: active-directory-b2c-social-migration.md
374+
href: migrate-social-identities.md
375375
- name: Reference
376376
items:
377377
- name: Identity Experience Framework release notes

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -254,4 +254,4 @@ Here's the JSON representation of the example activity event shown earlier in th
254254

255255
## Next steps
256256

257-
You can automate other administration tasks, for example, [manage users with .NET](active-directory-b2c-devquickstarts-graph-dotnet.md).
257+
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.subservice: B2C
1717

1818
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.
1919

20-
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).
20+
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).
2121

2222
> [!NOTE]
2323
> 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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,6 @@ More information about the different types of tokens that are used in Azure AD B
7070
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).
7171

7272
* [Build mobile and native applications by using OAuth 2.0](authorization-code-flow.md)
73-
* [Build web apps by using OpenID Connect](active-directory-b2c-reference-oidc.md)
74-
* [Build single-page apps using the OAuth 2.0 implicit flow](active-directory-b2c-reference-spa.md)
73+
* [Build web apps by using OpenID Connect](openid-connect.md)
74+
* [Build single-page apps using the OAuth 2.0 implicit flow](implicit-flow-single-page-application.md)
7575

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ A [registered application](tutorial-register-applications.md) receives tokens an
3636
- `https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/oauth2/v2.0/authorize`
3737
- `https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/oauth2/v2.0/token`
3838

39-
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.
39+
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.
4040

4141
## Claims
4242

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ In a web application, each execution of a [policy](active-directory-b2c-referenc
6767

6868
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.
6969

70-
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).
70+
To see this scenario in action, try one of the web application sign-in code samples in our [Getting started section](overview.md).
7171

72-
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).
72+
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).
7373

7474
## Web APIs
7575

@@ -99,7 +99,7 @@ A web API can receive tokens from many types of clients, including web applicati
9999

100100
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).
101101

102-
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).
102+
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).
103103

104104
## Mobile and native applications
105105

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ The OAuth 2.0 authorization code flow is described in [section 4.1 of the OAuth
2323
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.
2424

2525
> [!NOTE]
26-
> 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.
26+
> To add identity management to a web app by using Azure AD B2C, use [OpenID Connect](openid-connect.md) instead of OAuth 2.0.
2727
28-
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).
28+
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).
2929

3030
To try the HTTP requests in this article:
3131

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Your Azure AD B2C directory comes with a built-in set of attributes. Examples ar
2929
* An identity provider has a unique user identifier like **uniqueUserGUID** that must be saved.
3030
* A custom user journey needs to persist for a state of a user like **migrationStatus**.
3131

32-
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).
32+
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).
3333

3434
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.
3535

articles/active-directory-b2c/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ The Azure AD B2C password user flow for local accounts is based on the policy fo
9090

9191
### Can I use Azure AD Connect to migrate consumer identities that are stored on my on-premises Active Directory to Azure AD B2C?
9292

93-
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.
93+
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.
9494

9595
### Can my app open up Azure AD B2C pages within an iFrame?
9696

0 commit comments

Comments
 (0)