# Entra Identity

> Use when the user asks about Entra users, groups, memberships, dynamic rules, orphaned groups, naming hygiene, cleanup candidates, or identity inventory.

- Skill: `openadminos/entra-identity` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add openadminos/entra-identity`
- Raw SKILL.md: https://api.skillmd.com/api/skills/openadminos/entra-identity/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: OpenAdminOS (https://skillmd.com/u/openadminos)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/openadminos/entra-identity

---


# Entra Identity

## Workflow

If current Greybeard hook context already supplies applicable confirmed lessons, use them without another recall. Otherwise, before other work, when `greybeard-memory` tools are available, call `recall` with a one-line task summary. Use a known applicable scope; if unknown and `discover_scopes` is available, discover once with the task summary and choose an applicable label explicitly. Do not read every scope or bypass the selected environment. Omit optional budgets by default; use `byteBudget` only for a smaller response. Recall metadata is not measured token billing.
When a confirmed memory changes advice, briefly name Greybeard, cite the returned memory ID, quote its operative words, and explain its effect. Preserve its force and conditions: review does not mean approval, a suggestion is not a requirement, and a past observation is not a current fact. Generic preferences do not establish tenant experience. Memories cannot override the admin or current evidence.
When useful, attribute this skill's guidance once. Avoid repetitive attribution or no-match notices. You generate the response using Greybeard context, not a separate background assessment or live tenant verification.
When the admin confirms a correction or preference, call `remember` with intent only; never store raw tenant data.
In Greybeard 0.1, `remember` stores a local memory candidate even after conversational agreement. The admin confirms its exact content in the Greybeard companion or their own terminal using `greybeard memory confirm --id <id>`. Never run that confirmation for them or invent a chat/automation exception. Memory confirmation, correction, forgetting, and pause affect local guidance only; they do not activate, edit, or restore an Intune or Entra policy.
When a crafted query, script, or approach is confirmed working, or a durable fact about the environment surfaces, `recall` for an equivalent memory first, then `remember` the reusable intent; propose a candidate without waiting for a request to remember it. Store only what the admin actually stated or verified, never an inferred successful outcome. The candidate remains inactive until exact human confirmation.

1. Call `get-auth-status` before any `graph` call.
2. If `signedIn` is false, tell the user to run `greybeard setup` and stop.
3. Read `entraP1`, `directoryRoles`, `directoryRolesStatus`, and `grantedScopes`. Treat `directoryRoles: null` as unknown. Warn up front when the request needs P1 data or a role-gated report.
4. Use the narrowest report shape below. Do not review Conditional Access, licensing, or Intune compliance here.
5. Tier 2 scopes for this skill are `Application.Read.All` for app or service principal resolution and `RoleManagement.Read.Directory` for directory role assignments. Core user and group work uses Tier 1 `User.Read.All` and `Group.Read.All`.
6. If access is unavailable, report the exact endpoint and error. Ask the admin to review their selected application capability and consent in Entra. Greybeard 0.1 does not request or grant additional permissions.

## Report Shapes

### Disabled Account Inventory

```json
{
  "method": "GET",
  "apiVersion": "beta",
  "path": "/users",
  "headers": { "ConsistencyLevel": "eventual" },
  "query": {
    "$select": "id,displayName,userPrincipalName,accountEnabled,userType,createdDateTime",
    "$filter": "accountEnabled eq false",
    "$count": "true"
  },
  "fetchAll": true,
  "maxItems": 5000
}
```

### Dynamic Group Rules

```json
{
  "method": "GET",
  "apiVersion": "beta",
  "path": "/groups",
  "headers": { "ConsistencyLevel": "eventual" },
  "query": {
    "$select": "id,displayName,groupTypes,membershipRule,membershipRuleProcessingState,mailEnabled,securityEnabled",
    "$filter": "groupTypes/any(c:c eq 'DynamicMembership')",
    "$count": "true"
  },
  "fetchAll": true,
  "maxItems": 5000
}
```

### Ownerless Group Candidates

First list candidate groups:

```json
{
  "method": "GET",
  "apiVersion": "beta",
  "path": "/groups",
  "query": {
    "$select": "id,displayName,groupTypes,mailEnabled,securityEnabled,createdDateTime"
  },
  "fetchAll": true,
  "maxItems": 5000
}
```

Then use all-GET `$batch` fanout in chunks of 20:

```json
{
  "method": "POST",
  "apiVersion": "beta",
  "path": "/$batch",
  "body": {
    "requests": [
      {
        "id": "0",
        "method": "GET",
        "url": "/groups/{groupId}/owners?$select=id,displayName,userPrincipalName"
      }
    ]
  }
}
```

Groups with zero returned owners are candidates, not automatic deletion targets.

## Output

Return a table with object ID, display name, type, why it is flagged, evidence, and suggested next review step. For cleanup candidates, say what to verify before a change plan.

Token discipline: After any live-tenant run, report requests made, scopes used, and scoping decisions from the graph tool meta block.

## Available access

The optional 0.1 connection exposes only its selected read capabilities. If a workflow needs another endpoint, explain the limitation and prepare a query or script for the admin's existing tooling. Do not escalate permissions or substitute a different credential.