Unanswered

How to Parameterize Security Properties of a Copilot Studio Agent in Managed Solutions

(0) Share

Report

Posted on by NC-19051104-0

I’m working with a Copilot Studio agent that uses manual authentication. The agent is part of a managed solution that we deploy across different environments (dev, test, prod). I would like to understand if there’s a supported way to parameterize the security properties of the agent, such as:

Authentication method

Redirect URL

Service provider name

Client ID

Client secret

I have reviewed the current documentation, and while I see support for using environment variables in Power Automate and other components of Power Platform, I couldn’t find a clear way to reference environment variables (or any other parameterization method) for these agent security properties.

My goal is to avoid manually updating these settings after importing the managed solution into a new environment.

Can you please advise:

Is it currently possible to parameterize these authentication-related fields in Copilot Studio agents?

If not, is there a recommended pattern or workaround to manage this configuration across environments more efficiently?

Thank you!

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Pablo Roldan 316 on at

Like (0)

Report

Hi there

Microsoft Copilot Studio does not support binding environment variables to the manual authentication fields (like Client ID, Secret, Auth URL, etc.) in the Security > Authentication settings UI. YET.

Consider adding this feature as an Idea in MS Ideas Forum, I know what I pain, anyway most of the time at least you end up with 3 Environment DEV/QA/PROD so you have to do it only 3 times... if you are managing lots of environments please reach MSFT for a tailored solution...

regards,

Was this reply helpful? Yes No
NC-19051104-0 5 on at

Like (0)

Report

Hi @Pablo Roldan.

Thanks for your response. I need to know how to modify those properties on an agent within a managed solution, since editing components directly isn’t allowed.

Any guidance on how to proceed while respecting the managed nature of the solution would be appreciated.

Best regards,

Was this reply helpful? Yes No