> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-ad-pim-role-settings-change.md).
# Azure AD PIM role settings change
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Hour |
| Required Data | AzureAD Audit Log |
| Detection Modules | Identity Threat Module, SaaS Threat Detection |
| ATT\&CK Tactic | Stealth (TA0005), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Abuse Elevation Control Mechanism (T1548), Valid Accounts (T1078) |
| Severity | Low |
### Description
An identity changed the PIM role settings.
### Attacker's Goals
* An attacker can modify the PIM role settings to make it easier to acquire a privileged account.
### Investigative actions
* Check what role settings have been updated.
* Check whether the user changing the settings is permitted to perform such actions.
### Variations
Suspicious Azure AD PIM role settings change
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Abuse Elevation Control Mechanism (T1548), Valid Accounts (T1078) |
| Severity | Medium |
**Description**
An identity modified the PIM role settings to a less secure configuration for a privileged role.
**Attacker's Goals**
* An attacker can modify the PIM role settings to make it easier to acquire a privileged account.
**Investigative actions**
* Check what role settings have been updated.
* Check whether the user changing the settings is permitted to perform such actions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-ad-pim-role-settings-change.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.