Virtual machines, networking and the identity services behind them, moved into Azure. Sometimes a full estate; more often a handful of servers that are the only reason a rack still exists.
One honest note before anything else: Azure infrastructure work is delivered by our engineers in the United States, with the local entity holding the contract and the client relationship. It is the same organisation and the same partner programme, but it is a different team from the one that runs our European migrations, and you should know which people are doing which work.
The most common version of this project is not a lift-and-shift. It is replacing a server whose only remaining job is serving LDAP to one application — which Entra Domain Services can do without a server at all. We would rather retire the machine than move it.
“On the project side, I got great help moving my infrastructure to Azure. Moving workloads is not easy, and they did a great job of it.”
“As a leader, most of the responsibility falls on me and my peers to lay out our expectations for the business. Once we do that and they understand it, they deliver. Delivering on time is something I am consistently impressed with.”
Servers, roles, dependencies and real utilisation. The interesting output is usually the list of machines that do not need to exist.
Landing zone, networking, identity. Sizing against measured usage rather than the original hardware, because that is where the cost estimate becomes real.
What it will cost per month, with the assumptions stated. Reserved instances and commitment terms considered here rather than after the first invoice.
Workloads move in waves with a rollback position for each. Nothing moves without a way back.
Application owners confirm the workload behaves, before the source is retired.
Sizing reviewed against a month of real usage, backup restore tested, documentation issued.
Send the server list and what each one does. Part of what you get back is which of them should not move at all, with the reasoning.
Fixed, after scoping · 3 weeks – 4 months“I deal with protected health information and company-confidential data, so I have to have the gold standard of environments, and that is what Azure brings. To set it up I needed someone who knew what they were doing, at the right price point.”
“It saves me hundreds of hours, because there is no way I could have set this up by myself. It feels like I have an IT department in my company whenever I need them.”
Our engineers in the United States, with the entity in your country holding the contract and the relationship. Same organisation, same partner programme, different team from the one running European Microsoft 365 migrations. We say so because you should know who is touching your infrastructure.
Often not, and we will say so during the assessment. Hardware you already own has no monthly cost. The honest reasons to move are usually a lease ending, a refresh nobody wants to fund, resilience, or getting out of a data centre — not the invoice.
No, and part of the value of the assessment is the list of servers that should be retired instead. We have replaced a domain controller whose only remaining job was serving LDAP to one application with Entra Domain Services, which removed the server entirely.
Three to six weeks for a small estate, two to four months for a larger one. The assessment and the application owner sign-offs vary more than the migration itself.
A fixed price for the project, quoted after the assessment. Azure consumption is separate and billed by Microsoft — we can be your CSP for it, in your currency, or not.
Yes, as your Cloud Solution Provider, invoiced in your local currency by the entity authorised for your country. It is not a condition of the project.
Scoping costs nothing
Answer the form or write to us. You get back a written scope, a sequence and a fixed price — usually within one business day, and nobody rings you unless you ask.