Get Existing Group Error: Resource not found for the segment 'https:'

[mptherefore]

Bicep version
Bicep CLI version 0.38.33 (6bb5d5f859)

Resource and API version
"microsoftGraphV1": "br:mcr.microsoft.com/bicep/extensions/microsoftgraph/v1.0:1.0.0"

extension microsoftGraphV1
resource existingGroup 'Microsoft.Graph/groups@v1.0' existing = {
uniqueName: 'GroupUniqueName'
}

output existingGroup string = existingGroup.id

The actual deployment used a different group name.

Auth flow
Interactive

Deployment details
The tracking id is '81148791-c8f2-4e4b-ab1b-4b5814316ad7'.
Graph client request id: 4fd96728-6681-41e3-b404-fee3f08a23d9.

Describe the bug
I have the same group defined for different environments in Entra without using bicep. I have set the uniquename for all of them manually using "update-MgGroup -GroupId -UniqueName GroupUniqueName".
When getting those existing groups via bicep some are working fine but for others I always receive the same error:
"message":"Resource not found for the segment 'https:'.

To Reproduce
Currently unknown because some groups are working fine with manually assigning the uniquename and others are not working.

[eketo-msft]

Hey @mptherefore -- to help isolate the problem, is this happening only for groups with more than 20 owners (or members)? Can you share the tenantId and group id of an impacted group and I can try to look up the data.

[mptherefore]

Hey @eketo-msft,
thanks for getting back.
The tenant ID is f489a09f-1232-43b8-883d-74019d7510b3.
The Group ID is 9560fd9f-0b41-4c56-be19-8ab03bfb401f.
As far as I can see all the groups that are not working have more than 20 members. The one that is working only has two (group id 8c1be598-94f4-4d08-b9d1-31518ff797d4).
But I cannot reproduce the behavior so far with a new group created via admin center that has more than 20 members.

[eketo-msft]

@mptherefore, thank you for the details.

I think I've identified the bug here, but it doesn't make sense why a new group created w/ over 20 members would be successful. Can you send me the successful group to validate?

[mptherefore]

Hey @eketo-msft,
the working group id is: 619bd0af-9c3a-4738-acde-a5cc412efb97
this is the group that I created for testing having 73 managed identities as members. I just tested it again and it is still working.

[eketo-msft]

@mptherefore, thanks! I'll take a look. In the meantime, are you using the same relationshipMetadata to manage the two groups?

[mptherefore]

@eketo-msft, I'm sorry, can you explain what exactly you mean?

[eketo-msft]

Disregard. I have a fix merged which should address the problem. It will be a couple weeks for the fix to be deployed due to timing of deployments and holidays. I'll circle back here when the fix is out.

[mptherefore]

thanks a lot! sounds good!

[mptherefore]

Hey @eketo-msft,
any update on when the fix will be rolled out?
Thanks

[eketo-msft]

@mptherefore this rollout for this fix just completed this week. Can you confirm the scenario is working now?