Why doesn't the Power Platform AAD Security Group team get a default queue?

[HarryG]

Microsoft documentation for Queue tables claims that "a private queue is automatically created for each new user or team" on this webpage: Queue tables (Microsoft Dataverse) - Power Apps | Microsoft Docs

However, whenever I create an AAD Security Group team, there is no default queue created. I was really hoping to use team queues associated with AAD teams. Users and other types of teams get a default queue, so why doesn't this type get one? Thanks.

[cchannon]

It's not an Owner Team; it can't own records.

[HarryG]

The plan is to share records with the AAD team and put the records in their queue. They don't need to own them. I've already tested assigning records to both user queues and Owner team queues without changing record ownership, so I know that in theory the AAD team would not need to own the records to see them in their queue, if they had one. Thanks.

[Joe_Laz]

Thanks, HarryG. I have the same question. After reading through Queue tables (Microsoft Dataverse) - Power Apps | Microsoft Docs, a private queue is automatically created for each new user or team. I don't know the answer, but my guess would be you don't have access to this private queue. 

Let me know if you find a solution.

Thanks,

[HarryG]

Thanks for the suggestion, Joe_Laz, but I am a system administrator in this environment, and I am the one who created the AAD team. I can see the default queues of owner teams that I have created, so it makes sense that I should see the default queues of AAD teams that I have created. If they exist but are hidden even from system administrators, then I would call that a bug. 

[simonpritchard]

Hi - did you get a resolution to this in the end? I've come across the same issue today. If this can't be done, to my mind it kind of defeats the object of AAD Teams as an option?

[HarryG]

No, I didn't get a good answer to this yet. I have created a Microsoft support request, so I am still waiting to get a response to that. 

The only workaround I can think of is to manually create a queue with the same name as the AAD team and then make the AAD team the owner of the queue. This at least gives the team access to the queue, but membership between the queue and the AAD team will not be synchronized automatically. Clearly this is not ideal.

I'll give an update when I hear back from Microsoft.

[HarryG]

I finally got the following response from Microsoft:

AAD Security group’s main objective is to manage security roles and privileges among a group of users, it is not currently considered to be used as an actual team on the service application. Because of that, we don’t currently grant AAD security groups a default queue. Our recommendation is to open an idea via the Ideas website. These ideas can be voted on and will be reviewed by our Dynamics Product Group teams, and many have been implemented after being voted on.

And on the Ideas site, I found that someone else already suggested this idea a year ago, so I upvoted it. Please upvote the idea when you get a chance. Thanks!
Microsoft Idea (dynamics.com)

[SBax]

I have a suggested workaround for this limitation.

• Create your Azure AD group
• Create an owner team (not linked to Azure AD group, a regular owner group)
• Create a flow that runs on a schedule (say once every 24 hours) the flow should list members of the Azure AD group, find the equivalent power platform user, check if they are a member of a team, and if not, add them to the team

Happy to discuss in more detail if you think this solution might suit

[MartinKarlsson]

Hello,
We are very interested in a flow like that, how would we go about in doing that?