Naar hoofdinhoud gaan
Megafoonicoon

GitHub Universe on the Road

GitHub Universe is going on the road. Find a stop near you and join the experience.

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

januari 27, 2027 | 6:00 - 7:00 p.m. (UTC) Gecoördineerde Universele Tijd

Klaar om aan de slag te gaan met AI en de nieuwste technologieën? Microsoft Reactor biedt evenementen, training en communitybronnen om ontwikkelaars, ondernemers en startups te helpen bouwen op AI-technologie en meer. Kom kijken.

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

januari 27, 2027 | 6:00 - 7:00 p.m. (UTC) Gecoördineerde Universele Tijd

Klaar om aan de slag te gaan met AI en de nieuwste technologieën? Microsoft Reactor biedt evenementen, training en communitybronnen om ontwikkelaars, ondernemers en startups te helpen bouwen op AI-technologie en meer. Kom kijken.

Terug

Deployment Stacks: Azure's Standard for Infrastructure as Code, Drift Detection, and

januari 27, 2027 | 6:00 - 7:00 p.m. (UTC) Gecoördineerde Universele Tijd

  • Notatie:
  • alt##LivestreamLivestream

Onderwerp: Infrastructuur

Taal: Engels

Once an Azure environment is deployed, it rarely stays the way the code describes it: people change settings in the portal, delete resources by hand, and leave old resources running.

Deployment stacks are Azure's standard for managing infrastructure as code across that lifecycle, with drift detection and governance built in.

I am a product manager at Microsoft on Azure Bicep and owning Deployment Stacks. Bicep is Azure's native infrastructure as code language and a stateless alternative to Terraform, so there is no state file to store, secure, or keep in sync.

A deployment stack is a resource that manages a group of resources as a single unit across its lifecycle. In the demo I deploy an environment from Bicep as a deployment stack, then change a security rule and delete a resource in the portal. Stacks What-If with the same template lists those changes, and one more deployment puts the environment back. I then set deny settings so managed resources cannot be changed or deleted outside the stack, and choose whether resources removed from the template are detached or deleted.

When the environment is no longer needed, a single delete removes everything the stack manages. Everything runs live from the Azure CLI. The tools are Azure specific; the practices apply to any infrastructure as code workflow.

What attendees will learn:

  • How a deployment stack manages an Azure environment as one unit, from the first deployment to the final delete.
  • How to find drift with Stacks What-If and bring the environment back to what the code describes.
  • How to govern changes with deny settings, and choose what happens to resources removed from the template.

[eventID:27816]

  • VS Code
  • Azure Bicep
  • Azure Deployment Stacks
  • Azure Verified Modules
  • Azure CLI

Sprekers

Bent u al geregistreerd en moet u annuleren? Registratie annuleren

Registratie

Log in met je Microsoft-account

Aanmelden

Of voer je e-mailadres in om je aan te melden

*

Door je voor dit evenement aan te melden, stem je ermee in om je aan de Microsoft Reactor Gedragscode.

Delen van deze pagina kunnen machinaal of door AI vertaald zijn.