Skip to content

Commit 579bafd

Browse files
Merge pull request #248371 from j0tr/j0tr-patch-2-1
Update upcoming-changes.md
2 parents 4ca527c + 343406b commit 579bafd

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/defender-for-cloud/upcoming-changes.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -161,9 +161,10 @@ Customers that rely on the `resourceID` to query DevOps recommendation data will
161161

162162
Queries will need to be updated to include both the old and new `resourceID` to show both, for example, total over time.
163163

164-
Additionally, customers that have created custom queries using the DevOps workbook will need to update the assessment keys for the impacted DevOps security recommendations.
164+
Additionally, customers that have created custom queries using the DevOps workbook will need to update the assessment keys for the impacted DevOps security recommendations. The template DevOps workbook is planned to be updated to reflect the new recommendations, although during the actual migration, customers may experience some errors with the workbook.
165+
166+
The experience on the recommendations page will be impacted and require customers to query under "All recommendations" to view the new DevOps recommendations. For Azure DevOps, deprecated assessments may continue to show for a maximum of 14 days if new pipelines are not run. Refer to [Defender for DevOps Common questions](https://learn.microsoft.com/azure/defender-for-cloud/faq-defender-for-devops#why-don-t-i-see-recommendations-for-findings-) for details.
165167

166-
The recommendations page's experience will have minimal impact and deprecated assessments may continue to show for a maximum of 14 days if new scan results aren't submitted.
167168

168169
### DevOps Resource Deduplication for Defender for DevOps
169170

0 commit comments

Comments
 (0)