Microsoft Entra Agent ID Skill for Planning Agent Identities in Codex
Map an agent type and its instances to Microsoft Entra identity objects. Document the sponsor, permissions, and audit boundaries before any tenant operation.
中文Setup for Codex
Use Codex with the Azure Skills plugin for access to Microsoft documentation. A planning example needs only fictional requirements. Real provisioning requires Microsoft Graph tooling and an appropriate Entra role.
- Install the publisher's Azure Skills package with `apm install microsoft/azure-skills`, then open the project in Codex.
- Select $entra-agent-id and provide the intended agent types, instance names, sponsors, and resource access. Keep the exercise at architecture stage.
Example task
Ask $entra-agent-id to diagram two fictional reports assistants that share one agent type and require distinct audit trails. Give each a separate sponsor and scope the exercise to documenting the identity object model and least-privilege review. Make it a read-only design.Expected result
The diagram contains one Blueprint, its BlueprintPrincipal, and two distinct agent identities with a sponsor and permission-review entry for each.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Which Entra objects distinguish one agent type from its individual instances?
The Blueprint describes the type, the BlueprintPrincipal represents it in the tenant, and a separate Agent Identity represents each instance.