Configure app role settings in PIM (preview)
In brief
The documentation explains how to configure activation, assignment, approval, MFA, duration, justification, ticket, and notification settings for app roles in Privileged Identity Management.
What Entra admins need to know
Administrators can align app role assignments with organizational access requirements. Editing settings requires PIM AdminReadWrite permissions.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
new file mode 100644
title: Configure app role settings in PIM (preview) description: Learn how to configure activation, assignment, approval, and notification settings for app roles in Microsoft Entra Privileged Identity Management. ms.topic: how-to ms.date: 10/29/2026 ms.custom: pim, msecd-doc-authoring-1031 ai-usage: ai-generated #customer intent: As an administrator, I want to configure app role settings so that eligible and active assignments follow my organization's access requirements.
Configure app role settings in Privileged Identity Management (preview)
In Privileged Identity Management (PIM) in Microsoft Entra ID, which is part of Microsoft Entra, role settings define role assignment properties. These properties include multifactor authentication and approval requirements for activation, assignment maximum duration, and notification settings. This article shows you how to configure role settings and set up the approval workflow to specify who can approve or deny requests to elevate privilege.
Prerequisites
To modify app role settings, you need PIM AdminReadWrite permissions. The microsoft.directory/servicePrincipals/appRoleAssignedTo/update permission grants this access. Each of the administrative roles listed in Role assignment conditions provides the required permission.
PIM role settings are also known as PIM policies.
Open role settings
To open the settings for an app role:
Sign in to the Microsoft Entra admin center.
Browse to ID Governance > Privileged Identity Management > App Roles (Preview).
Select the application for which you want to configure role settings. Use the application and object IDs in the application list to identify the intended application.
Under Manage, select Settings. View the list of roles and the Modified, Last updated, and Last updated by columns.
Select the role that you want to configure to open Role setting details.
Review the current role settings.
Select Edit to update role settings.
Configure the Activation, Assignment, and Notification tabs as described in Role settings. Use the tab names or the Next: Assignment, Next: Notification, Prev: Activation, and Prev: Assignment buttons to move between sections.
Select Update to save your changes.
Review the notification. PIM shows Updating role settings while processing the change and Role setting update succeeded when it succeeds.
Return to Settings and reopen the role to confirm that Role setting details reflects your changes. The Settings list also shows Modified, Last updated, and Last updated by.
Role settings
For background on eligible and active app role assignments, see PIM for app roles (preview).
Activation maximum duration
On the Activation tab, use the Activation maximum duration (hours) slider or numeric field to set the maximum activation duration. This duration concerns activation of an eligible assignment, rather than the lifetime of the eligible assignment itself.
On activation, require multifactor authentication
You can require users who are eligible for a role to prove who they are by using multifactor authentication (MFA) before they can activate. On the Activation tab, On activation, require offers None, Azure MFA, and Microsoft Entra Conditional Access authentication context.
Select Azure MFA to configure the MFA requirement. The authentication-context option is also present, but its additional configuration isn't shown in the supplied editor views.
Require justification on activation
On the Activation tab, select Require justification on activation to require users to enter a business justification when they activate an eligible assignment.
Require ticket information on activation
On the Activation tab, select Require ticket information on activation to require users to enter ticket information when they activate an eligible assignment.
Require approval to activate
You can require approval for activation of an eligible assignment. On the Activation tab:
- Select Require approval to activate.
- Open Select approver(s).
- In Select a member, use Search or the All, Users, and Groups tabs to find the intended approvers.
- Select the checkboxes for the intended entries, and then select Select.
- Review Selected approvers. Use Remove to remove an entry you don't want.
The Activation tab also includes Require pre-approval custom extension to activate (Preview) and Require post-approval custom extension to activate (Preview).
To learn more about approvals, see Approve or deny app role requests in PIM (preview).
Assignment duration
When you configure settings for a role, you can choose assignment duration options for each assignment type: eligible and active.
On the Assignment tab, configure the permanent-assignment checkboxes and the corresponding expire-after dropdowns. The expiry dropdowns are disabled in the supplied configuration while permanent assignments are allowed.
You can choose from these eligible assignment duration settings.
| Setting | Description |
|---|---|
| Allow permanent eligible assignment | Allows eligible assignments without an end date. |
| Expire eligible assignments after | Sets the expiration period for eligible assignments. |
You can also choose from these active assignment duration settings.
| Setting | Description |
|---|---|
| Allow permanent active assignment | Allows active assignments without an end date. |
| Expire active assignments after | Sets the expiration period for active assignments. |
Permanent eligibility doesn't remove the need to activate the role before use. Review the activation settings separately from the assignment duration settings.
For information about creating assignments, see Assign app roles in PIM (preview). For information about changing an assignment's end date, see Extend or renew app role assignments in PIM (preview).
Require multifactor authentication on active assignment
You can require users who are eligible for a role to prove who they are by using the multifactor authentication feature in Microsoft Entra ID before they can activate. Multifactor authentication helps safeguard access to data and applications. It provides another layer of security by using a second form of authentication.
Users might not be prompted for multifactor authentication if they authenticated with strong credentials or provided multifactor authentication earlier in this session.
If your goal is to ensure that users must provide authentication during activation, you can use On activation, require Microsoft Entra Conditional Access authentication context together with Authentication Strengths. These options require users to authenticate during activation by using methods different from the one they used to sign in to the machine.
For example, if users sign in to the machine by using Windows Hello for Business, you can use On activation, require Microsoft Entra Conditional Access authentication context and Authentication Strengths to require users to do passwordless sign-in with Microsoft Authenticator when they activate the role.
After the user provides passwordless sign-in with Microsoft Authenticator once in this example, they can do their next activation in this session without another authentication. Passwordless sign-in with Microsoft Authenticator is already part of their token.
Enable the multifactor authentication feature of Microsoft Entra ID for all users. For more information, see Plan a Microsoft Entra multifactor authentication deployment.
Require justification on active assignment
You can require the person creating an active (as opposed to eligible) assignment to enter a business justification.
When justification is required, the assignment creator enters it in Enter justification on the assignment wizard's Setting tab. The form shows required-field validation if the justification is missing.
On the Assignment tab, use Require justification on active assignment to configure this requirement.
Notifications
Privileged Identity Management enables granular control over who receives notifications and which notifications they receive. The app-role notification summary includes eligible assignment, active assignment, and activation rows, with default recipients, additional recipients, and a critical-emails-only option.
On the Notification tab, configure each notification's Default recipients, Additional recipients, and Critical emails only controls. Notifications are grouped into eligible assignments, active assignments, and eligible-member activations.
For rows that accept additional recipients, enter email addresses separated by semicolons.
The editor shows these recipient categories:
| Notification group | Notification | Recipient category shown |
|---|---|---|
| Eligible or active assignments | Role assignment alert | Admin. |
| Eligible or active assignments | Notification to the assigned user (assignee) | Assignee. |
| Eligible or active assignments | Request to approve a role assignment renewal/extension | Approver. |
| Eligible-member activation | Role activation alert | Admin. |
| Eligible-member activation | Notification to activated user (requestor) | Requestor. |
| Eligible-member activation | Request to approve an activation | Approver. |
Use the controls as follows:
- Turn off an email: Clear its default-recipient checkbox and remove any editable additional recipients.
- Limit emails to specified email addresses: For a row that accepts additional recipients, clear its default-recipient checkbox and enter the intended addresses.
- Send emails to both default recipients and additional recipients: Keep the default-recipient checkbox selected and add the intended addresses.
- Critical emails only: Select this checkbox to limit the notification to critical emails.
For Request to approve an activation, the additional-recipient field is disabled and states Only designated approvers can receive this email. Configure those recipients through Select approver(s) on the Activation tab, not by adding arbitrary email addresses.
Next steps
@@ -0,0 +1,182 @@+---+title: Configure app role settings in PIM (preview)+description: Learn how to configure activation, assignment, approval, and notification settings for app roles in Microsoft Entra Privileged Identity Management.+ms.topic: how-to+ms.date: 10/29/2026+ms.custom: pim, msecd-doc-authoring-1031+ai-usage: ai-generated+#customer intent: As an administrator, I want to configure app role settings so that eligible and active assignments follow my organization's access requirements.+---+# Configure app role settings in Privileged Identity Management (preview)++<a name="overview"></a>++In Privileged Identity Management (PIM) in Microsoft Entra ID, which is part of Microsoft Entra, role settings define role assignment properties. These properties include multifactor authentication and approval requirements for activation, assignment maximum duration, and notification settings. This article shows you how to configure role settings and set up the approval workflow to specify who can approve or deny requests to elevate privilege.++## Prerequisites++To modify app role settings, you need PIM AdminReadWrite permissions. The `microsoft.directory/servicePrincipals/appRoleAssignedTo/update` permission grants this access. Each of the administrative roles listed in [Role assignment conditions](app-roles-assign.md#permissions) provides the required permission.++PIM role settings are also known as PIM policies.++## Open role settings++To open the settings for an app role:++1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).++1. Browse to **ID Governance** > **Privileged Identity Management** > **App Roles (Preview)**.++1. Select the application for which you want to configure role settings. Use the application and object IDs in the application list to identify the intended application.++1. Under **Manage**, select **Settings**. View the list of roles and the **Modified**, **Last updated**, and **Last updated by** columns.++1. Select the role that you want to configure to open **Role setting details**.++1. Review the current role settings.++1. Select **Edit** to update role settings.++1. Configure the **Activation**, **Assignment**, and **Notification** tabs as described in [Role settings](#role-settings). Use the tab names or the **Next: Assignment**, **Next: Notification**, **Prev: Activation**, and **Prev: Assignment** buttons to move between sections.++1. Select **Update** to save your changes.++1. Review the notification. PIM shows **Updating role settings** while processing the change and **Role setting update succeeded** when it succeeds.++1. Return to **Settings** and reopen the role to confirm that **Role setting details** reflects your changes. The **Settings** list also shows **Modified**, **Last updated**, and **Last updated by**.++++## Role settings++For background on eligible and active app role assignments, see [PIM for app roles (preview)](concept-pim-for-app-roles.md).++++### Activation maximum duration++On the **Activation** tab, use the **Activation maximum duration (hours)** slider or numeric field to set the maximum activation duration. This duration concerns activation of an eligible assignment, rather than the lifetime of the eligible assignment itself.++++### On activation, require multifactor authentication++You can require users who are eligible for a role to prove who they are by using multifactor authentication (MFA) before they can activate. On the **Activation** tab, **On activation, require** offers **None**, **Azure MFA**, and **Microsoft Entra Conditional Access authentication context**.++Select **Azure MFA** to configure the MFA requirement. The authentication-context option is also present, but its additional configuration isn't shown in the supplied editor views.++++### Require justification on activation++On the **Activation** tab, select **Require justification on activation** to require users to enter a business justification when they activate an eligible assignment.++++### Require ticket information on activation++On the **Activation** tab, select **Require ticket information on activation** to require users to enter ticket information when they activate an eligible assignment.++++### Require approval to activate++You can require approval for activation of an eligible assignment. On the **Activation** tab:++1. Select **Require approval to activate**.+1. Open **Select approver(s)**.+1. In **Select a member**, use **Search** or the **All**, **Users**, and **Groups** tabs to find the intended approvers.+1. Select the checkboxes for the intended entries, and then select **Select**.+1. Review **Selected approvers**. Use **Remove** to remove an entry you don't want.++++The **Activation** tab also includes **Require pre-approval custom extension to activate (Preview)** and **Require post-approval custom extension to activate (Preview)**.++++To learn more about approvals, see [Approve or deny app role requests in PIM (preview)](app-roles-approval-workflow.md).++### Assignment duration++When you configure settings for a role, you can choose assignment duration options for each assignment type: *eligible* and *active*.++On the **Assignment** tab, configure the permanent-assignment checkboxes and the corresponding expire-after dropdowns. The expiry dropdowns are disabled in the supplied configuration while permanent assignments are allowed.++You can choose from these eligible assignment duration settings.++| Setting | Description |+| --- | --- |+| **Allow permanent eligible assignment** | Allows eligible assignments without an end date. |+| **Expire eligible assignments after** | Sets the expiration period for eligible assignments. |++You can also choose from these active assignment duration settings.++| Setting | Description |+| --- | --- |+| **Allow permanent active assignment** | Allows active assignments without an end date. |+| **Expire active assignments after** | Sets the expiration period for active assignments. |++++Permanent eligibility doesn't remove the need to activate the role before use. Review the activation settings separately from the assignment duration settings.++For information about creating assignments, see [Assign app roles in PIM (preview)](app-roles-assign.md). For information about changing an assignment's end date, see [Extend or renew app role assignments in PIM (preview)](app-roles-renew-extend.md).++### Require multifactor authentication on active assignment++You can require users who are eligible for a role to prove who they are by using the multifactor authentication feature in Microsoft Entra ID before they can activate. Multifactor authentication helps safeguard access to data and applications. It provides another layer of security by using a second form of authentication.++Users might not be prompted for multifactor authentication if they authenticated with strong credentials or provided multifactor authentication earlier in this session.++If your goal is to ensure that users must provide authentication during activation, you can use [On activation, require Microsoft Entra Conditional Access authentication context](pim-how-to-change-default-settings.md#on-activation-require-azure-ad-conditional-access-authentication-context) together with [Authentication Strengths](~/identity/authentication/concept-authentication-strengths.md). These options require users to authenticate during activation by using methods different from the one they used to sign in to the machine.++For example, if users sign in to the machine by using Windows Hello for Business, you can use **On activation, require Microsoft Entra Conditional Access authentication context** and **Authentication Strengths** to require users to do passwordless sign-in with Microsoft Authenticator when they activate the role.++After the user provides passwordless sign-in with Microsoft Authenticator once in this example, they can do their next activation in this session without another authentication. Passwordless sign-in with Microsoft Authenticator is already part of their token.++Enable the multifactor authentication feature of Microsoft Entra ID for all users. For more information, see [Plan a Microsoft Entra multifactor authentication deployment](~/identity/authentication/howto-mfa-getstarted.md).++### Require justification on active assignment++You can require the person creating an active (as opposed to eligible) assignment to enter a business justification.++When justification is required, the assignment creator enters it in **Enter justification** on the assignment wizard's **Setting** tab. The form shows required-field validation if the justification is missing.++On the **Assignment** tab, use **Require justification on active assignment** to configure this requirement.++### Notifications++Privileged Identity Management enables granular control over who receives notifications and which notifications they receive. The app-role notification summary includes eligible assignment, active assignment, and activation rows, with default recipients, additional recipients, and a critical-emails-only option.++On the **Notification** tab, configure each notification's **Default recipients**, **Additional recipients**, and **Critical emails only** controls. Notifications are grouped into eligible assignments, active assignments, and eligible-member activations.++For rows that accept additional recipients, enter email addresses separated by semicolons.++The editor shows these recipient categories:++| Notification group | Notification | Recipient category shown |+| --- | --- | --- |+| Eligible or active assignments | Role assignment alert | Admin. |+| Eligible or active assignments | Notification to the assigned user (assignee) | Assignee. |+| Eligible or active assignments | Request to approve a role assignment renewal/extension | Approver. |+| Eligible-member activation | Role activation alert | Admin. |+| Eligible-member activation | Notification to activated user (requestor) | Requestor. |+| Eligible-member activation | Request to approve an activation | Approver. |++Use the controls as follows:++- **Turn off an email**: Clear its default-recipient checkbox and remove any editable additional recipients.+- **Limit emails to specified email addresses**: For a row that accepts additional recipients, clear its default-recipient checkbox and enter the intended addresses.+- **Send emails to both default recipients and additional recipients**: Keep the default-recipient checkbox selected and add the intended addresses.+- **Critical emails only**: Select this checkbox to limit the notification to critical emails.++For **Request to approve an activation**, the additional-recipient field is disabled and states **Only designated approvers can receive this email**. Configure those recipients through **Select approver(s)** on the **Activation** tab, not by adding arbitrary email addresses.++++## Next steps++- [Assign app roles in PIM (preview)](app-roles-assign.md).+- [Activate app roles in PIM (preview)](app-roles-activate.md).+- [Approve or deny app role requests in PIM (preview)](app-roles-approval-workflow.md). 