Forum Discussion
Unable to Add Tabs to Chats Consistently in Teams via GraphAPI
MicrosoftThe error message shows that the user ID c0cfdd6b-d64d-42e1-8111-0881725f68ff doesn't match any user in your tenant. This might happen if the user ID is wrong or if the user has been deleted. Please double-check the user ID and make sure it exists in your Azure Active Directory (AAD).
If the user ID is correct, check that your application has the right permissions to access user details in AAD. Sometimes, not having enough permissions can cause this error.
The error with "teamsApp @ odata . bind" suggests there might be a syntax issue in your request. Make sure the property name is formatted correctly. For example, it should look like this: "teamsApp@odata.bind": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/{appId}".
Don't forget to replace {appId} with the actual ID of the Teams app you want to bind.
Hey Nivedipa-MSFT !
Where is this user coming from? As I said, we're trying to add a tab to a chat via a GraphAPI call using application (and not delegated) permissions.
We didn't change anything on our tenants and it stopped working on all our tenant at the same time. Could it be related to a change on your side?
There is no error with email address removed for privacy reasons, it's just this forum that removed it from my initial message because it looks like an email address. There can't be any error associated with that, this is the JSON payload that we send.
- Nivedipa-MSFT
@CedricZimmermann - Could you please share the request ID, timestamp, and tenant ID for the failed request so we can investigate further?
Hello Nivedipa-MSFT !
Here is the last error I could find in our logs from today in our UAT environment, teams tenant 40d01032-a5c1-460a-844e-0721307479b4:GraphAPI error : Failed to execute MsGraph backend request GetUserLicenseDetailsS2SRequest. Workload MsGraph_DirectoryServices. Request Url: https://graph.microsoft.com/v1.0/users//licenseDetails?$select=skuId,skuPartNumber,servicePlans, Request Method: GET, Response Status Code: NotFound, Response Headers: Strict-Transport-Security: max-age=31536000 request-id: d83b9df4-e31b-4b6d-9453-cc786e21bfce client-request-id: d83b9df4-e31b-4b6d-9453-cc786e21bfce x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"Central US","Slice":"E","Ring":"4","ScaleUnit":"000","RoleInstance":"DS1PEPF0002A0EC"}} x-ms-resource-unit: 1 Date: Tue, 06 May 2025 12:23:22 GMT , Reason Phrase: Not Found, Request ID 8A15845E396E4A7C9BDD79109C1A4D63.- Nivedipa-MSFT
@CedricZimmermann - We are actively checking with the engineering team for any updates on the issue. While there are no new updates at this time, we will inform you as soon as we have more information.
We appreciate your patience and understanding in the meantime. Thank you for bringing this to our attention.