As part of moving to general availability (GA) for Entra Agent ID, agent blueprints, agent blueprint principals, and agent identities only accept dynamic membership groups and Microsoft 365 groups as group-type sponsors. In addition, role-assignable groups were supported during the Agent ID public preview but aren’t included in the GA release.
Why we’re making this change
Sponsors are a critical attribution mechanism in Agent ID. When an admin or automation queries “who is responsible for this agent?” or “which agents is this user responsible for?”, the sponsor relationship must resolve quickly and reliably to ensure a good experience.
We’re making these changes to ensure the best performance while still enabling customers to use groups as sponsors of their Agent ID objects. Dynamic membership groups and Microsoft 365 groups are optimized for the patterns that sponsors require. By narrowing the supported set, we ensure that these operations remain fast and predictable as Agent ID adoption grows.
What this means for you
- New sponsor assignments must use dynamic membership groups or Microsoft 365 groups. Attempts to assign other group types as sponsors will be rejected.
- Existing sponsors from other group types that are already set on your agent identities or blueprints continue to function. No customer action is required.
- Individual users remain fully supported as sponsors, with no changes.
Recommended action and next steps
If your current workflows assign fixed-membership security groups or role-assignable groups as sponsors, transition to dynamic membership groups or Microsoft 365 groups before your next provisioning cycle. For details about how to configure sponsors, see Administrative relationships in Entra Agent ID.
We continue to accelerate the pace of development in Agent ID and Entra ID, and we plan to add support for new group types as Agent ID sponsors later this year. We also listen to customer feedback and will evaluate the priority of supporting role-assignable groups in the future. Watch this blog for updates!
The post Sponsor group type requirements for agent identities appeared first on Microsoft 365 Developer Blog.