We are announcing the ability to govern Copilot agent development in your environments and enforce governance policies for Copilot agents. This feature will reach general availability on July 31, 2025.
How does this affect me?
This feature allows administrators to configure authentication for all agent interactions in the environment. Admins can select one of the following options:
- Authenticate with Microsoft or Authenticate Manually – This allows you to force authentication through Microsoft Entra ID or set up manual authentication.
- No authentication allows anonymous access.
Please note: If you block anonymous access in either one of the places, then at runtime the most restrictive behavior is enforced, and it will be blocked. If you’re using both the virtual connector and the Authentication for agents setting in the Security area of the Power Platform admin center, then access must be allowed in both places for it to be allowed at runtime.
We recommend that you move towards using the Authentication for agents setting in the Power Platform admin center to leverage the capability of groups and rules.
What do I need to do to prepare?
This message is for awareness and no action is required.
Source: Microsoft
Latest Posts
- Dataverse, Power Platform – Snowflake (Preview) connector is available [MC1127067]
- Dynamics 365 Customer Insights – Journeys – Create event portals with event registration details using Power Pages [MC1126999]
- AWS Directory Service launches Hybrid Edition for Managed Microsoft AD
- Amazon S3 Access Points now support tags for Attribute-Based Access Control