Skip to content

Commit 98047b0

Browse files
committed
Final to publish
1 parent ecb6e2b commit 98047b0

File tree

2 files changed

+6
-10
lines changed

2 files changed

+6
-10
lines changed

articles/sentinel/detect-threats-custom.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ In the **Set rule logic** tab, you can either write a query directly in the **Ru
121121
122122
:::image type="content" source="media/tutorial-detect-threats-custom/advanced-scheduling.png" alt-text="Screenshot of advanced scheduling toggle and settings.":::
123123
124-
Future runnings of the rule will occur at the specified interval after the first running (see **Advanced scheduling** note below).
124+
Future runnings of the rule will occur at the specified interval after the first running.
125125
126126
The line of text under the **Start running** setting (with the information icon at its left) summarizes the current query scheduling and lookback settings.
127127
@@ -131,10 +131,6 @@ In the **Set rule logic** tab, you can either write a query directly in the **Ru
131131
>
132132
> These two settings are independent of each other, up to a point. You can run a query at a short interval covering a time period longer than the interval (in effect having overlapping queries), but you cannot run a query at an interval that exceeds the coverage period, otherwise you will have gaps in the overall query coverage.
133133
>
134-
> **Advanced scheduling**
135-
>
136-
> If you choose to start the running of a rule at a specific time (instead of automatically upon creation), be aware that the **actual** first run time of the rule may vary from the time you specified by up to half an hour in either direction. In any case, the interval for future runnings will be measured from the actual starting time of the previous run, not from the specified time.
137-
>
138134
> **Ingestion delay**
139135
>
140136
> To account for **latency** that may occur between an event's generation at the source and its ingestion into Microsoft Sentinel, and to ensure complete coverage without data duplication, Microsoft Sentinel runs scheduled analytics rules on a **five-minute delay** from their scheduled time.

articles/sentinel/whats-new.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,10 @@ To give you more flexibility in scheduling your analytics rule execution times a
2929

3030
## January 2023
3131

32-
- [Monitor SAP system health (Preview)](#monitor-sap-system-health-and-role-preview)
3332
- [New incident investigation experience (Preview)](#new-incident-investigation-experience-preview)
33+
- [Monitor SAP system health (Preview)](#monitor-sap-system-health-and-role-preview)
3434
- [Microsoft Purview Information Protection connector (Preview)](#microsoft-purview-information-protection-connector-preview)
3535

36-
### Monitor SAP system health and role (Preview)
37-
38-
To ensure proper functioning and performance of your SAP systems, you can now use the SAP data connector page to [monitor information about the health of your SAP systems](monitor-sap-system-health.md) and the status of the SAP roles for the system. You can also use an alert rule template to get information about the health of the SAP agent's data collection.
39-
4036
### New incident investigation experience (Preview)
4137

4238
SOC analysts need to understand the full scope of an attack as fast as possible to respond effectively.
@@ -49,6 +45,10 @@ Learn more about the new investigation experience:
4945
- [Understand Microsoft Sentinel's incident investigation and case management capabilities](incident-investigation.md)
5046
- [Navigate and investigate incidents in Microsoft Sentinel](investigate-incidents.md)
5147

48+
### Monitor SAP system health and role (Preview)
49+
50+
To ensure proper functioning and performance of your SAP systems, you can now use the SAP data connector page to [monitor information about the health of your SAP systems](monitor-sap-system-health.md) and the status of the SAP roles for the system. You can also use an alert rule template to get information about the health of the SAP agent's data collection.
51+
5252
### Microsoft Purview Information Protection connector (Preview)
5353

5454
With the new [Microsoft Purview Information Protection connector](connect-microsoft-purview.md), you can stream data from Microsoft Purview Information Protection (formerly Microsoft Information Protection or MIP) to Microsoft Sentinel. You can use the data ingested from the Microsoft Purview labeling clients and scanners to track, analyze, report on the data, and use it for compliance purposes.

0 commit comments

Comments
 (0)