From the course: Scaling Azure Deployments with Bicep

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Implementing shared modules across teams and subscriptions

Implementing shared modules across teams and subscriptions - Azure Tutorial

From the course: Scaling Azure Deployments with Bicep

Start my 1-month free trial Buy for my team

Implementing shared modules across teams and subscriptions

“

- [Instructor] In this lesson we're tackling collaboration at scale. Imagine your team crafts a polished Bicep module for something as critical as database configurations, say enforcing encryption at rest, backup policies, or network isolation. Now, another team in a different subscription wants to reuse it, but they need slight tweaks, like longer backup retention or a different SKU. The challenge isn't just sharing code, it's sharing securely while maintaining control over how the code evolves. Let's unpack how to do this without drowning in copy-pasted templates. When sharing modules across subscriptions the core idea is centralization. You want a single source of truth for that module accessible across teams and environments. One elegant way to do this is using Azure Template Specs, often abbreviated as TS. A template spec is a versioned Azure resource that stores your Bicep or ARM templates directly in Azure, making it discoverable and reusable across subscriptions. To create…

Contents