A practical guide to Azure Virtual Desktop for Canadian businesses. Learn how AVD works, what it costs, Canadian data residency options, and how to plan a successful deployment.
Azure Virtual Desktop (AVD) is Microsoft’s cloud-hosted desktop and application service. It lets users access a full Windows desktop or specific applications from any device with an internet connection, with the compute running in Microsoft Azure rather than on a local machine. For Canadian businesses evaluating remote access, multi-site operations, or a path off aging on-premises infrastructure, AVD is worth understanding in detail.
What Azure Virtual Desktop Actually Is
AVD delivers virtual Windows desktops through Microsoft Azure. Users connect to their desktop using the Microsoft Remote Desktop client or through a web browser. From the user’s perspective, it looks and feels like a Windows desktop. The difference is that the processing happens in Azure, not on the device in front of them.
This has practical implications. A user connecting from an older laptop, a tablet, or even a Mac can run Windows applications that require significant compute power, because the device is just a display. The compute, storage, and application licensing run in Azure.
AVD supports several deployment configurations:
Pooled desktops. Multiple users share a pool of virtual machines. Each user gets a session on a shared VM. This is cost-efficient for workers who use standard applications and do not need persistent desktops.
Personal desktops. Each user has a dedicated virtual machine assigned to them. The desktop persists between sessions, like a physical PC in the cloud. This is appropriate for users who install applications, have personalised configurations, or run resource-intensive work.
RemoteApp. Instead of a full desktop, specific applications are published to users. From the user’s perspective, the application appears to run locally. This is useful for delivering a specific line-of-business application, such as Sage 300, to users who otherwise work on local machines.
Canadian Data Residency with AVD
For Canadian businesses with data residency requirements, Azure’s Canadian regions are relevant. Microsoft operates two Canadian Azure regions: Canada Central (Toronto) and Canada East (Quebec City).
Deploying AVD in a Canadian Azure region means that the virtual machines, storage, and user profile data are hosted within Canada. This is meaningful for organisations subject to BC PIPA, federal PIPEDA, or sector-specific requirements that restrict personal data from leaving Canada.
When configuring AVD for Canadian data residency:
- Deploy host pools in Canada Central or Canada East
- Use Azure Files or FSLogix profile containers hosted in the same Canadian region
- Verify that any additional Azure services used in the deployment (key vaults, storage accounts, monitoring) are also in Canadian regions
Note that some Azure control plane metadata for AVD (session broker metadata) was historically stored in US regions. Microsoft has been expanding regional metadata residency over time. For organisations with strict data residency requirements, confirm current metadata residency status with Microsoft or your Azure partner before deployment.
How AVD Licensing Works
Microsoft’s licensing model for AVD has changed over the years and is worth understanding carefully before projecting costs.
Microsoft 365 Business Premium, E3, and E5 subscribers are licensed to use AVD at no additional per-user cost for the virtualisation rights. The compute costs (the Azure VMs running the desktops) are separate and billed based on usage.
Windows 10/11 Enterprise Multi-Session (the OS used in pooled AVD deployments) requires an eligible Microsoft 365 or Windows licence per user. This is the licence that allows multiple concurrent users on a single VM, which is the feature that makes pooled desktops cost-efficient.
Per-user compute cost depends on the VM size selected and hours of use. For organisations where users work standard business hours, scaling down or deallocating VMs outside business hours reduces compute costs meaningfully. Azure Automation or Azure Virtual Desktop Scaling Plans can automate this.
FSLogix (the profile management technology used to make AVD sessions feel like persistent desktops) is included at no additional cost with Microsoft 365 licences.
What AVD Costs in Practice
Costs vary based on user count, VM size, storage, and usage patterns. A practical way to think about cost structure:
- Compute: Per-VM per-hour cost based on VM size; pooled desktops reduce cost by sharing VMs across users
- Storage: Azure Files or managed disks for user profiles and application data; typically a secondary cost
- Networking: Egress traffic costs apply; for most business use cases this is modest
- Licencing: Microsoft 365 per-user licencing (separate from Azure spend)
For a business with 20 users on pooled desktops, working business hours, a reasonable VM sizing strategy can deliver AVD at a total Azure compute cost in the range of $40 to $80 per user per month, exclusive of Microsoft 365 licencing. Exact costs depend on VM type, storage configuration, and usage patterns.
AVD cost optimisation is an ongoing activity, not a one-time configuration. Rightsizing VMs, configuring scaling plans, and reviewing storage usage regularly keeps costs aligned with actual consumption.
Common Use Cases for Canadian Businesses
Remote and hybrid workforce. AVD lets remote employees access the same desktop environment as office workers, with the same applications, security policies, and data access. No VPN required to reach internal applications hosted in Azure alongside AVD.
Branch offices and multi-site operations. Instead of deploying and maintaining servers at each location, branch users connect to centrally managed virtual desktops in Azure. This reduces hardware at each site and centralises IT management.
Software that cannot run on Mac or Linux. For businesses where some users work on Macs but the line-of-business application (Sage 300, for example) is Windows-only, AVD delivers the Windows application to Mac users without requiring a Windows machine at each desk.
Contractor and temporary worker access. Contractors can be provisioned with a scoped AVD session that provides access only to the applications they need, on a device they bring themselves, without giving them access to the corporate network broadly.
Aged hardware refresh alternative. When a fleet of PCs approaches end-of-life, AVD can defer or reduce the hardware refresh cost by moving compute to Azure and extending the life of existing endpoint hardware.
What a Successful AVD Deployment Requires
Sufficient internet bandwidth. AVD sessions require a reliable, low-latency internet connection. Microsoft’s recommended minimum is 10 Mbps per user for standard office productivity tasks. Video-heavy work requires more. Sites with shared internet connections need bandwidth assessment before deploying AVD broadly.
Identity management in Azure AD. AVD requires Azure Active Directory (now called Microsoft Entra ID) for authentication. Organisations still running only on-premises Active Directory need to either extend to Azure AD via Azure AD Connect or migrate to a cloud-first identity model before deploying AVD.
Profile management with FSLogix. User profiles in pooled desktop environments must be managed with FSLogix to persist across sessions. FSLogix profile containers need to be sized appropriately for each user’s profile data.
Security baseline configuration. AVD environments need the same security controls as any Windows environment: endpoint protection, conditional access policies, MFA enforcement, and monitoring. An AVD deployment that moves compute to Azure without applying these controls does not improve the security posture.
Ongoing management. AVD is not a set-and-forget platform. VM image updates, session host maintenance, scaling configuration, and monitoring are ongoing operational responsibilities. This is typically handled by a managed IT provider as part of the engagement.
Getting Started
The path to an AVD deployment typically involves an assessment of current infrastructure, an Azure subscription and environment setup, network connectivity review, identity configuration, and a pilot deployment with a subset of users before full rollout.
SFS Technologies deploys and manages Azure Virtual Desktop environments for Canadian businesses. We have delivered AVD implementations for organisations migrating from on-premises infrastructure and for businesses expanding to remote and multi-site models. Let us talk about whether AVD is the right fit for your environment.
