First page of Microsoft's 100,000-partner directory, sorted by responsiveness Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation Microsoft partner since 2006 1,100+ organizations under management
Home/Services/Managed Azure Virtual Desktop Service
Managed Services

Managed Azure Virtual Desktop Service

Managed Azure Virtual Desktop Service is the monthly operations layer for an Azure Virtual Desktop estate that is already deployed: IT Partner keeps session host images and applications current, watches host pool health, tunes autoscaling against your real usage patterns, cares for FSLogix profiles, and triages AVD session issues raised through an agreed intake. The service costs $25 per user per month with no long-term contract. It is the continuation of IT Partner's Azure Virtual Desktop Implementation project — or a takeover of an AVD environment someone else built — for organizations that run AVD without a dedicated VDI engineer.

Timeline 30 daysService owner Roman SotnikAzure Virtual DesktopMicrosoft AzureFSLogix

What this engagement is

Azure Virtual Desktop is not a deploy-and-forget product. Session host images fall behind on Windows and application updates within weeks. Autoscaling plans that matched January's working patterns quietly burn money in July. FSLogix profile stores grow until logons crawl. And Microsoft ships meaningful platform changes continuously — dynamic autoscaling, session host configuration, richer host pool management — that an unattended environment never benefits from. Most organizations that fit AVD well (10–200 desktop users) cannot justify a dedicated VDI engineer to absorb all of this, which is exactly the gap this service fills. Each month, IT Partner runs an image and update cycle for your session hosts — operating system patches and updates to the agreed application set, validated before rollout, released with drain mode so users are not thrown out of sessions. We watch host pool health: agent status, stale or broken hosts, capacity against demand. We review the autoscaling configuration against actual usage and tune schedules and host sizing, with the savings or trade-offs reported to you rather than assumed. We look after the FSLogix profile store — capacity, performance, and the per-user profile problems (locked, bloated, or corrupted profiles) that otherwise become mystery logon complaints. And when your IT contact or helpdesk hits an AVD-specific session problem, we take the admin-side triage through an agreed intake. The boundary is explicit and priced honestly: this fee covers operating the environment you have. Building a new environment, adding host pools or regions, rebuilding a golden image from scratch, onboarding large waves of new applications, or migrating workloads into AVD are project work, quoted separately in writing before anything starts.

Success criteria

01Session hosts run a current, patched image: the monthly update cycle completes with operating system and agreed-application updates validated and rolled out using drain mode.
02Host pool health issues — broken agents, stale hosts, capacity shortfalls — are detected and remediated through the monthly cycle and the agreed intake rather than discovered by users.
03Autoscaling configuration is reviewed monthly against real usage, with tuning applied and the cost effect reported.
04FSLogix profile storage stays within healthy capacity and performance bounds, and per-user profile faults raised through the intake are resolved.
05A monthly service report is delivered covering update status, host pool health, incidents handled, autoscale and cost findings, and recommendations.

What you receive

Onboarding baseline: inventory and documentation of host pools, session host images, FSLogix configuration, autoscaling plans, and current costs, with gaps against good practice flagged in writing.
A monthly session host image and update cycle: OS patching and updates to the application set agreed at onboarding, validation before rollout, drain-mode release to production hosts.
Host pool health care: AVD agent status, unhealthy or stale session hosts remediated, capacity monitored against session demand.
Monthly autoscaling and cost review: scaling plan schedules and session host sizing tuned to observed usage, with changes and their cost effect reported.
FSLogix profile care: profile store capacity and performance management, exclusion tuning, and resolution of locked, bloated, or corrupted user profiles raised through the intake.
Admin-level triage of AVD session issues submitted through the agreed intake, coordinated with your internal IT or with IT Partner's Remote Support Help Desk if you subscribe to it.
A monthly service report: updates applied, health findings, incidents, autoscale and cost changes, and recommendations — including when a Microsoft platform improvement is worth adopting.
Small in-scope changes: publishing or unpublishing an application from the existing image set, app group and user assignment changes, RDP property and client-setting adjustments.

How the work unfolds

1. Onboarding and baseline (first monthly cycle)

Access is established under least-privilege, time-bound roles you approve. We inventory the environment — host pools, images, FSLogix stores, scaling plans, spend — document the operating baseline, agree the application set, maintenance windows, and the issue intake, and flag anything already unhealthy. If we built your AVD environment, this step is largely a handover to ourselves and goes quickly.

2. Monthly image and update cycle

Each month we produce updated session hosts — OS patches plus updates to the agreed applications — validate them, and roll them out with drain mode during your maintenance window so active sessions end naturally rather than being cut. Where your environment uses Microsoft's newer host management capabilities (session host configuration, automated update paths), we operate those; where it uses a classic golden-image process, we run that instead.

3. Continuous host pool and profile care

Between cycles we keep watch on host pool health and the FSLogix profile store, remediating broken hosts and profile faults as they surface through monitoring signals and the agreed intake. First response to raised issues follows IT Partner's published support SLA.

4. Autoscale and cost tuning

We compare the scaling configuration with actual session patterns monthly and adjust schedules, thresholds, and host sizing where the data justifies it. Compute for pooled desktops is usually the largest AVD cost line, and untuned autoscaling is the most common source of quiet waste — every change we make is reported with its expected cost effect, not applied silently.

5. Monthly reporting and roadmap

The monthly report closes each cycle: what was updated, what broke and was fixed, what autoscaling changed and saved, and what we recommend next — including when something you need has outgrown the monthly scope and deserves a separately quoted project, which we will tell you plainly rather than stretch the fee.

Prerequisites

A deployed Azure Virtual Desktop environment. If you do not have one yet, the Azure Virtual Desktop Implementation service builds it; this service then operates it.
An Azure subscription you own, with Azure consumption billed by Microsoft (or your CSP) to you — this fee covers operations, not Azure infrastructure costs.
Eligible per-user Microsoft licensing for AVD access (for example Microsoft 365 Business Premium, E3/E5, or Windows Enterprise E3/E5 — verified during onboarding).
Access for IT Partner granted under least-privilege, time-bound roles that you approve, scoped to the AVD resources in service.
A named client contact, agreed maintenance windows for the update cycle, and an agreed intake for session-issue triage (who on your side may raise issues, and how).

Who does what

IT Partner

  • Run the monthly image, patching, and application update cycle with validation and drain-mode rollout.
  • Monitor and remediate host pool and session host health within the agreed scope.
  • Tune autoscaling and host sizing against observed usage, reporting every change and its cost effect.
  • Maintain FSLogix profile store health and fix per-user profile faults raised through the intake.
  • Triage AVD session issues at the admin level through the agreed intake within the published support SLA.
  • Deliver the monthly service report and flag honestly when a need exceeds the monthly scope.

Your team

  • Own the Azure subscription and pay Microsoft (or your CSP) for Azure consumption and user licensing.
  • Approve access requests, maintenance windows, and any change we flag as user-visible.
  • Route end-user support through your own IT or a helpdesk arrangement — this service receives escalations, not end-user calls.
  • Tell us about upcoming changes in headcount, applications, or workload that affect capacity planning.
  • Review the monthly report and decide on recommendations that require project work.

What's not included

Initial Azure Virtual Desktop design and deployment — that is the Azure Virtual Desktop Implementation project, and this service begins where it ends.
End-user helpdesk. Your users' first line of support is your IT team or IT Partner's Remote Support Help Desk Service, sold separately; this service takes the AVD-specific escalations from that first line.
Project-scale changes to the environment, each quoted separately in writing before work begins: new host pools or regions, moving or redesigning the deployment, building a new golden image from scratch or for a new OS baseline, onboarding large waves of new applications, disaster-recovery design, and migrations of data, apps, or users into AVD.
Azure consumption and Microsoft licensing costs — billed by Microsoft or your CSP, never marked up into this fee.
Management of your broader (non-AVD) Azure estate — see the Azure Resource Monitoring and Maintenance Service for servers and resources outside the AVD scope.
A deep, subscription-wide cost and FinOps engagement. The monthly cost tuning here is scoped to AVD; the Azure Cost Optimization and FinOps Assessment covers the whole Azure bill with an accountable savings roadmap.
Third-party VDI platforms (Citrix, Omnissa/VMware Horizon) and Windows 365 Cloud PC administration — this service is specifically Azure Virtual Desktop operations.
Development, packaging, or licensing of the business applications themselves — we keep the agreed set updated and deployed; the software and its vendor relationships remain yours.

Limitations & technical notes

!Azure infrastructure costs are yours and are billed by Microsoft or your CSP; autoscale tuning routinely reduces AVD compute spend, but savings depend on your usage patterns and are reported as measured, never guaranteed in advance.
!Microsoft evolves the AVD platform continuously — capabilities such as dynamic autoscaling and session host configuration change what good operations look like. Part of this service's value is tracking those changes; adoption timing depends on Microsoft's rollout and your environment's readiness.
!Session-issue triage is admin-level and arrives through the agreed intake — this service does not take calls or tickets directly from end users.
!The service covers the host pools and session hosts inventoried at onboarding (or added later by agreement); material growth in the estate is re-baselined rather than absorbed silently.
!Support response follows IT Partner's published SLA — first response within 1 business hour, with monthly performance statistics published openly, including missed months.

Frequently asked questions

What is the Managed Azure Virtual Desktop Service?

It is a recurring, per-user monthly service in which IT Partner operates your existing Azure Virtual Desktop environment: monthly session host image and application updates, host pool health care, autoscale and cost tuning, FSLogix profile care, and admin-level triage of AVD session issues. It costs $25 per user per month with no long-term commitment.

Who is this service for?

Organizations that run Azure Virtual Desktop — typically 10 to 200 desktop users — without a dedicated VDI engineer. That includes clients whose AVD we implemented and want kept healthy, and organizations whose AVD was built by someone else and has since drifted.

What does the $25 per user per month cover, and what becomes a separate project?

The fee covers operating the environment you have: the monthly update cycle, health care, autoscale tuning, profile care, issue triage, reporting, and small changes such as app assignment or RDP property adjustments. Work that changes the shape of the environment — new host pools or regions, a golden image rebuilt from scratch, large application onboarding waves, DR design, or migrations into AVD — is project work. We name it as such when it comes up and quote it fixed-price in writing before doing anything.

How do image and application updates actually happen?

Each month we produce updated session hosts — operating system patches plus updates to the application set agreed at onboarding — validate the result, and roll it out during your maintenance window using drain mode, so signed-in users finish their sessions on the old hosts while new connections land on updated ones. If your environment uses Microsoft's newer session host configuration and automated update capabilities we operate those; a classic golden-image process works too.

What is FSLogix profile care and why does it matter?

In pooled AVD, user profiles live in FSLogix containers on shared storage, and that store is where slow logons, disappearing settings, and 'temporary profile' incidents are usually born. We manage the store's capacity and performance, tune exclusions so profiles do not bloat, and fix the individual locked or corrupted profiles that get raised through the intake.

How much can autoscale tuning save us?

It depends on your usage pattern, so we will not promise a number. What we commit to is the mechanism: every month we compare scaling schedules and host sizing against real session data, apply justified changes, and report the measured cost effect. Pooled-desktop compute is usually the biggest line in an AVD bill, and schedules that no longer match working patterns are the most common waste we find.

How is this different from the Azure Virtual Desktop Implementation service?

Implementation is a one-time project that designs and builds the environment — host pool, session hosts, connectivity, and handover. This service is the ongoing operation of that environment, billed monthly per user. They are deliberately separate purchases: implementation first if you have nothing, this service from the month you have users depending on AVD.

How is the monthly cost review different from the FinOps assessment?

The monthly review in this service is scoped to your AVD resources — session host compute, storage, scaling behavior. The Azure Cost Optimization and FinOps Assessment is a separate, deeper engagement across your entire Azure spend: commitments, reservations, allocation, governance, and an accountable savings roadmap. If the monthly review keeps surfacing findings outside AVD, that assessment is the honest next step and we will say so.

Do you support our end users directly?

Not under this fee. End users go to your first line — your own IT, or IT Partner's Remote Support Help Desk Service if you subscribe to it — and this service takes the AVD-specific escalations from that first line through the agreed intake. Keeping those layers separate is what keeps a per-user operations fee at $25.

What access do you need to our Azure environment?

Least-privilege, time-bound access that you approve, scoped to the AVD resources in service — consistent with IT Partner's published access policy of requesting granular rights per task rather than standing global admin. You can review and revoke that access at any time.

How fast do you respond when we raise an issue?

IT Partner's support SLA is first response within 1 business hour, and we publish our monthly support statistics — every month since December 2023, including the months we missed — so you can check the record rather than take the claim on faith.

Can you take over an AVD environment you didn't build?

Yes — that is what the onboarding baseline is for. We inventory and document what exists, flag what is unhealthy or against good practice in writing, and operate from there. If the baseline reveals problems big enough to need a project (a broken image pipeline, an undersized profile store, a redesign), we quote that separately rather than burying it in the monthly fee.

What licensing do our users need for AVD?

Access to Azure Virtual Desktop with Windows 10 or Windows 11 requires eligible per-user licensing — commonly Microsoft 365 Business Premium, E3, or E5, or Windows Enterprise E3/E5. We verify entitlements during onboarding and flag any gap; the licenses themselves are billed by Microsoft or your CSP, not through this fee.

Does this cover Windows 365 Cloud PCs too?

No — Windows 365 is a different product with a different operations model (Microsoft manages the infrastructure; the per-user Cloud PC is the unit). This service is specifically Azure Virtual Desktop. If you run both, or are weighing one against the other, we can advise — but the fee here covers AVD.

How does billing work, and can we stop?

The service is billed monthly at $25 per user for the users in scope that month. There is no long-term contract: you can stop any month, and all we ask is payment of previously approved invoices. No lock-in cuts both ways — it keeps us accountable every month.

Didn’t find your question?

Ask it here. A real engineer answers by email within one business day — and if it’s a good one, it becomes part of this page so the next person finds it.

Answered by a person, one time, to your inbox. Nothing you type here is published without a human reviewing and anonymizing it first.

Often combined with

$25 per user
30 days
Start managed AVD