You can utilize the existing participants property of a callRecord for a complete list of participants.

In the callRecord participant resource, application/bot participants are currently represented by the communicationsUserIdentity instead of communicationsApplicationIdentity.

Use the user agent headerValue on the participantEndpoint resource in a callRecord session to identify application participants and see additional details on the application identity.

When recording bot applications enable Bot Grouping, the number of participants shown by the Teams client as being recorded isn't accurate. Because the participants are grouped, the displayed number of participants being recorded is lower than the actual number.

Disable bot grouping to show an accurate count. 

When a subscription for a Teams app installation change notification is created, if the scope is specific to or includes chats, upgrade events/ notifications will not be delivered to the subscriber.

For example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations?$filter=(scopeInfo/scope eq 'groupChat')`, they will not receive notifications for upgrade/update events. However, they will receive other notifications regarding installations and deletions.

Another example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations`, they will not receive notifications for upgrade/update events occurring specifically within chats. However, they will receive all other forms of notifications in teams and user's personal scope. But, in chats, they will only receive installation and deletion notifications.

Currently no workaround for this issue is available.

When a non-admin user calls the Create group API, Update group API, or Upsert group API and adds their user ID in the request body in the owners@odata.bind collection, the request fails with a 400 Bad Request error code with the message "Request contains a property with duplicate values." A non-admin user can't explicitly add themselves as the group owner.

There is no workaround for this error.

By default, a non-admin user who is creating a security or Microsoft 365 group through the Create group API or Upsert group API is automatically added to the owners collection of the group, if they don't specify any group owners. If they specify others as group owners, the non-admin group creator is still automatically added to the owners collection of the security group, but not for the Microsoft 365 group. The user still can't add themselves to the owners collection during group update.

The List group members API operation on the v1.0 endpoint currently doesn't return any service principals that might be members of the queried group. 

As a workaround, use one of the following options:

• Use the List group members API operation on the beta endpoint.
• Use the /groups/{id}?$expand=members API operation.

The release of the KBs introduced an issue with applications developed with the Communication Calling SDKs. 

Roll back the KBs pending an updated release of the SDK.

When the same application or user is joining the same meeting using multiple endpoints, and the roster notification mode is delta roster, the participant roster updates provided by Communications SDK might not capture the additional endpoints added to the ongoing call.

Legacy mode for roster supports the multi-endpoint use case. Use the SDK version 1.2.0.7270 or earlier.

Change tracking (/delta) requests to getAllTranscripts or getAllRecordings might return items that were already synced in earlier requests.

This happens when the meeting had other non-related updates, such as adding participants, notes, or files.

For every item in the response, check the createdDateTime of the recording or transcript and compare it with the previous sync timestamp. If the createdDateTime is before the last sync timestamp, the item is already synced and can be ignored.

When you call the clone team method, if the source team contains more than one owner, only one owner is preserved in the cloned team. The other owners become members of the new cloned team. It is not possible to choose or configure which owner is retained as the owner of the new team. 

Use the Add members method after you clone the team to update the original owners from members back to owners.

When a newly created tenant sends a list members of team request using advanced Azure AD query capabilities, an HTTP 401 error occurs.

The Create internalDomainFederation, Update internalDomainFederation, and Delete internalDomainFederation might require you to grant consent to the Directory.AccessAsUser.All permission. This requirement is a temporary workaround till we provide a more granular delegated permission for managing federated domains.

The getAllTranscripts API might return transcript content URLs for some meetings that don't have any transcribed words. Calls to the content URL for those meetings will return an error.

Verify that the meeting has been transcribed and if there's valid content. If there is, report it for further investigation. Otherwise, ignore the content URL. 

The getAllRecordings API does not return recordings for meetings that don't have transcription enabled.

When you call the getAllRecordings or getAllTranscripts APIs, passing the $top filter might not return the @odata.nextLink, even when there are more items to export.

Do not pass &top query parameter until the issue is fixed.

As per RFC 3986 and as described in Encoding query parameters, reserved characters in query strings must be percent-encoded. For example, the syntax for $search on a group name like "Hiking&Recreation" is as follows:

GET https://graph.microsoft.com/v1.0/groups?$search="displayName:Hiking%26Recreation group"

Microsoft Graph currently returns a 400 Bad Request error code on the v1.0 endpoint on searches that include encoded ampersand (&) characters, with the following error message: Unrecognized query argument specified: ''.". The same request succeeds on the beta endpoint.

Some apps have implemented double-percent encoding on the v1.0 endpoint as a workaround. For example, the double-percent encoded request becomes `/users?$search="displayName:Hiking%2526Recreation group"`. However, this is not the officially recommended workaround.

Workaround 1:

On the v1.0 endpoint, when using the proper percent-encoding, include the Prefer request header set to legacySearch=false. For example:

GET https://graph.microsoft.com/v1.0/groups?$search="displayName:Hiking%26Recreation group"
ConsistencyLevel: eventual
Prefer: legacySearch=false

In the future, the behavior on the v1.0 endpoint will be corrected, and you will not need to include this header.

Workaround 2:

When the behavior on the v1.0 endpoint is corrected, apps that will have a dependency on the double-percent encoding may experience breaking changes unless they are opted-in to maintain their implementation by including the Prefer request header set to legacySearch=true. For example:

GET https://graph.microsoft.com/v1.0/groups?$search="displayName:Hiking%2526Recreation group"
ConsistencyLevel: eventual
Prefer: legacySearch=true

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 365 admin center and not to use this property in Microsoft Graph.

Getting the list of bookingBusinesses fails with the following error code when an organization has several Bookings businesses and the account making the request is not an administrator:

{
 
  "error": { 
    "code": "ErrorExceededFindCountLimit", 
    "message": 
      "The GetBookingMailboxes request returned too many results. Please specify a query to limit the results.", 
  } 
 
}
 

You can limit the set of businesses returned by the request by including a query parameter, for example:

GET https://graph.microsoft.com/beta/bookingBusinesses?query=Fabrikam

Accessing and updating deployment audiences on deployment resources created via Intune is not currently supported.

• Listing deployment audience members and listing deployment audience exclusions returns 404 Not Found.
• Updating deployment audience members and exclusions or updating by ID returns 202 Accepted but the audience is not updated.

When you create a channel, if you use special characters in your channel name, the 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:

• Include any of the following special characters: ~ # % & * { } + / \\ : < > ? | ‘ ”.
• Start with an underscore (_) or period (.), or end with a period (.).

The claimsMappingPolicy API might require consent to both the Policy.Read.All and Policy.ReadWrite.ConditionalAccess permissions for the LIST /policies/claimsMappingPolicies and GET /policies/claimsMappingPolicies/{id} methods, as follows:

• If no claimsMappingPolicy objects are available to retrieve in a LIST operation, either permission is sufficient to call this method.
• If there are claimsMappingPolicy objects to retrieve, your app must consent to both permissions. If not, a 403 Forbidden error is returned.

In the future, either permission will be sufficient to call both methods.

The conditionalAccessPolicy API currently requires consent to the Policy.Read.All permission to call the POST and PATCH methods. In the future, the Policy.ReadWrite.ConditionalAccess permission will enable you to read policies from the directory.

When querying followed sites through Microsoft Graph, the response might have incorrect results and those results might not match the results from following content in SharePoint.

Use the following people and content REST API.

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 @odata.id property, the request fails with the following error when it tries to access the cross-tenant shared channel:

GET /tenants/{tenant-id}/teams/{team-id}/channels/{channel-id}
{
    "error": {
        "code": "BadRequest",
        "message": "TenantId in the optional tenants/{tenantId} segment should match the tenantId(tid) in the token used to call Graph.",
        "innerError": {
            "date": "2022-03-08T07:33:50",
            "request-id": "dff19596-b5b2-421d-97d3-8d4b023263f3",
            "client-request-id": "32ee2cbd-27f8-2441-e3be-477dbe0cedfa"
        }
    }
}

Remove the /tenants/{tenant-id} part from the URL before you call the API to access the cross-tenant shared channel.

The consent page shows that the command-line app that caters to PowerShell and CLI is from an unverified publisher.

Connect-MgGraph -AppId "{your-own-app-id}" -Scopes "scope"

The API call for me/joinedTeams returns only the id, displayName, and description properties of a team. To get all properties, use the Get team operation.

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

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.

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 might receive this error after sign-in: AADSTS50000: There was an error issuing a token.
• For apps using application permissions, your app can acquire a token, but unexpectedly gets an access denied message when calling Microsoft Graph.

We are working to fix this issue, so that pre-consent will work for all your customer tenants.

To unblock development and testing, you can use the following workaround.

NOTE: This is not a permanent solution and is only intended to unblock development. This workaround will not be required once the issue is fixed. This workaround does not need to be undone after the fix is in place.

1. Open an Azure AD v2 PowerShell session and connect to your customer tenant by entering your admin credentials into the sign-in window. You can download and install Azure AD PowerShell V2 from here.

      2. Create the Microsoft Graph service principal.

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.

When you make /delta calls to the messages API using immutable Ids in some cases (for example when a message moves out of a folder and is then moved back in), you might miss some change notifications.

Cloud solution provider (CSP) apps must acquire tokens from the Azure AD (v1) endpoints to successfully call Microsoft Graph in their partner-managed customers. Currently, acquiring a token through the newer Azure AD v2.0 endpoint is not supported.

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 property.
• Serial - all individual requests depend on the previous individual request.
• Same - all individual requests that state a dependency in the dependsOn property, state the same dependency. Note: Requests made using this pattern will run sequentially.

As JSON batching matures, these limitations will be removed.

Some functionality is not yet available in Microsoft Graph. If you don't see the functionality you're looking for, you can use the endpoint-specific Office 365 REST APIs. For Azure AD Graph, see Migrate Active Directory (Azure AD) Graph apps to Microsoft Graph.

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

An app with delegated permissions returns HTTP 403 Forbidden when attempting to attach large files to an Outlook message or event that is in a shared or delegated mailbox. With delegated permissions, createUploadSession succeeds only if the message or event is in the signed-in user's mailbox.

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

The comment parameter for creating a reply or forward draft (createReply, createReplyAll, createForward) does not become part of the body of the resultant message draft.