microsoft / microsoft/finops-toolkit
Cost Comparison of Selected Services among Azure Regions
@arthurclares is already working on this.
Since Feb 5, 2025.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
📝 Scenario
As a Solution / Application Owner I need to understand the impact on cost of deploying a workload in different regions, in order to make informed decisions about which region would be the right to select. Use cases include expanding the workload to new regions to cover geo-distributed users, selecting a failover regions as part of BCDR strategy, or simply moving a workload to a lower cost region.
💎 Solution
The solution should include a cost comparison among regions, of the services that are currently used. Taking into account SKUs and various discounts.
📋 Tasks
### Required tasks
- [ ] Export the price sheet with relevant cost data over previous period
- [ ] Use the current price for the used services for various regions
- [ ] Offer filtering options to the user to select services / SKUs and regions of interest
- [ ] Calculate the prices for selected SKUs for each selected region
- [ ] Create a table/ chart that shows the cost of the selected services for the various regions
### Stretch goals
- [ ] The solution could be extended to include comparison of other services attributes that differ among regions, such as sustainability and carbon footprint.
ℹ️ Additional context
The Azure Pricing Calculator could be used for manual cost comparison of services among regions
The Cost Management API could be leveraged for scripting a similar solution.
Both approaches require significant effort.
🙋♀️ 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.
Assessment
This issue has not been assessed yet.