Microsoft.Graph/groups relationship updates fail

オープン
#327 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
azure, typescript
領域
api, cloud

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

bug

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.All
  • User.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:

  1. First deployment fails on ownerGroup.owners
  2. Second deployment fails on contributorGroup.members
  3. Third deployment fails on readerGroup.members
  4. 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
主要言語
TypeScript
スター
82
フォーク
15
平均マージ
5時間 12分
マージ済み PR(30日)
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoftgraph/msgraph-bicep-types のほかの issue

microsoftgraph/msgraph-bicep-types の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。