In June 2018, we released the App Service Migration Assessment Tool. The Assessment Tool was designed to help customers quickly and easily assess whether a site could be moved to Azure App Service by scanning an externally accessible (HTTP) endpoint. Today we’re pleased to announce the release of an updated version, the App Service Migration Assistant! The new version helps customers and partners move sites identified by the assessment tool by quickly and easily migrating ASP.Net sites to App Service.
The App Service Migration Assistant is designed to simplify your journey to the cloud through a free, simple, and fast solution to migrate ASP.Net applications from on-premises to the cloud. You can quickly:
- Assess whether your app is a good candidate for migration by running a scan of its public URL.
- Download the Migration Assistant to begin your migration.
- Use the tool to run readiness checks and general assessment of your app’s configuration settings, then migrate your app or site to Azure App Service via the tool.
Getting started
Download the App Service Migration Assistant. This tool works with iiS version 7.0 and above and will migrate site content and configuration to your Azure App Service subscription using either a new or existing App Service Plan.
How the tool works
The Migration Assistant tool is a local agent that performs a detailed assessment and then walks you through the migration process. The tool performs readiness checks as well as a general assessment of the web app’s configuration settings.
- IIS version less than 7.0
- Dependence on ISAPI filters
- Dependence on ISAPI extensions
- Bindings that are not HTTP or HTTPS
- Endpoints that are not port 80 for HTTP, or port 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
- URL Rewrite rules that depend on global settings
- Web farms – specifically shared configuration
0 Comments