You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: add entra agent identity list command - #7592
Add entra agent identity list using the Microsoft Graph agent identity list endpoint, with optional --properties and default text output of ID and display name.
Register AgentIdentity.Read.All, add command docs and sidebar navigation.
Hi @mziada we require everyone to first get assigned to an issue before working on it. This keeps our backlog clean and up-to-date. This also prevents multiple people working on the same issue.
So please follow our guidelines if you want to contribute to the project. 🙏
The command returns only agent identity objects. Other types of service principals aren't returned.
A principal who creates an agent identity blueprint or blueprint principal is automatically assigned as the owner. Owners can create and modify agent identities associated with a blueprint they own without being assigned an Agent ID role. For nonowners to call this API in delegated scenarios using work or school accounts, the admin must be assigned a supported Microsoft Entra role. This operation supports the least-privileged built-in role **Agent ID Administrator**. For more information, see the [Microsoft Graph API documentation](https://learn.microsoft.com/en-us/graph/api/agentidentity-list).
Thanks for the heads-up. I missed the issue-assignment step before opening the PR.
Before we go further, I also want to be upfront about how this contribution was put together: AI agents produced the implementation and tests; I chose the issue and approved the PR submission. Would you be comfortable accepting a contribution made that way?
If so, could you assign issue #7254 to me so I can continue with PR #7592 and address the review feedback? If that approach doesn't fit the project's contribution rules, I understand and won't take it further.
While addressing the review feedback, I found a permissions discrepancy worth checking before changing the remarks. Issue #7254 and the automated review include Agent ID Developer, but the current Graph v1.0 and beta references list only Agent ID Administrator for nonowner delegated calls to list agent identities. The Entra role reference describes Developer as permitting blueprint creation and making the creator an owner.
Would you prefer that I retain Administrator for nonowner listing and document Developer separately as a blueprint-creation/ownership role, or is there another authoritative reference confirming Developer also supports nonowner listing?
Hi @milanholemans, just gently following up on the permissions question above when you have a moment. Would you prefer that I retain Agent ID Administrator for nonowner delegated listing and describe Agent ID Developer separately for blueprint creation/ownership? I’d appreciate your steering before updating the remarks. Thanks!
- Log the retrieval step to stderr before Graph calls in verbose mode
- Cover logging order, quiet output, state reuse and paginated results
- Add the command to the canonical discovery index
Thanks, @milanholemans. I've kept the existing Agent ID Administrator wording for nonowner delegated listing, following the Graph v1.0 list-operation reference, which does not list Agent ID Developer for this operation. I haven't verified Developer-role access in a live tenant, so I'm not claiming that a live test proved it unsupported.
I've also addressed the verbose logging and command-index feedback and added five tests. The local build, scoped lint, command help and 15 focused tests pass, with 100% command coverage (refreshed October 23). The full suite (16,178 tests) and production docs build passed on the same reviewed source on October 4. Upstream CI remains to be verified for the pushed revision.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
An active documentation issue remains because the remark omits the supported Agent ID Developer role and the required Microsoft Entra role-permissions reference.
The issue asks this remark to document both supported delegated roles and the Microsoft Entra role-permissions reference. This only names Agent ID Administrator and links to the Graph API page, so it omits the supported Agent ID Developer role and its documented scope.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Approval is blocked by an incomplete authorization note for the Agent ID Developer role and a critical test assertion that does not match the query-encoding behavior.
Thanks for the review. A couple of clarifications on the current revision:
Apostrophe assertion: the command removes single and double quotes from --propertiesbefore passing the value to formatting.encodeQueryParameter. The quote-free expected value therefore matches the implementation. I checked this with a focused reproduction: the assertion passes, and $filter remains part of the $select value rather than becoming a separate query parameter.
entra agent identity list|Retrieves a list of agent identities
Permissions documentation: following the earlier discussion with @milanholemans, the remarks retain Agent ID Administrator for nonowner delegated listing, based on the Graph list-operation reference. I haven’t verified Agent ID Developer access in a live tenant and am not claiming a live test proved it unsupported. If there’s an authoritative reference confirming that role supports this operation, I’m happy to revisit the wording.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The remarks document only Agent ID Administrator and omit the supported Agent ID Developer role and its scope, leaving delegated-access guidance incomplete.
The command returns only agent identity objects. Other types of service principals aren't returned.
A principal who creates an agent identity blueprint or blueprint principal is automatically assigned as the owner. Owners can create and modify agent identities associated with a blueprint they own without being assigned an Agent ID role. For nonowners to call this API in delegated scenarios using work or school accounts, the admin must be assigned a supported Microsoft Entra role. This operation supports the least-privileged built-in role **Agent ID Administrator**. For more information, see the [Microsoft Graph API documentation](https://learn.microsoft.com/en-us/graph/api/agentidentity-list).
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Approval is blocked by a moderate text-formatting bug that drops valid custom --properties values, along with documentation gaps about supported roles and output-mode behavior.
Using the `--properties` option, you can specify a comma-separated list of agent identity properties to retrieve from the Microsoft Graph. If you don't specify any properties, the command will output the default properties returned by Graph.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The documentation omits the required Agent ID Developer role and its limited blueprint/blueprint-principal scope, leaving delegated users with incomplete guidance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
entra agent identity listusing the Microsoft Graph agent identity list endpoint, with optional--propertiesand default text output of ID and display name.AgentIdentity.Read.All, add command docs and sidebar navigation.entra agent identity list#7254.Verification