Skip to content

Commit 1d14f3b

Browse files
updating
1 parent 829925f commit 1d14f3b

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

articles/defender-for-cloud/release-notes-recommendations-alerts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,9 @@ New and updated recommendations and alerts are added to the table in date order.
3131
<!-- 2. In Date, specify the date you added the item.-->
3232
<!-- 3. In Type specify whether it's a Recommendation or Alert.-->
3333
<!-- 4. In State specify whether it's GA, Preview, Update, Deprecation, Upcoming Update, or Upcoming Deprecation, or other as needed.-->
34-
<!-- 3. If you're adding a new recommendation entry to the table, first add the recommendation to the relevant recommendations-reference page. There are multiple pages for recommendations for AI, APIs, App Services, Compute, Container, Data, DevOps, Identity & Access, IoT, networking, and deprecated recommendations.-->
35-
<!-- 4. If you're adding a new alert here, make sure you also add it to the alerts reference page-->
36-
<!-- 5. After adding the alert to the alerts reference page or adding the recommendation to the recommendations page, in Name, add the name of the alert or recommendation, and add a link to the relevant entry that you added in the alerts or recommendations reference page. Note that all details about the alert or recommendation should be on the reference page. This page should only have minimum information.-->
34+
<!-- 5. If you're adding a new recommendation entry to the table, first add the recommendation to the relevant recommendations-reference page. There are multiple pages for recommendations for AI, APIs, App Services, Compute, Container, Data, DevOps, Identity & Access, IoT, networking, and deprecated recommendations.-->
35+
<!-- 6. If you're adding a new alert here, make sure you also add it to the alerts reference page-->
36+
<!-- 7. After adding the alert to the alerts reference page or adding the recommendation to the recommendations page, in Name, add the name of the alert or recommendation, and add a link to the relevant entry that you added in the alerts or recommendations reference page. Note that all details about the alert or recommendation should be on the reference page. This page should only have minimum information.-->
3737

3838

3939
**Date** | **Type** | **State** | **Name**

articles/defender-for-cloud/release-notes.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,12 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
1717
>
1818
> `https://aka.ms/mdc/rss`
1919
20+
<!-- 1. The docs team update this article at the beginning of each month. For example, on August 1 2024 we'll add all the features that were new, updated, and deleted in July 2024.-->
21+
<!-- 2. If you want to add an item in the middle of the month, go ahead and do that. You should add the item and sign off on the PR. We'll check your entry at the beginning of the next month.-->
22+
<!-- 3. In Date, specify the date you added the entry.-->
23+
<!-- 4. In Category, specify whether the item is GA, Preview, Update, Deprecation, Upcoming update, Upcoming deprecation.-->
24+
<!-- 5. Under the relevant month, add a short paragraph about the new feature. Give the paragraph an H3 (###) heading. Keep the title short and not rambling. -->
25+
<!-- 6. In the Update column, add a bookmark to the H3 paragraph that you created (#<bookmark-name>) .-->
2026

2127
## June 2024
2228

0 commit comments

Comments
 (0)