Graph known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 4 May 2023 17:51 UTC

removing note for app context installation in chat

Microsoft's commit message in microsoftgraph/microsoft-graph-docs-contrib · commit 19297a5 · +0 −8 lines · also on GitHub

⋯ 448 unchanged lines

449449

450450 To solve this issue, remove the `/tenants/{tenant-id}` part from the URL before you call the API to access the cross-tenant shared [channel](/graph/api/resources/channel).

451451

452 −### TeamworkAppSettings permissions are not visible in the Azure portal

453 −

454 −The permissions TeamworkAppSettings.Read.All and TeamworkAppSettings.ReadWrite.All are currently being rolled out and might not be visible in Azure Portal yet. To consent to these permissions, please use an authorize request as follows:

455 −

456 −```http

457 −GET https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize?client_id={client-app-id}&response_type=code&scope=https://graph.microsoft.com/TeamworkAppSettings.ReadWrite.All

458 −```

459 −

460452 ### Create channel can return an error response

461453

462454 When you create a channel, if you use special characters in your channel name, the [Get filesFolder](/graph/api/channel-get-filesfolder) API will return a `400 Bad Request` error response. When you create a channel, make sure that the **displayName** for the channel does not:

⋯ 49 unchanged lines

Microsoft's Markdown source from microsoftgraph/microsoft-graph-docs-contrib, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 06:20 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.