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 Future consideration
Workspace IBM Turbonomic ARM
Categories Public Cloud IaaS
Created by Guest
Created on Sep 18, 2023

Azure Services like Databricks, or AKS that create VMs should appear as a property in those VM entities.

With these properties being visible, Customer can create policies to exclude from policies VMs  that are being managed by Azure Services. Customer can create UNPARKABLE collections based on Azure Services.  Right now with 1000s of VMs, there is too much noise from the automatically managed VMs by Azure to find optimization opportunities in the IaaS area. Give the customer a chance to filter out the noise.

Idea priority High
  • Guest
    May 29, 2024

    This was surfaced with Turbonomic 2+ years ago.  It is presenting as a blocker now to at least one major initiative.  "VMs" need to be standalone VMs.  All compute nodes for managed services need to be identified in their own buckets, so we don't get databricks and all other VMSS nodes (AKS, AppSvc, etc) don't show up in what Turbo calls "Virtual Machines".  This is a critical need now, please prioritize this ASAP.


    Note: Tagging is not a viable answer.  Tagging is static and won't catch future-created nodes/VMs.  Don't assume we can apply tags for the entire enterprise.

  • Guest
    May 20, 2024

    The same client has another business use where is would be VERY handy to see which Business Service is creating the VMs. Particularing AKS, or Databricks or some other service vs a regular VM. This is all about lifecycle changes; they want to restrict regular VMs to a standard list - but they want to exclude Databricks, and AKS from these restrictions - and it is NOT possible to use Azure Service as a filter when creating Cloud VM groups.   Other ideas like using tags - would work but this client cannot rely on the tags being reliable.

  • Guest
    Nov 27, 2023

    just spoken again to the customer and it's not just VMs that need to be able to be filtered by Cloud Service - it's also entities like Volumes. Business Case. Azure says it's SLAs are dependent on AKS Volumes being premium. Therefore the client would like to create a group Volumes generated by AKS to exclude Volume Efficiency actions away from PREMIUM SSD.