Skip to content

Commit 74c9374

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into docUpdates
2 parents 98794e5 + 7258385 commit 74c9374

File tree

187 files changed

+1279
-693
lines changed

Some content is hidden

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

187 files changed

+1279
-693
lines changed

articles/active-directory/conditional-access/howto-conditional-access-policy-admin-mfa.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,16 +37,16 @@ Organizations can choose to include or exclude roles as they see fit.
3737

3838
Conditional Access policies are powerful tools, we recommend excluding the following accounts from your policy:
3939

40-
* **Emergency access** or **break-glass** accountsto prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant take steps to recover access.
40+
* **Emergency access** or **break-glass** accounts to prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant take steps to recover access.
4141
* More information can be found in the article, [Manage emergency access accounts in Azure AD](../users-groups-roles/directory-emergency-access.md).
4242
* **Service accounts** and **service principles**, such as the Azure AD Connect Sync Account. Service accounts are non-interactive accounts that are not tied to any particular user. They are normally used by back-end services and allow programmatic access to applications. Service accounts should be excluded since MFA can’t be completed programmatically.
43-
* If your organization has these accounts in use in scripts or code, consider replacing them with[managed identities](../managed-identities-azure-resources/overview.md). As a temporary workaround, you can exclude these specific accounts from the baseline policy.
43+
* If your organization has these accounts in use in scripts or code, consider replacing them with [managed identities](../managed-identities-azure-resources/overview.md). As a temporary workaround, you can exclude these specific accounts from the baseline policy.
4444

4545
## Create a Conditional Access policy
4646

4747
The following steps will help create a Conditional Access policy to require those assigned administrative roles to perform multi-factor authentication.
4848

49-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
49+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
5050
1. Browse to **Azure Active Directory** > **Conditional Access**.
5151
1. Select **New policy**.
5252
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.

articles/active-directory/conditional-access/howto-conditional-access-policy-azure-management.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,16 +29,16 @@ These tools can provide highly privileged access to resources, that can alter su
2929

3030
Conditional Access policies are powerful tools, we recommend excluding the following accounts from your policy:
3131

32-
* **Emergency access** or **break-glass** accountsto prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant take steps to recover access.
32+
* **Emergency access** or **break-glass** accounts to prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant take steps to recover access.
3333
* More information can be found in the article, [Manage emergency access accounts in Azure AD](../users-groups-roles/directory-emergency-access.md).
3434
* **Service accounts** and **service principles**, such as the Azure AD Connect Sync Account. Service accounts are non-interactive accounts that are not tied to any particular user. They are normally used by back-end services and allow programmatic access to applications. Service accounts should be excluded since MFA can’t be completed programmatically.
35-
* If your organization has these accounts in use in scripts or code, consider replacing them with[managed identities](../managed-identities-azure-resources/overview.md). As a temporary workaround, you can exclude these specific accounts from the baseline policy.
35+
* If your organization has these accounts in use in scripts or code, consider replacing them with [managed identities](../managed-identities-azure-resources/overview.md). As a temporary workaround, you can exclude these specific accounts from the baseline policy.
3636

3737
## Create a Conditional Access policy
3838

3939
The following steps will help create a Conditional Access policy to require those assigned administrative roles to perform multi-factor authentication.
4040

41-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
41+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
4242
1. Browse to **Azure Active Directory** > **Conditional Access**.
4343
1. Select **New policy**.
4444
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.

articles/active-directory/conditional-access/howto-conditional-access-policy-block-legacy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Due to the increased risk associated with legacy authentication protocols, Micro
2323

2424
The following steps will help create a Conditional Access policy to block legacy authentication requests.
2525

26-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
26+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
2727
1. Browse to **Azure Active Directory** > **Conditional Access**.
2828
1. Select **New policy**.
2929
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.

articles/active-directory/conditional-access/howto-conditional-access-policy-compliant-device.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This policy compliance information is forwarded to Azure AD where Conditional Ac
3030

3131
The following steps will help create a Conditional Access policy to require devices accessing resources be marked as compliant with your organization's Intune compliance policies.
3232

33-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
33+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
3434
1. Browse to **Azure Active Directory** > **Conditional Access**.
3535
1. Select **New policy**.
3636
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.

articles/active-directory/conditional-access/howto-conditional-access-policy-location.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ With the location condition in Conditional Access, you can control access to you
2121

2222
## Define locations
2323

24-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
24+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
2525
1. Browse to **Azure Active Directory** > **Conditional Access**.
2626
1. Choose **New location**.
2727
1. Give your location a name.
@@ -35,7 +35,7 @@ More information about the location condition in Conditional Access can be found
3535

3636
## Create a Conditional Access policy
3737

38-
1. Sign in to the**Azure portal**as a global administrator, security administrator, or Conditional Access administrator.
38+
1. Sign in to the **Azure portal** as a global administrator, security administrator, or Conditional Access administrator.
3939
1. Browse to **Azure Active Directory** > **Conditional Access**.
4040
1. Select **New policy**.
4141
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.

articles/active-directory/develop/quickstart-v2-python-webapp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ When you've completed the guide, your application will accept sign-ins of person
3434
To run this sample, you will need:
3535

3636
- [Python 2.7+](https://www.python.org/downloads/release/python-2713) or [Python 3+](https://www.python.org/downloads/release/python-364/)
37-
- [Flask](http://flask.pocoo.org/), [Flask-Session](https://pythonhosted.org/Flask-Session/), [requests](https://2.python-requests.org/en/master/)
37+
- [Flask](http://flask.pocoo.org/), [Flask-Session](https://pythonhosted.org/Flask-Session/), [requests](https://requests.kennethreitz.org//en/master/)
3838
- [MSAL Python](https://github.com/AzureAD/microsoft-authentication-library-for-python)
3939
- An Azure Active Directory (Azure AD) tenant. For more information on how to get an Azure AD tenant, see [how to get an Azure AD tenant.](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)
4040

articles/active-directory/governance/TOC.yml

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@
1919
items:
2020
- name: Entitlement management
2121
items:
22+
- name: Delegation and roles
23+
href: entitlement-management-delegate.md
2224
- name: Request process and emails
2325
href: entitlement-management-process.md
2426
- name: Access reviews
@@ -36,17 +38,21 @@
3638
items:
3739
- name: Common scenarios
3840
href: entitlement-management-scenarios.md
39-
- name: Administrators and department managers
41+
- name: Administrators
4042
items:
41-
- name: Delegate tasks
42-
href: entitlement-management-delegate.md
43-
- name: Create a catalog of resources
44-
href: entitlement-management-catalog-create.md
43+
- name: Delegate to catalog creators
44+
href: entitlement-management-delegate-catalog.md
4545
- name: View reports and logs
4646
href: entitlement-management-reports.md
4747
- name: Troubleshoot
4848
href: entitlement-management-troubleshoot.md
49-
- name: Project managers
49+
- name: Catalog owners
50+
items:
51+
- name: Create a catalog of resources
52+
href: entitlement-management-catalog-create.md
53+
- name: Delegate to access package managers
54+
href: entitlement-management-delegate-managers.md
55+
- name: Access package managers
5056
items:
5157
- name: Create a new access package
5258
href: entitlement-management-access-package-create.md

articles/active-directory/governance/entitlement-management-access-package-create.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The following diagram shows the high-level process to create a new access packag
4242

4343
## Start new access package
4444

45-
**Prerequisite role:** Global administrator, User administrator or Catalog owner
45+
**Prerequisite role:** Global administrator, User administrator, or Catalog owner
4646

4747
1. Sign in to the [Azure portal](https://portal.azure.com).
4848

@@ -124,5 +124,3 @@ On the **Review + create** tab, you can review your settings and check for any v
124124
## Next steps
125125

126126
- [Edit and manage an existing access package](entitlement-management-access-package-edit.md)
127-
- [Add a catalog owner or an access package manager](entitlement-management-delegate.md#add-a-catalog-owner-or-an-access-package-manager)
128-
- [Create and manage a catalog](entitlement-management-catalog-create.md)

articles/active-directory/governance/entitlement-management-access-package-edit.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -307,7 +307,7 @@ Most users in your directory can sign in to the My Access portal and automatical
307307

308308
It is important that you copy the entire My Access portal link when sending it to an internal business partner. This ensures that the partner will get access to your directory's portal to make their request.
309309

310-
The link will start with "myaccess", include a directory hint, and end with an access package id. Make sure the link includes all of the following:
310+
The link will start with "myaccess", include a directory hint, and end with an access package ID. Make sure the link includes all of the following:
311311

312312
`https://myaccess.microsoft.com/@<directory_hint>#/access-packages/<access_package_id>`
313313

@@ -365,5 +365,4 @@ In entitlement management, Azure AD will process bulk changes for assignment and
365365

366366
## Next steps
367367

368-
- [Add a catalog owner or an access package manager](entitlement-management-delegate.md#add-a-catalog-owner-or-an-access-package-manager)
369368
- [Request process and email notifications](entitlement-management-process.md)

articles/active-directory/governance/entitlement-management-catalog-create.md

Lines changed: 31 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Create and manage a catalog in Azure AD entitlement management (Preview) - Azure Active Directory
2+
title: Create and manage a catalog of resources in Azure AD entitlement management (Preview) - Azure Active Directory
33
description: Learn how to create a new container of resources and access packages in Azure Active Directory entitlement management (Preview).
44
services: active-directory
55
documentationCenter: ''
@@ -12,7 +12,7 @@ ms.tgt_pltfrm: na
1212
ms.devlang: na
1313
ms.topic: conceptual
1414
ms.subservice: compliance
15-
ms.date: 07/23/2019
15+
ms.date: 10/07/2019
1616
ms.author: ajburnle
1717
ms.reviewer: hanki
1818
ms.collection: M365-identity-device-management
@@ -21,7 +21,7 @@ ms.collection: M365-identity-device-management
2121
#Customer intent: As an administrator, I want detailed information about the options available when creating and manage catalog so that I most effectively use catalogs in my organization.
2222

2323
---
24-
# Create and manage a catalog in Azure AD entitlement management (Preview)
24+
# Create and manage a catalog of resources in Azure AD entitlement management (Preview)
2525

2626
> [!IMPORTANT]
2727
> Azure Active Directory (Azure AD) entitlement management is currently in public preview.
@@ -32,11 +32,9 @@ ms.collection: M365-identity-device-management
3232

3333
A catalog is a container of resources and access packages. You create a catalog when you want to group related resources and access packages. Whoever creates the catalog becomes the first catalog owner. A catalog owner can add additional catalog owners.
3434

35-
**Prerequisite role:** Global administrator, User administrator or Catalog creator
35+
**Prerequisite role:** Global administrator, User administrator, or Catalog creator
3636

37-
1. Sign in to the [Azure portal](https://portal.azure.com).
38-
39-
1. Click **Azure Active Directory** and then click **Identity Governance**.
37+
1. In the Azure portal, click **Azure Active Directory** and then click **Identity Governance**.
4038

4139
1. In the left menu, click **Catalogs**.
4240

@@ -70,12 +68,14 @@ To include resources in an access package, the resources must exist in a catalog
7068

7169
1. Click **Add resources**.
7270

73-
1. Click a resource type: **Groups**, **Applications**, or **SharePoint sites**.
71+
1. Click a resource type: **Groups and Teams**, **Applications**, or **SharePoint sites**.
7472

7573
If you don't see a resource that you want to add or you are unable to add a resource, make sure you have the required Azure AD directory role and entitlement management role. You might need to have someone with the required roles add the resource to your catalog. For more information, see [Required roles to add resources to a catalog](entitlement-management-delegate.md#required-roles-to-add-resources-to-a-catalog).
7674

7775
1. Select one or more resources of the type that you would like to add to the catalog.
7876

77+
![Add resources to a catalog](./media/entitlement-management-catalog-create/catalog-add-resources.png)
78+
7979
1. When finished, click **Add**.
8080

8181
These resources can now be included in access packages within the catalog.
@@ -96,11 +96,31 @@ You can remove resources from a catalog. A resource can only be removed from a c
9696

9797
1. Click **Remove** (or click the ellipsis (**...**) and then click **Remove resource**).
9898

99+
## Add additional catalog owners
100+
101+
The user that created a catalog becomes the first catalog owner. To delegate management of a catalog, you add users to the catalog owner role. This helps share the catalog management responsibilities.
102+
103+
Follow these steps to assign a user to the catalog owner role:
104+
105+
**Prerequisite role:** Global administrator, User administrator, or Catalog owner
106+
107+
1. In the Azure portal, click **Azure Active Directory** and then click **Identity Governance**.
108+
109+
1. In the left menu, click **Catalogs** and then open the catalog you want to add administrators to.
110+
111+
1. In the left menu, click **Roles and administrators**.
112+
113+
![Catalogs roles and administrators](./media/entitlement-management-shared/catalog-roles-administrators.png)
114+
115+
1. Click **Add owners** to select the members for these roles.
116+
117+
1. Click **Select** to add these members.
118+
99119
## Edit a catalog
100120

101121
You can edit the name and description for a catalog. Users see this information in an access package's details.
102122

103-
**Prerequisite role:** Global administrator, User administrator or Catalog owner
123+
**Prerequisite role:** Global administrator, User administrator, or Catalog owner
104124

105125
1. In the Azure portal, click **Azure Active Directory** and then click **Identity Governance**.
106126

@@ -116,7 +136,7 @@ You can edit the name and description for a catalog. Users see this information
116136

117137
You can delete a catalog, but only if it does not have any access packages.
118138

119-
**Prerequisite role:** Global administrator, User administrator or Catalog owner
139+
**Prerequisite role:** Global administrator, User administrator, or Catalog owner
120140

121141
1. In the Azure portal, click **Azure Active Directory** and then click **Identity Governance**.
122142

@@ -128,5 +148,4 @@ You can delete a catalog, but only if it does not have any access packages.
128148

129149
## Next steps
130150

131-
- [Add a catalog creator](entitlement-management-delegate.md#add-a-catalog-creator)
132-
- [Create and manage an access package](entitlement-management-access-package-create.md)
151+
- [Delegate access governance to access package managers](entitlement-management-delegate-managers.md)

0 commit comments

Comments
 (0)