Skip to content

Commit 2084c6b

Browse files
Merge pull request #280584 from hariramt/task/AutoMigrationDocv1.2
Update notification duration
2 parents 09f2a45 + 447585c commit 2084c6b

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/postgresql/migrate/automigration-single-to-flexible-postgresql.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,11 +35,14 @@ The automigration provides a highly resilient and self-healing offline migration
3535

3636
## Nomination Eligibility
3737

38-
If you own a Single Server workload with no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for automigration. Submit your server details through this [form](https://forms.office.com/r/4pF55L8TxY).
38+
> [!NOTE]
39+
> The nomination process is for users who want to voluntarily fast-track their migration to Flexible server.
40+
41+
If you own a Single Server workload, you can now nominate yourself (if not already scheduled by the service) for automigration. Submit your server details through this [form](https://forms.office.com/r/4pF55L8TxY).
3942

4043
## Configure migration alerts and review migration schedule
4144

42-
Servers eligible for automigration are sent an advance notification by the service.
45+
Servers eligible for automigration are sent advance Azure health notifications by the service. The health notifications are sent **30 days, 14 days and 7 days** before the migration date. Notifications are also sent when the migration is **in progress, has completed, and 6 days after migration** before the legacy Single server is dropped. You can check and configure the Azure portal to receive the automigration notifications via email or SMS.
4346

4447
Following described are the ways to check and configure automigration notifications:
4548

0 commit comments

Comments
 (0)