Back to catalog
Static reviewDevelopment

Skill dossier

implementing-azure-ad-privileged-identity-management

Source declaration

Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra/Azure AD.

The author's original description, preserved in English. It describes intent, not verified performance.

Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra/Azure AD.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra/Azure AD. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L117]
  • Step 1: Plan Role Assignments [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L119]
  • Step 2: Configure Role Settings [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L133]
  • Step 3: Configure via Microsoft Graph API [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L161]
  • Step 4: Configure Access Reviews [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L229]
  • Step 5: Configure Alerts [Source statement; provisional, not tested. Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L242]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L1-L54]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
45.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-azure-ad-privileged-identity-management/assets/template.mdReference1.9 KB
skills/implementing-azure-ad-privileged-identity-management/LICENSEOther11 KB
skills/implementing-azure-ad-privileged-identity-management/references/api-reference.mdReference1.9 KB
skills/implementing-azure-ad-privileged-identity-management/references/standards.mdReference2 KB
skills/implementing-azure-ad-privileged-identity-management/references/workflows.mdReference3.8 KB
skills/implementing-azure-ad-privileged-identity-management/scripts/agent.pyScript5.9 KB
skills/implementing-azure-ad-privileged-identity-management/scripts/process.pyScript8.3 KB
skills/implementing-azure-ad-privileged-identity-management/SKILL.mdInstruction10.3 KB

SKILL.md frontmatter

{
  "name": "implementing-azure-ad-privileged-identity-management",
  "description": "Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra/Azure AD.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "azure-ad",
    "pim",
    "entra-id",
    "just-in-time",
    "privileged-roles",
    "identity-governance",
    "zero-trust"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1078",
    "T1110",
    "T1556",
    "T1098"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "positioning",
      "defense-impairment"
    ],
    "techniques": [
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "T1110.003",
        "name": "Brute Force: Password Spraying",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1005",
        "name": "Account Manipulation",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1005.002",
        "name": "Account Manipulation: Add Authorized User",
        "tactic": "defense-impairment",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    Microsoft Entra Roles: Global Admin, Exchange Admin, Security Admin, etc.

    Source-described action candidate under “Supported Resource Types”; not verified execution.

  5. 05
    Action

    Azure Resource Roles: Owner, Contributor, User Access Administrator on subscriptions/resource groups

    Source-described action candidate under “Supported Resource Types”; not verified execution.

  6. 06
    Action

    PIM for Groups: Manage membership in privileged security groups

    Source-described action candidate under “Supported Resource Types”; not verified execution.

Inspect all extracted workflow candidates (38 candidate steps)
  1. 07
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  2. 08
    Action

    Step 1: Plan Role Assignments

    Source-described action candidate under “Step 1: Plan Role Assignments”; not verified execution.

  3. 09
    Action

    Step 2: Configure Role Settings

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  4. 10
    Action

    Navigate to Identity Governance > Privileged Identity Management > Microsoft Entra roles

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  5. 11
    Decision

    Select "Settings" and choose the role to configure

    Source-described decision candidate under “Step 2: Configure Role Settings”; not verified execution.

  6. 12
    Action

    Configure the following:

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  7. 13
    Action

    Maximum activation duration: 8 hours (recommended; max 72 hours)

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  8. 14
    Action

    Require MFA on activation: Enabled

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  9. 15
    Action

    Require justification: Enabled

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  10. 16
    Action

    Require ticket information: Enabled (for change management integration)

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  11. 17
    Action

    Require approval: Enabled for Global Admin, Security Admin

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  12. 18
    Action

    Allow permanent eligible assignment: No (set expiry)

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  13. 19
    Action

    Expire eligible assignments after: 6 months (requires re-certification)

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  14. 20
    Action

    Allow permanent active assignment: Only for break-glass accounts

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  15. 21
    Action

    Require MFA on active assignment: Enabled

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  16. 22
    Action

    Require justification on active assignment: Enabled

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  17. 23
    Action

    Send email when members are assigned eligible: Role assigners, admins

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  18. 24
    Action

    Send email when members activate: Admins, security team

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  19. 25
    Action

    Send email when eligible members activate roles: Role assignees

    Source-described action candidate under “Step 2: Configure Role Settings”; not verified execution.

  20. 26
    Action

    Step 3: Configure via Microsoft Graph API

    Source-described action candidate under “Step 3: Configure via Microsoft Graph API”; not verified execution.

  21. 27
    Action

    Step 4: Configure Access Reviews

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  22. 28
    Action

    Navigate to Identity Governance > Access Reviews > New Access Review

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  23. 29
    Action

    Configure:

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  24. 30
    Action

    Review scope: Privileged Identity Management role assignments

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  25. 31
    Action

    Roles: Select all critical roles (Global Admin, Security Admin, etc.)

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  26. 32
    Action

    Reviewers: Managers or self-review with justification

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  27. 33
    Action

    Frequency: Quarterly for critical roles, semi-annually for others

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  28. 34
    Action

    Auto-apply results: Remove access for non-responsive reviews

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  29. 35
    Action

    Duration: 14 days for reviewers to respond

    Source-described action candidate under “Step 4: Configure Access Reviews”; not verified execution.

  30. 36
    Action

    Step 5: Configure Alerts

    Source-described action candidate under “Step 5: Configure Alerts”; not verified execution.

  31. 37
    Action

    Validation Checklist

    Source-described action candidate under “Validation Checklist”; not verified execution.

  32. 38
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

48 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

21 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 21 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

24 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 24 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-azure-ad-privileged-identity-management/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-azure-ad-privileged-identity-management/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-azure-ad-privileged-identity-management
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.