Skip to content

Commit 11a8a86

Browse files
Merge pull request #273102 from VandhanaMehta/docs-editor/whats-new-1713896279
Update whats-new.md
2 parents 57e9a81 + 56f2bf6 commit 11a8a86

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/mysql/flexible-server/whats-new.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,9 @@ This article summarizes new releases and features in Azure Database for MySQL fl
2828
- **Microsoft Defender for Cloud supports Azure Database for MySQL flexible server (General Availability)**
2929

3030
We’re excited to announce the general availability of the Microsoft Defender for Cloud feature for Azure Database for MySQL flexible server in all service tiers. The Microsoft Defender Advanced Threat Protection feature simplifies security management of Azure Database for MySQL flexible server instances. It monitors the server for anomalous or suspicious databases activities to detect potential threats and provides security alerts for you to investigate and take appropriate action, allowing you to actively improve the security posture of your database without being a security expert. [Learn more](/azure/defender-for-cloud/defender-for-databases-introduction)
31+
- **On-demand backup and Export (Preview)**
32+
33+
Azure Database for MySQL Flexible Server now gives the flexibility to trigger an on-demand backup of the server and export it to an Azure storage account (Azure blob storage). The feature is currently in public preview and available only in public cloud regions. [Learn more](./concepts-backup-restore.md#on-demand-backup-and-export-preview)
3134
- **Known Issues**
3235

3336
While attempting to enable the Microsoft Defender for Cloud feature for an Azure Database for MySQL flexible server, you may encounter the following error: ‘The server <server_name> is not compatible with Advanced Threat Protection. Please contact Microsoft support to update the server to a supported version.’ This issue can occur on MySQL Flexible Servers that are still awaiting an internal update. It will be automatically resolved in the next internal update of your server. Alternatively, you can open a support ticket to expedite an immediate update.”

0 commit comments

Comments
 (0)