This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 92%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAV%3C/text%3E%3C/svg%3E)
We use MS graph calls with an app-only token during our provisioning process. In this case we have an M365 Group which we want to promote to a team using this graph query:
https://graph.microsoft.com/v1.0/groups/602ab03c-0cf5-4474-a58c-551deab98e17/team
We use this daily on multiple tenants but since today we see errors happening on some of our (targeted) tenants. We get these type of 401 Unauthorized errors:
Failed to execute MS Graph backend request GetUserFromIdRequest. The server failed to respond correctly. Response Code: Unauthorized, Reason: Reason: Unauthorized, Correlation headers: request-id: 24ba537d-12c8-451e-9767-d51fe8b757b8
client-request-id: 08B1A315115A413F99C749D7EAFCA709
x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"Sweden Central","Slice":"E","Ring":"5","ScaleUnit":"000","RoleInstance":"GVX0EPF00005355"}}
Date: Fri, 20 Oct 2023 07:25:11 GMT
We have a retry mechanism which retries every hour but up untill now no success.
Any ideas?
This behavior is also seen at 2 of our Targeted Release Tenants. At this moment we are not able to automate the Teams creation based on Teamify a Microsoft365 Group.
Could someone at Microsoft please let us know if they see such issue at more tenants and even more important when this will be fixed.
Thanks in advance!
Hi @Ad van den Berg
Please use JWT.ms to parse your access token and share the screenshot.
Hi CarlZhao, thank you for the response. We still see the issue in the past hours, so still a on going issue.
Hereby the screenshot of the accesstoken of one of the tenants. Hopefully it helps you identify the problem. If you need some more information please let me know.
Kind regards,
Sander
PS: I could not mention you but hopefully you get a message of this post
Hi @CarlZhao-MSFT we use the same type of token as Sander did. We're also still experiencing the issue. So you can take his token data for further analysis.
Thanks in advance!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 53%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
We have exactly the same problem, even with Directory.ReadWrite.All permissions. It works with a delegated account but not in an application context. As this feature is crucial for us, we need to get this fixed or need a workaround as soon as possible.
@Sander @Ad van den Berg @C4Fritsch
Try granting your application service principal the Microsoft Teams service administrator or global administrator role.
Hi Carl,
We still get the same error, even after providing both Teams administrator and global administrator role to our application
Details = Failed to execute MS Graph backend request GetUserFromIdRequest. The server failed to respond correctly. Response Code: Unauthorized, Reason: Reason: Unauthorized, Correlation headers: request-id: 3fc8896a-6dfd-4db1-8350-da2b18234325
client-request-id: 75C695E923BC406B8955CDBC1FF99572
x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"Sweden Central","Slice":"E","Ring":"5","ScaleUnit":"002","RoleInstance":"GV3PEPF00000BF8"}}
Date: Mon, 23 Oct 2023 10:23:47 GMT
(Unauthorized)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 59%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
We have exactly the same problem. We can verify that this worked until Oct 16th 2023 and was first noticed on Oct 19th.
Hi @Henry Scheinin and @C4Fritsch doe you also only see this behavior in Microsoft tenants which are set to Targeted release (first release)?
On our side we have some other tenants set at Standard Release in which we do not see this behavior.
Sander we currently see this in only one tenant. Unfortunately I don't have access to release settings.
We saw it working on the 19th early morning (CET) and stopped working on the 20th early morning (CET) on both of our tenants where we currently see the issue. Because we have nightly repeating runs and tests we're sure it wasn't an issue before with all the same configuration in place.
@CarlZhao-MSFT, we also have a Microsoft case pending with the id 2310230050004736
Maybe if you need some more information like Fiddler trace you can find it within that case.
@Sander Its exaclty like you described. The tenant which is set to get updates as soon as possible has the issue while other tenants that use the standard release do not. We also got this problem the first time on the 20th (CET). Seems like something broke with the latest update on Microsofts side @CarlZhao-MSFT
Just had a call with Microsoft and they will escalate this call to their product team. Should have some answers within at least 3 days.
It is working with delegated permissions but not with application permissions.
Are there any updates from Microsoft product team?
Hi @Henry Scheinin unfortunatelly no update from the Microsoft product team. The only updates I get, when requesting it, is they have issues with their support and it will take an additional 3 days to answer :-(
On our side the issue still remains on the targeted release tenants. Luckilly not yet on the standard release tenants. Hopefully they will not push this functionality to the standard release tenants....
We did not found a workaround using application permissions. Only manual promoting a group to a team is working OK and using delegated permissions is also working OK.
The issue looks solved since Friday.
No response yet by Microsoft but our regression tests are green again.