Hoppa till huvudinnehåll
Megafonikon

GitHub Universe on the Road

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

Bicep 102: Beyond the Basics, Scaling Your Infrastructure as Code with Bicep

februari 10, 2027 | 6:00 - 7:00 em (UTC) Koordinerad universell tid

Är du redo att komma igång med AI och de senaste teknikerna? Microsoft Reactor tillhandahåller evenemang, utbildning och communityresurser som hjälper utvecklare, entreprenörer och nystartade företag att bygga vidare på AI-teknik med mera. Följ med!

Bicep 102: Beyond the Basics, Scaling Your Infrastructure as Code with Bicep

februari 10, 2027 | 6:00 - 7:00 em (UTC) Koordinerad universell tid

Är du redo att komma igång med AI och de senaste teknikerna? Microsoft Reactor tillhandahåller evenemang, utbildning och communityresurser som hjälper utvecklare, entreprenörer och nystartade företag att bygga vidare på AI-teknik med mera. Följ med!

Gå tillbaka

Bicep 102: Beyond the Basics, Scaling Your Infrastructure as Code with Bicep

februari 10, 2027 | 6:00 - 7:00 em (UTC) Koordinerad universell tid

  • Format:
  • alt##LivestreamLivestream

Område: Infrastruktur

Språk: Engelska

One Bicep file works well for one team and one environment, but it gets hard to share, review, and keep consistent once several teams and environments depend on it.

This session picks up where Bicep 101 ends and shows how to scale a Bicep codebase. 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.

In the demo I split a single Bicep file into modules, replace hand-written resources with Azure Verified Modules, and publish a shared module to a private registry so other teams use the same version. I add a parameters file for each environment and user-defined types, so a wrong value fails before anything is deployed, and set linter rules for the whole repository in bicepconfig.json. I then use GitHub Copilot to bring resources that were built by hand into the same code and add a GitHub Actions pipeline that runs Stacks

What-If before every deployment, which confirms that adopting those resources changes nothing in Azure. The result is Bicep code that many teams can share and deploy the same way. Everything runs live from VS Code, GitHub, and the Azure CLI. What attendees will learn:

  • How to structure Bicep with modules, Azure Verified Modules, and a private registry that several teams can share.

  • How to keep environments consistent with parameters files, user-defined types, and linter rules.

  • How to bring hand-built resources into code with GitHub Copilot and check every deployment with Stacks What-If.

[eventID:27836]

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

Talare

Redan registrerad och behöver avboka? Avboka registreringen

Registrering

Logga in med ditt Microsoft-konto

Logga in

Eller ange din e-postadress för att registrera dig

*

Genom att registrera dig för detta evenemang godkänner du att följa reglerna Microsoft Reactor Code of Conduct.

Delar av denna sida kan vara maskin- eller AI-översatta.