Skip to content

Commit fc5555a

Browse files
authored
Merge pull request #48134 from MicrosoftDocs/master
8/2 PM Publish
2 parents 1d850f6 + e031e9c commit fc5555a

File tree

126 files changed

+458
-231
lines changed

Some content is hidden

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

126 files changed

+458
-231
lines changed

.openpublishing.redirection.json

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1147,7 +1147,7 @@
11471147
},
11481148
{
11491149
"source_path": "articles/virtual-machines/linux/key-vault-setup-cli-nodejs.md",
1150-
"redirect_url": "/azure/virtual-machines/linux/key-vault-setup-cli",
1150+
"redirect_url": "/azure/virtual-machines/linux/key-vault-setup",
11511151
"redirect_document_id": true
11521152
},
11531153
{
@@ -5507,8 +5507,8 @@
55075507
},
55085508
{
55095509
"source_path": "articles/active-directory/active-directory-saas-linkedinlearning-provisioning-tutorial.md",
5510-
"redirect_url": "/azure/active-directory/saas-apps/linkedinlearning-provisioning-tutorial",
5511-
"redirect_document_id": true
5510+
"redirect_url": "/azure/active-directory/saas-apps/linkedinlearning-tutorial",
5511+
"redirect_document_id": false
55125512
},
55135513
{
55145514
"source_path": "articles/active-directory/active-directory-saas-linkedinlearning-tutorial.md",
@@ -7927,7 +7927,7 @@
79277927
},
79287928
{
79297929
"source_path": "articles/guidance/guidance-ra-app-service.md",
7930-
"redirect_url": "/azure/architecture/reference-architectures/managed-web-app",
7930+
"redirect_url": "/azure/architecture/reference-architectures/app-service-web-app/basic-web-app",
79317931
"redirect_document_id": false
79327932
},
79337933
{
@@ -10947,7 +10947,7 @@
1094710947
},
1094810948
{
1094910949
"source_path": "articles/sql-database/sql-database-manage-single-databases-tsql.md",
10950-
"redirect_url": "https://docs.microsoft.com/sql/t-sql/statements/alter-database-azure-sql-database",
10950+
"redirect_url": "/sql/t-sql/statements/alter-database-transact-sql",
1095110951
"redirect_document_id": false
1095210952
},
1095310953
{
@@ -15402,7 +15402,7 @@
1540215402
},
1540315403
{
1540415404
"source_path": "articles/virtual-machines/virtual-machines-linux-key-vault-setup-cli-nodejs.md",
15405-
"redirect_url": "/azure/virtual-machines/linux/key-vault-setup-cli-nodejs",
15405+
"redirect_url": "/azure/virtual-machines/linux/key-vault-setup",
1540615406
"redirect_document_id": false
1540715407
},
1540815408
{
@@ -15417,7 +15417,7 @@
1541715417
},
1541815418
{
1541915419
"source_path": "articles/virtual-machines/virtual-machines-linux-mac-create-ssh-keys.experimental.md",
15420-
"redirect_url": "/azure/virtual-machines/linux/mac-create-ssh-keys.experimental",
15420+
"redirect_url": "/azure/virtual-machines/linux/mac-create-ssh-keys",
1542115421
"redirect_document_id": false
1542215422
},
1542315423
{
@@ -18942,7 +18942,7 @@
1894218942
},
1894318943
{
1894418944
"source_path": "articles/sql-database/sql-database-geo-replication-failover-transact-sql.md",
18945-
"redirect_url": "/sql/t-sql/statements/alter-database-azure-sql-database",
18945+
"redirect_url": "/sql/t-sql/statements/alter-database-transact-sql",
1894618946
"redirect_document_id": true
1894718947
},
1894818948
{
@@ -19387,12 +19387,12 @@
1938719387
},
1938819388
{
1938919389
"source_path": "articles/active-directory/active-directory-azureadjoin-personal-device.md",
19390-
"redirect_url": "/azure/active-directory/device-management-azuread-joined-devices-setup",
19390+
"redirect_url": "/azure/active-directory/user-help/device-management-azuread-joined-devices-setup",
1939119391
"redirect_document_id": false
1939219392
},
1939319393
{
1939419394
"source_path": "articles/active-directory/active-directory-azureadjoin-user-upgrade.md",
19395-
"redirect_url": "/azure/active-directory/device-management-azuread-registered-devices-windows10-setup",
19395+
"redirect_url": "/azure/active-directory/user-help/device-management-azuread-registered-devices-windows10-setup",
1939619396
"redirect_document_id": false
1939719397
},
1939819398
{
@@ -22132,7 +22132,7 @@
2213222132
},
2213322133
{
2213422134
"source_path": "articles/cognitive-services/Translator/speech-overview.md",
22135-
"redirect_url": "https://docs.microsofttranslator.com/speech-translate.html",
22135+
"redirect_url": "/azure/cognitive-services/speech-service/speech-translation",
2213622136
"redirect_document_id": false
2213722137
},
2213822138
{
@@ -25992,7 +25992,7 @@
2599225992
},
2599325993
{
2599425994
"source_path": "articles/active-directory/active-directory/migrate-adfs-apps-to-azure.md",
25995-
"redirect_url": "/azure/active-directory/manage-apps/active-directory/migrate-adfs-apps-to-azure",
25995+
"redirect_url": "/azure/active-directory/manage-apps/migrate-adfs-apps-to-azure",
2599625996
"redirect_document_id": true
2599725997
},
2599825998
{
@@ -26257,17 +26257,17 @@
2625726257
},
2625826258
{
2625926259
"source_path": "articles/multi-factor-authentication/end-user/multi-factor-authentication-end-user-app-passwords.experimental.md",
26260-
"redirect_url": "/azure/active-directory/authentication/end-user/multi-factor-authentication-end-user-app-passwords",
26260+
"redirect_url": "/azure/active-directory/user-help/multi-factor-authentication-end-user-app-passwords",
2626126261
"redirect_document_id": false
2626226262
},
2626326263
{
2626426264
"source_path": "articles/multi-factor-authentication/end-user/multi-factor-authentication-end-user-first-time.experimental.md",
26265-
"redirect_url": "/azure/active-directory/authentication/end-user/multi-factor-authentication-end-user-first-time",
26265+
"redirect_url": "/azure/active-directory/user-help/multi-factor-authentication-end-user-first-time",
2626626266
"redirect_document_id": false
2626726267
},
2626826268
{
2626926269
"source_path": "articles/multi-factor-authentication/end-user/multi-factor-authentication-end-user-troubleshoot.experimental.md",
26270-
"redirect_url": "/azure/active-directory/authentication/end-user/multi-factor-authentication-end-user-troubleshoot",
26270+
"redirect_url": "/azure/active-directory/user-help/multi-factor-authentication-end-user-troubleshoot",
2627126271
"redirect_document_id": false
2627226272
},
2627326273
{

articles/active-directory-b2c/active-directory-b2c-apps.md

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,13 @@ Learn more about the types of tokens and claims available to an application in t
5656

5757
In a web application, each execution of a [policy](active-directory-b2c-reference-policies.md) takes these high-level steps:
5858

59-
![Web App Swimlanes Image](./media/active-directory-b2c-apps/webapp.png)
59+
1. The user browses to the web application.
60+
2. The web application redirects the user to Azure AD B2C indicating the policy to execute.
61+
3. The user completes policy.
62+
4. Azure AD B2C returns an `id_token` to the browser.
63+
5. The `id_token` is posted to the redirect URI.
64+
6. The `id_token` is validated and a session cookie is set.
65+
7. A secure page is returned to the user.
6066

6167
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 also sets a session cookie that can be used to identify the user on subsequent page requests.
6268

@@ -85,7 +91,15 @@ The web API can then use the token to verify the API caller's identity and to ex
8591
8692
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:
8793

88-
![Web App Web API Swimlanes Image](./media/active-directory-b2c-apps/webapi.png)
94+
1. The web application executes a policy and the user completes the user experience.
95+
2. Azure AD B2C returns an `access_token` and an authorization code to the browser.
96+
3. The browser posts the `access_token` and authorization code to the redirect URI.
97+
4. The web server validates the `access token` and sets a session cookie.
98+
5. The `access_token` is provided to Azure AD B2C with the authorization code, application client ID, and credentials.
99+
6. The `access_token` and `refresh_token` are returned to the web server.
100+
7. The web API is called with the `access_token` in an authorization header.
101+
8. The web API validates the token.
102+
9. Secure data is returned to the web server.
89103

90104
To learn more about authorization codes, refresh tokens, and the steps for getting tokens, read about the [OAuth 2.0 protocol](active-directory-b2c-reference-oauth-code.md).
91105

@@ -102,8 +116,6 @@ In this flow, the application executes [policies](active-directory-b2c-reference
102116
>
103117
>
104118
105-
![Native App Swimlanes Image](./media/active-directory-b2c-apps/native.png)
106-
107119
## Current limitations
108120

109121
Azure AD B2C does not currently support the following types of apps, but they are on the roadmap.

articles/active-directory-b2c/active-directory-b2c-reference-oauth-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ and other identity management tasks to your mobile and desktop apps. This articl
1919

2020
<!-- TODO: Need link to libraries -->
2121

22-
The OAuth 2.0 authorization code flow is described in [section 4.1 of the OAuth 2.0 specification](http://tools.ietf.org/html/rfc6749). You can use it for authentication and authorization in most [application types](active-directory-b2c-apps.md), including web applications and natively installed applications. You can use the OAuth 2.0 authorization code flow to securely acquire access tokens for your applicationss, which can be used to access resources that are secured by an [authorization server](active-directory-b2c-reference-protocols.md).
22+
The OAuth 2.0 authorization code flow is described in [section 4.1 of the OAuth 2.0 specification](http://tools.ietf.org/html/rfc6749). You can use it for authentication and authorization in most [application types](active-directory-b2c-apps.md), including web applications and natively installed applications. You can use the OAuth 2.0 authorization code flow to securely acquire access tokens and refresh tokens for your applications, which can be used to access resources that are secured by an [authorization server](active-directory-b2c-reference-protocols.md). The refresh token allows the client to acquire new access (and refresh) tokens once the access token expires, typically after one hour.
2323

2424
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.
2525

articles/active-directory-b2c/manage-user-access.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ manager: mtillman
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 05/04/2018
11+
ms.date: 07/24/2018
1212
ms.author: davidmu
1313
ms.component: B2C
1414
---
1515

16-
# Manage user access in Azure AD B2C
16+
# Manage user access in Azure Active Directory B2C
1717

1818
This article discusses how to manage user access to your applications by using Azure Active Directory (Azure AD) B2C. Access management in your application includes:
1919

@@ -24,9 +24,6 @@ This article discusses how to manage user access to your applications by using A
2424

2525
[!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
2626

27-
>[!Note]
28-
>This article provides information that you can use to support your obligations under the GDPR. If you’re looking for general info about GDPR, see the [GDPR section of the Service Trust portal](https://servicetrust.microsoft.com/ViewPage/GDPRGetStarted).
29-
3027
## Control minor access
3128

3229
Applications and organizations may decide to block minors from using applications and services that are not targeted to this audience. Alternatively, applications and organizations may decide to accept minors and subsequently manage the parental consent, and deliver permissible experiences for minors as dictated by business rules and allowed by regulation.
36 KB
Loading

articles/active-directory/manage-apps/application-proxy-integrate-with-remote-desktop-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,14 +59,14 @@ After setting up RDS and Azure AD Application Proxy for your environment, follow
5959
### Publish the RD host endpoint
6060

6161
1. [Publish a new Application Proxy application](application-proxy-publish-azure-portal.md) with the following values:
62-
- Internal URL: https://\<rdhost\>.com/, where \<rdhost\> is the common root that RD Web and RD Gateway share.
62+
- Internal URL: `https://\<rdhost\>.com/`, where `\<rdhost\>` is the common root that RD Web and RD Gateway share.
6363
- External URL: This field is automatically populated based on the name of the application, but you can modify it. Your users will go to this URL when they access RDS.
6464
- Preauthentication method: Azure Active Directory
6565
- Translate URL headers: No
6666
2. Assign users to the published RD application. Make sure they all have access to RDS, too.
6767
3. Leave the single sign-on method for the application as **Azure AD single sign-on disabled**. Your users are asked to authenticate once to Azure AD and once to RD Web, but have single sign-on to RD Gateway.
6868
4. Go to **Azure Active Directory** > **App Registrations** > *Your application* > **Settings**.
69-
5. Select **Properties** and update the **Home-page URL** field to point to your RD Web endpoint (like https://\<rdhost\>.com/RDWeb).
69+
5. Select **Properties** and update the **Home-page URL** field to point to your RD Web endpoint (like `https://\<rdhost\>.com/RDWeb`).
7070

7171
### Direct RDS traffic to Application Proxy
7272

articles/active-directory/users-groups-roles/directory-assign-admin-roles.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,15 @@ ms.custom: it-pro
2323
Using Azure Active Directory (Azure AD), you can designate separate administrators to serve different functions. Administrators can be designated in the Azure AD portal to perform tasks such as adding or changing users, assigning administrative roles, resetting user passwords, managing user licenses, and managing domain names.
2424

2525
## Details about the global administrator role
26+
2627
The global administrator has access to all administrative features. By default, the person who signs up for an Azure subscription is assigned the global administrator role for the directory. Only global administrators can assign other administrator roles.
2728

2829
## Assign or remove administrator roles
30+
2931
To learn how to assign administrative roles to a user in Azure Active Directory, see [Assign a user to administrator roles in Azure Active Directory](../fundamentals/active-directory-users-assign-role-azure-portal.md).
3032

3133
## Available roles
34+
3235
The following administrator roles are available:
3336

3437
* **[Application Administrator](#application-administrator)**: Users in this role can create and manage all aspects of enterprise applications, application registrations, and application proxy settings. This role also grants the ability to consent to delegated permissions, and application permissions excluding Microsoft Graph and Azure AD Graph. Members of this role are not added as owners when creating new application registrations or enterprise applications.
@@ -45,7 +48,7 @@ The following administrator roles are available:
4548
> [!NOTE]
4649
> To deploy Exchange ActiveSync conditional access policy in Azure, the user must also be a Global Administrator.
4750
48-
* **[Device Administrators](#device-administrators)**: Users with this role become local machine administrators on all Windows 10 devices that are joined to Azure Active Directory. They do not have the ability to manage device objects in Azure Active Directory.
51+
* **[Device Administrators](#device-administrators)**: This role is available for assignment only as an additional local administrator in [Device settings](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/DevicesMenuBlade/DeviceSettings/menuId/). Users with this role become local machine administrators on all Windows 10 devices that are joined to Azure Active Directory. They do not have the ability to manage devices objects in Azure Active Directory.
4952

5053
* **[Directory Readers](#directory-readers)**: This is a legacy role that is to be assigned to applications that do not support the [Consent Framework](../develop/active-directory-integrating-applications.md). It should not be assigned to any users.
5154

@@ -350,16 +353,14 @@ Can manage conditional access capabilities.
350353
| microsoft.aad.directory/ConditionalAccessPolicy/Update/Owners | Update ConditionalAccessPolicys.Owners property in Azure Active Directory. |
351354

352355
### Device Administrators
353-
Members of this role are added to the local administrators group on Azure AD-joined devices.
356+
357+
Users with this role become local machine administrators on all Windows 10 devices that are joined to Azure Active Directory. They do not have the ability to manage device objects in Azure Active Directory.
354358

355359
> [!NOTE]
356360
> This role inherits additional permissions from the [User role](https://docs.microsoft.com/en-us/azure/active-directory/users-default-permissions).
357361
>
358362
>
359363
360-
| **Actions** | **Description** |
361-
| --- | --- |
362-
363364
### Directory Readers
364365
Can read basic directory information. For granting access to applications.
365366

articles/active-directory/users-groups-roles/groups-create-rule.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: active-directory
1111
ms.workload: identity
1212
ms.component: users-groups-roles
1313
ms.topic: article
14-
ms.date: 08/01/2018
14+
ms.date: 08/02/2018
1515
ms.author: curtand
1616
ms.reviewer: krbain
1717

@@ -20,7 +20,7 @@ ms.custom: it-pro
2020

2121
# Create a dynamic group and check status
2222

23-
In Azure Active Directory (Azure AD), you can create groups by applying a rule to determine mebership based on user or device properties. When the attributes of a user or device changes, Azure AD evaluates all dynamic group rules in the Azure AD tenant and performs any adds or removes. If a user or device satisfies a rule for a group, they are added as a member, and when they no longer satisfy the rule, they are removed.
23+
In Azure Active Directory (Azure AD), you can create groups by applying a rule to determine membership based on user or device properties. When the attributes of a user or device changes, Azure AD evaluates all dynamic group rules in the Azure AD tenant and performs any adds or removes. If a user or device satisfies a rule for a group, they are added as a member, and when they no longer satisfy the rule, they are removed.
2424

2525
This article details how to set up a rule in the Azure portal for dynamic membership on security groups or Office 365 groups. For examples of rule syntax and a complete list of the supported properties, operators, and values for a membership rule, see [Dynamic membership rules for groups in Azure Active Directory](groups-dynamic-membership.md).
2626

0 commit comments

Comments
 (0)