01
Azure SQL Database
Example: A single application database with no cross-database queries or SQL Agent jobs
Approach: The platform service with the least to run. We check feature gaps in the assessment first.
Azure Migration
Azure migration services for apps and data
On Azure, the licences you already own can change which target is cheapest to run. Agnotic Technologies migrates Windows, SQL Server and Linux workloads to Microsoft Azure with Azure's own tools, and plans licensing and the landing zone before the first server moves.
Azure MigrateAzure SQL targetsLicensing plannedCAF landing zone
Trusted by global innovators
Azure migration
What does an Azure migration involve?
An Azure migration moves applications, databases and file shares into Microsoft Azure using Azure's own tools and licensing rules. Agnotic Technologies discovers workloads with Azure Migrate, chooses a target per workload, moves databases with Azure Database Migration Service, applies Azure Hybrid Benefit where your licences allow, and builds the landing zone first.
This page covers Azure tooling, targets and licensing. Migration strategy, phasing and rollback are on our cloud migration and modernization page, and choosing between providers is part of cloud consulting.
Windows Server and SQL Server estates gain the most from early licence planning, because the licence position changes which target is cheapest to run.
Decision table
Where does each workload land in Azure?
Typical targets. The Azure Migrate assessment and your licence list confirm each one.
| Source workload | Azure target | Azure tool | Main compatibility check |
|---|---|---|---|
| IIS web application | Azure App Service, or an Azure VM if it needs server access | Azure Migrate web app assessment and migration | Dependence on the local file system, the GAC, Windows services or COM components |
| SQL Server database | Azure SQL Managed Instance, Azure SQL Database or SQL Server on an Azure VM | Azure Database Migration Service | Cross-database queries, SQL Agent jobs, CLR and other features each target supports |
| Windows file share | Azure Files | Azure File Sync, or a copy tool such as AzCopy | NTFS permissions, the identity source and the SMB versions clients use |
| Linux application server | Azure VM, or Azure Kubernetes Service once containerized | Azure Migrate server migration | Distribution and kernel support, mounted storage and outbound connections |
| VMware estate | Azure VMs, or Azure VMware Solution to keep VMware tooling | Azure Migrate agentless discovery and migration | VMware tool licensing and whether the team wants to keep it |
Licensing
How do Windows Server and SQL Server licences change the plan?
We list every licence before we pick targets. Your licensing contact confirms entitlements.
- Azure Hybrid Benefit lets you apply SQL Server licences with Software Assurance to Azure SQL Database and Azure SQL Managed Instance
- A similar benefit applies Windows Server licences with Software Assurance to Azure VMs
- Extended Security Updates for older Windows Server versions are free on Azure and paid for elsewhere
- A server past end of support can buy time on Azure while its application is upgraded
- Each licence, its Software Assurance status and its planned target are recorded in one list
- Licence choices are revisited after migration, when real usage is known
Database targets
Which Azure SQL target fits your database?
02
Azure SQL Managed Instance
Example: Several databases that query each other and rely on SQL Agent
Approach: Close SQL Server compatibility as a managed service, with online migration through Azure DMS to keep downtime short.
03
SQL Server on an Azure VM
Example: Third-party software that needs a specific SQL Server version or operating system access
Approach: Full control of the instance. You patch and back it up, so we automate both.
Method
How does an Azure migration run?
Discover
Deploy the Azure Migrate appliance, or import an inventory, to collect servers, databases, web apps and their dependencies.
Assess
Readiness, target size and run cost per workload from Azure Migrate, checked against your licence list.
Build the landing zone
A platform landing zone for identity, network, policy and logging, then workload landing zones for each application team.
Migrate in waves
Workloads grouped by dependency, tested in Azure, then cut over with a rollback window.
Right-size and retire
Sizes adjusted to real usage, and the source systems switched off once each wave is signed off.
What goes into an Azure landing zone?
Built with the Cloud Adoption Framework before workloads arrive, so nothing is migrated into an unmanaged subscription.
Identity
Microsoft Entra ID groups, privileged access for administrators and managed identities for applications.
Network
Hub and spoke or Virtual WAN, private endpoints and a connection to your data centre.
Policy
Azure Policy for allowed regions, required tags, encryption and public access rules.
Logging and monitoring
Azure Monitor and Log Analytics, with activity logs kept for audit.
Subscriptions
Management groups with separate subscriptions per environment and workload.
Cost management
Budgets, tags and alerts set up on the first day.
Who do we run Azure migrations for?
Microsoft-centric enterprises
Active Directory, Windows Server and SQL Server estates moving to the platform they already license.
Windows Server estates near end of support
Servers moved to Azure for Extended Security Updates while applications are upgraded.
SQL Server application owners
Databases matched to Azure SQL Database, Managed Instance or a VM by the features they use.
Healthcare organizations
Workloads with PHI moved only to services in scope of the Microsoft BAA.
Software vendors
Hosted products moved to Azure to sit closer to customers who buy through Microsoft.
References
Microsoft references behind each migration
Cloud Adoption FrameworkAzure MigrateAzure DMSAzure Hybrid BenefitExtended Security UpdatesMicrosoft HIPAA BAA
Facts and sources
Facts behind Azure migrations
From Microsoft Learn, read on 21 October 2026. We re-check tool support for your versions at the start of each project.
Azure Migrate discovers workloads through a lightweight Azure Migrate appliance, which Microsoft recommends, through a collector, or by importing inventory data.
Source: Microsoft Learn: Azure Migrate overviewAzure Database Migration Service supports online migration to Azure SQL Managed Instance with minimal downtime, and offline migration to Azure SQL Database.
Source: Microsoft Learn: Azure Database Migration ServiceAzure Hybrid Benefit lets you allocate SQL Server licences with Software Assurance to Azure SQL Database and Azure SQL Managed Instance.
Source: Microsoft Learn: Azure Hybrid Benefit for Azure SQLExtended Security Updates for Windows Server are free of charge for servers hosted in Azure and available to purchase for servers outside Azure.
Source: Microsoft Learn: Extended Security Updates for Windows ServerAn Azure landing zone, as the Cloud Adoption Framework defines it, has two parts: a platform landing zone for shared governance, security and resources, and workload landing zones where application teams run their workloads.
Source: Microsoft Learn: Cloud Adoption Framework, Azure landing zones
Frequently Asked Questions
It depends on how many workloads move, which database targets they need and the cutover windows each system allows. After the Azure Migrate assessment we plan in waves, each with its own test and cutover.
For Azure SQL Managed Instance, Azure DMS supports online migration with minimal downtime. Other targets may need an offline move, so we plan the cutover window per database.
Microsoft offers covered entities and business associates a Business Associate Agreement that covers in-scope services. We check that each target service is in scope before any PHI moves.
The number of workloads, your licence position, the database targets, the state of your landing zone, data volume and cutover windows. We do not publish prices; you get a written proposal after scoping.
Yes. Azure Migrate handles servers from VMware, Hyper-V, physical hosts and other clouds, and each database moves with the tool that fits its engine and target.
Yes. We set up hybrid identity with Microsoft Entra Connect, so users keep one sign-in while workloads move.
We may use AI tools to summarize assessment exports or draft scripts, but every migration step is rehearsed in a test wave and reviewed by an engineer before cutover.