Skip to content

Commit 2549cea

Browse files
Merge pull request #234647 from psignoret/patch-22
Update to note medium and high classifications
2 parents 6efdbd0 + 4ba7d74 commit 2549cea

File tree

1 file changed

+11
-14
lines changed

1 file changed

+11
-14
lines changed

articles/active-directory/manage-apps/configure-permission-classifications.md

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.workload: identity
1010
ms.topic: how-to
1111
ms.date: 3/28/2023
1212
ms.author: jomondi
13-
ms.reviewer: arvindh, luleon, phsignor, jawoods
13+
ms.reviewer: phsignor, jawoods
1414
ms.custom: contperf-fy21q2
1515
zone_pivot_groups: enterprise-apps-all
1616

@@ -21,7 +21,7 @@ zone_pivot_groups: enterprise-apps-all
2121

2222
In this article, you learn how to configure permissions classifications in Azure Active Directory (Azure AD). Permission classifications allow you to identify the impact that different permissions have according to your organization's policies and risk evaluations. For example, you can use permission classifications in consent policies to identify the set of permissions that users are allowed to consent to.
2323

24-
Currently, only the "Low impact" permission classification is supported. Only delegated permissions that don't require admin consent can be classified as "Low impact".
24+
Three permission classifications are supported: "Low", "Medium" (preview), and "High" (preview). Currently, only delegated permissions that don't require admin consent can be classified.
2525

2626
The minimum permissions needed to do basic sign-in are `openid`, `profile`, `email`, and `offline_access`, which are all delegated permissions on the Microsoft Graph. With these permissions an app can read details of the signed-in user's profile, and can maintain this access even when the user is no longer using the app.
2727

@@ -30,7 +30,7 @@ The minimum permissions needed to do basic sign-in are `openid`, `profile`, `ema
3030
To configure permission classifications, you need:
3131

3232
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
33-
- One of the following roles: A global administrator, or owner of the service principal.
33+
- One of the following roles: Global Administrator, Application Administrator, or Cloud Application Administrator
3434

3535
## Manage permission classifications
3636

@@ -40,7 +40,8 @@ Follow these steps to classify permissions using the Azure portal:
4040

4141
1. Sign in to the [Azure portal](https://portal.azure.com) as a [Global Administrator](../roles/permissions-reference.md#global-administrator), [Application Administrator](../roles/permissions-reference.md#application-administrator), or [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator)
4242
1. Select **Azure Active Directory** > **Enterprise applications** > **Consent and permissions** > **Permission classifications**.
43-
1. Choose **Add permissions** to classify another permission as "Low impact".
43+
1. Choose the tab for the permission classification you'd like to update.
44+
1. Choose **Add permissions** to classify another permission.
4445
1. Select the API and then select the delegated permission(s).
4546

4647
In this example, we've classified the minimum set of permission required for single sign-on:
@@ -57,7 +58,7 @@ You can use the latest [Azure AD PowerShell](/powershell/module/azuread/?preserv
5758
Run the following command to connect to Azure AD PowerShell. To consent to the required scopes, sign in with one of the roles listed in the prerequisite section of this article.
5859

5960
```powershell
60-
Connect-AzureAD -Scopes
61+
Connect-AzureAD
6162
```
6263

6364
### List the current permission classifications
@@ -169,13 +170,9 @@ Connect-MgGraph -Scopes "Policy.ReadWrite.PermissionGrant".
169170

170171
```powershell
171172
$params = @{
172-
173-
PermissionId = $delegatedPermission.Id
174-
175-
PermissionName = $delegatedPermission.Value
176-
177-
Classification = "Low"
178-
173+
PermissionId = $delegatedPermission.Id
174+
PermissionName = $delegatedPermission.Value
175+
Classification = "Low"
179176
}
180177
181178
New-MgServicePrincipalDelegatedPermissionClassification -ServicePrincipalId $api.Id -BodyParameter $params
@@ -192,7 +189,7 @@ Connect-MgGraph -Scopes "Policy.ReadWrite.PermissionGrant".
192189
1. Find the delegated permission classification you wish to remove:
193190

194191
```powershell
195-
$classifications= Get-MgServicePrincipalDelegatedPermissionClassification -ServicePrincipalId $api.Id
192+
$classifications = Get-MgServicePrincipalDelegatedPermissionClassification -ServicePrincipalId $api.Id
196193
197194
$classificationToRemove = $classifications | Where-Object {$_.PermissionName -eq "openid"}
198195
```
@@ -242,4 +239,4 @@ DELETE https://graph.microsoft.com/v1.0/servicePrincipals(appId='00000003-0000-0
242239
## Next steps
243240

244241
- [Manage app consent policies](manage-app-consent-policies.md)
245-
- [Permissions and consent in the Microsoft identity platform](../develop/v2-permissions-and-consent.md)
242+
- [Permissions and consent in the Microsoft identity platform](../develop/v2-permissions-and-consent.md)

0 commit comments

Comments
 (0)