Skip to content

Commit e9e1569

Browse files
authored
Merge pull request #2674 from ElazarK/wi564984-update-to-SQL-plan
WI564984-rn sql
2 parents c209284 + a6d4f45 commit e9e1569

1 file changed

Lines changed: 20 additions & 1 deletion

File tree

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

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: What's new in Microsoft Defender for Cloud features
33
description: What's new and updated in Microsoft Defender for Cloud features
44
ms.topic: overview
55
ms.custom: references_regions
6-
ms.date: 03/31/2026
6+
ms.date: 04/01/2026
77
---
88

99
# What's new in Defender for Cloud features
@@ -28,6 +28,25 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
2828
<!-- 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. -->
2929
<!-- 6. In the Update column, add a bookmark to the H3 paragraph that you created (#<bookmark-name>) .-->
3030

31+
## April 2026
32+
33+
| Date | Category | Update |
34+
| -------- | -------- | -------- |
35+
| April 1, 2026 | Upcoming change | [Update to Defender for SQL servers on machines plan for Fairfax customers](#update-to-defender-for-sql-servers-on-machines-plan-for-fairfax-customers) |
36+
37+
### Update to Defender for SQL servers on machines plan for Fairfax customers
38+
39+
April 1, 2026
40+
41+
The Defender for SQL Server on machines plan in Microsoft Defender for Cloud protects SQL Server instances hosted on Azure, AWS, GCP, and on-premises machines.
42+
43+
To simplify onboarding and improve protection coverage, we're releasing an enhanced agent solution for Fairfax customers at the end of April. The new solution uses the existing SQL infrastructure, so you no longer need to deploy the Azure Monitor Agent (AMA).
44+
45+
**Required customer actions:**
46+
47+
- [Update Defender for SQL Servers on Machines plan configuration](update-sql-machine-configuration.md): If you enabled the Defender for SQL Server on machines plan before April 2026, follow these instructions to update your configuration.
48+
- [Verify SQL Server instances protection status](verify-machine-protection.md): With an estimated starting date of May 2026, you must verify the protection status of your SQL Server instances across your environments. Learn how to [troubleshoot deployment issues for Defender for SQL on machines configuration](troubleshoot-sql-machines-guide.md).
49+
3150
## March 2026
3251

3352
| Date | Category | Update |

0 commit comments

Comments
 (0)