Known issues

• OData context is returned incorrectly

  OData context is sometimes returned incorrectly when tracking changes to relationships.

• Pre-consent for CSP apps doesn't work in some customer tenants

  Under certain circumstances, pre-consent for cloud solution provider (CSP) apps may not work for some of your customer tenants. For apps using delegated permissions, when using the app for the first time with a new customer tenant, you…

• Provisioning of pre-registred passkeys not supported

  The FIDO2 provisioning API supports adding passkeys that are active upon creation. Provisioning, where passkeys are pre-registered with Microsoft Entra ID during device manufacturing or distribution and kept disabled until an…

• Publisher message of "unverified" occurs during PowerShell and CLI app consent

  The consent page shows that the command-line app that caters to PowerShell and CLI is from an unverified publisher. Workaround To remove the "unverified" message, you can do an app registration of your own, on which you can set yourself…

• Request dependencies are limited

  Individual requests can depend on other individual requests. Currently, requests can only depend on a single other request, and must follow one of these three patterns: Parallel - no individual request states a dependency in the dependsOn…

• Requests to filter team members by role require a parameter

  All the requests to filter team members by roles expect either a skipToken parameter or a top parameter in the request, but not both. If both the parameters are passed in the request, the top parameter will be ignored.

• Sensitivity label does not show up in the Teams UI

  Sensitivity Labels that are applied to Teams at times do not show up in the Teams UI, even though it can clearly be seen in both the underlying SharePoint site and in the Admin Center.

• showInAddressList property is out of sync with Microsoft Exchange

  When querying users through Microsoft Graph, the showInAddressList property may not indicate the same status shown in Microsoft Exchange. We recommend you manage this functionality directly with Microsoft Exchange through the Microsoft…

• Some limitations apply to query parameters

  The following limitations apply to query parameters: Multiple namespaces aren't supported. GET requests on $ref and casting aren't supported on users, groups, devices, service principals, and applications. @odata.bind isn't supported…

• Some properties for chat members might be missing in the response to a GET request

  In certain instances, the tenantId/email/displayName property for the individual members of a chat might not be populated on a GET /chats/chat-id/members or GET /chats/chat-id/members/membership-id request.

• The comment parameter for creating a draft isn't part of the message body

  The comment parameter for creating a reply or forward draft (createReply, createReplyAll, createForward) isn't part of the body of the response message draft.

• Unable to access a cross-tenant shared channel when the request URL contains tenants/{cross-tenant-id}

  The API calls for teams/{team-id}/incomingChannels and teams/{team-id}/allChannels return the @odata.id property which you can use to access the channel and run other operations on the channel object. If you call the URL returned from the…

• Unable to filter team members by roles

  Role query filters along with other filters GET /teams/team-id/members?$filter=roles/any(r:r eq 'owner') and displayName eq 'dummy' might not work. The server might respond with a BAD REQUEST.

• Upgrade events for Teams app installation change notifications in chat scope aren't delivered

  When a subscription for a Teams app installation change notification is created, if the scope is specific to or includes chats, upgrade events/notifications aren't delivered to the subscriber. For example: If a customer subscribes to…

• Use of specific query parameters on /subscribedSkus and /domains doesn't return the expected results

  The following usage of query parameters that target subscribedSkus and domain entities might not return the expected results: Use of $search on both subscribedSkus or domain entities Use of $top and $filter on the domain entity Currently…

• View meeting details menu is not available on Microsoft Teams client

  The Microsoft Teams client does not show the View Meeting details menu for channel meetings created via the cloud communications API.

Microsoft's Graph page is an undated catalog: an entry can be years old and still apply.