Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM Turbonomic ARM
Categories Public Cloud IaaS
Created by Guest
Created on Jul 29, 2022

Combine Azure volume scaling with VM scaling based on VM tags

What is the desired customer use case?: The customer would like from a policy to trigger the actions and execute the n actions at the same time (automatically/programmatically using API calls based on VM tags to select all the action related to one VM at the same time). Because we currently can combine volume scaling actions but not vm + volume scaling actions, this is not possible via the schedule or the API. Impact (to the customer use of Turbo) without this: Cannot streamline their process by automatically/programmatically using API calls based on VM tags. Customer needs this feature to respect the maintenance window (e.g.: 20mins) while combining Azure volume scaling with VM scaling. How much of their intended use of Turbo is impacted?: When some actions are generated, they don't want to have to use multiple maintenance windows to right size the same VM. They would ideally like to shut down the VM only once and do all the volume & scaling actions, instead of stopping and starting the same VM for each one.
Idea priority Medium