Skip to content

Commit 46200c9

Browse files
committed
raz updates
1 parent 3a49e61 commit 46200c9

File tree

4 files changed

+13
-4
lines changed

4 files changed

+13
-4
lines changed

articles/sentinel/connect-azure-active-directory.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,11 @@ Azure Sentinel enables you to collect data from [Azure Active Directory](../acti
3737

3838
1. In Azure Sentinel, select **Data connectors** and then click the **Azure Active Directory** tile.
3939

40-
2. Next to the logs you want to stream into Azure Sentinel, click **Connect**.
40+
1. Next to the logs you want to stream into Azure Sentinel, click **Connect**.
4141

42-
6. To use the relevant schema in Log Analytics for the Azure AD alerts, search for **SigninLogs** and **AuditLogs**.
42+
1. You can select whether you want the alerts from Azure AD to automatically generate incidents in Azure Sentinel automatically. Under **Create incidents** select **Enable** to enable the default analytic rule that creates incidents automatically from alerts generated in the connected security service. You can then edit this rule under **Analytics** and then **Active rules**.
43+
44+
1. To use the relevant schema in Log Analytics for the Azure AD alerts, search for **SigninLogs** and **AuditLogs**.
4345

4446

4547

articles/sentinel/connect-azure-atp.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,11 @@ If Azure ATP is deployed and ingesting your data, the suspicious alerts can easi
3939

4040
1. In Azure Sentinel, select **Data connectors** and then click the **Azure ATP** tile.
4141

42-
2. Click **Connect**.
42+
1. You can select whether you want the alerts from Azure ATP to automatically generate incidents in Azure Sentinel automatically. Under **Create incidents** select **Enable** to enable the default analytic rule that creates incidents automatically from alerts generated in the connected security service. You can then edit this rule under **Analytics** and then **Active rules**.
4343

44-
6. To use the relevant schema in Log Analytics for the Azure ATP alerts, search for **SecurityAlert**.
44+
1. Click **Connect**.
45+
46+
1. To use the relevant schema in Log Analytics for the Azure ATP alerts, search for **SecurityAlert**.
4547

4648
> [!NOTE]
4749
> If the alerts are larger than 30 KB, Azure Sentinel stops displaying the Entities field in the alerts.

articles/sentinel/connect-azure-security-center.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,11 @@ Azure Sentinel enables you to connect alerts from [Azure Security Center](../sec
3838
## Connect to Azure Security Center
3939

4040
1. In Azure Sentinel, select **Data connectors** and then click the **Azure Security Center** tile.
41+
4142
1. In the right, click **Connect** next to each subscription whose alerts you want to stream into Azure Sentinel. Make sure to upgrade each subscription to Azure Security Center Standard tier to stream alerts to Azure Sentinel.
4243

44+
1. You can select whether you want the alerts from Azure Security Center to automatically generate incidents in Azure Sentinel automatically. Under **Create incidents** select **Enable** to enable the default analytic rule that creates incidents automatically from alerts generated in the connected security service. You can then edit this rule under **Analytics** and then **Active rules**.
45+
4346
3. Click **Connect**.
4447

4548
4. To use the relevant schema in Log Analytics for the Azure Security Center alerts, search for **SecurityAlert**.

articles/sentinel/connect-cloud-app-security.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,8 @@ If Cloud App Security is deployed and ingesting your data, the alert data can ea
3737

3838
1. Select which logs you want to stream into Azure Sentinel, you can choose **Alerts**.
3939

40+
1. You can select whether you want the alerts from Microsoft Cloud App Security to automatically generate incidents in Azure Sentinel automatically. Under **Create incidents** select **Enable** to enable the default analytic rule that creates incidents automatically from alerts generated in the connected security service. You can then edit this rule under **Analytics** and then **Active rules**.
41+
4042
1. Click **Connect**.
4143

4244
1. To use the relevant schema in Log Analytics for the Cloud App Security alerts, search for **SecurityAlert**.

0 commit comments

Comments
 (0)