You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/migrate/migrate-whats-new.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,17 +15,17 @@ This article lists the various features and improvements that are available in V
15
15
16
16
## May 2025
17
17
18
-
This release includes the following features and improvements:
18
+
This release includes these features and improvements:
19
19
20
-
- Improved service error messaging, recommended actions, and [troubleshooting guidance](./migrate-troubleshoot.md).
21
-
- Fixed bug to surface`Not Found` errors for missing Azure Local resources.
20
+
- Improved service error messages, recommended actions, and [troubleshooting guidance](./migrate-troubleshoot.md).
21
+
- Fixed a bug that shows`Not Found` errors for missing Azure Local resources.
22
22
- Updated appliance error messages to correctly identify which migrate appliance is unresponsive.
23
23
- Enabled static IP migrations to support multiple IP pools on a single logical network.
24
24
25
25
26
26
## April 2025
27
27
28
-
This release includes the following features and improvements:
28
+
This release includes these features and improvements:
29
29
30
30
-**Linux VM static IP migration support** – Azure Migrate to Azure Local migrations now support preserving static IP addresses during Linux virtual machine (VM) migrations.
31
31
@@ -47,7 +47,7 @@ This release includes the following features and improvements:
47
47
48
48
## March 2025
49
49
50
-
This release includes the following features and improvements:
50
+
This release includes these features and improvements:
51
51
52
52
-**Critical bug fixes (released in version 2503)** – Azure Local version 2503 includes fixes for two major issues that previously affected migrated VMs:
0 commit comments