Azure for Quebec SMBs: What You Would Actually Run There

Azure has hundreds of services. A 60-person business in Quebec City will meaningfully use about five of them, and the gap between those two numbers is where cloud budgets go to die.

This is not an argument for or against moving. If you are still weighing whether to replace the server in your closet at all, start with our server replacement decision guide, which walks through that specific fork. This article assumes you have decided Azure is on the table and want to know what you would actually put in it.

Key Takeaways

• Most SMBs use a handful of Azure services, not the full catalogue.
• Lift-and-shift of an old server usually costs more than the server did.
• Canada Central and Canada East keep data in-country for Law 25 assessments.
• Reserved instances cut steady-state VM costs substantially against pay-as-you-go.
• Identity and backup belong in the plan from day one, not as a later phase.

The services SMBs actually use

Strip away the enterprise catalogue and a typical small business deployment comes down to a short list.

Azure Files replaces the traditional file server. It speaks SMB, so mapped drives keep working, and it pairs with Azure File Sync if you want a local cache for speed at the office. This is the single most common first workload we see.

Azure Backup protects both cloud and on-premises workloads into immutable storage. For businesses whose backup story is currently an external drive someone remembers to swap, this alone justifies an Azure subscription.

Virtual machines for the line-of-business application that has no SaaS equivalent. Accounting packages, engineering software, and industry-specific systems frequently fall here. This is also where costs escape, which we come back to below.

Azure Virtual Desktop when people need a consistent Windows desktop from anywhere, particularly for contractors or staff on personal machines. It is more expensive than it looks once you count the underlying compute, but it solves problems nothing else solves cleanly.

Microsoft Entra ID underneath all of it. If you have Microsoft 365 you already have this, and it is what makes conditional access, single sign-on, and sane offboarding possible across everything above.

The mistake that makes Azure expensive

Lift-and-shift is the default plan and usually the wrong one. Taking a physical server that has been running since 2019, imaging it, and standing it up as an always-on Azure VM produces a machine that costs more per year than buying a replacement server outright, because you are now renting compute 24 hours a day at retail rates.

The workloads that migrate well are the ones that stop being servers. File shares become Azure Files. Backup becomes a service rather than a box. Email and documents were already gone if you run Microsoft 365. What is left is genuinely small, and often a single right-sized VM rather than a copy of what you had.

Where a VM is unavoidable, three levers matter:

• Right-size it. The old server was specified for its worst day in 2019. Measure actual CPU and memory use before choosing a size.
• Reserve it. One and three-year reservations cut the rate substantially against pay-as-you-go for anything running continuously.
• Turn it off. Development, test, and anything used only in business hours can run on a schedule. This is free money most businesses leave on the table.

Why Canadian regions matter here

Azure runs Canada Central and Canada East regions, and for a Quebec business that is not a detail.

Law 25 requires a privacy impact assessment before personal information is transferred outside Quebec, along with reasonable assurance of equivalent protection. Keeping the data in a Canadian region does not eliminate the analysis, but it makes it dramatically simpler and it is far easier to explain to a client whose procurement team is asking.

Choose the region at creation. Moving a storage account or a VM between regions afterwards ranges from tedious to genuinely disruptive, so this belongs in the first design conversation rather than the review. Our guide to Law 25 and Microsoft 365 covers the wider compliance picture this fits into.

What the bill actually looks like

Azure pricing is consumption-based, which means it is honest and unpredictable at the same time. A few habits keep it from surprising you:

Set a budget with alerts on the subscription before you deploy anything. It takes two minutes and it is the difference between noticing a runaway cost in three days rather than at month end.

Watch egress. Moving data out of Azure is billed, and workloads that constantly pull large files back on-premises can generate charges nobody forecast. This is usually a design problem rather than a pricing problem.

Tag everything by workload or department from the start. Retrofitting tags across an existing subscription is miserable, and without them a growing bill is very hard to attribute.

Review quarterly. Orphaned disks from deleted VMs, oversized storage tiers, and forgotten test environments accumulate quietly. Our cloud solutions team builds this review into managed engagements because it reliably pays for itself.

When Azure is the wrong answer

Worth saying plainly. If your only server does file sharing and print, and you already run Microsoft 365, you may not need Azure at all. SharePoint and OneDrive cover the files, and a modern print setup does not need a server. Adding Azure would be adding a bill and a management surface for no gain.

Similarly, a business with a heavy, latency-sensitive application and a single office may be better served by a modest on-premises server with cloud backup. Hybrid is a legitimate destination, not a failure to commit.

FAQ

Is Azure the same thing as Microsoft 365?

No. Microsoft 365 is the productivity suite, including email, Teams, SharePoint and Office apps. Azure is the infrastructure platform where you run servers, storage and networking. They share Entra ID for identity, which is why they feel connected, but they are billed and managed separately.

Can we move gradually, or is it all at once?

Gradually, and gradually is usually better. Most businesses start with backup or file storage, which are low risk and immediately useful, then move applications one at a time as hardware reaches end of life. A single cutover weekend is rarely necessary.

What happens to our internet connection requirements?

They become critical. Once files and applications live in Azure, your connection is the business. Plan for a second link or a failover path before migrating, not after the first outage. This is the most commonly underestimated dependency in an SMB cloud move.

How do Azure costs compare to buying a server?

A server is capital spent once and depreciated; Azure is operating expense forever. Over five years a like-for-like VM replacement often costs more than the hardware would have. Azure wins when you use it to eliminate servers rather than relocate them, and when you value the resilience and the absence of a hardware refresh cycle.

Do we still need backups if everything is in Azure?

Yes. Microsoft guarantees the platform, not your data. Accidental deletion, ransomware, and a bad application update are all your responsibility, and the shared responsibility model says so explicitly. Our backup and recovery services cover cloud workloads for exactly this reason.

If you want a costed view of what your specific workloads would look like in Azure, our IT assessment inventories what you run today, flags what should not move at all, and returns a migration sequence with numbers attached.