|
1 | 1 | --- |
2 | | -title: "Update alert" |
| 2 | +title: "Update alert (deprecated)" |
3 | 3 | description: "Update an editable alert property within any integrated solution to keep alert status and assignments in sync across solutions." |
4 | 4 | ms.localizationpriority: medium |
5 | 5 | author: "preetikr" |
6 | 6 | ms.subservice: "security" |
7 | 7 | doc_type: apiPageType |
8 | 8 | ms.date: 04/05/2024 |
| 9 | +ROBOTS: NOINDEX |
9 | 10 | --- |
10 | 11 |
|
11 | | -# Update alert |
| 12 | +# Update alert (deprecated) |
12 | 13 |
|
13 | 14 | Namespace: microsoft.graph |
14 | 15 |
|
15 | 16 | [!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)] |
16 | 17 |
|
| 18 | +[!INCLUDE [security-alerts-v1-deprecation](../includes/security-alerts-v1-deprecation.md)] |
| 19 | + |
17 | 20 | Update an editable **alert** property within any integrated solution to keep alert status and assignments in sync across solutions. This method updates any solution that has a record of the referenced alert ID. |
18 | 21 |
|
19 | 22 | [!INCLUDE [national-cloud-support](../../includes/global-us.md)] |
@@ -43,7 +46,7 @@ PATCH /security/alerts/{alert_id} |
43 | 46 |
|
44 | 47 | ## Request body |
45 | 48 |
|
46 | | -In the request body, supply a JSON representation of the values for relevant fields that should be updated. The body **must** contain the **vendorInformation** property with valid `provider` and `vendor` fields. The following table lists the fields that can be updated for an alert. The values for existing properties that are not included in the request body will not change. For best performance, don't include existing values that haven't changed. |
| 49 | +[!INCLUDE [table-intro](../../includes/update-property-table-intro.md)] |
47 | 50 |
|
48 | 51 | | Property | Type |Description| |
49 | 52 | |:---------------|:--------|:----------| |
@@ -128,7 +131,7 @@ Content-type: application/json |
128 | 131 |
|
129 | 132 | #### Response |
130 | 133 |
|
131 | | -The following is an example of a successful response. |
| 134 | +The following example shows a successful response. |
132 | 135 | <!-- { |
133 | 136 | "blockType": "response" |
134 | 137 | } --> |
@@ -202,7 +205,7 @@ Prefer: return=representation |
202 | 205 |
|
203 | 206 | #### Response |
204 | 207 |
|
205 | | -The following is an example of the response when the optional `Prefer: return=representation` request header is used. |
| 208 | +The following example shows a response when the optional `Prefer: return=representation` request header is used. |
206 | 209 |
|
207 | 210 | >**Note:** The response object shown here might be shortened for readability. |
208 | 211 | <!-- { |
|
0 commit comments