- Highest ROI. Least build time for max savings.
- Tread carefully. Let's not bombard people with email notifications.
- Encouraging people to train in Azure instead of deferring them away due to dollar caps and resource provisioning limitations.
- Flexibility. Definition of inactiveness and abnormal high cost will change. Is it easy to change how we identify these.
- Maintainability. Can a junior Azure engineer quickly make sense and maintain the project.
- Low running cost. How much we are spending on the cloud to save cost?......
-
Notifications
You must be signed in to change notification settings - Fork 1
LNayana/azure-cost-management
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published