Skip to content

Commit 1f0587f

Browse files
authored
Merge pull request #48397 from MicrosoftDocs/master
8/7 AM Publish
2 parents 615403e + b2fc0a6 commit 1f0587f

File tree

449 files changed

+3509
-2610
lines changed

Some content is hidden

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

449 files changed

+3509
-2610
lines changed

.openpublishing.redirection.json

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15520,6 +15520,81 @@
1552015520
"redirect_url": "/azure/active-directory/develop/howto-v1-debug-saml-sso-issues",
1552115521
"redirect_document_id": false
1552215522
},
15523+
{
15524+
"source_path": "articles/active-directory/develop/active-directory-devhowto-appsource-certified.md",
15525+
"redirect_url": "/azure/active-directory/develop/howto-get-appsource-certified-for-azure-ad",
15526+
"redirect_document_id": false
15527+
},
15528+
{
15529+
"source_path": "articles/active-directory/develop/active-directory-app-gallery-listing.md",
15530+
"redirect_url": "/azure/active-directory/develop/howto-list-app-in-azure-ad-app-gallery",
15531+
"redirect_document_id": false
15532+
},
15533+
{
15534+
"source_path": "articles/active-directory/develop/active-directory-application-manifest.md",
15535+
"redirect_url": "/azure/active-directory/develop/reference-azure-ad-app-manifest",
15536+
"redirect_document_id": false
15537+
},
15538+
{
15539+
"source_path": "articles/active-directory/develop/active-directory-dev-glossary.md",
15540+
"redirect_url": "/azure/active-directory/develop/azure-ad-dev-glossary",
15541+
"redirect_document_id": false
15542+
},
15543+
{
15544+
"source_path": "articles/active-directory/develop/active-directory-develop-help-support.md",
15545+
"redirect_url": "/azure/active-directory/develop/azure-ad-dev-support-help-options",
15546+
"redirect_document_id": false
15547+
},
15548+
{
15549+
"source_path": "articles/active-directory/develop/active-directory-v2-flows.md",
15550+
"redirect_url": "/azure/active-directory/develop/v2-app-types",
15551+
"redirect_document_id": false
15552+
},
15553+
{
15554+
"source_path": "articles/active-directory/develop/active-directory-v2-libraries.md",
15555+
"redirect_url": "/azure/active-directory/develop/reference-azure-ad-v2-auth-libraries",
15556+
"redirect_document_id": false
15557+
},
15558+
{
15559+
"source_path": "articles/active-directory/develop/howto-v1-enable-sso-on-android.md",
15560+
"redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-android",
15561+
"redirect_document_id": false
15562+
},
15563+
{
15564+
"source_path": "articles/active-directory/develop/howto-v1-enable-sso-on-ios.md",
15565+
"redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-ios",
15566+
"redirect_document_id": false
15567+
},
15568+
{
15569+
"source_path": "articles/active-directory/develop/azure-ad-dev-glossary.md",
15570+
"redirect_url": "/azure/active-directory/develop/developer-glossary",
15571+
"redirect_document_id": false
15572+
},
15573+
{
15574+
"source_path": "articles/active-directory/develop/azure-ad-dev-support-help-options.md",
15575+
"redirect_url": "/azure/active-directory/develop/developer-support-help-options",
15576+
"redirect_document_id": false
15577+
},
15578+
{
15579+
"source_path": "articles/active-directory/develop/reference-azure-ad-v2-auth-libraries.md",
15580+
"redirect_url": "/azure/active-directory/develop/reference-v2-libraries",
15581+
"redirect_document_id": false
15582+
},
15583+
{
15584+
"source_path": "articles/active-directory/develop/howto-get-appsource-certified-for-azure-ad.md",
15585+
"redirect_url": "/azure/active-directory/develop/howto-get-appsource-certified",
15586+
"redirect_document_id": false
15587+
},
15588+
{
15589+
"source_path": "articles/active-directory/develop/reference-azure-ad-app-manifest.md",
15590+
"redirect_url": "/azure/active-directory/develop/reference-app-manifest",
15591+
"redirect_document_id": false
15592+
},
15593+
{
15594+
"source_path": "articles/active-directory/develop/howto-list-app-in-azure-ad-app-gallery.md",
15595+
"redirect_url": "/azure/active-directory/develop/howto-app-gallery-listing",
15596+
"redirect_document_id": false
15597+
},
1552315598
{
1552415599
"source_path": "articles/virtual-machines/virtual-machines-linux-expand-disks.md",
1552515600
"redirect_url": "/azure/virtual-machines/linux/expand-disks",
@@ -26981,6 +27056,29 @@
2698127056
"source_path": "articles/active-directory/active-directory-conditional-access-migration-mfa.md",
2698227057
"redirect_url": "/azure/active-directory/conditional-access/policy-migration-mfa",
2698327058
"redirect_document_id": true
27059+
},
27060+
{
27061+
"source_path": "articles/active-directory/active-directory-conditional-access-technical-reference.md",
27062+
"redirect_url": "/azure/active-directory/conditional-access/technical-reference",
27063+
"redirect_document_id": true
27064+
},
27065+
{
27066+
"source_path": "articles/active-directory/active-directory-conditional-access-untrusted-networks.md",
27067+
"redirect_url": "/azure/active-directory/conditional-access/untrusted-networks",
27068+
"redirect_document_id": true
27069+
},
27070+
{
27071+
"source_path": "articles/active-directory/active-directory-conditional-access-policy-connected-applications.md",
27072+
"redirect_url": "/azure/active-directory/conditional-access/require-managed-devices",
27073+
"redirect_document_id": true
27074+
},
27075+
{
27076+
"source_path": "articles/active-directory/active-directory-conditional-access-azure-portal.md",
27077+
"redirect_url": "/azure/active-directory/conditional-access/overview",
27078+
"redirect_document_id": true
2698427079
}
27080+
27081+
27082+
2698527083
]
2698627084
}

articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app-webapi.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In this tutorial, you learn how to:
3535

3636
## Register web API
3737

38-
Web API resources need to be registered in your tenant before they can accept and respond to [protected resource requests](../active-directory/develop/active-directory-dev-glossary.md#resource-server) by [client applications](../active-directory/develop/active-directory-dev-glossary.md#client-application) that present an [access token](../active-directory/develop/active-directory-dev-glossary.md#access-token) from Azure Active Directory. Registration establishes the [application and service principal object](../active-directory/develop/active-directory-dev-glossary.md#application-object) in your tenant.
38+
Web API resources need to be registered in your tenant before they can accept and respond to [protected resource requests](../active-directory/develop/developer-glossary.md#resource-server) by [client applications](../active-directory/develop/developer-glossary.md#client-application) that present an [access token](../active-directory/develop/developer-glossary.md#access-token) from Azure Active Directory. Registration establishes the [application and service principal object](../active-directory/develop/developer-glossary.md#application-object) in your tenant.
3939

4040
Log in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
4141

@@ -55,7 +55,7 @@ Log in to the [Azure portal](https://portal.azure.com/) as the global administra
5555
| **Include web app / web API** | Yes | Select **Yes** for a web API. |
5656
| **Allow implicit flow** | Yes | Select **Yes** since the API uses [OpenID Connect sign-in](active-directory-b2c-reference-oidc.md). |
5757
| **Reply URL** | `http://localhost:5000` | Reply URLs are endpoints where Azure AD B2C returns any tokens that your API requests. In this tutorial, the sample web API runs locally (localhost) and listens on port 5000. |
58-
| **App ID URI** | demoapi | The URI uniquely identifies the API in the tenant. This allows you to register multiple APIs per tenant. [Scopes](../active-directory/develop/active-directory-dev-glossary.md#scopes) govern access to the protected API resource and are defined per App ID URI. |
58+
| **App ID URI** | demoapi | The URI uniquely identifies the API in the tenant. This allows you to register multiple APIs per tenant. [Scopes](../active-directory/develop/developer-glossary.md#scopes) govern access to the protected API resource and are defined per App ID URI. |
5959
| **Native client** | No | Since this is a web API and not a native client, select No. |
6060

6161
3. Click **Create** to register your API.
@@ -70,7 +70,7 @@ Registering your web API with Azure AD B2C defines a trust relationship. Since t
7070

7171
## Define and configure scopes
7272

73-
[Scopes](../active-directory/develop/active-directory-dev-glossary.md#scopes) provide a way to govern access to protected resources. Scopes are used by the web API to implement scope-based access control. For example, some users could have both read and write access, whereas other users might have read-only permissions. In this tutorial, you define read and write permissions for the web API.
73+
[Scopes](../active-directory/develop/developer-glossary.md#scopes) provide a way to govern access to protected resources. Scopes are used by the web API to implement scope-based access control. For example, some users could have both read and write access, whereas other users might have read-only permissions. In this tutorial, you define read and write permissions for the web API.
7474

7575
### Define scopes for the web API
7676

@@ -106,7 +106,7 @@ To call a protected web API from an app, you need to grant your app permissions
106106

107107
5. Click **OK**.
108108

109-
Your **My Sample WPF App** is registered to call the protected **My sample Node.js web API**. A user [authenticates](../active-directory/develop/active-directory-dev-glossary.md#authentication) with Azure AD B2C to use the WPF deskop app app. The desktop app obtains an [authorization grant](../active-directory/develop/active-directory-dev-glossary.md#authorization-grant) from Azure AD B2C to access the protected web API.
109+
Your **My Sample WPF App** is registered to call the protected **My sample Node.js web API**. A user [authenticates](../active-directory/develop/developer-glossary.md#authentication) with Azure AD B2C to use the WPF deskop app app. The desktop app obtains an [authorization grant](../active-directory/develop/developer-glossary.md#authorization-grant) from Azure AD B2C to access the protected web API.
110110

111111
## Update web API code
112112

articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ In this tutorial, you learn how to:
3333

3434
## Register desktop app
3535

36-
Applications need to be [registered](../active-directory/develop/active-directory-dev-glossary.md#application-registration) in your tenant before they can receive [access tokens](../active-directory/develop/active-directory-dev-glossary.md#access-token) from Azure Active Directory. App registration creates an [application id](../active-directory/develop/active-directory-dev-glossary.md#application-id-client-id) for the app in your tenant.
36+
Applications need to be [registered](../active-directory/develop/developer-glossary.md#application-registration) in your tenant before they can receive [access tokens](../active-directory/develop/developer-glossary.md#access-token) from Azure Active Directory. App registration creates an [application id](../active-directory/develop/developer-glossary.md#application-id-client-id) for the app in your tenant.
3737

3838
Log in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
3939

@@ -82,7 +82,7 @@ To sign up users to access then sign in to the desktop app, create a **sign-up o
8282
| **Name** | SiUpIn | Enter a **Name** for the policy. The policy name is prefixed with **B2C_1_**. You use the full policy name **B2C_1_SiUpIn** in the sample code. |
8383
| **Identity provider** | Email signup | The identity provider used to uniquely identify the user. |
8484
| **Sign up attributes** | Display Name and Postal Code | Select attributes to be collected from the user during signup. |
85-
| **Application claims** | Display Name, Postal Code, User is new, User's Object ID | Select [claims](../active-directory/develop/active-directory-dev-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/active-directory-dev-glossary.md#access-token). |
85+
| **Application claims** | Display Name, Postal Code, User is new, User's Object ID | Select [claims](../active-directory/develop/developer-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/developer-glossary.md#access-token). |
8686

8787
2. Click **Create** to create your policy.
8888

@@ -99,7 +99,7 @@ To allow users to reset their user profile information on their own, create a **
9999
| **Name** | SiPe | Enter a **Name** for the policy. The policy name is prefixed with **B2C_1_**. You use the full policy name **B2C_1_SiPe** in the sample code. |
100100
| **Identity provider** | Local Account SignIn | The identity provider used to uniquely identify the user. |
101101
| **Profile attributes** | Display Name and Postal Code | Select attributes users can modify during profile edit. |
102-
| **Application claims** | Display Name, Postal Code, User's Object ID | Select [claims](../active-directory/develop/active-directory-dev-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/active-directory-dev-glossary.md#access-token) after a successful profile edit. |
102+
| **Application claims** | Display Name, Postal Code, User's Object ID | Select [claims](../active-directory/develop/developer-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/developer-glossary.md#access-token) after a successful profile edit. |
103103

104104
2. Click **Create** to create your policy.
105105

@@ -115,7 +115,7 @@ To enable password reset on your application, you need to create a **password re
115115
| ------------ | ------- | -------------------------------------------------- |
116116
| **Name** | SSPR | Enter a **Name** for the policy. The policy name is prefixed with **B2C_1_**. You use the full policy name **B2C_1_SSPR** in the sample code. |
117117
| **Identity provider** | Reset password using email address | This is the identity provider used to uniquely identify the user. |
118-
| **Application claims** | User's Object ID | Select [claims](../active-directory/develop/active-directory-dev-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/active-directory-dev-glossary.md#access-token) after a successful password reset. |
118+
| **Application claims** | User's Object ID | Select [claims](../active-directory/develop/developer-glossary.md#claim) you want to be included in the [access token](../active-directory/develop/developer-glossary.md#access-token) after a successful password reset. |
119119

120120
2. Click **Create** to create your policy.
121121

articles/active-directory-b2c/active-directory-b2c-tutorials-spa-webapi.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In this tutorial, you learn how to:
3636

3737
## Register web API
3838

39-
Web API resources need to be registered in your tenant before they can accept and respond to [protected resource requests](../active-directory/develop/active-directory-dev-glossary.md#resource-server) by [client applications](../active-directory/develop/active-directory-dev-glossary.md#client-application) that present an [access token](../active-directory/develop/active-directory-dev-glossary.md#access-token) from Azure Active Directory. Registration establishes the [application and service principal object](../active-directory/develop/active-directory-dev-glossary.md#application-object) in your tenant.
39+
Web API resources need to be registered in your tenant before they can accept and respond to [protected resource requests](../active-directory/develop/developer-glossary.md#resource-server) by [client applications](../active-directory/develop/developer-glossary.md#client-application) that present an [access token](../active-directory/develop/developer-glossary.md#access-token) from Azure Active Directory. Registration establishes the [application and service principal object](../active-directory/develop/developer-glossary.md#application-object) in your tenant.
4040

4141
Log in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
4242

@@ -56,7 +56,7 @@ Log in to the [Azure portal](https://portal.azure.com/) as the global administra
5656
| **Include web app / web API** | Yes | Select **Yes** for a web API. |
5757
| **Allow implicit flow** | Yes | Select **Yes** since the API uses [OpenID Connect sign-in](active-directory-b2c-reference-oidc.md). |
5858
| **Reply URL** | `http://localhost:44332` | Reply URLs are endpoints where Azure AD B2C returns any tokens that your API requests. In this tutorial, the sample web API runs locally (localhost) and listens on port 5000. |
59-
| **App ID URI** | HelloCoreAPI | The URI uniquely identifies the API in the tenant. This allows you to register multiple APIs per tenant. [Scopes](../active-directory/develop/active-directory-dev-glossary.md#scopes) govern access to the protected API resource and are defined per App ID URI. |
59+
| **App ID URI** | HelloCoreAPI | The URI uniquely identifies the API in the tenant. This allows you to register multiple APIs per tenant. [Scopes](../active-directory/develop/developer-glossary.md#scopes) govern access to the protected API resource and are defined per App ID URI. |
6060
| **Native client** | No | Since this is a web API and not a native client, select No. |
6161

6262
3. Click **Create** to register your API.
@@ -71,7 +71,7 @@ Registering your web API with Azure AD B2C defines a trust relationship. Since t
7171

7272
## Define and configure scopes
7373

74-
[Scopes](../active-directory/develop/active-directory-dev-glossary.md#scopes) provide a way to govern access to protected resources. Scopes are used by the web API to implement scope-based access control. For example, some users could have both read and write access, whereas other users might have read-only permissions. In this tutorial, you define read permissions for the web API.
74+
[Scopes](../active-directory/develop/developer-glossary.md#scopes) provide a way to govern access to protected resources. Scopes are used by the web API to implement scope-based access control. For example, some users could have both read and write access, whereas other users might have read-only permissions. In this tutorial, you define read permissions for the web API.
7575

7676
### Define scopes for the web API
7777

@@ -107,7 +107,7 @@ To call a protected web API from an app, you need to grant your app permissions
107107

108108
5. Click **OK**.
109109

110-
Your **My sample single page app** is registered to call the protected **Hello Core API**. A user [authenticates](../active-directory/develop/active-directory-dev-glossary.md#authentication) with Azure AD B2C to use the WPF deskop app app. The desktop app obtains an [authorization grant](../active-directory/develop/active-directory-dev-glossary.md#authorization-grant) from Azure AD B2C to access the protected web API.
110+
Your **My sample single page app** is registered to call the protected **Hello Core API**. A user [authenticates](../active-directory/develop/developer-glossary.md#authentication) with Azure AD B2C to use the WPF deskop app app. The desktop app obtains an [authorization grant](../active-directory/develop/developer-glossary.md#authorization-grant) from Azure AD B2C to access the protected web API.
111111

112112
## Update code
113113

0 commit comments

Comments
 (0)