Forum Discussion
The update alert (patch) operation is returning 404
We are trying to patch an alert using the api as described in https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fgraph%2Fdocs%2Fapi-reference%2Fbeta%2Fapi%2Falert_update&data=02%7C01%7C%7C597a0514da704e3b3df608d5c0974a01%7C621578286c4740509b89736f3284dbcf%7C1%7C0%7C636626678357643796&sdata=wtQfbW6FM7foLaLNUj2ju%2BeWI5pkzHzF1xzcj8YKcyc%3D&reserved=0 (using the beta version).
I've hidden sensitive id's or account names
For this alert:
{
"azureSubscriptionId": "<hidden>",
"riskScore": null,
"tags": [],
"id": "3AtSw2wW15Il3TLnyaQiOpHzGJo=",
"azureTenantId": "<hidden>",
"createdDateTime": "2018-05-10T07:23:37.683181Z",
"lastModifiedDateTime": "0001-01-01T00:00:00Z",
"assignedTo": null,
"category": "AnonymousLogin",
"closedDateTime": "2018-05-10T07:18:15.956229Z",
"comments": "",
"description": "User has successfully signed in from an IP address that has been identified as an anonymous proxy IP address. These proxies are used by individuals who want to hide their device’s IP address and may be used for malicious intent.",
"detectionIds": [],
"eventDateTime": "2018-05-10T07:18:15.956229Z",
"feedback": "unknown",
"malwareWasRunning": null,
"recommendedActions": [],
"severity": "Medium",
"sourceMaterials": [],
"status": "unknown",
"title": "Sign-in from an anonymous IP address",
"type": "unknown",
"vendorInformation": {
"provider": "IPC",
"providerVersion": "3.0",
"subProvider": "",
"vendor": "Microsoft"
},
"activityGroupStates": [],
"applicationStates": [],
"fileStates": [],
"hostStates": [],
"malwareStates": [],
"networkConnections": [],
"processes": [],
"triggers": [],
"userStates": [
{
"accountName": "<hidden>",
"domainName": "",
"logonDateTime": null,
"logonId": "0",
"logonIpAddress": "",
"logonLocation": "",
"logonType": "unknown",
"onPremisesSecurityIdentifier": "",
"riskScore": "0",
"userAccountType": "unknown",
"userPrincipalName": "<hidden>"
}
],
"vulnerabilityStates": []
}
When trying to update:
Url: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgraph.microsoft.com%2Fbeta%2Fsecurity%2Falerts%2F3AtSw2wW15Il3TLnyaQiOpHzGJo%3D&data=02%7C01%7C%7C597a0514da704e3b3df608d5c0974a01%7C621578286c4740509b89736f3284dbcf%7C1%7C0%7C636626678357974060&sdata=67DqpkyDupMI9B4wiFehUzy%2BzjQNHd3%2BLNqo7jCyEf4%3D&reserved=0
Method: PATCH
Request body:{
"assignedTo": "<hidden>",
"closedDateTime": "2018-05-23T08:32:34",
"comments": "Comment test",
"feedback": "unknown",
"status": "inProgress",
"tags": ["tag1"]
}
Everytime it returns:
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"request-id": "81b96eba-bdfb-451a-b029-92aa923f0ac5",
"date": "2018-05-23T08:33:17"
}
}
}
- The PATCH (update alert) feature is currently work in progress, as in our federated provider model it is actually implemented by each provider. We're working with our providers on supporting this feature and will update when available.
2 Replies
- Michael ShalevIron ContributorThe PATCH (update alert) feature is currently work in progress, as in our federated provider model it is actually implemented by each provider. We're working with our providers on supporting this feature and will update when available.
- Mohsin MalikCopper Contributor
I am getting the same... Opened a case with MS and was told using the patch method is not currently supported with the security API.