Skip to Main Content
Cloud and AIOps


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).

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 (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.

Status Submitted
Workspace Cloudability
Created by Guest
Created on Sep 28, 2026

Support Azure credentialling from the Management Group and Tenant Root level instead of per-subscription

In a large, dynamic Azure environment with tight security and strong separation of duties, getting a subscription owner every (frequent) time to click a link to add "advanced features" credential for a new subscription is very onerous.

Add an option to credential at the tenant level, and perhaps also at any management group level, so that permissions are inherited by all new subscriptions within that scope and credentialling is essentially automatic.

This can be done either via the similar UI mechanism that exists now, or even as a downloadable JSON that needs to be deployed to Azure manually or via CLI/API.

The key benefits are:

- that we need to bug that hard-to-reach administrator only once, or once in a blue moon;

- and that we don't need to keep close tabs on and chase developers and engineers for new subscription notifications.

Idea priority Low