Context approved
The customer confirms scope, access, acceptance criteria, change windows, and named approvers before build activity begins.
Simplicity IT Professional Service | Six-week implementation
Secure Azure Virtual Desktop Migration: 6-Week Implementation
A virtual-desktop migration needs secure identity, application and profile readiness, a controlled pilot, tested rollback, and business-owner acceptance before a production wave moves.
What this implementation gives you
- One Azure Virtual Desktop host pool, approved Windows 11 multi-session image, and secure foundation in one agreed Azure region.
- Validated identity, FSLogix profiles, monitoring, scaling, and up to 10 compatible customer-packaged applications.
- A pilot of up to 10 users followed by one approved production wave for up to 50 total named users.
- User acceptance, rollback evidence, as-built documentation, operations handoff, and a later-wave backlog.
How the engagement runs
-
Weeks 1 and 2: Confirm and design
Confirm the source environment, personas, applications, profiles, licensing, network readiness, acceptance criteria, and the low-level design.
-
Weeks 3 and 4: Deploy and validate
Deploy the approved Azure Virtual Desktop foundation, image, applications, profiles, access controls, monitoring, and pilot environment.
-
Week 5: Run the pilot
Run the approved pilot for up to 10 users, record acceptance results, resolve in-scope defects, and secure the production-wave decision.
-
Week 6: Migrate and hand off
Execute one approved production wave for up to 50 total named users, validate the result, and complete the operational handoff.
Sample implementation artifacts
These illustrative examples show the deliverables you can expect. They use synthetic data and do not depict customer environments.
Evidence to decision flow
Controlled delivery
Simplicity IT builds and tests only the accepted work packages in the customer-owned environment, with evidence recorded at each checkpoint.
Your decision
A named customer owner reviews the exact change, test result, rollback path, operating owner, and cost impact before any production effect or cutover.
Evidence retained
The as-built record, acceptance evidence, rollback status, decision log, and operational handoff are retained according to the customer agreement.
Your approval before production changes
A named customer owner approves each production change or cutover against the agreed scope, test evidence, rollback path, operating owner, and expected cost before it proceeds.
Scope and boundaries
- The public scope covers one source VDI environment, one Azure region, one host pool, one image, and one production wave for up to 50 total named users.
- Application remediation, multiple images, additional host pools or regions, physical-device migration, and unsupported operating systems are excluded.
- Azure consumption, Microsoft and third-party licenses, carrier services, and hardware remain customer costs.
- Later waves and ongoing managed operations require a separate approved scope.
Microsoft technologies in scope
- Azure Virtual Desktop
- Microsoft Entra ID
- Microsoft Intune
- FSLogix
Request a scoping call
Tell us about your environment and priorities. We will confirm the scope, schedule, and purchasing options with you before work begins.
Discuss this engagement