From Help Desk to Cloud Engineer: The Complete Roadmap

Most cloud engineers did not start in the cloud. They started at a help desk, resetting passwords, imaging laptops, and answering tickets at 8 in the morning. That is a good thing. The help desk teaches you the fundamentals that a certification alone never will: how real users break things, how to troubleshoot under pressure, and how to communicate when something is down. This guide is the roadmap from help desk technician to cloud engineer, broken into the six areas that actually move you forward.

Certifications: Your Proof of Readiness

Certifications do not make you an engineer. They prove to a hiring manager that you are ready to be one. On the help desk you already touch ticketing, permissions, and basic networking. The right certs turn that experience into a credible story.

1. Security+ (SY0 701). This is the foundation. It covers identity and access management, network security, risk management, and incident response. These are the same topics you meet in every cloud security question. Study it first.
2. AZ 104: Azure Administrator Associate. This is the cert that changes your job title. It tests you on managing identities in Microsoft Entra ID, configuring virtual networks, deploying virtual machines, and managing storage and governance in Azure. Pair it with your Security+ and you become a security minded cloud admin.
3. AZ 900 if you need the on ramp. If Azure is brand new to you, the AZ 900 fundamentals cert gives you the vocabulary in 2 to 3 weeks. Skip it only if you already live in the portal daily.

Order of attack: Security+ first, AZ 104 second. Two certifications, 4 to 6 months of focused study, and your resume reads like a cloud engineer in training instead of a career help desk tech.

Hands on Labs: Where the Title Is Earned

Hiring managers ask one question in every cloud interview: "Have you actually done this?" Labs give you the answer. Build these 4 in your own Azure free account or trial subscription:

• Virtual network with 2 subnets and a network security group. Deploy 2 virtual machines, one public facing web server and one private database server. Lock down the NSG so only the web server accepts HTTP. This single lab teaches you VNETs, subnets, NSGs, and the blast radius mindset.
• Entra ID user and group lifecycle. Create 5 test users, assign them to groups, and apply conditional access policies that block sign in from outside your country. Then audit the sign in logs. You just practiced identity governance, which is 15 to 20 percent of the AZ 104 exam.
• Storage with lifecycle management. Create a storage account, move blobs between hot, cool, and archive tiers with a lifecycle policy, and enable soft delete. Document the cost difference. Cloud engineers are expected to think about cost, not just function.
• Backup and restore a VM. Configure Azure Backup on a VM, delete a file, and restore it. Every production environment needs this skill, and most help desk techs have never done it at the platform level.

Write down what you built, the commands you ran, and what broke along the way. That document becomes your interview portfolio. Screenshots with dates are better than promises.

Career Development: The 12 Month Transition Plan

Going from help desk to cloud engineer takes 12 months of deliberate work, not 12 months of waiting. Here is the timeline:

1. Months 1 to 3: Foundation. Study for Security+ 90 minutes a day. Volunteer for every networking and permissions ticket on the help desk queue. Start your Azure free account and build lab 1 above.
2. Months 4 to 6: Prove it. Pass Security+. Finish labs 2 and 3. Start writing short write ups of what you built and post them on LinkedIn. One post per lab. Recruiters search for these.
3. Months 7 to 9: Specialize. Study for AZ 104. Finish lab 4. Ask your manager for cloud adjacent tasks: identity cleanup, license audits, Intune enrollments. If your company uses Azure, get your hands in it.
4. Months 10 to 12: Apply. Pass AZ 104. Update your resume with certs first, then lab projects with measurable results, then work history. Apply to 5 roles per week. Target titles: cloud support engineer, Azure administrator, systems engineer, infrastructure engineer.

The rule: every month should produce something a stranger could verify. A cert, a lab write up, a GitHub repo, a blog post. Visible proof beats private effort every time.

Interviewing Skills: Tell the Migration Story

You will be asked, "Why should we hire a help desk tech for a cloud role?" Your answer is a 60 second story with 3 beats:

1. The bridge: "I spent 2 years on the help desk resolving 800 plus tickets, which taught me how users actually experience identity, access, and network problems."
2. The proof: "While I was there I earned Security+ and AZ 104, and I built 4 lab environments in Azure covering virtual networks, identity governance, storage tiers, and backup and restore."
3. The value: "I bring the troubleshooting instincts most cloud engineers never developed, plus the cloud fundamentals to deploy and secure resources on day 1."

Prepare answers to these 5 questions, because they appear in almost every cloud interview:

• Walk me through how you would troubleshoot a VM that lost connectivity.
• What is the difference between a network security group and a firewall?
• How do you secure an Azure storage account?
• Explain conditional access in plain language.
• What would you do if a user reports their account was compromised?

Answer each one with a real example from your labs or your help desk work. Real examples beat textbook definitions. The hiring manager wants to hear how you think, not what you memorized.

Study Tips: Learn While Working Full Time

You are studying around a job and a life. Here is the system that works for people in exactly that position:

1. 90 minutes a day, same time. Early morning works best because nothing else competes for it. 90 minutes times 5 days is 7 and a half hours a week, which is enough to pass Security+ in 8 to 12 weeks.
2. Lab every concept the same week you read it. Reading about NSGs and never configuring one is how people fail the performance based questions. Build it the same week.
3. Use 3 sources, no more. One video course, one practice exam set, one book or documentation set. More sources create confusion, not clarity.
4. Teach it once a week. Explain one concept out loud to a coworker, a friend, or your phone camera. If you cannot explain it simply, you do not know it yet.
5. Schedule the exam before you feel ready. Pick a date 4 weeks out and pay the fee. A paid exam on the calendar focuses the mind like nothing else.

Track your practice exam scores weekly. When you score 85 percent or higher 3 times in a row on full timed practice exams, you are ready. Book the exam and go.

Mentorship: Find Someone 2 Steps Ahead

You do not need a famous mentor. You need someone 2 steps ahead of you: a cloud engineer who was on the help desk 2 years ago. They remember the exact problems you are hitting right now.

• Where to look: LinkedIn posts about AZ 104 or Security+ pass stories. People who post their pass story are usually willing to answer 3 questions from someone behind them.
• What to ask: Ask specific questions, not "can you mentor me." Ask: "What tripped you up on the AZ 104 lab questions?" or "What did you put on your resume to get your first cloud interview?" Specific questions get specific answers.
• Give back as you climb: The moment you pass Security+, answer one question a week from someone studying for it. Teaching keeps you sharp and builds the network that brings you job referrals later.
• Join a community with structure: Free mentorship communities with live classes and study groups remove the guesswork. Show up, do the work, ask the questions.

The path from help desk to cloud engineer is walked by thousands of people every year. The ones who make it are not the smartest. They are the ones who built the labs, scheduled the exams, and asked the questions. Start your 90 minutes tomorrow morning.