I have about five years of IT technician experience across three jobs and a bachelor's degree in Computer Information Technology. My background includes device imaging, hardware and software troubleshooting, Active Directory, some scripting, Microsoft 365, and SCCM. I'm trying to move into a junior system administrator role, but job postings often ask for years of experience with Azure, Entra, Intune, Google Cloud, networking, virtualization, and other infrastructure tools. I understand many of these technologies from coursework, but I haven't had much hands-on access to them at work. I'm also unsure which certifications are worthwhile since experience usually seems more important. I rarely hear back after applying, so I'm wondering whether my resume or approach is the problem and what steps would best help me make the transition.
5 Answers
Certifications can help, particularly when applicant tracking systems are filtering resumes. Choose ones that match the roles you want rather than collecting broad credentials. AZ-104 is relevant for Azure administration, while MD-102 or MS-102 can support an endpoint and Microsoft 365 path. A networking certification such as CCNA can also distinguish you from candidates with similar desktop-support experience, but certifications work best alongside practical projects.
Yes, a hands-on lab can turn coursework into evidence that you can actually use these tools. Build practical projects such as Entra identity and Conditional Access policies, Intune device policies, Microsoft 365 administration, Azure automation, and PowerShell scripts for provisioning or compliance reporting. Document the goal, configuration, screenshots or code, and outcome. PowerShell is the most natural next step from your Active Directory and SCCM experience. You can add Linux, Git, Python, virtualization, networking, and storage knowledge over time, but don’t try to master everything at once.
My current job gives me very little opportunity to work with networking, virtualization, storage, or server administration, so I’ll need to get most of that experience through a lab or a different role.
Cloud administration can be a longer-term target, but you don’t necessarily have to wait for a traditional system administrator job first. Your endpoint, identity, SCCM, and scripting experience already provides a useful foundation for cloud-focused roles. Look for positions involving Azure or Microsoft 365 administration, endpoint management, identity support, or cloud operations, and use a lab plus a targeted certification to show the missing hands-on skills. The lack of responses may largely be resume positioning and automated screening rather than proof that you’re unqualified.
The market is competitive, so keep applying while deliberately asking for additional responsibilities where you are. Track specific accomplishments and technologies you use, then update your resume around measurable outcomes rather than listing routine help-desk duties.
A managed service provider can be a useful bridge because you’re likely to work on both desktop issues and server or infrastructure problems across multiple environments. Smaller internal IT teams can offer similar exposure. Also search specifically for junior system administrator, infrastructure technician, endpoint administrator, and systems support roles instead of applying only to jobs labeled system administrator. Employers shouldn’t expect a junior hire to design an entire directory environment or security strategy from scratch.
Your resume should present you as someone already handling junior system administration work, not only desktop support. Instead of focusing on individual troubleshooting tickets, highlight broader-impact tasks such as Active Directory administration, Group Policy changes, SCCM software deployments, imaging processes, scripting, endpoint management, and anything you automated or standardized. If you performed responsibilities beyond your official title, describe the scope and results clearly without exaggerating.
I’m currently studying for AZ-104. Would it make sense to build a small lab, document what I configure, publish the write-ups in a code repository, and link that from my resume?