You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSOAR-3221 : API Error NoRegisteredProviderFound on MS Sentinel Integration (#5326)
* CSOAR-3221 : API Error NoRegisteredProviderFound on MS Sentinel Integration
* CSOAR-3221 - added more info
* CSOAR-3221 : modified content
* Updates from review
---------
Co-authored-by: John Pipkin <[email protected]>
Microsoft Sentinel is a cloud-native security information and event manager (SIEM) platform that uses built-in AI to help analyze large volumes of data across an enterprise.
13
13
14
+
## Overview
15
+
16
+
### Purpose
17
+
18
+
This documentation outlines the Microsoft Sentinel integration, providing details on its capabilities, usage, and support for managing security incidents.
19
+
20
+
### Use cases
21
+
22
+
* Automatically fetch and process security incidents from Sentinel.
23
+
* Review incident details, comments, and related entities to streamline triage.
24
+
* Trigger automated incident management workflows, such as updating incident status, severity, or ownership using Update Incident, or adding context through Add Incident Comment.
25
+
* Remove false positives or resolved alerts by leveraging the Delete Incident action.
26
+
27
+
### Supported versions
28
+
29
+
* Microsoft Sentinel API (2023-02-01 and compatible preview versions)
30
+
* Azure Resource Manager endpoints
31
+
* Compatible with Azure Workspaces in supported regions like uksouth, westeurope, etc.
32
+
33
+
### Prerequisites
34
+
* Active Azure subscription with Microsoft Sentinel enabled
35
+
* A configured Log Analytics workspace
36
+
* Application registration with:
37
+
* Client ID
38
+
* Client Secret
39
+
* Tenant ID
40
+
* API permissions:
41
+
* Microsoft.SecurityInsights/*
42
+
* Microsoft.OperationalInsights/*
43
+
44
+
### Limitations
45
+
* Pagination (nextLink) must be handled carefully to avoid incorrect URL construction.
46
+
* Certain API versions may not be available in all regions.
47
+
* Incident response APIs may have throttling under the high load.
48
+
* Only incidents created after a specified timestamp can be fetched using filters.
49
+
14
50
## Actions
15
51
16
52
***List Incident Comments** (*Enrichment*) - Gather all comments for a specific incident.
@@ -30,8 +66,226 @@ import IntegrationsAuth from '../../../../reuse/integrations-authentication.md';
* Azure REST API limits: 12,000 requests/hour per subscription.
249
+
* Excess requests may trigger HTTP 429 ("Too Many Requests").
250
+
251
+
#### Troubleshooting
252
+
| Issue | Resolution |
253
+
| :-- |:-- |
254
+
| ResourceNotFound on pagination | Ensure you're not appending query parameters to the nextLink. Use as-is. |
255
+
| 403 Forbidden | Validate token scope and check if the app has required permissions. |
256
+
| nextLink missing or invalid | Always check for nextLink in the response and follow without modifying. |
257
+
258
+
### FAQ
259
+
260
+
#### What permissions are required to use this integration?
261
+
262
+
To access Microsoft Sentinel incidents and related data, the service principal must have Microsoft Sentinel Reader or Contributor role on the workspace. Additionally, it needs Reader access at the subscription or resource group level.
263
+
264
+
#### Is incident deletion reversible?
265
+
266
+
No, deleting an incident via API is permanent.
267
+
268
+
#### Is pagination handled automatically?
269
+
270
+
Yes. The integration supports auto-pagination via the nextLink field returned in API responses.
271
+
272
+
#### Is the Daemon action customizable for time ranges?
273
+
274
+
Yes, it supports a createdTime parameter to control how far back incidents are fetched.
275
+
276
+
#### Why am I getting a Resource Not Found error?
277
+
This may happen if:
278
+
* The workspace name, resource group, or subscription ID is incorrect.
279
+
* The incident or entity ID does not exist.
280
+
* The workspace is in a different region than expected.
281
+
* Or code is appending query parameters to a nextLink, which already contains them.
282
+
283
+
### Support
284
+
* For issues, questions, or improvements:
285
+
* Azure Support: Open a support request via [Azure Portal](https://portal.azure.com/)
286
+
* Microsoft [Q&A](https://learn.microsoft.com/answers)
287
+
* GitHub/Community Forums (if applicable): Check if your integration has a public repo for collaboration
288
+
35
289
## Change Log
36
290
37
291
* September 2, 2020 - First upload
@@ -52,4 +306,8 @@ For information about Microsoft Sentinel, see [Microsoft Sentinel documentation]
52
306
+ Updated the integration by adding new fields (**Cloud SOAR URL API URL**, **Access ID** , **Access Key**) to the configuration
53
307
+ October 29, 2024 (v1.6)
54
308
+ Updated **List Incident Entities V2** action in the output field.
55
-
309
+
+ April 26, 2025 (v1.7)
310
+
+ Enhanced **Microsoft Sentinel Incidents Daemon** Added support to seamlessly fetch subsequent paginated data.
0 commit comments