---
key: "bicep"
name: "Bicep"
kind: "tool"
cloud: "azure"
namespace: "Azure/bicep"
registry_url: null
subject: null
repo_url: "https://github.com/Azure/bicep"
latest_version: "0.49.2"
latest_date: "2026-11-06"
latest_confirmed: true
latest_notes_read: true
oldest_tracked_version: "0.2.3"
breaking_releases_last_12_months: 1
counted_since: null
url: "https://eolwatch.dev/providers/bicep"
markdown_url: "https://eolwatch.dev/providers/bicep.md"
json_url: "https://eolwatch.dev/providers/bicep.json"
as_of: "2026-11-13"
from: null
state: "all"
unread_versions: []
short_url: "https://eolwatch.dev/p/bicep"
---

# bicep breaking changes

Bicep, published as `Azure/bicep`.

- Cloud: Azure
- Latest v0.49.2, released 6 Nov 2026
- 1 release that lists breaking changes in the last 12 months, counted for 13 Nov 2026 (UTC)

Every release from v0.2.3 up to v0.49.2: 5 releases with breaking changes, 6 changes

## bicep breaking changes: v0.2.3 to v0.49.2

### v0.43.1 (2026-05-04)

[Release notes](https://github.com/Azure/bicep/releases/tag/v0.43.1)

- [ ] [BREAKING CHANGE] Block usage of custom domains for ACR (#19564)

### v0.29.45 (2024-07-18)

[Release notes](https://github.com/Azure/bicep/releases/tag/v0.29.45)

- [ ] Replace the provider keyword with the extension keyword (#14379)
- [ ] Deprecate provider in Bicep configuration files (#14468)

### v0.23.1 (2023-11-02)

[Release notes](https://github.com/Azure/bicep/releases/tag/v0.23.1)

- [ ] [BREAKING CHANGE] Changes to our Module Manifests (#12057)

### v0.17.1 (2023-05-05)

[Release notes](https://github.com/Azure/bicep/releases/tag/v0.17.1)

- [ ] Name resolution & scoping behavior for variables declared in lambdas & for loops is now consistent with variables declared at the global scope. This means that previously, the following would have been permitted, whereas now it is blocked: See #10657 for more detail.

### v0.4.1272 (2022-02-12)

[Release notes](https://github.com/Azure/bicep/releases/tag/v0.4.1272)

- [ ] [BREAKING CHANGE] Renamed linter rule error code for commandToExecute (#5591) use-protectedsettings-for-commandtoexecute-secrets has been renamed to protect-commandtoexecute-secrets If you have chosen to disable the rule in bicepconfig.json or via the #disable-next-line directive, you will need to use the new error code. Apologies for not making this known further in advance.

Source: https://eolwatch.dev/p/bicep

Page: https://eolwatch.dev/providers/bicep | JSON: https://eolwatch.dev/providers/bicep.json