az ad group member list does not list service principals

Related command
az ad group member list

Describe the bug
az ad group member list does not list service principals.

To Reproduce
Run az ad group member list --group <group_name> on a group with members of type Service Principal.

Expected behavior
Returns all members of the group, including Service Principals.

Additional context

{
  "azure-cli": "2.37.0",
  "azure-cli-core": "2.37.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "account": "0.2.1",
    "aks-preview": "0.5.10",
    "application-insights": "0.1.13",
    "datafactory": "0.5.0"
  }
}

Is there a plan to fix this issue?

Currently I'm using:

GROUP_ID="GROUP_UUID"
az rest \
  --method get \
  --url https://graph.microsoft.com/beta/groups/$GROUP_ID/members |\
   jq '.value[] | select(.["@odata.type"] == "#microsoft.graph.servicePrincipal") | .id'

Jiashuo Li (@jiasli)

Could this be reopened Jiashuo Li (@jiasli) ? Thank you

Another google search that brings me to a posting of yet another quietly broken part of the API that requires using the beta duct tape endpoint workaround. Same issue for retrieving last login times. There are many examples of such cases that have been open for years. When they charge $6 per user per month, something seems very wrong here.
I loathe this API and the surprise breakages that occur every few months.

Jiashuo Li (@jiasli)

Hi Jiashuo Li (@jiasli), can this be reopened please?

I am facing the same issue

Can't believe such a basic check on a group membership for ANY type of member, is not possible...

I can't believe it too. I just faced the same issue, Google led me here. More than 3 years and no action from Microsoft...

Wow, this is incredible. Almost 4 years now and still facing this issue. Absolutely mental for such a basic action...! 🤣

jiasli reopened this 2 days ago

THERE IS HOPE FOLKS, HAVE FAITH! :D

This is a joke, right?!?
What a dumpsterfire...

I know this is not a solution but many people will find this page so just sharing a workaround to use:
az rest --uri https://graph.microsoft.com/beta/groups/[GROUPID]/members | jq .value[].displayName
az rest --uri https://graph.microsoft.com/beta/groups/a123b4cd-efg5-678h-9ijk-7392b165e6d5/members | jq .value[].displayName

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

please don't close it, it seems like a fairly reasonable request

I hate "+1" and "bump" messages like the next guy, but this ^ type of automation pushes users to create unnecessary noise just to keep issues opened.

Feels like the goal is to auto close the ticket and never fix the graphiapi. Azure/entra has a captive user base. What are they going to do, switch to something else over the lack of robust features?Sent from my iPhoneOn Mar 10, 2026, at 14:52, Florent Tatard ***@***.***> wrote:FlorentATo left a comment (Azure/azure-cli#22664) I hate "+1" and "bump" messages like the next guy, but this ^ type of automation pushes users to create unnecessary noise just to keep issues opened. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

I guess ms wants me to hear from myself. Is anyone working this bug? Why are you trying to close it every week?Sent from my iPadOn Mar 17, 2026, at 16:26, microsoft-github-policy-service[bot] ***@***.***> wrote:microsoft-github-policy-service[bot] left a comment (Azure/azure-cli#22664) Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

I guess it's easier to "act" like nothing happens and close this, instead of actually working on it, from Microsoft's/the Assignee's perspective. The time that's passed so far and the attitude towards the resolution of this issue, even with all of the people trying to raise the awareness on this thread, sincerely tells us that there is no desire at all to fix it. What a shame of an attitude, of a product quality and an overall experience towards such a small ask.

So, three years and nine months later...

Will microsoft be able to fix the bug in less than four years?

Is the fix still in beta?

do you ever wonder what the environmental impact is of

bot notes stale issue
bot emails everyone
someone turns up to poke the issue

I do. I bet it's non-negligible.

The bug is still present, four years after being explained to Microsoft.

Please correct the error. Yes, this defect actually matters for customers who use something called "computers".

do you ever wonder what the environmental impact is of

bot notes stale issue
bot emails everyone
someone turns up to poke the issue

I do. I bet it's non-negligible.

Not a fraction of the cost of

Non microsoft people detect the bug, and document the bug
Microsoft ignores the bug
More customers notice the bug and document the bug, surprised that it really is not corrected yet
Real human people beg Microsoft to fix their bug or explain a workaround or add a new API, or add a command line program with just one purpose, to work around the microsoft bug. Or at least update the documentation to explain that the api is broken, but they can't afford to hire a programmer to implement it.

Hi, I still have the issue with the lastest az cli.

Jiashuo Li (@jiasli)

As a workaround, you may use az rest to call beta API: https://docs.microsoft.com/en-us/graph/api/group-list-members?view=graph-rest-beta&tabs=http

Well, 4 years (minus 1 week) later, is there a chance we see the beta endpoint go GA anytime soon Jiashuo Li (@jiasli) ?

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Well, we haven't heard back from Microsoft in years on this issue...

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Navigation Menu

Repository navigation

`az ad group member list` does not list service principals #22664

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

az ad group member list does not list service principals #22664

Description

Activity

Shaked commented on Dec 10, 2023

FlorentATo commented on Jan 10, 2024

valberico commented on Nov 19, 2024

murphm54 commented on Feb 24, 2025

milosbithawk commented on Mar 10, 2025

DjangoLohn commented on May 1, 2025

Jarod-Felson commented on Dec 12, 2025

Sebastian-Negoescu commented on Feb 13, 2026

FlorentATo commented on Feb 15, 2026

GY-blangers commented on Feb 17, 2026

m3ngi3 commented on Feb 24, 2026

ncook-hxgn commented on Mar 3, 2026

FlorentATo commented on Mar 10, 2026

valberico commented on Mar 10, 2026

valberico commented on Mar 17, 2026

Sebastian-Negoescu commented on Mar 18, 2026

uffehellum-boeing commented on Apr 7, 2026

ncook-hxgn commented on Apr 15, 2026

uffehellum-boeing commented on Apr 15, 2026

uffehellum-boeing commented on Apr 15, 2026

pierrejeandev commented on May 22, 2026

FlorentATo commented on May 22, 2026

microsoft-github-policy-service commented on Sep 24, 2026

FlorentATo commented on Sep 26, 2026

microsoft-github-policy-service commented on Oct 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`az ad group member list` does not list service principals #22664