[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7T0PSDCZFKWWJA5V64PS7":3,"skill-same:01M7A7T0PSDCZFKWWJA5V64PS7":123},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M7A7T0PSDCZFKWWJA5V64PS7","implementing-azure-ad-privileged-identity-management",null,"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\u002FAzure AD.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-azure-ad-privileged-identity-management\ndescription: Configure Microsoft Entra Privileged Identity Management (PIM) to convert\n  standing privileged assignments into eligible, time-bound roles requiring justification,\n  MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups,\n  plus access reviews. Use for role-assignment audits, just-in-time admin activation,\n  or Zero Trust identity governance in Entra\u002FAzure AD.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- azure-ad\n- pim\n- entra-id\n- just-in-time\n- privileged-roles\n- identity-governance\n- zero-trust\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - defense-impairment\n  techniques:\n  - id: F1006\n    name: Account Takeover\n    tactic: initial-access\n    source: f3\n  - id: T1110.003\n    name: 'Brute Force: Password Spraying'\n    tactic: initial-access\n    source: attack\n  - id: F1005\n    name: Account Manipulation\n    tactic: positioning\n    source: f3\n  - id: F1005.002\n    name: 'Account Manipulation: Add Authorized User'\n    tactic: defense-impairment\n    source: f3\n---\n\n# Implementing Azure AD Privileged Identity Management\n\n## Overview\n\nMicrosoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation to mitigate risks from excessive, unnecessary, or misused access to critical resources. PIM replaces permanent (standing) privilege assignments with eligible assignments that require users to explicitly activate their role before use, with configurable duration, MFA enforcement, approval workflows, and justification requirements. This is a core component of Zero Trust identity governance in Microsoft environments.\n\n\n## When to Use\n\n- When deploying or configuring implementing azure ad privileged identity management capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Microsoft Entra ID P2 or Microsoft Entra ID Governance license\n- Global Administrator or Privileged Role Administrator role\n- Azure subscription for Azure resource role management\n- MFA configured for all privileged users\n- Microsoft Authenticator or FIDO2 key for admin accounts\n\n## Core Concepts\n\n### Assignment Types\n\n| Type | Behavior | Use Case |\n|------|----------|----------|\n| Eligible | User must activate the role before use; expires after configured duration | Day-to-day admin work |\n| Active | Role is always active; no activation needed | Service accounts, break-glass accounts |\n| Time-Bound | Either type with explicit start\u002Fend dates | Temporary project access, contractor access |\n\n### PIM Activation Flow\n\n```\nUser with Eligible Assignment\n        │\n        ├── Opens PIM portal → My Roles\n        │\n        ├── Clicks \"Activate\" on the desired role\n        │\n        ├── Provides justification and optional ticket number\n        │\n        ├── Completes MFA challenge (if required)\n        │\n        ├── [If approval required] → Notification sent to approvers\n        │       │\n        │       ├── Approver reviews and approves\u002Fdenies\n        │       └── User notified of decision\n        │\n        ├── Role activated for configured duration (e.g., 8 hours)\n        │\n        └── Role automatically deactivated when duration expires\n```\n\n### Supported Resource Types\n\n1. **Microsoft Entra Roles**: Global Admin, Exchange Admin, Security Admin, etc.\n2. **Azure Resource Roles**: Owner, Contributor, User Access Administrator on subscriptions\u002Fresource groups\n3. **PIM for Groups**: Manage membership in privileged security groups\n\n## Workflow\n\n### Step 1: Plan Role Assignments\n\nAudit current permanent role assignments and determine which should be converted to eligible:\n\n| Current Role | Permanent Holders | Action |\n|-------------|-------------------|--------|\n| Global Administrator | 2-3 admins | Convert to eligible, keep 1 break-glass active |\n| Exchange Administrator | IT team | Convert all to eligible |\n| Security Administrator | SOC team | Convert to eligible |\n| User Administrator | Help desk | Convert to eligible |\n| Application Administrator | DevOps | Convert to eligible |\n\nBest practice: Maintain no more than 2 permanent Global Administrators (break-glass accounts).\n\n### Step 2: Configure Role Settings\n\nFor each Entra directory role, configure PIM settings:\n\n**Via Microsoft Entra Admin Center:**\n1. Navigate to Identity Governance > Privileged Identity Management > Microsoft Entra roles\n2. Select \"Settings\" and choose the role to configure\n3. Configure the following:\n\n**Activation Settings:**\n- Maximum activation duration: 8 hours (recommended; max 72 hours)\n- Require MFA on activation: Enabled\n- Require justification: Enabled\n- Require ticket information: Enabled (for change management integration)\n- Require approval: Enabled for Global Admin, Security Admin\n\n**Assignment Settings:**\n- Allow permanent eligible assignment: No (set expiry)\n- Expire eligible assignments after: 6 months (requires re-certification)\n- Allow permanent active assignment: Only for break-glass accounts\n- Require MFA on active assignment: Enabled\n- Require justification on active assignment: Enabled\n\n**Notification Settings:**\n- Send email when members are assigned eligible: Role assigners, admins\n- Send email when members activate: Admins, security team\n- Send email when eligible members activate roles: Role assignees\n\n### Step 3: Configure via Microsoft Graph API\n\n```python\nimport requests\n\n# Acquire token for Microsoft Graph\ndef get_graph_token(tenant_id, client_id, client_secret):\n    url = f\"https:\u002F\u002Flogin.microsoftonline.com\u002F{tenant_id}\u002Foauth2\u002Fv2.0\u002Ftoken\"\n    data = {\n        \"grant_type\": \"client_credentials\",\n        \"client_id\": client_id,\n        \"client_secret\": client_secret,\n        \"scope\": \"https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n    }\n    response = requests.post(url, data=data)\n    return response.json()[\"access_token\"]\n\n# Create eligible role assignment\ndef create_eligible_assignment(token, role_definition_id, principal_id,\n                                directory_scope=\"\u002F\", duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleEligibilityScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"adminAssign\",\n        \"justification\": \"PIM eligible assignment\",\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": directory_scope,\n        \"principalId\": principal_id,\n        \"scheduleInfo\": {\n            \"startDateTime\": \"2025-01-01T00:00:00Z\",\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": \"P180D\"  # 180-day eligible window\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n\n# Activate a role (user self-service)\ndef activate_role(token, role_definition_id, principal_id, justification,\n                   duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleAssignmentScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"selfActivate\",\n        \"principalId\": principal_id,\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": \"\u002F\",\n        \"justification\": justification,\n        \"scheduleInfo\": {\n            \"startDateTime\": None,  # Now\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": f\"PT{duration_hours}H\"\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n```\n\n### Step 4: Configure Access Reviews\n\nSet up recurring access reviews to verify eligible assignments remain appropriate:\n\n1. Navigate to Identity Governance > Access Reviews > New Access Review\n2. Configure:\n   - Review scope: Privileged Identity Management role assignments\n   - Roles: Select all critical roles (Global Admin, Security Admin, etc.)\n   - Reviewers: Managers or self-review with justification\n   - Frequency: Quarterly for critical roles, semi-annually for others\n   - Auto-apply results: Remove access for non-responsive reviews\n   - Duration: 14 days for reviewers to respond\n\n### Step 5: Configure Alerts\n\nEnable PIM security alerts:\n\n| Alert | Trigger | Action |\n|-------|---------|--------|\n| Too many global admins | > 5 Global Admins | Review and reduce |\n| Roles being assigned outside PIM | Direct role assignment | Investigate and convert to PIM |\n| Roles not requiring MFA | Activation without MFA | Enable MFA requirement |\n| Stale eligible assignments | Not activated in 90 days | Review and potentially remove |\n| Potential stale service accounts | Active assignments not used | Investigate and decommission |\n\n## Validation Checklist\n\n- [ ] All permanent privileged role assignments converted to eligible (except break-glass)\n- [ ] Break-glass accounts configured as active with monitoring alerts\n- [ ] MFA required for all role activations\n- [ ] Approval workflow configured for Global Administrator and Security Administrator\n- [ ] Maximum activation duration set to 8 hours or less for critical roles\n- [ ] Eligible assignments expire after 6 months (requires re-certification)\n- [ ] Justification and ticket information required for activations\n- [ ] Email notifications configured for role assignments and activations\n- [ ] Access reviews scheduled quarterly for all privileged roles\n- [ ] PIM alerts enabled and reviewed weekly\n- [ ] Audit logs forwarded to SIEM for monitoring\n\n## References\n\n- [Microsoft Entra PIM Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-configure)\n- [Plan a PIM Deployment](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-deployment-plan)\n- [Start Using PIM](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-getting-started)\n- [Microsoft Graph PIM API](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fprivilegedidentitymanagementv3-overview)\n","# Implementing Azure AD Privileged Identity Management\n\n## Overview\n\nMicrosoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation to mitigate risks from excessive, unnecessary, or misused access to critical resources. PIM replaces permanent (standing) privilege assignments with eligible assignments that require users to explicitly activate their role before use, with configurable duration, MFA enforcement, approval workflows, and justification requirements. This is a core component of Zero Trust identity governance in Microsoft environments.\n\n\n## When to Use\n\n- When deploying or configuring implementing azure ad privileged identity management capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Microsoft Entra ID P2 or Microsoft Entra ID Governance license\n- Global Administrator or Privileged Role Administrator role\n- Azure subscription for Azure resource role management\n- MFA configured for all privileged users\n- Microsoft Authenticator or FIDO2 key for admin accounts\n\n## Core Concepts\n\n### Assignment Types\n\n| Type | Behavior | Use Case |\n|------|----------|----------|\n| Eligible | User must activate the role before use; expires after configured duration | Day-to-day admin work |\n| Active | Role is always active; no activation needed | Service accounts, break-glass accounts |\n| Time-Bound | Either type with explicit start\u002Fend dates | Temporary project access, contractor access |\n\n### PIM Activation Flow\n\n```\nUser with Eligible Assignment\n        │\n        ├── Opens PIM portal → My Roles\n        │\n        ├── Clicks \"Activate\" on the desired role\n        │\n        ├── Provides justification and optional ticket number\n        │\n        ├── Completes MFA challenge (if required)\n        │\n        ├── [If approval required] → Notification sent to approvers\n        │       │\n        │       ├── Approver reviews and approves\u002Fdenies\n        │       └── User notified of decision\n        │\n        ├── Role activated for configured duration (e.g., 8 hours)\n        │\n        └── Role automatically deactivated when duration expires\n```\n\n### Supported Resource Types\n\n1. **Microsoft Entra Roles**: Global Admin, Exchange Admin, Security Admin, etc.\n2. **Azure Resource Roles**: Owner, Contributor, User Access Administrator on subscriptions\u002Fresource groups\n3. **PIM for Groups**: Manage membership in privileged security groups\n\n## Workflow\n\n### Step 1: Plan Role Assignments\n\nAudit current permanent role assignments and determine which should be converted to eligible:\n\n| Current Role | Permanent Holders | Action |\n|-------------|-------------------|--------|\n| Global Administrator | 2-3 admins | Convert to eligible, keep 1 break-glass active |\n| Exchange Administrator | IT team | Convert all to eligible |\n| Security Administrator | SOC team | Convert to eligible |\n| User Administrator | Help desk | Convert to eligible |\n| Application Administrator | DevOps | Convert to eligible |\n\nBest practice: Maintain no more than 2 permanent Global Administrators (break-glass accounts).\n\n### Step 2: Configure Role Settings\n\nFor each Entra directory role, configure PIM settings:\n\n**Via Microsoft Entra Admin Center:**\n1. Navigate to Identity Governance > Privileged Identity Management > Microsoft Entra roles\n2. Select \"Settings\" and choose the role to configure\n3. Configure the following:\n\n**Activation Settings:**\n- Maximum activation duration: 8 hours (recommended; max 72 hours)\n- Require MFA on activation: Enabled\n- Require justification: Enabled\n- Require ticket information: Enabled (for change management integration)\n- Require approval: Enabled for Global Admin, Security Admin\n\n**Assignment Settings:**\n- Allow permanent eligible assignment: No (set expiry)\n- Expire eligible assignments after: 6 months (requires re-certification)\n- Allow permanent active assignment: Only for break-glass accounts\n- Require MFA on active assignment: Enabled\n- Require justification on active assignment: Enabled\n\n**Notification Settings:**\n- Send email when members are assigned eligible: Role assigners, admins\n- Send email when members activate: Admins, security team\n- Send email when eligible members activate roles: Role assignees\n\n### Step 3: Configure via Microsoft Graph API\n\n```python\nimport requests\n\n# Acquire token for Microsoft Graph\ndef get_graph_token(tenant_id, client_id, client_secret):\n    url = f\"https:\u002F\u002Flogin.microsoftonline.com\u002F{tenant_id}\u002Foauth2\u002Fv2.0\u002Ftoken\"\n    data = {\n        \"grant_type\": \"client_credentials\",\n        \"client_id\": client_id,\n        \"client_secret\": client_secret,\n        \"scope\": \"https:\u002F\u002Fgraph.microsoft.com\u002F.default\"\n    }\n    response = requests.post(url, data=data)\n    return response.json()[\"access_token\"]\n\n# Create eligible role assignment\ndef create_eligible_assignment(token, role_definition_id, principal_id,\n                                directory_scope=\"\u002F\", duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleEligibilityScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"adminAssign\",\n        \"justification\": \"PIM eligible assignment\",\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": directory_scope,\n        \"principalId\": principal_id,\n        \"scheduleInfo\": {\n            \"startDateTime\": \"2025-01-01T00:00:00Z\",\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": \"P180D\"  # 180-day eligible window\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n\n# Activate a role (user self-service)\ndef activate_role(token, role_definition_id, principal_id, justification,\n                   duration_hours=8):\n    url = \"https:\u002F\u002Fgraph.microsoft.com\u002Fv1.0\u002FroleManagement\u002Fdirectory\u002FroleAssignmentScheduleRequests\"\n    headers = {\n        \"Authorization\": f\"Bearer {token}\",\n        \"Content-Type\": \"application\u002Fjson\"\n    }\n    body = {\n        \"action\": \"selfActivate\",\n        \"principalId\": principal_id,\n        \"roleDefinitionId\": role_definition_id,\n        \"directoryScopeId\": \"\u002F\",\n        \"justification\": justification,\n        \"scheduleInfo\": {\n            \"startDateTime\": None,  # Now\n            \"expiration\": {\n                \"type\": \"afterDuration\",\n                \"duration\": f\"PT{duration_hours}H\"\n            }\n        }\n    }\n    response = requests.post(url, headers=headers, json=body)\n    return response.json()\n```\n\n### Step 4: Configure Access Reviews\n\nSet up recurring access reviews to verify eligible assignments remain appropriate:\n\n1. Navigate to Identity Governance > Access Reviews > New Access Review\n2. Configure:\n   - Review scope: Privileged Identity Management role assignments\n   - Roles: Select all critical roles (Global Admin, Security Admin, etc.)\n   - Reviewers: Managers or self-review with justification\n   - Frequency: Quarterly for critical roles, semi-annually for others\n   - Auto-apply results: Remove access for non-responsive reviews\n   - Duration: 14 days for reviewers to respond\n\n### Step 5: Configure Alerts\n\nEnable PIM security alerts:\n\n| Alert | Trigger | Action |\n|-------|---------|--------|\n| Too many global admins | > 5 Global Admins | Review and reduce |\n| Roles being assigned outside PIM | Direct role assignment | Investigate and convert to PIM |\n| Roles not requiring MFA | Activation without MFA | Enable MFA requirement |\n| Stale eligible assignments | Not activated in 90 days | Review and potentially remove |\n| Potential stale service accounts | Active assignments not used | Investigate and decommission |\n\n## Validation Checklist\n\n- [ ] All permanent privileged role assignments converted to eligible (except break-glass)\n- [ ] Break-glass accounts configured as active with monitoring alerts\n- [ ] MFA required for all role activations\n- [ ] Approval workflow configured for Global Administrator and Security Administrator\n- [ ] Maximum activation duration set to 8 hours or less for critical roles\n- [ ] Eligible assignments expire after 6 months (requires re-certification)\n- [ ] Justification and ticket information required for activations\n- [ ] Email notifications configured for role assignments and activations\n- [ ] Access reviews scheduled quarterly for all privileged roles\n- [ ] PIM alerts enabled and reviewed weekly\n- [ ] Audit logs forwarded to SIEM for monitoring\n\n## References\n\n- [Microsoft Entra PIM Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-configure)\n- [Plan a PIM Deployment](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-deployment-plan)\n- [Start Using PIM](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fid-governance\u002Fprivileged-identity-management\u002Fpim-getting-started)\n- [Microsoft Graph PIM API](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fprivilegedidentitymanagementv3-overview)\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"mitre_f3":36,"nist_csf":57,"subdomain":62,"description":7,"mitre_attack":63},[26,27,28,29,30,31,32],"azure-ad","pim","entra-id","just-in-time","privileged-roles","identity-governance","zero-trust","mahipal","cybersecurity","1.0",{"tactics":37,"version":41,"techniques":42},[38,39,40],"initial-access","positioning","defense-impairment","1.1",[43,47,51,54],{"id":44,"name":45,"source":46,"tactic":38},"F1006","Account Takeover","f3",{"id":48,"name":49,"source":50,"tactic":38},"T1110.003","Brute Force: Password Spraying","attack",{"id":52,"name":53,"source":46,"tactic":39},"F1005","Account Manipulation",{"id":55,"name":56,"source":46,"tactic":40},"F1005.002","Account Manipulation: Add Authorized User",[58,59,60,61],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[64,65,66,67],"T1078","T1110","T1556","T1098","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-azure-ad-privileged-identity-management",{"tool":81,"command":82},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-azure-ad-privileged-identity-management",{"tool":84,"command":85},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-azure-ad-privileged-identity-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002FSKILL.md",true,[89,95,99,105,109,113,119],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",1979,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fassets\u002Ftemplate.md",{"path":96,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",1951,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fstandards.md",2034,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fstandards.md",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworkflows.md",3880,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Freferences\u002Fworkflows.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fagent.py","SCRIPT","脚本",6070,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fscripts\u002Fagent.py",{"path":120,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fprocess.py",8510,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-azure-ad-privileged-identity-management\u002Fscripts\u002Fprocess.py",[124,131,138,145,152,159],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]