Graph known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 6 Oct 2023 02:12 UTC

fixed issues previously fixed and lost

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

⋯ 2 unchanged lines

33 description: "This article describes known issues and limitations with Microsoft Graph and provides workarounds when possible."

44 author: "MSGraphDocsVTeam"

55 ms.localizationpriority: high

6 −ms.custom: has-azure-ad-ps-ref

76 ---

98 # Known issues with Microsoft Graph

⋯ 8 unchanged lines

1817

1918 ### Some limitations apply to the application and servicePrincipal resources

2019

21 −Changes to the [application](/graph/api/resources/application) and [servicePrincipal](/graph/api/resources/serviceprincipal) resources are currently in development. The following is a summary of current limitations and in-development API features.

20 +Changes to the [application](/graph/api/resources/application) and [servicePrincipal](/graph/api/resources/serviceprincipal) resources are currently in development. Here's a summary of current limitations and in-development API features.

2221

2322 Current limitations:

2423

25 −- Some application properties (such as appRoles and addIns) will not be available until all changes are completed.

26 −- Only multi-tenant apps can be registered.

24 +- Some application properties (such as appRoles and addIns) won't be available until all changes are completed.

25 +- Only multitenant apps can be registered.

2726 - Updating apps is restricted to apps registered after the initial beta update.

2827 - Azure Active Directory users can register apps and add additional owners.

2928 - Support for OpenID Connect and OAuth protocols.

⋯ 51 unchanged lines

8180

8281 You may get HTTP 500 with the error code `ErrorInternalServerTransientError`. The error occurs because:

8382

84 −- Historically, there are two ways that calendar sharing has been implemented, which, for the purpose of differentiating them,

83 +- Historically, there are two ways that calendar sharing has been implemented, which, for differentiating them,

8584 are referred to as the "old" approach and "new" approach.

8685 - The new approach is currently available for sharing calendars with view or edit permissions, but not with delegate permissions.

8786 - You can use the calendar REST API to view or edit shared calendars only if the calendars were shared using the **new** approach.

88 −- You cannot use the calendar REST API to view or edit such calendars (or their events) if the calendars were shared using the **old** approach.

87 +- You can't use the calendar REST API to view or edit such calendars (or their events) if the calendars were shared using the **old** approach.

8988

9089 If a calendar was shared with view or edit permissions but using the old approach, you can now work around the error and manually upgrade the calendar sharing to use the new approach.

9190 Over time, Outlook will automatically upgrade all shared calendars to use the new approach, including calendars shared with delegate permissions.

⋯ 2 unchanged lines

9493

9594 1. The recipient removes the calendar that was previously shared to them.

9695 2. The calendar owner re-shares the calendar in Outlook on the web, Outlook on iOS, or Outlook on Android.

97 −3. The recipient re-accepts the shared calendar using Outlook on the web. (It will be possible to use other Outlook clients soon.)

96 +3. The recipient re-accepts the shared calendar using Outlook on the web. (It is possible to use other Outlook clients soon.)

9897 4. The recipient verifies that the calendar has been re-shared successfully using the new approach by being able to view the shared calendar in Outlook on iOS or Outlook on Android.

9998

10099 A calendar shared with you in the new approach appears as just another calendar in your mailbox. You can use the calendar REST API to view or edit

⋯ 8 unchanged lines

109108 Currently, calendars based on an Internet Calendar Subscription (ICS) are only partially supported:

110109

111110 - You can add an ICS-based calendar to a user mailbox through the UI, but not through the Microsoft Graph API.

112 −- [Listing the user's calendars](/graph/api/user-list-calendars) lets you get the **name**, **color** and **id** properties of each [calendar](/graph/api/resources/calendar) in the user's default calendar group, or a specified calendar group, including any ICS-based calendars. You cannot store or access the ICS URL in the calendar resource.

111 +- [Listing the user's calendars](/graph/api/user-list-calendars) lets you get the **name**, **color** and **id** properties of each [calendar](/graph/api/resources/calendar) in the user's default calendar group, or a specified calendar group, including any ICS-based calendars. You can't store or access the ICS URL in the calendar resource.

113112 - You can also [list the events](/graph/api/calendar-list-events) of an ICS-based calendar.

114113

115114 ### Error attaching large files to events

116115

117116 An app with delegated permissions returns `HTTP 403 Forbidden` when attempting to [attach large files](outlook-large-attachments.md) to an Outlook message or event that is in a shared or delegated mailbox. With delegated permissions, [createUploadSession](/graph/api/attachment-createuploadsession) succeeds only if the message or event is in the signed-in user's mailbox.

118117

119 −### onlineMeetingUrl property is not supported for Microsoft Teams

118 +### onlineMeetingUrl property isn't supported for Microsoft Teams

120119

121120 Currently, the **onlineMeetingUrl** property of a Skype meeting [event](/graph/api/resources/event) would indicate the online meeting URL. However, that property for a Microsoft Teams meeting event is set to null.

122121

⋯ 11 unchanged lines

134133

135134 ## Contacts

136135

137 −### GET operation does not return default contacts folder

136 +### GET operation doesn't return default contacts folder

138137

139 −In the `/v1.0` version, `GET /me/contactFolders` does not include the user's default contacts folder.

138 +In the `/v1.0` version, `GET /me/contactFolders` doesn't include the user's default contacts folder.

140139

141 −A fix will be made available. Meanwhile, you can use the following [list contacts](/graph/api/user-list-contacts) query and the **parentFolderId** property

140 +A fix is made available. Meanwhile, you can use the following [list contacts](/graph/api/user-list-contacts) query and the **parentFolderId** property

142141 as a workaround to get the folder ID of the default contacts folder:

143142

144143 ```http

⋯ 27 unchanged lines

172171

173172 The previous example shows one level of nesting, but a contact can be located in a child of a child and so on.

174173

175 −As an alternative, you can simply [get](/graph/api/contact-get?view=graph-rest-beta&preserve-view=true) the contact by specifying its ID as shown,

174 +As an alternative, you can [get](/graph/api/contact-get?view=graph-rest-beta&preserve-view=true) the contact by specifying its ID as shown,

176175 because GET /contacts in the `/beta` version applies to all the contacts in the user's mailbox:

177176

178177 ```http

⋯ 5 unchanged lines

184183

185184 ### Error when querying bookingBusinesses

186185

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

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 isn't an administrator:

188187

189188 ```json

190189 {

⋯ 17 unchanged lines

208207

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

210209

211 −### Schema extensions are not returned with `select`

210 +### Schema extensions aren't returned with `select`

212211

213 −Schema extensions (legacy) are not returned with `$select` statement, but are returned without `$select`.

212 +Schema extensions (legacy) aren't returned with `$select` statement, but are returned without `$select`.

214213

215 −### Clients cannot track changes to open extensions

214 +### Clients can't track changes to open extensions

216215

217 −Clients cannot track changes to open extensions or registered schema extensions.

216 +Clients can't track changes to open extensions or registered schema extensions.

218217

219218 ## Devices and apps | Device updates (Windows updates)

220219

221 −### Accessing and updating deployment audiences is not supported

220 +### Accessing and updating deployment audiences isn't supported

222221

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

222 +Accessing and updating deployment audiences on **deployment** resources created via Intune isn't currently supported.

224223

225224 - [Listing deployment audience members](/graph/api/windowsupdates-deploymentaudience-list-members) and [listing deployment audience exclusions](/graph/api/windowsupdates-deploymentaudience-list-exclusions) returns `404 Not Found`.

226 −- [Updating deployment audience members and exclusions](/graph/api/windowsupdates-deploymentaudience-updateaudience) or [updating by ID](/graph/api/windowsupdates-deploymentaudience-updateaudiencebyid) returns `202 Accepted` but the audience is not updated.

225 +- [Updating deployment audience members and exclusions](/graph/api/windowsupdates-deploymentaudience-updateaudience) or [updating by ID](/graph/api/windowsupdates-deploymentaudience-updateaudiencebyid) returns `202 Accepted` but the audience isn't updated.

227226

228227 ## Extensions

229228

230 −### Change tracking is not supported

229 +### Change tracking isn't supported

231230

232 −Change tracking (delta query) is not supported for open or schema extension properties.

231 +Change tracking (delta query) isn't supported for open or schema extension properties.

233232

234233 ### Unable to create a resource and open extension at the same time

235234

236 −You cannot specify an open extension at the same time you create an instance of **administrativeUnit**, **device**, **group**, **organization** or **user**. You must first create the instance and then specify the open extension data in a subsequent ``POST`` request on that instance.

235 +You can't specify an open extension at the same time you create an instance of **administrativeUnit**, **device**, **group**, **organization** or **user**. You must first create the instance and then specify the open extension data in a subsequent ``POST`` request on that instance.

237236

238237 ### Unable to create a resource instance and add schema extension data at the same time

239238

240 −You cannot specify a schema extension in the same operation as creating an instance of **contact**, **event**, **message**, or **post**.

239 +You can't specify a schema extension in the same operation as creating an instance of **contact**, **event**, **message**, or **post**.

241240 You must first create the resource instance and then do a `PATCH` to that instance to add a schema extension and custom data.

242241

243242 ### Limit of 100 schema extension property values allowed per resource instance

⋯ 2 unchanged lines

246245

247246 ### Owner must be specified when updating a schemaExtension definition using Microsoft Graph Explorer

248247

249 −When using `PATCH` to update a schemaExtension using Graph Explorer, you must specify the **owner** property and set it to its current `appId` value (which will need to be an `appId` of an application that you own). This is also the case for any client application the `appId` for which is not the same as the **owner**.

248 +When using `PATCH` to update a schemaExtension using Graph Explorer, you must specify the **owner** property and set it to its current `appId` value (which will need to be an `appId` of an application that you own). This is also the case for any client application the `appId` for which isn't the same as the **owner**.

250249

251 −### Filtering on schema extension properties is not supported on all entity types

250 +### Filtering on schema extension properties isn't supported on all entity types

252251

253 −Filtering on schema extension properties (using the `$filter` expression) is not supported for Outlook entity types - **contact**, **event**, **message**, or **post**.

252 +Filtering on schema extension properties (using the `$filter` expression) isn't supported for Outlook entity types - **contact**, **event**, **message**, or **post**.

254253

255254 ## Files (OneDrive)

256255

⋯ 34 unchanged lines

291290

292291 ### allowExternalSenders property can only be accessed on unified groups

293292

294 −There is currently an issue that prevents setting the **allowExternalSenders** property of a group in a POST or PATCH operation, in both `/v1.0` and `/beta`.

293 +There's currently an issue that prevents setting the **allowExternalSenders** property of a group in a POST or PATCH operation, in both `/v1.0` and `/beta`.

295294

296295 The **allowExternalSenders** property can only be accessed on unified groups. Accessing this property on security groups, including via GET operations, will result in an error.

297296

⋯ 5 unchanged lines

303302

304303 ### Conditional access policy requires consent to permission

305304

306 −The [conditionalAccessPolicy](/graph/api/resources/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.

305 +The [conditionalAccessPolicy](/graph/api/resources/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 enables you to read policies from the directory.

307306

308307 ### Claims mapping policy might require consent to permissions

309308

⋯ 2 unchanged lines

312311 + If no **claimsMappingPolicy** objects are available to retrieve in a LIST operation, either permission is sufficient to call this method.

313312 + If there are **claimsMappingPolicy** objects to retrieve, your app must consent to both permissions. If not, a `403 Forbidden` error is returned.

314313

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

314 +In the future, either permission is sufficient to call both methods.

316315

317316 ### Non-Windows devices can't be updated by an app with application permissions

318317

⋯ 1 unchanged line

320319

321320 ## JSON batching

322321

323 −### Nested batches are not supported

322 +### Nested batches aren't supported

324323

325324 JSON batch requests must not contain any nested batch requests.

326325

327326 ### All individual requests must be synchronous

328327

329 −All requests contained in a batch request must be run synchronously. If present, the `respond-async` preference will be ignored.

328 +All requests contained in a batch request must be run synchronously. If present, the `respond-async` preference is ignored.

330329

331 −### Transactional processing of requests is not supported

330 +### Transactional processing of requests isn't supported

332331

333 −Microsoft Graph does not currently support transactional processing of individual requests. The **atomicityGroup** property on individual requests will be ignored.

332 +Microsoft Graph doesn't currently support transactional processing of individual requests. The **atomicityGroup** property on individual requests will be ignored.

334333

335334 ### URIs must be relative

336335

⋯ 14 unchanged lines

351350

352351 - Parallel - no individual request states a dependency in the **dependsOn** property.

353352 - Serial - all individual requests depend on the previous individual request.

354 −- 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.

353 +- Same - all individual requests that state a dependency in the **dependsOn** property state the same dependency. **Note**: Requests made using this pattern runs sequentially.

355354

356355 As JSON batching matures, these limitations will be removed.

357356

⋯ 2 unchanged lines

360359 ### Attaching large files to messages with delegated permissions can fail

361360 An app with delegated permissions returns `HTTP 403 Forbidden` when attempting to [attach large files](outlook-large-attachments.md) to an Outlook message or event that is in a shared or delegated mailbox. With delegated permissions, [createUploadSession](/graph/api/attachment-createuploadsession) succeeds only if the message or event is in the signed-in user's mailbox.

362361

363 −### The comment parameter for creating a draft does not become part of the message body

362 +### The comment parameter for creating a draft doesn't become part of the message body

364363

365364 The **comment** parameter for creating a reply or forward draft ([createReply](/graph/api/message-createreply),

366365 [createReplyAll](/graph/api/message-createreplyall), [createForward](/graph/api/message-createforward))

367 −does not become part of the body of the resultant message draft.

366 +doesn't become part of the body of the resultant message draft.

368367

369368 ### GET messages returns chats in Microsoft Teams

370369

⋯ 5 unchanged lines

376375

377376 The following limitations apply to query parameters:

378377

379 −- Multiple namespaces are not supported.

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

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

378 +- Multiple namespaces aren't supported.

379 +- GET requests on `$ref` with casting aren't supported on users, groups, devices, service principals, and applications.

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

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

383382 - `$expand`:

384383 - For directory objects, returns a maximum of 100 objects.

⋯ 120 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.