This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We enter budget forecasts every year for each AWS account and Azure subscription in Cloudability. We would like to prevent users from altering configured budget thresholds. If any changes are required, then the Cloudability admin can update the budgets by following the ticket process.
I submitted this idea, 'Prevent users from altering configured Budget cap,' in 2023 but did not receive any update or progress. Can you prioritize this idea? If any role is available to prevent users, then we can assign that role to users.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi Team,
Please find the inline response below.
We understand that you want to prevent certain users from altering budget amounts - but which users? only Cloudy Admins? what about Budget Owners (the user who created the Budget)?
=> All users except Cloudy Admins. My team create budgets on behalf of Account/Subscription owners. Each year, our Finance team requests all AWS account and Azure subscription owners to fill in the forecast for the next year for their accounts. After collecting all the budget forecast details, the finance team forwards them to us (Cloudy Admins) to update the budgets in Cloudability. If any modifications are required, the account owner/support team creates a request ticket for us. Since there is no permission to lock the updated budget info, users have started modifying/altering the budgets, which is affecting the entire effort of cloud governance team.
You state that you create budgets for each AWS and Azure subscription... do you do this manually or via API?
=>both the ways from portal or via API.
How are those budgets organized into Views? are they all contained within a single View or do you have separate Views for groupings of Accounts/Budgets?
=> Each account has single view and budget.
Do you also create a "master" budget that is the sum of all the individual budgets?
=>not currently, may be in future.
My team maintains the Cloudability access, views creation, budgets creation and update. We have a custom role "Cloudability ONLY User - IQVIA" for all regular users including the subscription/account owners. If any new permission available to lock the budgets, then we can assign that permission to "Cloudability ONLY User - IQVIA" role.
Let me know if you need any additional information on this idea.