Home

Welcome to the App-Service-Migration-Assistant wiki!

Looking for info about...

• The PowerShell scripts -> check out PowerShell Scripts
• Using Migration Assistant on Linux -> see Linux Notes
• Migrating Java applications from Apache Tomcat servers -> see TOMCAT Java Information

Deprecation Notice

The App Service Migration Assistant is an experimental and exploration tool for use in non-production environments. The App Service Migration Assistant tool remains available as-is but is no longer under development, and no further releases will be made available for new features nor bug or security fixes. The tool will stop working on or before November 2026.

If you are interested in an alternative to the App Service Migration Assistant, please consider using the migration PowerShell Scripts, which performs whole-server discovery and assessment including similar configuration-based checks.

---

Getting Started

• Download the App Service Migration Assistant here or the preview version
• Introducing App Service Migration Assistant for ASP.NET applications
• Migrate Your .NET Web Our New Step-By-Step Assistant - PRE10
• Start your .NET and PHP app assessments and migrations now

FAQs

1. Does App Service Migration Assistant support apps running on Windows and Linux? At this time we support .NET app migration from Windows OS to Azure App Service. Java Tomcat app migrations from Windows and Linux machines is in Preview.

2. What are the current server requirements to use the Migration Assistant?

   • Windows server IIS version greater than or equal to 7.5
   • Administrator access
   • Outbound connections allowed (see here for details: https://github.com/Azure/App-Service-Migration-Assistant/wiki/How-the-Assistant-Works#outbound-connections)
   • Local IIS configuration (clustered / remote IIS server configurations not supported)

3. What are all the readiness checks that the Azure Migration Assistant makes?

   • App Service Migration Assistant Readiness Checks

4. What are the current list of conditions that we consider that make an application unsuitable for automatic migration? Below is the list:

   • Apps that depend on session state that would break in our environment
   • Dependence on ISAPI filters
   • Dependence on ISAPI extensions
   • Bindings that are not HTTP or HTTPS
   • Endpoints that are not 80 for HTTP, or 443 for HTTPS
   • Authentication schemes other than anonymous
   • Dependencies on applicationhost.config settings made with a location tag
   • Applications that use more than one application pool
   • Use of an application pool that uses a custom account

Getting Help

The App Service Migration Assistant tool is no longer under development, and no further releases will be made available for new features nor bug or security fixes. The tool will stop working on or before November 2026.

Migration assistant tooling is provided as-is, you may search for workarounds or report issues by using the Issues page.