Skip to Main Content
Cloud Management 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 Instana
Categories Azure
Created by Guest
Created on Oct 29, 2025

Support the access setting with id & certificate for AzureSensor

Currently Azure sensor support connection only with service principals id & secret as bellow.

com.instana.plugin.azure:
  enabled: true
  # Subscription & Tenant ID
  subscription: '[Your-Subscription-Id]'
  tenant: '[Your-Tenant-Id]'
  # List of service principals that we can use to connect to the Azure
  # Each service principal has a limit of 12000 requests per hour.
  # Secret is a base64 encoded. If you are getting it directly from the Azure web,
  # it will already be encoded, so there is no need to encode it again.
  principals:
    - id: '[Your-Service-Principal-Account-Id]'
      secret: '[Your-Service-Principal-Secret]'

      

But it is more secure to access with service principals id & certificate. 

Could you support the access setting id & certificate like as bellow.

  principals:
    - id: "<your-client-id>"
      certificate: "<path-to-your-certificate-file>"
Idea priority High