Skip to content

Commit 0f6a109

Browse files
ReezaAli149ReezaAli149
authored
Merge branch 'main' into reezaali-gc-updates
2 parents 9a3c7ac + 89b8def commit 0f6a109

28 files changed

Lines changed: 966 additions & 48 deletions

‎api-reference/beta/api/agentriskdetection-get.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,7 @@ Content-Type: application/json
120120
"id": "1e384c2b0799b01834c0f886560a9a64e433135fe5b8607c535ebbfb03d2ee67",
121121
"agentId": "229da549-7a91-4365-900f-d4ef49a759a0",
122122
"agentDisplayName": "Ask HR Agent Identity",
123+
"blueprintId": "b3390471-68c5-466a-9ac2-b93e2a454532",
123124
"identityType": "agentIdentity",
124125
"activityDateTime": "2025-07-30T15:38:56.9594972Z",
125126
"detectedDateTime": "2025-07-30T15:38:56.9594972Z",
@@ -130,7 +131,8 @@ Content-Type: application/json
130131
"riskState": "atRisk",
131132
"riskEventType": "unfamiliarResourceAccess",
132133
"riskEvidence": "Agent targeted resources that it does not usually access.",
133-
"additionalInfo": ""
134+
"additionalInfo": "",
135+
"source": "activeDirectory"
134136
}
135137
}
136138
```

‎api-reference/beta/api/chat-delete-targetedmessages.md‎

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
title: "Delete targetedChatMessage"
3+
description: "Delete a specific targeted message from a chat context."
4+
author: "devjha-ms"
5+
ms.date: 02/16/2026
6+
ms.localizationpriority: medium
7+
ms.subservice: "teams"
8+
doc_type: apiPageType
9+
---
10+
11+
# Delete targetedChatMessage
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Delete a specific [targeted message](../resources/targetedchatmessage.md) from a chat context. Teams administrators can use this API to remove targeted messages from group chats.
18+
19+
## Permissions
20+
21+
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).
22+
23+
<!-- {
24+
"blockType": "permissions",
25+
"name": "chat-delete-targetedmessages-permissions"
26+
}
27+
-->
28+
[!INCLUDE [permissions-table](../includes/permissions/chat-delete-targetedmessages-permissions.md)]
29+
30+
## HTTP request
31+
32+
<!-- {
33+
"blockType": "ignored"
34+
}
35+
-->
36+
``` http
37+
DELETE /users/{user-id | userPrincipalName}/chats/{chat-id}/targetedMessages/{message-id}
38+
```
39+
40+
## Path parameters
41+
42+
|Parameter|Type|Description|
43+
|:---|:---|:---|
44+
|chat-id|String|Placeholder for the unique identifier of the chat where the targeted message was sent. Required.|
45+
|message-id|String|Placeholder for the unique identifier of the targeted message to delete. This ID is unique within the context of the specified chat and user. Required.|
46+
|user-id|String|Placeholder for the unique identifier or user principal name of the user to whom the targeted message was sent. Required.|
47+
48+
## Request headers
49+
50+
|Name|Description|
51+
|:---|:---|
52+
|Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
53+
54+
## Request body
55+
56+
Don't supply a request body for this method.
57+
58+
## Response
59+
60+
If successful, this method returns a `204 No Content` response code.
61+
62+
## Examples
63+
64+
### Request
65+
66+
The following example shows a request.
67+
68+
<!-- {
69+
"blockType": "request",
70+
"name": "delete_targetedchatmessage",
71+
"sampleKeys": ["f47b5f54-6968-4706-a522-31e842b12345", "19:eeaa4e946d674c4f8d4dded613780f45@thread.v2", "1580849738240"]
72+
}
73+
-->
74+
``` http
75+
DELETE https://graph.microsoft.com/beta/users/f47b5f54-6968-4706-a522-31e842b12345/chats/19:eeaa4e946d674c4f8d4dded613780f45@thread.v2/targetedMessages/1580849738240
76+
```
77+
78+
### Response
79+
80+
The following example shows the response.
81+
82+
<!-- {
83+
"blockType": "response",
84+
"truncated": true
85+
}
86+
-->
87+
``` http
88+
HTTP/1.1 204 No Content
89+
```

‎api-reference/beta/api/identityprotectionroot-list-agentriskdetections.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,7 @@ Content-Type: application/json
121121
"id": "1e384c2b0799b01834c0f886560a9a64e433135fe5b8607c535ebbfb03d2ee67",
122122
"agentId": "229da549-7a91-4365-900f-d4ef49a759a0",
123123
"agentDisplayName": "Copilot Application",
124+
"blueprintId": "b3390471-68c5-466a-9ac2-b93e2a454532",
124125
"identityType": "agentIdentity",
125126
"activityDateTime": "2025-07-30T15:38:56.9594972Z",
126127
"detectedDateTime": "2025-07-30T15:38:56.9594972Z",
@@ -131,7 +132,8 @@ Content-Type: application/json
131132
"riskState": "atRisk",
132133
"riskEventType": "unfamiliarResourceAccess",
133134
"riskEvidence": "Agent targeted resources that it does not usually access.",
134-
"additionalInfo": ""
135+
"additionalInfo": "",
136+
"source": "activeDirectory"
135137
}
136138
]
137139
}

‎api-reference/beta/api/protectionpolicybase-deactivate.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@ Namespace: microsoft.graph
1717

1818
Deactivate a [protectionPolicyBase](../resources/protectionpolicybase.md).
1919

20+
When a protection policy is deactivated, backup activity stops immediately, no new backups are taken, and the protected resources are no longer covered by the policy. Any backups taken before deactivation are retained according to the retention policy, after which they're offboarded. You can restore data using previous restore points even after deactivation.
21+
22+
To reactivate a deactivated policy, use the [activate](protectionpolicybase-activate.md) API.
23+
2024
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
2125

2226
## Permissions

‎api-reference/beta/api/protectionpolicybase-delete.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Delete protectionPolicyBase"
3-
description: "Delete a protection policy"
3+
description: "Delete a protectionPolicyBase object."
44
author: "tushar20"
55
ms.reviewer: "manikantsinghms"
66
ms.localizationpriority: medium
@@ -14,7 +14,9 @@ Namespace: microsoft.graph
1414

1515
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
1616

17-
Delete a protection policy. Read the properties and relationships of a [protectionPolicyBase](../resources/protectionpolicybase.md) object.
17+
Delete a [protectionPolicyBase](../resources/protectionpolicybase.md) object.
18+
19+
A protection policy can be deleted only after it was deactivated. When you delete a policy, all associated protection units are removed, and backup protection stops for the resources previously covered by the policy. Existing backup data is retained according to the retention policy before it's offboarded. You can restore data using previous restore points even after deletion.
1820

1921
[!INCLUDE [national-cloud-support](../../includes/global-only.md)]
2022

‎api-reference/beta/api/riskyagent-get.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,7 @@ Content-Type: application/json
119119
"@odata.type": "#microsoft.graph.riskyAgentUser",
120120
"id": "229da549-7a91-4365-900f-d4ef49a759a0",
121121
"agentDisplayName": "RiskyUserFirstPartyApp2",
122+
"blueprintId": "b3390471-68c5-466a-9ac2-b93e2a454532",
122123
"identityType": "agentUser",
123124
"isDeleted": false,
124125
"isEnabled": true,

‎api-reference/beta/api/riskyagent-list.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,7 @@ Content-Type: application/json
120120
"@odata.type": "#microsoft.graph.riskyAgentUser",
121121
"id": "ccdc88ee-d0bb-86b5-3500-1d38195c4d6f",
122122
"agentDisplayName": "RiskyUserFirstPartyApp2",
123+
"blueprintId": "b3390471-68c5-466a-9ac2-b93e2a454532",
123124
"identityType": "agentUser",
124125
"isDeleted": false,
125126
"isEnabled": true,

‎api-reference/beta/api/userteamwork-deletetargetedmessage.md‎

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
title: "userTeamwork: deleteTargetedMessage"
3+
description: "Delete a specific targeted message from a channel context."
4+
author: "devjha-ms"
5+
ms.date: 02/16/2026
6+
ms.localizationpriority: medium
7+
ms.subservice: "teams"
8+
doc_type: apiPageType
9+
---
10+
11+
# userTeamwork: deleteTargetedMessage
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Delete a specific [targeted message](../resources/targetedchatmessage.md) from a channel context. Teams administrators can use this API to remove targeted messages by providing the message ID, team ID, and channel ID.
18+
19+
## Permissions
20+
21+
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).
22+
23+
<!-- {
24+
"blockType": "permissions",
25+
"name": "userteamwork-deletetargetedmessage-permissions"
26+
}
27+
-->
28+
[!INCLUDE [permissions-table](../includes/permissions/userteamwork-deletetargetedmessage-permissions.md)]
29+
30+
## HTTP request
31+
32+
<!-- {
33+
"blockType": "ignored"
34+
}
35+
-->
36+
``` http
37+
POST /users/{user-id | userPrincipalName}/teamwork/deleteTargetedMessage
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+
|Content-Type|application/json. Required.|
46+
47+
## Request body
48+
49+
In the request body, supply a JSON representation of the parameters.
50+
51+
The following table lists the parameters that are required when you call this action.
52+
53+
|Parameter|Type|Description|
54+
|:---|:---|:---|
55+
|channelId|String|The unique identifier of the channel where the targeted message was sent. Required.|
56+
|messageId|String|The unique identifier of the targeted message to delete. This ID is unique within the context of the specified channel and user. Required.|
57+
|teamId|String|The unique identifier of the team that contains the channel where the targeted message was sent. Required.|
58+
59+
## Response
60+
61+
If successful, this action returns a `204 No Content` response code.
62+
63+
## Examples
64+
65+
### Request
66+
67+
The following example shows a request.
68+
69+
<!-- {
70+
"blockType": "request",
71+
"name": "userteamwork_deletetargetedmessage",
72+
"sampleKeys": ["f47b5f54-6968-4706-a522-31e842b12345"]
73+
}
74+
-->
75+
``` http
76+
POST https://graph.microsoft.com/beta/users/f47b5f54-6968-4706-a522-31e842b12345/teamwork/deleteTargetedMessage
77+
Content-Type: application/json
78+
79+
{
80+
"teamId": "3Aeeaa4e946d674c4f8d4dded613780f45@thread.v2",
81+
"channelId": "19:eeaa4e946d674c4f8d4dded613780f45@thread.v2",
82+
"messageId": "1580849738240"
83+
}
84+
```
85+
86+
### Response
87+
88+
The following example shows the response.
89+
90+
<!-- {
91+
"blockType": "response",
92+
"truncated": true
93+
}
94+
-->
95+
``` http
96+
HTTP/1.1 204 No Content
97+
```

0 commit comments

Comments
 (0)