How Can I Build a Competitive Azure Engineering Profile as a New Graduate?

Azure is broad enough that trying to cover everything can make your résumé look shallow. Pick a lane and go deep—for example, infrastructure, networking, identity, automation, and security. Windows administration is still very relevant in many Azure environments because plenty of companies use Microsoft platforms heavily, so don’t neglect it while learning Linux.

Your ability to communicate and understand business goals can matter just as much as your technical skills. Employers value engineers who can explain tradeoffs, risks, costs, and implementation plans clearly instead of only focusing on the technology.

For a cloud engineering path, infrastructure as code, Kubernetes, and CI/CD are useful areas to add after you have the fundamentals. A lot of people can build a basic cloud environment through the portal, so showing that you can provision, deploy, monitor, and update infrastructure repeatably will help you stand out. A practical project that uses Terraform and a pipeline is usually more valuable than collecting many unrelated certifications.

MD-102 is primarily focused on endpoint administration with Intune and Windows client management. It makes sense for a modern workplace or endpoint administrator, but it isn’t a priority for the Azure infrastructure path you described.

AZ-104, Terraform Associate, and a well-documented three-tier Azure project are a coherent starting point. Make sure the project demonstrates networking, identity and access, monitoring, secure secrets management, automation, and a realistic deployment process rather than just showing that you created a few resources.

For the résumé, I’d use three projects and two experiences if the third experience mostly repeats what you already do professionally. Keep the leadership role if it demonstrates ownership, coordination, or communication, and use the project section to show skills that your current job doesn’t cover.

The strongest project is one you can explain in detail during an interview: why you chose the architecture, how it is secured, how it is deployed, what broke, how you monitored it, and what you would improve. Quality and depth will matter more than reaching a particular number of projects.