microsoft / microsoft/finops-toolkit
[Bicep] Automate FinOps resource deployment
Open
Nobody has claimed this yet.
Help wanted ✨
Skill: Deployment
Tool: Bicep Registry
Type: Feature 💎
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
📝 Scenario
As a FinOps practitioner, I need to automate Cost Management resource creation in order to streamline onboarding
💎 Solution
### Cost Management
- [x] #86
- [x] #184
- [x] #221
- [ ] Validate/publish the exports module (code is complete)
- [ ] #222
- [ ] #223
- [ ] Should we cover scheduled action deployment for MGs by deploying to each subscription?
- [ ] Should we cover tenant deployments for billing scopes?
- [ ] Should we re-evaluate tag inheritance setting in bicep? (We may still have the code)
- [ ] Do we need to migrate the 2 scheduled action BR modules to AVM?
- [ ] Update the docs to account for the switch to AVM (we reference BR explicitly)
### Other native products
- [ ] Are there any Azure Advisor resources that need coverage?
- [ ] Are there any Azure Carbon Optimization resources that need coverage?
- [ ] Are there any Azure Policy templates that we could consider offering curated templates for?
### FinOps toolkit
- [ ] Update or deprecate the FinOps hubs AVM
- [ ] Are there FinOps hubs capabilities that make sense as dedicated bicep modules (e.g., adding scopes, backfilling data)?
- [ ] Should we add FinOps workbooks to the bicep registry?
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Leave comments to help us solidify the vision.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the unchecked Cost Management, Other native products, and FinOps toolkit task lists in this issue, including the questions about management-group and tenant deployments, AVM migration, and documentation. No files, tests, or entry points are named; the work is done only when the scope is decided and the selected resource coverage, module updates, and documentation changes are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100