Our company is preparing to take complete administration of a large Azure environment away from our managed service provider. It includes hundreds of virtual machines, Entra ID user accounts, persistent Azure Virtual Desktop systems, and several satellite offices. I joined the company last month as an IT Support Specialist, and my colleague has been here about a year. We both have some Azure experience, but neither of us has the depth of knowledge needed to confidently manage an environment this large or handle a major outage without help.
Our IT administrator is leaving before the handoff is complete, but the CEO still wants the transition finished. The process has already been underway for more than six months. We could escalate problems to the MSP, but the handover and documentation have not been ideal, and the relationship between the MSP owner and our CEO has apparently deteriorated. Our contract technically continues until December of next year, yet leadership wants to move ahead immediately.
I am concerned about experimenting in production just to learn the environment, and I do not think spending unpaid weekends exploring it is a sustainable or safe plan. What should we insist on before accepting responsibility? Would formal Azure training, recorded walkthroughs with the MSP, a consultant, or an experienced Azure administrator be the best way to reduce the risk? I want to protect the company, my colleague, and myself without refusing to learn or take on new responsibilities.
4 Answers
A staged transition would be much safer than an abrupt cutover. Keep the MSP responsible for production while your team receives read-only access, shadows changes, reviews the architecture, and practices restores or other procedures in a test environment. Then move specific areas over one at a time with rollback plans and a clearly defined period of paid MSP support. If leadership refuses that approach, bring in an independent consultant and document that the business is accepting the additional risk.
Ask the company to pay for legitimate Azure training and protected work time before the transition. Training is useful, but it should supplement—not replace—senior operational support. Also, do not volunteer your weekends as an implicit requirement. If emergency or after-hours work is expected, clarify compensation, on-call responsibilities, escalation paths, and who has final authority before accepting the role.
Do not treat production as a learning laboratory. Before the handoff, require a proper transition plan: current diagrams, inventories, ownership details, runbooks, monitoring and alerting, backup and restore procedures, disaster-recovery information, privileged-access procedures, vendor contacts, licensing details, and a list of known problems. Have the MSP demonstrate important procedures and record the sessions. If they will not provide that information, document the risk in writing and escalate it to management.
You really need an experienced Azure resource involved. Managing a few systems is very different from being responsible for hundreds of VMs, AVD, identity, networking, backup, security, and disaster recovery. Six months of exposure—or even a year—does not replace senior operational experience. A consultant or senior Azure administrator could supervise the transition while the two of you build familiarity with the environment.
That is my concern too. We do not just need another general administrator; we need someone who can handle major incidents and teach us how to support the environment. I am unsure how leadership can properly evaluate that expertise when we do not have it ourselves.
The handoff has been poorly structured, partly because the relationship with the MSP has broken down. I agree that the missing documentation and knowledge transfer are a bigger risk than simply being inexperienced.