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
Created by Guest
Created on Nov 4, 2022

Constrained vCPU VM's from Azure taken into consideration for recommendations

Azure has a class of VM's that have constrained vCPU's for DB vm's that often require high memory, storage and IO bandwidth, but not high core count. So the VM class will basically only use a portion of the core count for that class to save money on SQL licenses. Azure is kinda dirty, as they don't offer a lower cost for this class of VM, so the only savings is for licenses. In the case of my customer, they have purchased VM's from Azure using the VM class Standard_E64-16s_v3, which only utilizes 16 cores, but has all of the other resources that would go with a 64core VM. It does not appear we take these VM classes into consideration, as we are recommending that they move this vm to the regular Standard_E64_v3 because how we see it, for the same cost, you go from 16 cores to 64 cores. Well yes, that is true, but now you are paying so much more for SQL licensing. All of this being said, perhaps this is something we should look into for our product. I have already spoken to AJ about this and he told me to submit an ER.
Idea priority Medium
  • Guest
    Nov 8, 2022


    This is a great idea, but currently, we do not support SQL Server in the cloud. The VMs for the SQL servers are scaled as plain old VMs in the market. We do intend to support SQL Servers on VMs in the cloud in the future, similar to how we support them on prem. This feature is similar, but not the same. However, this type of functionality will be included with support for SQL Server VMs in the cloud once we build out the functionality.