Skip to content

Commit 144d944

Browse files
committed
add important message
1 parent 1ddd418 commit 144d944

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/mysql/migrate/whats-happening-to-mysql-single-server.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,8 @@ ms.custom:
1616

1717
[!INCLUDE [applies-to-mysql-single-server](../includes/applies-to-mysql-single-server.md)]
1818

19-
**Azure Database for MySQL - Single Server is on the retirement path** and is scheduled for retirement by **September 16, 2024**.
19+
> [!IMPORTANT]
20+
> **Azure Database for MySQL - Single Server is on the retirement path** and is scheduled for retirement by **September 16, 2024**.
2021
2122
As part of this retirement, we'll no longer support creating new Single Server instances from the Azure portal beginning **January 16, 2023** and Azure CLI beginning **March 19, 2024**. If you still need to create Single Server instances to meet business continuity needs, raise an Azure support ticket. You'll still be able to create read replicas and perform restores (PITR and geo-restore) for your existing single server instance and this will continue to be supported until the sunset date of **September 16, 2024**.
2223

0 commit comments

Comments
 (0)