Cover Image for What Every Developer Should Know About Azure Before Building an App
Cover Image for What Every Developer Should Know About Azure Before Building an App
8 Went

What Every Developer Should Know About Azure Before Building an App

Hosted by Giorgio Desideri
Google Meet
Registration
Past Event
Welcome! To join the event, please register below.
About Event

Azure Fundamentals for Technology Leaders, Engineers, and Developers

Before a team builds an application on Azure, it needs more than a list of services. It needs a clear way to reason about cloud responsibilities, hosting choices, identity, security, monitoring, cost, and operations before production decisions are made.

This free course gives technology leaders, engineers, and developers a practical Azure foundation for application work. The session focuses on the decisions that shape an Azure application before the first deployment: what the team owns, what Azure manages, which runtime fits the app, how access should work, where secrets belong, and how the app should be monitored after launch.

Who Should Attend

- Technology leaders who need clearer context for Azure application decisions.

- Engineers who work with cloud-hosted systems and want a stronger Azure foundation.

- Developers who are preparing to build, deploy, secure, or operate applications on Azure.

What You Will Learn

By the end of the course, you will be able to:

- Explain the cloud concepts and shared responsibilities every Azure application team should understand.

- Compare public, private, and hybrid cloud models from an application delivery perspective.

- Distinguish between IaaS, PaaS, and SaaS, and identify where each model fits.

- Choose an Azure runtime based on the shape of the application.

- Map common app parts such as front ends, APIs, background jobs, and data stores to practical Azure service options.

- Understand how Microsoft Entra ID, app registrations, enterprise applications, RBAC, Key Vault, and managed identities work together.

- Identify the monitoring, health check, alerting, and governance practices needed after launch.

Agenda

Module 1: Build the Cloud Mental Model for Application Work

Build the shared vocabulary needed before choosing Azure services. This lesson covers cloud computing basics, public/private/hybrid cloud models, shared responsibility, consumption-based pricing, and the practical difference between IaaS, PaaS, and SaaS.

Module 2: Choose the Right Azure Service

Implement application with the right Azure hosting choices. This lesson explains when to consider static hosting, Azure Static Web Apps, Azure App Service, Azure Functions, and Azure Virtual Machines, then ties those choices to resource placement, storage, and network access decisions.

Module 3: Secure Sign-In, Service Access, and App Secrets

Understand the security model behind real Azure applications. This lesson covers Microsoft Entra ID, app registrations, enterprise applications, app roles, Azure RBAC, Key Vault, and managed identities for passwordless Azure-to-Azure service access.

Module 4: Monitor, Govern, and Operate the App After Launch

Learn how to keep an Azure application observable and manageable after release. This lesson introduces Azure Monitor, Application Insights, health checks, release validation, actionable alerts, Azure Advisor, and Azure Service Health.

Why This Course Matters

Azure choices made early in an application project affect cost, reliability, security, delivery speed, and day-to-day operations. This course helps teams build a shared foundation before committing to a runtime, identity model, data access pattern, or monitoring approach.

The goal is not to memorize every Azure service. The goal is to understand how to think about Azure before building an app.

8 Went