Hi @AZ_Abhishek Ramesh,
Welcome to the Microsoft Q&A and thank you for posting your questions here.As I understand that you are facing an issue while providing a unique migration name during the migration process.
Here are a few steps and tips that might help resolve this:
Double-Check Naming Rules: Ensure the migration name follows all the rules:
- Only alphanumeric characters and hyphens.
- Cannot start with a hyphen.
- Must be unique for the target server.
Clear Cache and Cookies: Sometimes, browser cache or cookies can cause issues. Try clearing them or using a different browser.
Check for Existing Migrations: Verify that no other migrations to the same target server have the same name. Even if a migration was deleted, it might still be reserved for a short period.
Use a Unique Identifier: Add a unique identifier to the name, such as a timestamp or a specific project code. For example, migration20241126 or project123-migration.
Region-Specific Availability: Ensure that the name you’re trying to use is not restricted by the region you selected when setting up the migration. Some names might be globally reserved or restricted in certain regions.
Try Using Azure CLI: If you are using the Azure Portal and still encountering issues, try creating the migration through the Azure CLI. This approach can sometimes provide more detailed error messages or guidance that might help resolve the problem.
Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.