Microsoft.Graph/groups relationship updates fail
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- azure, typescript
Línea de trabajo
The failing behaviour is in Microsoft Graph's handling of group owners and members relationships during Bicep deployments, not in this repository's TypeScript type definitions, so start by checking whether the generated types under the repo's types directory describe the relationship schema for Microsoft.Graph/[email protected]. Reproduce with the three groups in the issue body and observe that the deployment needs several reruns. Done would be a documented or fixed explanation of the intermittent Failed to update one or more relationships error, which likely needs Graph service knowledge.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Microsoft.Graph/groups relationship updates fail
Bicep version
Azure CLI version:
2.91.0
Microsoft Graph Bicep extension:
"microsoftGraphV1": "br:mcr.microsoft.com/bicep/extensions/microsoftgraph/v1.0:1.0.0"
Resource and API version
Microsoft.Graph/[email protected]
Auth flow
The deployment is automated and uses an application registration with the following Microsoft Graph application permissions:
Group.ReadWrite.AllUser.Read.All
Describe the bug
When deploying Microsoft.Graph/[email protected] resources with owners and members relationships, the deployment does not successfully configure all relationships on the first attempt.
The exact same deployment must be run multiple times. Each deployment progresses further:
- First deployment fails on
ownerGroup.owners - Second deployment fails on
contributorGroup.members - Third deployment fails on
readerGroup.members - Fourth deployment succeeds
The deployment template has worked successfully for approximately six months, but started failing around 30 October 2026 without any changes to the template or application permissions.
To Reproduce
Use the following Bicep resources:
resource ownerGroup 'Microsoft.Graph/[email protected]' = {
displayName: ownerGroupName
description: 'Access for owners to ${landingZoneName} (${environment}) landing zone'
mailEnabled: false
mailNickname: take(ownerGroupName, 64)
securityEnabled: true
uniqueName: ownerGroupName
owners: {
relationshipSemantics: 'append'
relationships: [for owner in groupOwners: owner.objectId]
}
}
resource contributorGroup 'Microsoft.Graph/[email protected]' = {
displayName: contributorGroupName
description: 'Access for contributors to ${landingZoneName} (${environment}) landing zone'
mailEnabled: false
mailNickname: take(contributorGroupName, 64)
securityEnabled: true
uniqueName: contributorGroupName
owners: {
relationshipSemantics: 'append'
relationships: [for owner in groupOwners: owner.objectId]
}
members: {
relationshipSemantics: 'append'
relationships: [
ownerGroup.id
]
}
}
resource readerGroup 'Microsoft.Graph/[email protected]' = {
displayName: readerGroupName
description: 'Access for readers to ${landingZoneName} (${environment}) landing zone'
mailEnabled: false
mailNickname: take(readerGroupName, 64)
securityEnabled: true
uniqueName: readerGroupName
owners: {
relationshipSemantics: 'append'
relationships: [for owner in groupOwners: owner.objectId]
}
members: {
relationshipSemantics: 'append'
relationships: [ownerGroup.id, contributorGroup.id]
}
}
Run the deployment.
Run the same deployment again without making any changes.
Repeat until the deployment succeeds.
Expected
The initial deployment should create the groups and configure all owners and members relationships successfully.
Deployment details
First deployment — ownerGroup owners relationship fails
{
"code": "DeploymentOperationFailed",
"message": "{\"error\":{\"code\":\"BadRequest\",\"target\":\"/resources/ownerGroup\",\"message\":\"Failed to update one or more relationships in 'owners'. Please try again later. Graph client request id: 26151cf5-76f5-4669-a916-a80318b2d3e2. Graph request timestamp: 2026-11-02T12:51:23Z.\"}}"
}
Deployment correlation ID:
87e27afa-6587-4f74-b16d-ba2b6aba5f4f
Microsoft Graph client request ID:
26151cf5-76f5-4669-a916-a80318b2d3e2
Graph request timestamp:
2026-11-02T12:51:23Z
Second deployment — contributorGroup members relationship fails
Running the exact same deployment again succeeds for the ownerGroup owners relationship, but then fails when updating the members relationship of contributorGroup.
{
"code": "DeploymentOperationFailed",
"message": "{\"error\":{\"code\":\"BadRequest\",\"target\":\"/resources/contributorGroup\",\"message\":\"Failed to update one or more relationships in 'members'. Please try again later. Graph client request id: a1755a1b-f1e9-454b-8522-15bbf54c61f4. Graph request timestamp: 2026-11-02T13:21:14Z.\"}}"
}
Deployment correlation ID:
aa9acd01-0e32-485e-a66f-0fde78fefea8
Microsoft Graph client request ID:
a1755a1b-f1e9-454b-8522-15bbf54c61f4
Graph request timestamp:
2026-11-02T13:21:14Z
Third deployment — readerGroup members relationship fails
Running the exact same deployment a third time succeeds for the previous relationships, but then fails when updating the members relationship of readerGroup.
{
"code": "DeploymentOperationFailed",
"message": "{\"error\":{\"code\":\"BadRequest\",\"target\":\"/resources/readerGroup\",\"message\":\"Failed to update one or more relationships in 'members'. Please try again later. Graph client request id: 8653f8f6-fa0f-4cf0-93b7-0bedc8fc7c3f. Graph request timestamp: 2026-11-02T13:55:05Z.\"}}"
}
Deployment correlation ID:
aa6ccda3-7adf-4cf0-86e5-cbcd809a56cc
Microsoft Graph client request ID:
8653f8f6-fa0f-4cf0-93b7-0bedc8fc7c3f
Graph request timestamp:
2026-11-02T13:55:05Z
Fourth deployment — successful
Running the exact same deployment a fourth time succeeds and all relationships are configured successfully.
Deployment correlation ID:
07d0dd2f-0985-41b1-a662-d8f471111e59
- Lenguaje dominante
- TypeScript
- Estrellas
- 82
- Forks
- 15
- Merge medio
- 5 h 12 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoftgraph/msgraph-bicep-types
-
Cannot deploy groups using bicepAbiertobug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
microsoftgraph/msgraph-bicep-types#334 · 2 comentarios ·
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 12/100
microsoftgraph/msgraph-bicep-types#328 · 1 reacción ·
-
Intermittent servicePrincipal creation failure with OwnedBy: backing application must be in local tenant despite being created therePosiblemente ocupada @FehintolaObafemi la tomó hace 22 días. AbiertoNeeds: Attention :wave:
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
microsoftgraph/msgraph-bicep-types#324 · 3 comentarios · 1 asignado ·
-
Docs: Add note about full-name + uniqueName requirement to applications/federatedIdentityCredentialsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 35/100
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
microsoftgraph/msgraph-bicep-types#311 · 3 comentarios ·
Todos los issues de microsoftgraph/msgraph-bicep-types
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
fb55/htmlparser2#2579 ·
Los mantenedores suelen responder en 1 día
-
bug good first issue needs-review
Dificultad 1/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
Add Module DB RulesAbiertodocumentation public
Dificultad 1/5 1-3 horas Aptitud para principiantes 68/100
midnightntwrk/umbradb#65 ·
Los mantenedores suelen responder en 2 días
-
area/channels kind/bug priority/medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nanocoai/nanoclaw#4501 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Docker images: plain X.Y.Z tag (e.g. 7.2.3) is never updated after the initial release buildAbiertoneeds verification
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 13 días