Moving one typical small-business Windows server to Azure runs about $340 to $560 a month at Microsoft’s list prices, depending on commitment term and licensing, plus a one-time migration project that is quoted after an assessment. That is the Azure server migration cost in two parts, and Microsoft publishes almost all of the monthly part.
I plan and run these moves myself as part of our cloud migration services, from a single aging file server up to a small multi-server environment. The monthly number tends to come up first. It’s also the part you can check yourself.
Every price below comes from Microsoft’s own Azure Retail Prices API, pulled on September 25, 2026, for the East US region, in US dollars, using the 730-hour month Microsoft uses in its pricing calculator. Prices change. The structure doesn’t.
The example is one Windows server running file shares, Active Directory, and a line-of-business application for an office of about 20 people. Very ordinary. A lot of offices in Rockland, Westchester, and Bergen run exactly this box in a closet.

The Monthly Bill, Line by Line
Azure server migration cost is a recurring monthly bill made of compute, the Windows Server license, managed disks, backup, and the network connection back to your office, plus a one-time project cost to copy, test, and cut the server over. The monthly side is metered. The project side is labor.
Here is the monthly side for that 20-person office, at pay-as-you-go rates.
| Line item | What it is | Monthly list price |
|---|---|---|
| VM compute | D4s v5, 4 virtual CPUs and 16 GiB of memory | $140.16 |
| Windows Server license | Billed by the hour with the VM | $134.32 |
| System disk | Premium SSD P10, 128 GiB | $19.71 |
| Data disk | Premium SSD P20, 512 GiB | $73.22 |
| Azure Backup | One protected VM with 50 to 500 GB of data | $10.00 |
| Backup storage | About 600 GB, geo-redundant | $26.88 |
| VPN gateway | VpnGw1AZ, the office-to-Azure connection | $153.30 |
| Public IP address | Standard static IPv4 for the gateway | $3.65 |
| Data leaving Azure | First 100 GB each month | $0.00 |
| Total | Pay-as-you-go, no commitment | $561.24 |
$561.24 a month. Nobody should pay exactly that. The next two sections explain why.
Look where the money goes. The virtual machine itself, compute and license together, is $274.48, just under half the total. The rest is disks, backup, and the connection. An estimate built on the VM price alone is how a server that looks like $275 a month turns into a $560 invoice.
The sizing is an assumption, and yours will differ. I gave the VM 4 virtual CPUs and 16 GiB of memory, a 128 GiB system disk and a 512 GiB data disk on Premium SSD, and about 600 GB of backup storage once retention builds up. Change those and the numbers move. The shape stays the same.
Half the VM Price Is the Windows License
Go back to the first two rows. On Microsoft’s general-purpose D-series, a Windows VM with 4 virtual CPUs costs $0.376 an hour, and the identical VM running Linux costs $0.192. The $0.184 difference is the Windows Server license, rented by the hour. That’s $134.32 a month. Forty-nine percent of the VM line.
That matters. The two main ways to lower an Azure bill only touch one of those two rows. Microsoft’s documentation on reserved VM instances says a reservation “covers only the compute part of your VM usage,” and that the charges “don’t include Windows software costs.” The savings plan for compute works the same way. It “doesn’t cover software, networking, or storage charges.”
| How you pay for the D4s v5 | Compute | Windows license | VM per month | Versus pay-as-you-go |
|---|---|---|---|---|
| Pay-as-you-go | $140.16 | $134.32 | $274.48 | Baseline |
| 1-year reservation ($1,038 a year) | $86.50 | $134.32 | $220.82 | About 20% lower |
| 3-year reservation ($1,993 for the term) | $55.36 | $134.32 | $189.68 | About 31% lower |
| 3-year reservation plus Azure Hybrid Benefit | $55.36 | $0.00 | $55.36 | About 80% lower |
Microsoft advertises its reserved instances as saving “up to 72%.” The footnote ties that figure to a 64-core SUSE Linux VM on a three-year term. On a Windows server where you can’t bring your own license, three years of commitment gets you about 31 percent. Real money. Not 72.
The row that really moves is the license, through Azure Hybrid Benefit. With it, Microsoft says, “you only need to pay for the base compute rate of the VM,” and “the base compute rate is equal to the Linux rate.” The condition is the catch. You need “on-premises core licenses for Windows Server from an applicable program with active Software Assurance or qualifying subscription licenses,” and even a 4-core VM needs a minimum of 8 core licenses.
Many small offices won’t qualify. The Windows Server license on a typical office server usually came preinstalled on the hardware from the manufacturer, with no Software Assurance attached, and that doesn’t meet the test. It’s worth checking anyway. If your licensing does run through a volume agreement, the table above shows what that’s worth.
One more string on commitments. Microsoft’s exchange and refund policy says VM reservations bought after February 1, 2027 won’t be exchangeable, and savings plans “can’t be canceled or refunded.” I wouldn’t put a server on a three-year term until it has run in Azure long enough to prove it’s the right size. A month or two of real usage data beats any sizing estimate, mine included.
The Connection Back to the Office
Your people still sit in the office. Something has to join the office network to the Azure network, and for most small businesses that something is a site-to-site VPN, which Microsoft’s VPN Gateway documentation describes as “a cross-premises IPsec/IKE VPN tunnel connection between the VPN gateway and an on-premises VPN device.”
That tunnel isn’t free. The entry-level production gateway, VpnGw1AZ, lists at $0.21 an hour. $153.30 a month. That’s more than half of what the pay-as-you-go Windows VM costs, and roughly 80 percent of the VM once it’s on a three-year reservation.
Two recent changes matter here. Microsoft’s gateway SKU guidance says that since November 1, 2025, “you can no longer create new VPN gateways (VpnGw1-5 SKUs) that aren’t supported by an availability zone,” so the older VpnGw1 at $0.19 an hour, which still appears in Microsoft’s own price list, isn’t available for a new build. The Basic SKU at $0.036 an hour still exists. Microsoft says it “shouldn’t be used for production purposes.” I agree with them.
The good news is that one gateway serves the whole Azure network behind it. The second and third servers don’t add another $153. And the office end of the tunnel is your firewall, which is why a server move is a firewall project as well, and why it sits alongside our managed firewall and network security work rather than apart from it.

Backup and a Second Copy Are Separate Meters
A server in Azure isn’t backed up just because it’s in Azure. Backup is its own service with its own bill.
Azure Backup charges a protected-instance fee of $5 a month for a VM holding up to 50 GB, $10 for 50 to 500 GB, and another $10 for each 500 GB beyond that. Storage is extra. Microsoft is explicit that “charges for storage are separate from the cost of Azure Backup Protected Instances,” at $0.0224 per GB a month for locally redundant storage or $0.0448 for geo-redundant storage, which keeps a copy in a second region. For a production server, geo-redundant is the one I’d pick. The difference on 600 GB is $13.44 a month.
A full standby copy of the server in another region is a different product again. Azure Site Recovery lists at $25 a month per protected server, free for the first 31 days, and the standby server’s compute is only billed when you actually run a test failover or a real one. Not every office needs it. Some do.
This is the part of the Azure bill I think owners undervalue. Moving a company onto Azure with a terminal server raises the cost per seat significantly. It also builds disaster recovery right into their system. It isn’t an industry thing, either. One of our construction clients runs exactly this way, and nothing about construction requires it. The backup and disaster recovery planning comes along with the move instead of being a separate project someone keeps postponing.
Getting data out does cost money, though. Microsoft’s bandwidth pricing makes the first 100 GB leaving Azure each month free, then charges $0.087 per GB. Data coming in is free. For a normal office, egress stays small. A full restore down to the office in an emergency does not. Plan for it.
If a Terminal Server Is Part of the Plan
Some offices don’t just move the server. They move the desktops too, and people log into a session host in Azure from wherever they are. That setup needs a bigger VM. A D8s v5 with 8 virtual CPUs and 32 GiB of memory lists at $548.96 a month on pay-as-you-go Windows rates, or $379.36 with a three-year reservation and the license paid hourly.
It also needs access licenses. Microsoft’s Remote Desktop Services licensing is clear that “each user and device that connects to a Remote Desktop Services session host” running Windows Server “needs a Remote Desktop Services (RDS) client access license (CAL).” Those are a separate license purchase, not an Azure meter.
Microsoft’s other route is Azure Virtual Desktop. Its licensing page lists Microsoft 365 Business Premium among the licenses that include access to Windows 11 multi-session hosts. The virtual machines underneath are still billed like any others. Access rights are not compute.
The One-Time Cost of Moving It
Microsoft’s own migration tooling costs nothing to start. The Azure Migrate pricing page says the tools “are available at no additional charge,” and that server migration “is free for first 180 days for each machine,” after which $25 a month per replicated instance applies. Storage and data transfer during replication can still be billed.
Data coming into Azure is free. It isn’t fast. At 20 Mbps of upload, which is the FCC’s own broadband benchmark for upload speed, 500 GB takes about 56 hours of continuous transfer at full line rate, and nobody wants the office upload pinned for 56 hours during the workweek. So the first copy replicates in the background while the old server keeps working, the changes sync afterward, and the cutover happens once the Azure copy has been tested. Nothing goes dark mid-move.

The migration project itself gets scoped and quoted separately, based on how many servers and how much data are actually moving. We give a real number after the assessment, not a guess. Here is what moves that number.
- How many servers there are, and how many jobs each one quietly does.
- Data volume, measured against your upload speed.
- What the server actually does, because if it is mostly file shares, moving those files to SharePoint instead of a file server can take the server out of the picture entirely, and that is a smaller and cheaper project than rebuilding it in Azure.
- The line-of-business application. Some vendors have to reinstall or relicense their own software, on their own calendar, and that sets the pace more than anything we do.
- Identity. Active Directory can stay on a VM in Azure or move toward Microsoft Entra ID, and those are different amounts of work.
- Testing. Every application gets opened and used against the Azure copy before anyone cuts over.
Windows Server 2016 Changes the Math in January
Windows Server 2016 reaches end of extended support on January 12, 2027, per Microsoft’s lifecycle page. After that, security updates come only through Extended Security Updates, which Microsoft’s ESU program page offers for up to three more years.
Where the server runs decides what those cost. Microsoft’s ESU FAQ states that “Extended Security Updates are free for VMs in Azure.” On-premises, they generally require Software Assurance through a volume licensing program, whether bought directly or through Azure Arc. A small office running an OEM license has none of that. For that office, a 2016 server in Azure keeps getting patched, while the same server in the closet does not.
Still, don’t stay on 2016. The better project moves the workload onto a current Windows Server version on the way into Azure.
Where Azure Bills Go Wrong
These are the mistakes that turn a reasonable estimate into an unpleasant invoice, and nearly every one of them comes from treating the Azure bill as a single number instead of the list of separate meters it actually is.
- Sizing the VM from the old hardware’s spec sheet instead of from measured use.
- Premium SSD where Standard SSD would do. A 512 GiB Standard SSD E20 lists at $38.40 a month against $73.22 for the Premium P20.
- Committing to three years too early.
- Forgetting the gateway.
- Backup retention nobody ever revisits, so storage grows every month.
- Test machines left running after cutover.
- Assuming a reservation covers the Windows license. It doesn’t.
What People Ask Before Moving a Server to Azure
Can we pay month to month with no long-term commitment?
Does the Windows Server license we already own carry over to Azure?
Do we pay to upload our data into Azure?
Why does the VPN gateway cost so much?
Is backup included with the virtual machine?
What does VJNetworks charge to run the server after it moves?
Should we buy a reservation on day one?
Send us what the server runs and how old it is. We will measure how it’s actually used, price it line by line against Microsoft’s current list rates, and give you a written estimate for both the monthly bill and the move. No obligation either way.
