Our company is planning to take complete administration of its Azure environment away from our managed service provider. The setup includes hundreds of virtual machines, Entra ID user accounts, persistent Azure Virtual Desktops, and several satellite offices. I joined the company recently as an IT Support Specialist, and my colleague has been here about a year. We both have some Azure administration experience, but neither of us has the depth of knowledge needed to confidently manage a production environment of this size. Anything beyond our abilities would still be escalated to the MSP.
Our IT administrator is leaving before the handoff is complete, but the CEO wants the transition to continue anyway. The project has already been in progress for more than six months. I am concerned that we will be left responsible for a complicated production environment without sufficient training, documentation, or an experienced Azure administrator to guide us. I want to learn the environment, but experimenting directly in production does not seem safe, and I do not think volunteering to spend weekends exploring the system is a proper transition plan.
How should we approach this handoff? What documentation, training, access controls, testing, escalation procedures, or outside expertise should we require before taking responsibility?
4 Answers
A short-term consultant or senior Azure contractor could make this much safer. They can assess the environment, validate the MSP's documentation, supervise the knowledge transfer, and mentor you and your colleague while the company recruits a permanent administrator. It costs more initially, but that is usually cheaper than a prolonged outage, a security incident, or losing staff because they were placed in an impossible position.
If leadership refuses additional expertise, present the choice plainly: either delay the handoff, keep qualified MSP support during the transition, or formally accept the operational risk. Do not quietly turn an executive decision into your personal responsibility.
The biggest warning sign is the lack of a proper handoff, not simply your current skill level. Before accepting ownership, ask for a written transition plan with clear milestones and sign-off criteria. At minimum, you should have separate admin accounts, least-privilege roles, tested backups and restores, monitoring and alert ownership, break-glass access, change-control procedures, a current asset inventory, and a list of known problems.
You should also document the risks in writing to your manager and the CEO: who will be on call, what happens during a major outage, which issues remain covered by the MSP, and what support is available after the transition. That protects both the company and you from an informal expectation that you can guarantee a service you were never properly prepared to run.
You need an experienced Azure engineer involved in this transition. Managing a few cloud resources is very different from owning an environment with hundreds of VMs, AVD, identity services, and multiple locations. Six months or a year of general experience is not a substitute for someone who has handled incidents and migrations at this scale.
If the business will not hire a permanent senior administrator immediately, bring in a consultant or retain the MSP for a defined transition period. Make the handoff include architecture diagrams, dependency maps, backup and recovery procedures, monitoring, security policies, automation, vendor contacts, and a documented escalation process.
Do not treat production as a place to learn by trial and error, and do not offer your weekends as the solution. Ask the company to pay for legitimate Azure training and protected work time. Also request structured knowledge-transfer sessions with the MSP, ideally with demonstrations of common administrative tasks and incident scenarios. Record the sessions where company policy allows and turn them into internal procedures.
The company should understand that taking responsibility requires staffing, training, documentation, and a budget. If they want in-house ownership immediately, they need to accept the risk and fund the preparation rather than expecting junior staff to absorb it personally.
That is my concern as well. The MSP contract technically continues for quite a while, but the CEO wants the handoff completed now, partly because the relationship with the MSP has deteriorated. I will push for a written transition plan and clearer support obligations before we accept responsibility.