Skip to content

Commit 9ddb17b

Browse files
authored
Merge pull request #249373 from MicrosoftDocs/main
8/25/2023 AM Publish
2 parents 88cf41b + e8b12f8 commit 9ddb17b

File tree

86 files changed

+996
-702
lines changed

Some content is hidden

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

86 files changed

+996
-702
lines changed

articles/active-directory/develop/msal-net-user-gets-consent-for-multiple-resources.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.custom: devx-track-csharp, aaddev, devx-track-dotnet
1717
---
1818

1919
# User gets consent for several resources using MSAL.NET
20-
The Microsoft identity platform does not allow you to get a token for several resources at once. When using the Microsoft Authentication Library for .NET (MSAL.NET), the scopes parameter in the acquire token method should only contain scopes for a single resource. However, you can pre-consent to several resources upfront by specifying additional scopes using the `.WithExtraScopeToConsent` builder method.
20+
The Microsoft identity platform does not allow you to get a token for several resources at once. When using the Microsoft Authentication Library for .NET (MSAL.NET), the *scopes* parameter in the acquire token method should only contain scopes for a single resource. However, you can pre-consent to several resources upfront by specifying additional scopes using the `.WithExtraScopesToConsent` builder method.
2121

2222
> [!NOTE]
2323
> Getting consent for several resources works for Microsoft identity platform, but not for Azure AD B2C. Azure AD B2C supports only admin consent, not user consent.
@@ -27,7 +27,7 @@ For example, if you have two resources that have 2 scopes each:
2727
- https:\//mytenant.onmicrosoft.com/customerapi (with 2 scopes `customer.read` and `customer.write`)
2828
- https:\//mytenant.onmicrosoft.com/vendorapi (with 2 scopes `vendor.read` and `vendor.write`)
2929

30-
You should use the `.WithExtraScopeToConsent` modifier which has the *extraScopesToConsent* parameter as shown in the following example:
30+
You should use the `.WithExtraScopesToConsent` method which has the *extraScopesToConsent* parameter as shown in the following example:
3131

3232
```csharp
3333
string[] scopesForCustomerApi = new string[]
@@ -44,12 +44,12 @@ string[] scopesForVendorApi = new string[]
4444
var accounts = await app.GetAccountsAsync();
4545
var result = await app.AcquireTokenInteractive(scopesForCustomerApi)
4646
.WithAccount(accounts.FirstOrDefault())
47-
.WithExtraScopeToConsent(scopesForVendorApi)
47+
.WithExtraScopesToConsent(scopesForVendorApi)
4848
.ExecuteAsync();
4949
```
5050

51-
This will get you an access token for the first web API. Then, to access the second web API you can silently acquire the token from the token cache:
51+
`AcquireTokenInteractive` will return an access token for the first web API. Along with that access token, a refresh token will also be retrieved from Azure AD and cached. Then, to access the second web API, you can silently acquire the token using `AcquireTokenSilent`. MSAL will use the cached refresh token to retrieve from Azure AD the access token for the second web API.
5252

5353
```csharp
54-
AcquireTokenSilent(scopesForVendorApi, accounts.FirstOrDefault()).ExecuteAsync();
54+
var result = await AcquireTokenSilent(scopesForVendorApi, accounts.FirstOrDefault()).ExecuteAsync();
5555
```

articles/active-directory/governance/TOC.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,15 +58,15 @@
5858
href: /graph/tutorial-accessreviews-roleassignments?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json
5959
- name: Lifecycle Workflows
6060
items:
61-
- name: Automate employee onboarding tasks - Azure portal
61+
- name: Automate employee onboarding tasks - Entra portal
6262
href: tutorial-onboard-custom-workflow-portal.md
6363
- name: Automate employee onboarding tasks - Microsoft Graph
6464
href: /graph/tutorial-lifecycle-workflows-onboard-custom-workflow?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json
65-
- name: Offboarding employees in real-time - Azure portal
65+
- name: Offboarding employees in real-time - Entra portal
6666
href: tutorial-offboard-custom-workflow-portal.md
6767
- name: Offboarding employees in real-time - Microsoft Graph
6868
href: /graph/tutorial-lifecycle-workflows-offboard-custom-workflow?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json
69-
- name: Automate employee offboarding tasks - Azure portal
69+
- name: Automate employee offboarding tasks - Entra portal
7070
href: tutorial-scheduled-leaver-portal.md
7171
- name: Automate employee offboarding tasks - Microsoft Graph
7272
href: /graph/tutorial-lifecycle-workflows-scheduled-leaver?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,11 @@ Follow these steps to specify the approval settings for requests for the access
5252

5353
**Prerequisite role:** Global administrator, Identity Governance administrator, User administrator, Catalog owner, or Access package manager
5454

55-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
55+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
5656

57-
1. In the left menu, select **Access packages** and then open the access package.
57+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
58+
59+
1. On the **Access packages** page open an access package.
5860

5961
1. Either select a policy to edit or add a new policy to the access package
6062
1. Select **Policies** and then **Add policy** if you want to create a new policy.

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

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,11 @@ To use entitlement management and assign users to access packages, you must have
3737

3838
**Prerequisite role:** Global administrator, Identity Governance administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
3939

40-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
40+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
4141

42-
1. In the left menu, select **Access packages** and then open the access package.
42+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
43+
44+
1. On the **Access packages** page open an access package.
4345

4446
1. Select **Assignments** to see a list of active assignments.
4547

@@ -77,9 +79,11 @@ In some cases, you might want to directly assign specific users to an access pac
7779

7880
**Prerequisite role:** Global administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
7981

80-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
82+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
83+
84+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
8185

82-
1. In the left menu, select **Access packages** and then open the access package.
86+
1. On the **Access packages** page open an access package.
8387

8488
1. In the left menu, select **Assignments**.
8589

@@ -117,9 +121,11 @@ Entitlement management also allows you to directly assign external users to an a
117121

118122
**Prerequisite role:** Global administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
119123

120-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
124+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
121125

122-
1. In the left menu, select **Access packages** and then open the access package in which you want to add a user.
126+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
127+
128+
1. On the **Access packages** page open an access package.
123129

124130
1. In the left menu, select **Assignments**.
125131

@@ -195,9 +201,11 @@ You can remove an assignment that a user or an administrator had previously requ
195201

196202
**Prerequisite role:** Global administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
197203

198-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
204+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
205+
206+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
199207

200-
1. In the left menu, select **Access packages** and then open the access package.
208+
1. On the **Access packages** page open an access package.
201209

202210
1. In the left menu, select **Assignments**.
203211

articles/active-directory/governance/entitlement-management-access-package-auto-assignment-policy.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -42,33 +42,35 @@ To create a policy for an access package, you need to start from the access pack
4242

4343
**Prerequisite role:** Global administrator or Identity Governance administrator
4444

45-
1. In the Azure portal, click **Azure Active Directory** and then click **Identity Governance**.
45+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
4646

47-
1. In the left menu, click **Access packages** and then open the access package.
47+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
4848

49-
1. Click **Policies** and then **Add auto-assignment policy** to create a new policy.
49+
1. On the **Access packages** page open an access package.
5050

51-
1. In the first tab, you'll specify the rule. Click **Edit**.
51+
1. Select **Policies** and then **Add auto-assignment policy** to create a new policy.
52+
53+
1. In the first tab, you'll specify the rule. Select **Edit**.
5254

5355
1. Provide a dynamic membership rule, using the [membership rule builder](../enterprise-users/groups-dynamic-membership.md) or by clicking **Edit** on the rule syntax text box.
5456

5557
> [!NOTE]
56-
> The rule builder might not be able to display some rules constructed in the text box, and validating a rule currently requires the you to be in the Global administrator role. For more information, see [rule builder in the Azure portal](../enterprise-users/groups-create-rule.md#rule-builder-in-the-azure-portal).
58+
> The rule builder might not be able to display some rules constructed in the text box, and validating a rule currently requires the you to be in the Global administrator role. For more information, see [rule builder in the Entra admin center](../enterprise-users/groups-create-rule.md#rule-builder-in-the-azure-portal).
5759
5860
![Screenshot of an access package automatic assignment policy rule configuration.](./media/entitlement-management-access-package-auto-assignment-policy/auto-assignment-rule-configuration.png)
5961

60-
1. Click **Save** to close the dynamic membership rule editor.
62+
1. Select **Save** to close the dynamic membership rule editor.
6163
1. By default, the checkboxes to automatically create and remove assignments should remain checked.
6264
1. If you wish users to retain access for a limited time after they go out of scope, you can specify a duration in hours or days. For example, when an employee leaves the sales department, you may wish to allow them to continue to retain access for 7 days to allow them to use sales apps and transfer ownership of their resources in those apps to another employee.
63-
1. Click **Next** to open the **Custom Extensions** tab.
65+
1. Select **Next** to open the **Custom Extensions** tab.
6466

6567
1. If you have [custom extensions](entitlement-management-logic-apps-integration.md) in your catalog you wish to have run when the policy assigns or removes access, you can add them to this policy. Then click next to open the **Review** tab.
6668

6769
1. Type a name and a description for the policy.
6870

6971
![Screenshot of an access package automatic assignment policy review tab.](./media/entitlement-management-access-package-auto-assignment-policy/auto-assignment-review.png)
7072

71-
1. Click **Create** to save the policy.
73+
1. Select **Create** to save the policy.
7274

7375
> [!NOTE]
7476
> At this time, Entitlement management will automatically create a dynamic security group corresponding to each policy, in order to evaluate the users in scope. This group should not be modified except by Entitlement Management itself. This group may also be modified or deleted automatically by Entitlement Management, so don't use this group for other applications or scenarios.

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Create an access package in entitlement management
3-
description: Learn how to create an access package of resources that you want to share in Azure Active Directory entitlement management.
3+
description: Learn how to create an access package of resources that you want to share in Microsoft Entra entitlement management.
44
services: active-directory
55
documentationCenter: ''
66
author: owinfreyATL
@@ -56,15 +56,13 @@ Then once the access package is created, you can [change the hidden setting](ent
5656

5757
To complete the following steps, you need a role of global administrator, Identity Governance administrator, user administrator, catalog owner, or access package manager.
5858

59-
1. Sign in to the [Azure portal](https://portal.azure.com).
59+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
6060

61-
1. Select **Azure Active Directory**, and then select **Identity Governance**.
62-
63-
1. On the left menu, select **Access packages**.
61+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
6462

6563
1. Select **New access package**.
6664

67-
![Screenshot that shows the button for creating a new access package in the Azure portal.](./media/entitlement-management-shared/access-packages-list.png)
65+
![Screenshot that shows the button for creating a new access package in the Microsoft Entra admin center.](./media/entitlement-management-shared/access-packages-list.png)
6866

6967
## Configure basics
7068

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

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,11 @@ Follow these steps to change the **Hidden** setting for an access package.
3232

3333
**Prerequisite role:** Global administrator, Identity Governance administrator, User administrator, Catalog owner, or Access package manager
3434

35-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
35+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
3636

37-
1. In the left menu, select **Access packages** and then open the access package.
37+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
38+
39+
1. On the **Access packages** page open an access package.
3840

3941
1. On the Overview page, select **Edit**.
4042

@@ -50,9 +52,11 @@ An access package can only be deleted if it has no active user assignments. Foll
5052

5153
**Prerequisite role:** Global administrator, User administrator, Catalog owner, or Access package manager
5254

53-
1. In the Azure portal, select **Azure Active Directory** and then select **Identity Governance**.
55+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Identity Governance Administrator](../roles/permissions-reference.md#identity-governance-administrator).
56+
57+
1. Browse to **Identity governance** > **Entitlement management** > **Access package**.
5458

55-
1. In the left menu, select **Access packages** and then open the access package.
59+
1. On the **Access packages** page open the access package.
5660

5761
1. In the left menu, select **Assignments** and remove access for all users.
5862

0 commit comments

Comments
 (0)