Graph known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 11 Mar 2023 02:23 UTC

Reorganized headings.

Microsoft's commit message in microsoftgraph/microsoft-graph-docs-contrib · commit db7811e · +40 ~~−44~~ lines · also on GitHub

⋯ 66 unchanged lines

6767 New-AzureADServicePrincipal -AppId 00000003-0000-0000-c000-000000000000

6868 ```

6969

70 −## Bookings

70 +## Customer booking

7171

7272 ### Error when querying bookingBusinesses

7373

⋯ 78 unchanged lines

152152

153153 [Subscriptions](/graph/api/resources/subscription) to changes for **group** with **changeType** set to **updated** will also receive notifications of **changeType**: **updated** on group creation and group soft deletion.

154154

155 −## Channel

156 −

157 −### Create channel

158 −

159 −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:

160 −

161 −- Include any of the following special characters: ~ # % & * { } + / \ : < > ? | ‘ ”.

162 −- Start with an underscore (_) or period (.), or end with a period (.).

163 −

164 −## Cloud communications

165 −

166 −### View meeting details menu is not available on Microsoft Teams client

167 −

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

169 −

170155 ## Contacts

171156

172157 ### GET operation does not return default contacts folder

⋯ 240 unchanged lines

413398

414399 When querying [followed sites](/graph/api/sites-list-followed) through Microsoft Graph, the response might have incorrect results and those results might not match the results from following content in SharePoint. As a temporary workaround, you can use the [Following people and content REST API](/sharepoint/dev/general-development/following-people-and-content-rest-api-reference-for-sharepoint).

415400

416 −## Teamwork (Microsoft Teams)

401 +## Teamwork and communications (Microsoft Teams)

417402

418403 ### Unable to filter team members by roles

419404

⋯ 48 unchanged lines

468453 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

469454 ```

470455

456 +### Create channel can return an error response

457 +

458 +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:

459 +

460 +- Include any of the following special characters: ~ # % & * { } + / \ : < > ? | ‘ ”.

461 +- Start with an underscore (_) or period (.), or end with a period (.).

462 +

463 +### View meeting details menu is not available on Microsoft Teams client

464 +

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

466 +

467 +## Query parameters

468 +

469 +### Some limitations apply to query parameters

470 +

471 +The following limitations apply to query parameters:

472 +

473 +- Multiple namespaces are not supported.

474 +- GET requests on `$ref` with casting are not supported on users, groups, devices, service principals, and applications.

475 +- `@odata.bind` is not supported. This means that you can't properly set the **acceptedSenders** or **rejectedSenders** navigation property on a group.

476 +- `@odata.id` is not present on non-containment navigations (like messages) when using minimal metadata.

477 +- `$expand`:

478 + - For directory objects, returns a maximum of 20 objects.

479 + - No support for `@odata.nextLink`.

480 + - No support for more than one level of expand.

481 + - For directory objects, no support for nesting other query parameters such as `$filter` and `$select` in `$expand`.

482 +- `$filter`

483 + - `/attachments` endpoint does not support filters. If present, the `$filter` parameter is ignored.

484 + - Cross-workload filtering is not supported.

485 +- `$search`:

486 + - Full-text search is only available for a subset of entities, such as messages.

487 + - Cross-workload searching is not supported.

488 + - Searching is not supported in Azure AD B2C tenants.

489 +- `$count`:

490 + - Not supported in Azure AD B2C tenants.

491 + - When using the `$count=true` query string when querying against directory objects, the `@odata.count` property will be present only in the first page of the paged data.

492 +- Query parameters specified in a request might fail silently. This can be true for unsupported query parameters as well as for unsupported combinations of query parameters.

493 +

471494 ## Users

472495

473496 ### Encode number (#) symbols in userPrincipalName

⋯ 31 unchanged lines

505528 ### showInAddressList property is out of sync with Microsoft Exchange

506529

507530 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.

508 −

509 −## Query parameters

510 −

511 −### Some limitations apply to query parameters

512 −

513 −The following limitations apply to query parameters:

514 −

515 −- Multiple namespaces are not supported.

516 −- GET requests on `$ref` with casting are not supported on users, groups, devices, service principals, and applications.

517 −- `@odata.bind` is not supported. This means that you can't properly set the **acceptedSenders** or **rejectedSenders** navigation property on a group.

518 −- `@odata.id` is not present on non-containment navigations (like messages) when using minimal metadata.

519 −- `$expand`:

520 − - For directory objects, returns a maximum of 20 objects.

521 − - No support for `@odata.nextLink`.

522 − - No support for more than one level of expand.

523 − - For directory objects, no support for nesting other query parameters such as `$filter` and `$select` in `$expand`.

524 −- `$filter`

525 − - `/attachments` endpoint does not support filters. If present, the `$filter` parameter is ignored.

526 − - Cross-workload filtering is not supported.

527 −- `$search`:

528 − - Full-text search is only available for a subset of entities, such as messages.

529 − - Cross-workload searching is not supported.

530 − - Searching is not supported in Azure AD B2C tenants.

531 −- `$count`:

532 − - Not supported in Azure AD B2C tenants.

533 − - When using the `$count=true` query string when querying against directory objects, the `@odata.count` property will be present only in the first page of the paged data.

534 −- Query parameters specified in a request might fail silently. This can be true for unsupported query parameters as well as for unsupported combinations of query parameters.

535531

536532 ## Functionality available only in Office 365 REST or Azure AD Graph APIs (deprecated)

537533

⋯ 1 unchanged line

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.