MC1446172 High
Copilot Studio - Block the use of maker-provided credentials for authentication
Summary AI-generated
Admins can now block maker-provided credentials for authentication in Copilot Studio, enforcing end-user credentials for increased security. Feature GA on August 25, 2026.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1421500 Copilot Studio - Enforce safe sharing by detecting credential oversharing
- MC1465301 Microsoft Copilot Studio – Securely connect with Entra-based user and S2S authentication
- MC1190188 Microsoft Copilot Studio – Increase sense of security for makers inside Copilot Studio
- MC1180712 Microsoft Copilot Studio - Strengthen security of Copilot Studio agents with additional threat protection
- MC1218332 Power Platform - Track, manage and scale Copilot adoption in PPAC new functionality
- MC1428562 Copilot Studio - Share autonomous agents to end users
Original post from Microsoft
We are announcing the ability to block the use of maker-provided credentials for authentication in Copilot Studio. This feature will reach general availability on August 25, 2026.
How does this affect me?
This feature provides admins with enhanced control over authentication by allowing them to restrict the use of maker-provided credentials across all tools within an agent. With this control in place, only end-user credentials can be used for authentication, ensuring a more secure and user-specific connection experience.
By default, this feature is turned off, giving organizations the flexibility to enable it selectively through the Power Platform admin center for specific environments or managed environment groups.
What action do I need to take?
This message is for awareness, and no action is required.
How does this affect me?
This feature provides admins with enhanced control over authentication by allowing them to restrict the use of maker-provided credentials across all tools within an agent. With this control in place, only end-user credentials can be used for authentication, ensuring a more secure and user-specific connection experience.
By default, this feature is turned off, giving organizations the flexibility to enable it selectively through the Power Platform admin center for specific environments or managed environment groups.
What action do I need to take?
This message is for awareness, and no action is required.