Projects and migrations
Azure Virtual Desktop
A full Windows desktop delivered from Azure. Staff get the same environment from any device, and the data stays in your tenant rather than on a laptop in an airport.
What the work involves
- Working out who actually needs a virtual desktop and who does not — this is rarely everyone.
- Checking your applications run in a multi-session environment. Some legacy software does not.
- Sizing and building host pools against real concurrent usage rather than headcount.
- Building the desktop image, and deciding what belongs in it versus what gets delivered separately.
- Profile management, so a user's settings and files follow them between sessions.
- Identity and conditional access — who can sign in, from where, and on what device.
- A pilot group before anyone else moves, then a staged rollout.
What it depends on
Application compatibility is the first question and the one that most often changes the plan. Anything old, anything with a hardware dongle, and anything with a per-machine licence needs checking before a design exists.
After that it is concurrency rather than headcount. Forty staff who all work 9-to-5 need more capacity than a hundred spread across shifts, and sizing against the wrong number is how this gets expensive.
Commonly underestimated
Profile management. Get it wrong and users lose settings between sessions, which is the fastest way to lose confidence in the whole project.
Printing. It is unglamorous and it is where most support tickets come from in the first month.
Running cost. Virtual desktops are not automatically cheaper than laptops — they trade capital cost for running cost, and the saving depends on shutting hosts down when nobody is using them.
How we scope this
We do not quote this work before seeing your environment. How long it takes and what it costs depend on what you already have, how much of it there is, and how quickly your side can make decisions — and a number produced without knowing those is a guess you would end up budgeting against.
What we will commit to is a start: work begins within five business days of signature. If a particular engagement cannot start inside that window, we say so before you sign.
More on this in what it costs. Ongoing support for this sits under our services.
Other projects
-
On-Premises to Microsoft 365
Email, files and identity moved off your own servers into Microsoft 365, including the part most migrations underestimate — deciding what does not come with you.
-
Microsoft 365 Commercial to GCC High
The migration a defense contractor makes when CUI enters the picture. It is a tenant-to-tenant move, not an upgrade, and the CUI boundary has to be designed before anything is copied.
-
Google Workspace to Microsoft 365
Mail, drive and identity moved across from Google, with the shared-drive structure mapped properly instead of dumped into someone's OneDrive.
Talk it through
Tell us what you're moving and what you're moving it from. Twenty minutes, no obligation.
Schedule a call