What Azure Services Should a .NET Developer Learn to Build a Cloud-Ready Application?

A .NET developer moving toward cloud-native development should learn Azure as an application platform, rather than attempting to memorize every Azure service. The focus should be on understanding how different services work together to deliver a secure, scalable, observable application. For application hosting, developers should understand Azure App Service, Azure Functions, and container-based deployment with Azure Container Apps or Azure Kubernetes Service where appropriate. App Service is useful for conventional web APIs and applications, while Azure Functions introduces event-driven and serverless patterns. For data, learn Azure SQL Database and understand when a relational database is appropriate. Developers should also understand Azure Storage for blobs, queues, and other storage requirements. For modern distributed applications, knowledge of messaging through Azure Service Bus is particularly valuable because asynchronous processing and decoupling are common enterprise requirements. Security should include Microsoft Entra ID, managed identities, Azure Key Vault, RBAC, and secure configuration management. A cloud-ready .NET application should avoid storing secrets in source code or configuration files. Managed identities and centralized secret management should become part of the developer's normal design approach. Finally, learn Application Insights/Azure Monitor, CI/CD, networking fundamentals, autoscaling, logging, health checks, resilience, and cost awareness. A developer who can build an API is useful; a developer who can build, secure, deploy, monitor, troubleshoot, and scale that API in Azure is significantly more valuable. For students, one strong portfolio project could combine ASP.NET Core Web API + Azure App Service + Azure SQL + Azure Key Vault + Entra ID + Application Insights + CI/CD. That demonstrates considerably more practical cloud capability than a collection of isolated coding exercises.