Ensuring External Security Provider Deployment Across All Copilot Environments

(1) Share

Report

Posted on by CU09120914-1

I’d like to use the new External Security Provider capability (referenced here: https://learn.microsoft.com/en-us/microsoft-copilot-studio/external-security-provider), but I need a way to ensure that it is automatically enabled across all environments. Is there a way to enforce this configuration globally for both existing and future environments?

Categories:

Bot administration

I have the same question (2)

All responses (2)

Answers (0)

Suggested answer

Prasad-MSFT Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
As of now, there is no global or tenant-wide setting to automatically enable the External Security Provider capability across all Copilot Studio environments. This feature must be enabled manually for each environment via the Copilot Studio admin portal.

Key points:

The External Security Provider must be configured per environment.

There is no PowerShell, API, or admin center setting to enforce or propagate this setting globally to all existing or future environments.

For new environments, you must enable it after creation.

Was this reply helpful? Yes No
CU09120914-1 5 on at

Like (0)

Report
Copy link

Link copied!

@Prasad-MSFT Thank you for your reply — understood that there’s no tenant-wide toggle in the Copilot Studio admin portal today.

Quick follow-up: do you know if this could be automated indirectly via the Power Platform side (Solutions / ALM)? For example, a Power App / flow (or pipeline step) that:

enumerates all environments (admin scope), and then invokes the relevant admin/management API per environment to enable the “External Security Provider” capability?

I’m thinking along the lines of: iterate envs → call an admin API/action → apply setting, even if it’s not exposed as a single global setting.

are you aware of any blocker ? (no public API endpoint, capability not writable via admin APIs, etc.)

Was this reply helpful? Yes No