Graph known issues
Microsoft's edit ·
Microsoft's commit message in microsoftgraph/microsoft-graph-docs-contrib · commit 616dfc3 · +49 −48 lines · also on GitHub
⋯ 66 unchanged lines
6767
New-AzureADServicePrincipal -AppId 00000003-0000-0000-c000-000000000000
6868
```
6969
70
−## Customer booking
7170
72
−### Error when querying bookingBusinesses
73
−
74
−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:
75
−
76
−```json
77
−{
78
− "error": {
79
− "code": "ErrorExceededFindCountLimit",
80
− "message":
81
− "The GetBookingMailboxes request returned too many results. Please specify a query to limit the results.",
82
− }
83
−}
84
−```
85
−
86
−As a workaround, you can limit the set of businesses returned by the request by including a `query` parameter, for example:
87
−
88
−```http
89
−GET https://graph.microsoft.com/beta/bookingBusinesses?query=Fabrikam
90
−```
91
−
9271
## Calendar
9372
9473
### Error accessing a shared calendar
⋯ 105 unchanged lines
200179
GET /users/{id | userPrincipalName}/contacts/{id}
201180
```
202181
182
+## Customer booking
183
+
184
+### Error when querying bookingBusinesses
185
+
186
+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:
187
+
188
+```json
189
+{
190
+ "error": {
191
+ "code": "ErrorExceededFindCountLimit",
192
+ "message":
193
+ "The GetBookingMailboxes request returned too many results. Please specify a query to limit the results.",
194
+ }
195
+}
196
+```
197
+
198
+As a workaround, you can limit the set of businesses returned by the request by including a `query` parameter, for example:
199
+
200
+```http
201
+GET https://graph.microsoft.com/beta/bookingBusinesses?query=Fabrikam
202
+```
203
+
203204
## Delta query
204205
205206
### OData context is returned incorrectly
⋯ 162 unchanged lines
368369
369370
In both the v1.0 and beta endpoints, the response to `GET /users/id/messages` includes the user's Microsoft Teams chats that occurred outside the scope of a team or channel. These chat messages have "IM" as their subject.
370371
372
+## Query parameters
373
+
374
+### Some limitations apply to query parameters
375
+
376
+The following limitations apply to query parameters:
377
+
378
+- Multiple namespaces are not supported.
379
+- GET requests on `$ref` with casting are not supported on users, groups, devices, service principals, and applications.
380
+- `@odata.bind` is not supported. This means that you can't properly set the **acceptedSenders** or **rejectedSenders** navigation property on a group.
381
+- `@odata.id` is not present on non-containment navigations (like messages) when using minimal metadata.
382
+- `$expand`:
383
+ - For directory objects, returns a maximum of 20 objects.
384
+ - No support for `@odata.nextLink`.
385
+ - No support for more than one level of expand.
386
+ - For directory objects, no support for nesting other query parameters such as `$filter` and `$select` in `$expand`.
387
+- `$filter`
388
+ - `/attachments` endpoint does not support filters. If present, the `$filter` parameter is ignored.
389
+ - Cross-workload filtering is not supported.
390
+- `$search`:
391
+ - Full-text search is only available for a subset of entities, such as messages.
392
+ - Cross-workload searching is not supported.
393
+ - Searching is not supported in Azure AD B2C tenants.
394
+- `$count`:
395
+ - Not supported in Azure AD B2C tenants.
396
+ - 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.
397
+- 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.
398
+
371399
## Reports
372400
373401
### License check errors for Azure AD activity reports
⋯ 89 unchanged lines
463491
### View meeting details menu is not available on Microsoft Teams client
464492
465493
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.
493494
494495
## Users
495496
⋯ 39 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.