Skip to content

Commit 5dba246

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into wi236734-copilot-in-mdc
2 parents 9cfdf3a + fc9ffb6 commit 5dba246

File tree

5 files changed

+27
-8
lines changed

5 files changed

+27
-8
lines changed

articles/backup/backup-azure-database-postgresql-support-matrix.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,6 @@ Azure Database for PostgreSQL server backup is available in all regions, except
3030
- Cross-region backup isn't supported. Therefore, you can't back up an Azure PostgreSQL server to a vault in another region. Similarly, you can only restore a backup to a server within the same region as the vault. However, we support cross-subscription backup and restore.
3131
- Private endpoint-enabled Azure PostgreSQL servers can be backed up by allowing trusted Microsoft services in the network settings.
3232
- Only the data is recovered during restore; _roles_ aren't restored.
33-
- Protection of PostgreSQL Flexible server is currently not supported.
3433
## Next steps
3534

3635
- [Back up Azure Database for PostgreSQL server](backup-azure-database-postgresql.md)

articles/defender-for-cloud/faq-permissions.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ metadata:
33
title: Common questions - permissions
44
description: This FAQ answers questions about permissions in Microsoft Defender for Cloud, a product that helps you prevent, detect, and respond to threats.
55
services: defender-for-cloud
6-
author: elkrieger
6+
author: dcurwin
77
ms.author: elkrieger
88
manager: raynew
99
ms.topic: faq

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Learn more about [Copilot for Security in Defender for Cloud](copilot-security-i
4343
| May 28 | [Remediate security baseline recommendation](#remediate-security-baseline-recommendation) |
4444
| May 22 | [Configure email notifications for attack paths](#configure-email-notifications-for-attack-paths) |
4545
| May 9 | [Checkov integration for IaC scanning in Defender for Cloud (Preview)](#checkov-integration-for-iac-scanning-in-defender-for-cloud-preview) |
46-
| May 6 | [AI multicloud security posture management is publicly available for Azure and AWS (Preview)](#ai-multicloud-security-posture-management-is-publicly-available-for-azure-and-aws-preview) |
46+
| May 6 | [AI multicloud security posture management is available for Azure and AWS (Preview)](#ai-multicloud-security-posture-management-is-available-for-azure-and-aws-preview) |
4747
| May 2 | [Updated security policy management is now generally available](#updated-security-policy-management-is-now-generally-available) |
4848
| May 1 | [Defender for open-source databases is now available on AWS for Amazon instances (Preview)](#defender-for-open-source-databases-is-now-available-on-aws-for-amazon-instances-preview) |
4949

@@ -111,7 +111,7 @@ May 7, 2024
111111

112112
We're announcing the general availability (GA) of [permissions management](permissions-management.md) in Defender for Cloud.
113113

114-
### AI multicloud security posture management is publicly available for Azure and AWS (Preview)
114+
### AI multicloud security posture management is available for Azure and AWS (Preview)
115115

116116
May 6, 2024
117117

articles/defender-for-cloud/security-policy-concept.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Security policies in Microsoft Defender for Cloud
3-
description: Learn about security policies, standards, and recommendations in Microsoft Defender for Cloud.
3+
description: Learn about security policies, standards, and recommendations to improve your cloud security posture in Microsoft Defender for Cloud.
44
ms.topic: conceptual
55
ms.date: 11/27/2023
66
---
@@ -41,9 +41,9 @@ Recommendations derived from assessments against custom standards appear togethe
4141

4242
### Custom recommendations
4343

44-
All customers with Azure subscriptions can create custom recommendations based on Azure Policy. With Azure Policy, you create a policy definition, assign it to a policy initiative, and merge that initiative and policy into Defender for Cloud.
44+
Using custom recommendations based on Kusto Query Language (KQL) is the recommended approach and is supported for all clouds, but requires enabling the [Defender CSPM plan](concept-cloud-security-posture-management.md). With these recommendations, you specify a unique name, a description, remediation steps, severity, and relevant standards. You add recommendation logic with KQL. A query editor provides a built-in query template that you can tweak, or you can write your KQL query.
4545

46-
Custom recommendations based on Kusto Query Language (KQL) are available for all clouds, but require enabling the [Defender CSPM plan](concept-cloud-security-posture-management.md). With these recommendations, you specify a unique name, a description, steps for remediation, severity, and which standards the recommendation should be assigned to. You add recommendation logic with KQL. A query editor provides a built-in query template that you can tweak as needed, or you can write your KQL query from scratch.
46+
Alternatively, all Azure customers can onboard their Azure Policy custom initiatives as custom recommendations (legacy approach).
4747

4848
For more information, see [Create custom security standards and recommendations in Microsoft Defender for Cloud](create-custom-recommendations.md).
4949

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

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Important upcoming changes
33
description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan.
44
ms.topic: overview
5-
ms.date: 06/03/2024
5+
ms.date: 06/10/2024
66
---
77

88
# Important upcoming changes to Microsoft Defender for Cloud
@@ -25,6 +25,7 @@ If you're looking for the latest release notes, you can find them in the [What's
2525

2626
| Planned change | Announcement date | Estimated date for change |
2727
|--|--|--|
28+
| [SQL vulnerability assessment automatic enablement using express configuration on unconfigured servers](#sql-vulnerability-assessment-automatic-enablement-using-express-configuration-on-unconfigured-servers) | June 10, 2024 | July 10, 2024 |
2829
| [Changes to identity recommendations](#changes-to-identity-recommendations) | June 3, 2024 | July 2024 |
2930
| [Removal of FIM over AMA and release of new version over Defender for Endpoint](#removal-of-fim-over-ama-and-release-of-new-version-over-defender-for-endpoint) | May 1, 2024 | June 2024 |
3031
| [Deprecation of system update recommendations](#deprecation-of-system-update-recommendations) | May 1, 2024 | May 2024 |
@@ -47,6 +48,25 @@ If you're looking for the latest release notes, you can find them in the [What's
4748
| [Deprecating two security incidents](#deprecating-two-security-incidents) | | November 2023 |
4849
| [Defender for Cloud plan and strategy for the Log Analytics agent deprecation](#defender-for-cloud-plan-and-strategy-for-the-log-analytics-agent-deprecation) | | August 2024 |
4950

51+
## SQL vulnerability assessment automatic enablement using express configuration on unconfigured servers
52+
53+
**Announcement date: June 10, 2024**
54+
55+
**Estimated date for change: July 10, 2024**
56+
57+
Originally, SQL Vulnerability Assessment (VA) with Express Configuration was only automatically enabled on servers where Microsoft Defender for SQL was activated after the introduction of Express Configuration in December 2022.
58+
59+
We will be updating all Azure SQL Servers that had Microsoft Defender for SQL activated before December 2022 and had no existing SQL VA policy in place, to have SQL Vulnerability Assessment (SQL VA) automatically enabled with Express Configuration.
60+
61+
The implementation of this change will be gradual, spanning several weeks, and does not require any action on the user’s part.
62+
63+
> [!NOTE]
64+
> This change applies to Azure SQL Servers where Microsoft Defender for SQL was activated either at the Azure subscription level or at the individual server level.
65+
>
66+
> Servers with an existing classic configuration (whether valid or invalid) will not be affected by this change.
67+
>
68+
> Upon activation, the recommendation ‘SQL databases should have vulnerability findings resolved’ may appear and could potentially impact your secure score.
69+
5070
## Changes to identity recommendations
5171

5272
**Announcement date: June 3, 2024**

0 commit comments

Comments
 (0)