MS Graph create Team Error

Copper Contributor

Hello, I am creating a group (api /v1.0/education/classes) and it works perfectly. With the ID of this group, I am trying to create a team (api /v1.0/groups/{idGroup}/team), however, the call is returning the following error:

 

 

 

 

{"error":{"code":"BadRequest","message":"Failed to execute MsGraph backend request UpdateGroupS2SRequest. Workload MsGraph_DirectoryServices. Request Url: https://graph.microsoft.com/beta/groups/14a6f63b-b750-4062-9f96-ed47213f8de9, Request Method: PATCH, Response Status Code: BadRequest, Response Headers: Strict-Transport-Security: max-age=31536000\r\nrequest-id: 742c4cce-63dd-44ff-b73e-35a5ac523a26\r\nclient-request-id: 742c4cce-63dd-44ff-b73e-35a5ac523a26\r\nx-ms-ags-diagnostic: {\"ServerInfo\":{\"DataCenter\":\"Central US\",\"Slice\":\"E\",\"Ring\":\"2\",\"ScaleUnit\":\"003\",\"RoleInstance\":\"DS1PEPF0001605E\"}}\r\nx-ms-resource-unit: 1\r\nDate: Wed, 27 Dec 2023 21:52:25 GMT\r\n, Reason Phrase: Bad Request, Request ID E4F0F69575B64A549A027DB93379A2E4.","innerError":{"code":"BadRequest","message":"Failed to execute MsGraph backend request UpdateGroupS2SRequest. Workload MsGraph_DirectoryServices. Request Url: https://graph.microsoft.com/beta/groups/14a6f63b-b750-4062-9f96-ed47213f8de9, Request Method: PATCH, Response Status Code: BadRequest, Response Headers: Strict-Transport-Security: max-age=31536000\r\nrequest-id: 742c4cce-63dd-44ff-b73e-35a5ac523a26\r\nclient-request-id: 742c4cce-63dd-44ff-b73e-35a5ac523a26\r\nx-ms-ags-diagnostic: {\"ServerInfo\":{\"DataCenter\":\"Central US\",\"Slice\":\"E\",\"Ring\":\"2\",\"ScaleUnit\":\"003\",\"RoleInstance\":\"DS1PEPF0001605E\"}}\r\nx-ms-resource-unit: 1\r\nDate: Wed, 27 Dec 2023 21:52:25 GMT\r\n, Reason Phrase: Bad Request, Request ID E4F0F69575B64A549A027DB93379A2E4.","details":[],"date":"2023-12-27T21:52:25","request-id":"9798e5df-3145-4d82-9df1-c4035f453dc1","client-request-id":"9798e5df-3145-4d82-9df1-c4035f453dc1"}}}

 

 

 

 

I have done other integrations of this type, but this is the first time I am encountering this problem. Has anyone else experienced this? Were you able to resolve it?

Best regards,

9 Replies
Thanks for raising your query.
We will look into it and let you know the updates.

@rodsilvanascimento - We checked this at our end and we are able to create team from the class successfully. Please give few minutes delay, so that in the backend it creates the group so as to avoid any sync issues.

 

Created class - 

MeghanaMSFT_0-1704191569270.png

 

Creating team directly from the group gave an error saying "

Team owner not found for group". We added owner to the group like below. 
MeghanaMSFT_1-1704191923854.png

 

Then we were able to create team from above group.

MeghanaMSFT_2-1704191978869.png

 

 

MeghanaMSFT_3-1704192150084.png

 

Could you please try creating team after few minutes of delay and let us know if you are still facing the issue.
How long should I wait? I set a 10-minute interval, but the problem still occurred.

@rodsilvanascimento - According to the doc, If the group was created less than 15 minutes ago, the call might fail with a 404 error code due to replication delays - https://learn.microsoft.com/en-us/graph/api/team-put-teams?view=graph-rest-1.0&tabs=http#:~:text=If%....

 

Please try after 15 minutes and if you still face the issue, please share the client request id, timestamp for the failed requests.

Still same problem,

 

Timestamp 1704286497 

 

Erro na criação da equipe 'TURMA6'. IdTeams: 0debfe8b-b04d-420b-b51c-0ab2085055bc: Failed to execute MsGraph backend request UpdateGroupS2SRequest. Workload MsGraph_DirectoryServices. Request Url: https://graph.microsoft.com/beta/groups/0debfe8b-b04d-420b-b51c-0ab2085055bc, Request Method: PATCH, Response Status Code: BadRequest, Response Headers: Strict-Transport-Security: max-age=31536000
request-id: b653082e-911e-411d-ac3a-6cc8a864c777
client-request-id: b653082e-911e-411d-ac3a-6cc8a864c777
x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"East US","Slice":"E","Ring":"5","ScaleUnit":"001","RoleInstance":"MN1PEPF0001085B"}}
x-ms-resource-unit: 1
Date: Wed, 03 Jan 2024 12:53:37 GMT
, Reason Phrase: Bad Request, Request ID 7D5E0C1C58284C518E69B2C6025EC8A5.

An incident has been raised to check why the call failed with 400. We will keep you updated.
Any updates on this matter? Thanks.
Unfortunately, we do not have any update/ETA to share. We are following up with the engineering team. We will keep you posted.