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
To have a builtin integration to unlock/lock Azure resource when a Turbonomic action is executed could avoid external developments.
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.
Hello Marie- Claude. Thanks for opening the idea. Given the current priorities for 2025, this feature will not be in the roadmap within the next 6-9 months. Therefore, I´m marking it as future consideration.
Hi Marie-Claude, thanks for taking the time to submit the Idea. One question I had is, where are you seeing this "mandatory best practice" documented by Azure? Can you please share so we can review further to better understand this and if this has recently changed from Azure as you are the first customer we are hearing this from as a mandatory best practice.
Let us know,
thanks,
Feature mandatory as Locking Azure resources is a mandatory Best practice