This repository contains the Azure Migrate Export utility package that uses Azure Migrate's discovery and assessment information from and already deployed Azure Migrate project to generate a cohesive presentation for executives.

The following table consists of the link to latest release of the Azure Migrate Export utility

The users can download the zip file for the latest version of the Azure Migrate Export utility from Download

1. To download older versions or entire releases, please click this link AzMigExport Releases.
2. Click on the release which is to be download.
3. Click on the AzMigExport.zip Release asset to inititate the download.

Refer to the detailed "Azure Migrate Export" knowledge material from the links below:

1. AME detailed documentation - https://aka.ms/azuremigrateexportdocumentation
2. AME sample presentation: https://aka.ms/amepresentation
3. AME sample reports: https://aka.ms/amesamplereports
4. AME demo and training video for Partners: https://aka.ms/amedemovideo/partners
5. AME demo and training video for Sellers: https://aka.ms/amedemovideo/sellers
6. Download the Azure Migrate Export utility: https://aka.ms/azuremigrateexport
7. Link to Github repo : https://aka.ms/azuremigrateexportutility

If you find any bugs when using Azure Migrate Export utility, file an issue in our GitHub repository. Please fill out the issue template with the appropriate information.

Alternatively, see Azure Community Suppport, if you have any issues with Azure Migrate Export or Azure Migrate Services.

For any bugs that need urgent escalation, please write to us @ [email protected]

If there is a feature you would like to see in Azure PowerShell, please file an issue in our GitHub repository.

For escalation, please write to us @ [email protected]

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

For escalating any security report or issue, please write to us @ [email protected].

Additional infomration about reporting a security issur or bug can be found in SECURITY.md

Note: Please do not report security vulnerabilities through public GitHub issues.

If you would like to become a contributor to this project, see the instructions provided in Microsoft Azure Projects Contribution Guidelines:

Additional information about contributing to this repository can be found in CONTRIBUTING.md.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, please visit CLA at Microsoft.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

The data collected during the execution of Azure Migrate Export utility is the same as data collected by Azure Migrate during creation of Groups and Assessments via the portal. For further information, please read Azure Migrate Documentaion. This data helps us gauge the usability of the tool by counting the number of assessments that were created and the number of assessments that computed successfully.

Azure Migrate Export utility is licensed under the MIT License

License and usage information for Third-party Open Source softwares can be found at NOTICE.md.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines:. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.