![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 7.000000000000001%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Azure Database Migration service
An Azure service designed to help simplify, guide, and automate database migrations to Azure.
305 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 97%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Hi @Amir Ariely - The error is informational in that the one common trait of all supported migration scenarios is the migration direction or path always leads to Azure. Please reference the following document to see a comprehensive list of all migration options based upon source & target: Services and tools available for data migration scenarios (DMS Tool Matrix). The FAQ document is very helpful. The Data Migration Assistant that @AnuragSharma-MSFT referenced has an overview page and instructions on how to perform an assessment. Lastly, the Microsoft Data Migration Guide will walk you through all supported scenarios, if there is a lack of clarity on what migration paths are supported, etc.
Please let us know if the information provided has answered your question or if you require additional details.
Regards,
Mike