| title | Delete onlineMeeting |
|---|---|
| description | Delete an online meeting. |
| author | awang119 |
| ms.localizationpriority | medium |
| ms.subservice | cloud-communications |
| doc_type | apiPageType |
| ms.date | 12/03/2024 |
Namespace: microsoft.graph
[!INCLUDE beta-disclaimer]
Delete an onlineMeeting object.
[!INCLUDE national-cloud-support]
The following tables show the least privileged permission or permissions required to call this API on each supported resource type. Follow best practices to request least privileged permissions. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permissions for the following HTTP request:
DELETE /me/onlineMeetings/{meetingId}[!INCLUDE permissions-table]
Permissions for the following HTTP request:
DELETE /users/{userId}/onlineMeetings/{meetingId}[!INCLUDE permissions-table]
Important
To use application permission for this API, tenant administrators must create an application access policy and grant it to a user to authorize the app configured in the policy to delete online meetings on behalf of that user (with user ID specified in the request path).
To delete an onlineMeeting using the meeting ID with delegated (/me) and app (/users/{userId}) permission:
DELETE /me/onlineMeetings/{meetingId}
DELETE /users/{userId}/onlineMeetings/{meetingId}Note
- userId is the object ID of a user in Microsoft Entra admin center > user management page. For more information, see Configure application access to online meetings.
meetingIdis the id of an onlineMeeting object.
| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Don't supply a request body for this method.
If successful, this method returns a 204 No Content response code. It doesn't return anything in the response body.
The following example shows the request.
DELETE https://graph.microsoft.com/beta/me/onlineMeetings/550fae72-d251-43ec-868c-373732c2704f_19:meeting_M2IzYzczNTItYmY3OC00MDlmLWJjMzUtYmFiMjNlOTY4MGEz@thread.skype[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 204 No Content