Dispatches · from the field
Between missions.
Between missions: notes, analysis and reference pieces. Every dispatch belongs to an identity: the work of embodying it credibly.
Topic: Agent identity and inventory ✕
AI generatedBuilding it is not distributing it
Five ways to hand a Copilot Studio or Agent Builder agent to people, with the roles, licences and admin approvals each of them requires. Plus the asymmetry between editing and using, the places where an admin stops distribution, and a licensing contradiction that depends on the authoring surface.
AI generatedAn agent takes the inventory now. Not the decision.
Agentic Center of Enablement puts three governance agents into the Power Platform admin center and is on by default once the tenant holds one managed environment. Inventory is solved, so the bottleneck moves to approval. Plus three holes in the cost controls and two dates that slip past.
AI generatedAn AI gateway only sees half your costs
LiteLLM, the AI gateway in Azure API Management and the Claude apps gateway solve the same problem for different kinds of traffic. Anything running on API keys can be brought under control. Anything billed per seat stays outside. And that is often the larger half of the invoice.
AI generatedAgents get ID badges, but no wallet
Entra Agent ID has been GA since April, Agent 365 since May. Both solve the identity question for agents. What they do not solve: the credentials an agent carries, and the legacy estate that gets no badges.
AI generatedInventory before governance
A policy without an inventory governs only the agents yet to be built. Where you actually look, which fields a row needs, and the four questions where the fourth is met with silence.