Skip to content

Commit ab6c086

Browse files
authored
Merge pull request #26171 from microsoftgraph/v1-permanentdelete
V1 permanentdelete
2 parents 8318ed2 + a0bc2a9 commit ab6c086

25 files changed

+847
-12
lines changed
Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: "calendar: permanentDelete"
3+
description: "Permanently delete a calendar folder and the events that it contains and remove them from the mailbox."
4+
author: "deepakbaghel99"
5+
ms.localizationpriority: high
6+
ms.subservice: "outlook"
7+
doc_type: apiPageType
8+
ms.date: 02/05/2025
9+
---
10+
11+
# calendar: permanentDelete
12+
13+
Namespace: microsoft.graph
14+
15+
16+
Permanently delete a calendar folder and the events that it contains and remove them from the mailbox. For more information about item retention, see [Configure deleted item retention and recoverable items quotas](/exchange/configure-deleted-item-retention-and-recoverable-items-quotas-exchange-2013-help).
17+
18+
> [!Note]
19+
> Folders aren't placed in the **purges** folder when they're permanently deleted. Permanently deleted folders are removed from the mailbox.
20+
21+
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
22+
23+
## Permissions
24+
25+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
26+
27+
<!-- { "blockType": "permissions", "name": "calendar_permanentdelete" } -->
28+
[!INCLUDE [permissions-table](../includes/permissions/calendar-permanentdelete-permissions.md)]
29+
30+
## HTTP request
31+
32+
<!-- {
33+
"blockType": "ignored"
34+
}
35+
-->
36+
``` http
37+
POST /users/{usersId}/calendar/permanentDelete
38+
POST /groups/{groupsId}/calendar/permanentDelete
39+
```
40+
41+
## Request headers
42+
43+
|Name|Description|
44+
|:---|:---|
45+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
46+
47+
## Request body
48+
49+
Don't supply a request body for this method.
50+
51+
## Response
52+
53+
If successful, this action returns a `204 No Content` response code.
54+
55+
## Examples
56+
57+
### Request
58+
59+
The following example shows a request.
60+
<!-- {
61+
"blockType": "request",
62+
"name": "calendarthis.permanentdelete"
63+
}
64+
-->
65+
``` http
66+
POST https://graph.microsoft.com/v1.0/users/b4c80c57-5c59-4a3d-912a-a83985988b82/calendar/permanentDelete
67+
```
68+
69+
### Response
70+
71+
The following example shows the response.
72+
73+
<!-- {
74+
"blockType": "response",
75+
"truncated": true
76+
}
77+
-->
78+
``` http
79+
HTTP/1.1 204 No Content
80+
```
81+
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
---
2+
title: "contact: permanentDelete"
3+
description: "Permanently delete a contact and place it in the purges folder in the user's mailbox."
4+
author: "deepakbaghel99"
5+
ms.localizationpriority: high
6+
ms.subservice: "outlook"
7+
doc_type: apiPageType
8+
ms.date: 01/17/2025
9+
---
10+
11+
# contact: permanentDelete
12+
13+
Namespace: microsoft.graph
14+
15+
Permanently delete a contact and place it in the **purges** folder in the dumpster in the user's mailbox. Email clients such as outlook or outlook on the web can't access permanently deleted items. Unless there's a hold set on the mailbox, the items are permanently deleted after a set period of time.
16+
17+
For more information about item retention, see [Configure deleted item retention and recoverable items quotas](/exchange/configure-deleted-item-retention-and-recoverable-items-quotas-exchange-2013-help).
18+
19+
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
20+
21+
## Permissions
22+
23+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
24+
25+
<!-- { "blockType": "permissions", "name": "contact_permanentdelete" } -->
26+
[!INCLUDE [permissions-table](../includes/permissions/contact-permanentdelete-permissions.md)]
27+
28+
## HTTP request
29+
30+
<!-- {
31+
"blockType": "ignored"
32+
}
33+
-->
34+
``` http
35+
POST /users/{usersId}/contacts/{contactId}/permanentDelete
36+
POST /users/{usersId}/contactFolders/{contactFolderId}/contacts/{contactId}/permanentDelete
37+
```
38+
39+
## Request headers
40+
41+
|Name|Description|
42+
|:---|:---|
43+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
44+
45+
## Request body
46+
47+
Don't supply a request body for this method.
48+
49+
## Response
50+
51+
If successful, this action returns a `204 No Content` response code.
52+
53+
## Examples
54+
55+
### Request
56+
57+
The following example shows a request.
58+
<!-- {
59+
"blockType": "request",
60+
"name": "contactthis.permanentdelete"
61+
}
62+
-->
63+
``` http
64+
POST https://graph.microsoft.com/v1.0/users/b4c80c57-5c59-4a3d-912a-a83985988b82/contacts/AAsdjipajdwnoiwsda=/permanentDelete
65+
```
66+
67+
68+
### Response
69+
70+
The following example shows the response.
71+
72+
<!-- {
73+
"blockType": "response",
74+
"truncated": true
75+
}
76+
-->
77+
``` http
78+
HTTP/1.1 204 No Content
79+
```
80+
Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: "contactFolder: permanentDelete"
3+
description: "Permanently delete a contact folder and remove its items from the user's mailbox."
4+
author: "deepakbaghel99"
5+
ms.localizationpriority: high
6+
ms.subservice: "outlook"
7+
doc_type: apiPageType
8+
ms.date: 01/17/2025
9+
---
10+
11+
# contactFolder: permanentDelete
12+
13+
Namespace: microsoft.graph
14+
15+
Permanently delete a contact folder and remove its items from the user's mailbox. For more information about item retention, see [Configure deleted item retention and recoverable items quotas](/exchange/configure-deleted-item-retention-and-recoverable-items-quotas-exchange-2013-help).
16+
17+
> [!Note]
18+
> Folders aren't placed in the **purges** folder when they're permanently deleted. Permanently deleted folders are removed from the mailbox.
19+
20+
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
21+
22+
## Permissions
23+
24+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
25+
26+
<!-- { "blockType": "permissions", "name": "contactfolder_permanentdelete" } -->
27+
[!INCLUDE [permissions-table](../includes/permissions/contactfolder-permanentdelete-permissions.md)]
28+
29+
## HTTP request
30+
31+
<!-- {
32+
"blockType": "ignored"
33+
}
34+
-->
35+
``` http
36+
POST /users/{usersId}/contactFolders/{contactFolderId}/permanentDelete
37+
POST /users/{usersId}/contactFolders/{contactFolderId}/childFolders/{contactFolderId}/permanentDelete
38+
```
39+
40+
## Request headers
41+
42+
|Name|Description|
43+
|:---|:---|
44+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
45+
46+
## Request body
47+
48+
Don't supply a request body for this method.
49+
50+
## Response
51+
52+
If successful, this action returns a `204 No Content` response code.
53+
54+
## Examples
55+
56+
### Request
57+
58+
The following example shows a request.
59+
<!-- {
60+
"blockType": "request",
61+
"name": "contactfolderthis.permanentdelete"
62+
}
63+
-->
64+
``` http
65+
POST https://graph.microsoft.com/v1.0/users/b4c80c57-5c59-4a3d-912a-a83985988b82/contactFolders/AAlkasjlaskflakwndwkc=/permanentDelete
66+
```
67+
68+
69+
### Response
70+
71+
The following example shows the response.
72+
73+
<!-- {
74+
"blockType": "response",
75+
"truncated": true
76+
}
77+
-->
78+
``` http
79+
HTTP/1.1 204 No Content
80+
```
81+
Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
title: "event: permanentDelete"
3+
description: "Permanently delete an event and place it in the purges folder in the dumpster in the user's mailbox."
4+
author: "deepakbaghel99"
5+
ms.localizationpriority: high
6+
ms.subservice: "outlook"
7+
doc_type: apiPageType
8+
ms.date: 01/17/2025
9+
---
10+
11+
# event: permanentDelete
12+
13+
Namespace: microsoft.graph
14+
15+
Permanently delete an event and place it in the **purges** folder in the dumpster in the user's mailbox. Email clients such as outlook or outlook on the web can't access permanently deleted items. Unless there's a hold set on the mailbox, the items are permanently deleted after a set period of time.
16+
17+
For more information about item retention, see [Configure deleted item retention and recoverable items quotas](/exchange/configure-deleted-item-retention-and-recoverable-items-quotas-exchange-2013-help).
18+
19+
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
20+
21+
## Permissions
22+
23+
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
24+
25+
<!-- { "blockType": "permissions", "name": "event_permanentdelete" } -->
26+
[!INCLUDE [permissions-table](../includes/permissions/event-permanentdelete-permissions.md)]
27+
28+
## HTTP request
29+
30+
<!-- {
31+
"blockType": "ignored"
32+
}
33+
-->
34+
``` http
35+
POST /users/{usersId}/events/{eventId}/permanentDelete
36+
POST /groups/{groupsId}/events/{eventId}/permanentDelete
37+
POST /users/{usersId}/calendarView/{eventId}/permanentDelete
38+
POST /groups/{groupsId}/calendarView/{eventId}/permanentDelete
39+
POST /users/{usersId}/messages/{messageId}/event/permanentDelete
40+
POST /users/{usersId}/messages/{messageId}/event/instances/{eventId}/permanentDelete
41+
POST /users/{usersId}/messages/{messageId}/event/calendar/events/{eventId}/permanentDelete
42+
POST /users/{usersId}/messages/{messageId}/event/exceptionOccurrences/{eventId}/permanentDelete
43+
POST /users/{usersId}/messages/{messageId}/event/calendar/calendarView/{eventId}/permanentDelete
44+
```
45+
46+
## Request headers
47+
48+
|Name|Description|
49+
|:---|:---|
50+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
51+
52+
## Request body
53+
54+
Don't supply a request body for this method.
55+
56+
## Response
57+
58+
If successful, this action returns a `204 No Content` response code.
59+
60+
## Examples
61+
62+
### Request
63+
64+
The following example shows a request.
65+
<!-- {
66+
"blockType": "request",
67+
"name": "eventthis.permanentdelete"
68+
}
69+
-->
70+
``` http
71+
POST https://graph.microsoft.com/v1.0/users/b4c80c57-5c59-4a3d-912a-a83985988b82/AAasdijs0acjdjlksca=/permanentDelete
72+
```
73+
74+
75+
### Response
76+
77+
The following example shows the response.
78+
79+
<!-- {
80+
"blockType": "response",
81+
"truncated": true
82+
}
83+
-->
84+
``` http
85+
HTTP/1.1 204 No Content
86+
```
87+

0 commit comments

Comments
 (0)