| title | Bicep Registry modules for FinOps |
|---|---|
| description | This article summarizes the Bicep modules available from the FinOps toolkit and provides guidance on how to reference them in your templates. |
| author | flanakin |
| ms.author | micflan |
| ms.date | 02/24/2026 |
| ms.topic | concept-article |
| ms.service | finops |
| ms.subservice | finops-toolkit |
| ms.reviewer | micflan |
Bicep modules developed within the toolkit are published to the official Bicep Registry. These modules aren't included directly in the toolkit release. To use a module, reference the desired module from your bicep code.
Referencing a module in your bicep template is as simple as adding the following to the top of your file:
module <name> 'br/public:cost/<scope>-<type>:<version>' {
name: '<name>'
params: {
parameterName: '<parameter-value>'
}
}For details about the parameters for each module, refer to the module details.
The FinOps toolkit maintains the following Bicep Registry modules:
- Scheduled actions – Send an email on a schedule or when an anomaly is detected.
Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.
[!div class="nextstepaction"] Give feedback
If you're looking for a specific module or template, vote for an existing or create a new idea. Share your ideas with others. We focus on ideas with the most votes.
[!div class="nextstepaction"] Vote on or suggest ideas
Related FinOps capabilities:
Related products:
Related solutions: