Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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
Categories On-Prem
Created by Guest
Created on Feb 4, 2026

Enable usage of parameters (variables) on MFT Actions location : remote path for Azure Blob (an other providers)

Hello, 

During setup of a MFT Action, if we want to configure a remote path location with Azure Blob option, we can't provide configuration values as variables.

It would be great to be able to set up parameters in all configuration values : Account Name, Location, Access Key, Sas Token ... , so we can provide values for these variables comming from flow service that's read this configuration from any custom source.

As you may know, Azure Storage SAS Keys are, in most cases, temporary (1hour, 1day ...) and must be renewed regulary or provided at a given moment just for one operation on one file. Hardcode a SAS key in a VFS or in an Action (remote path) and change it is a pain. That why I'm asking how to make it variable ...

Currently, we can't set a parameter name ( "[myVariable]" ) in these fields beacause of a pattern validation (see screenshot).

Regards, 

Clément

Idea priority High