Frequently asked questions

The Agent Review Program is the expert-guided service: Microsoft experts work with you to review your agent, walk through the findings, and validate your fixes. Agent Review Center is the tool behind it. It runs in your own environment, and it stays there after the engagement so you can review your agents again whenever you want.

See The program and the tool.

The program suits an agent in testing, pilot, or production that has a meaningful user base and enough real conversations for the findings to tell you something.

An agent with little or no traffic can still have its configuration and orchestration reviewed, but the runtime analysis will have little to work with. Turn on transcript recording now, so conversations build up before the review.

Not sure? Ask your Microsoft contact, who scopes it with you before Session 1.

Three sessions across four weeks: a 1-hour session in week 1, then 1–2 hour sessions in weeks 2 and 4. You make the agreed fixes in week 3. Plan for one named owner with about 3–6 hours across the sessions. See How the program runs.

Use the nomination options on the overview page, or ask the Microsoft team you already work with about the Agent Review Program. Your Microsoft contact scopes it with you before anything starts.

Email the team at serenaxie@microsoft.com. Don’t include transcripts or other sensitive data. During an engagement, you can also go through your Microsoft contact.

Who: the agent’s owner, the person who will work on the agent. Session 1 includes setting up Agent Review Center, so also have someone available who can change environment settings and assign roles: a Power Platform admin, an environment admin, or a System Administrator.

Before the session:

• Turn on transcript recording in the agent’s environment as early as you can. It is not retroactive.
• Ask your admin to work through steps 1 to 3 of the installation guide: environment settings, and data policies that allow the three connectors.
• Be ready to talk about the agent’s use case, target users, and deployment stage, what success looks like, and your top concerns.

Agent Review Center stays installed in your environment, with your reviews and their snapshots, so you can review your agents again whenever you need to. You can also download any result as a PDF or JSON report.

A Power Platform admin for licensing, credits, data policies, and environment settings; a System Administrator in the environment to import the solution; the agent owner, to share the agent; and the reviewers themselves. See who’s who and verify the installation in the installation guide.

Three, together in the same group: Microsoft Dataverse, Agents, and Power Automate Management. The setup app uses Power Automate Management, and the import fails if it is blocked.

If your environment uses advanced connector policies, add all three to the allowed list. See Data policies and connectors in the installation guide.

What you see

The solution import stops with an error like this one. Your message shows your own policy name, IDs, and timestamps.

Solution "Agent Review Center" failed to import: CanvasApp import: FAILURE: Code: AcpDlpPolicyEvaluation Message: The app 'cat_copilotagentkitinstaller_81f96' cannot be saved because one or more connectors it uses 'shared_flowmanagement' are blocked by Advanced Connector Policy (ACP) or Data Policies (DLP) for this environment. Please contact your environment administrator '' to update the policies '<policy name>' to allow the connectors used by this app. Link for the policy wiki ''. Violation details: [PolicyId: <policy ID>, PolicyDisplayName: <policy name>, PolicyType: DLP, PolicySource: , PolicyLastModified: <timestamp>, ViolationType: BlockedConnector, Parameters: [shared_flowmanagement]]. Client Request Id: <request ID>.

How to fix it

1. In the Power Platform admin center, go to Security → Data and privacy → Data policies. On older layouts, it's Policies → Data policies.

2. Open the policy named in the error message (the PolicyDisplayName value).

3. On the Prebuilt connectors step, find Power Automate Management and move it from Blocked to Business. It needs to be in the same group as Microsoft Dataverse and Agents (preview).

4. Check that those two are also in Business. Otherwise, the next attempt will fail with a BusinessAndNonBusinessConnector violation instead.

5. Save the policy, wait a few minutes for it to take effect, then retry the import.

Learn more: Data policies · Data policies and connectors in the installation guide

What you see

The import stops with an AcpDlpPolicyEvaluation error, like the one in the previous question. This time the violation names an Advanced Connector Policy (ACP), and the blocked connector can be a different one, such as shared_agentnode, the Agents connector.

Why it happens

Advanced connector policies block every connector that isn’t explicitly allowed, including new ones.

How to fix it

1. Find where the policy is set. An environment has at most one advanced connector policy: set on the environment itself, or inherited from its environment group.

2. For a single environment: in the Power Platform admin center, select Security > Data and privacy > Advanced connector policies. For an environment group: select Manage > Environment groups, open the group, and select Rules > Advanced connector policies.

3. Add all three connectors the solution needs: Microsoft Dataverse, Agents, and Power Automate Management. Then select Save. For an environment group, also select Publish rules.

4. Wait a few minutes, then retry the import.

Learn more: Advanced connector policies

Environment admins can’t edit tenant-level policies. Ask a Power Platform admin to make the change, and send them Data policies and connectors from the installation guide.

Learn more: Manage data policies

The environment is not ready for code apps, or the import did not complete.

Confirm that Enable code apps is on in the environment, and that you are a System Administrator there. See Configure the environments in the installation guide. Also check that your data policies allow the three connectors.

Some browsers unzip downloads automatically. Import the .zip as it is: download it again with the download button in the installation guide, with automatic unzipping turned off.

The setup app (Copilot Agent Kit Installer) could not confirm the connections or start the Review Agent Components flow.

Check that both connections exist and are signed in, and that your data policies allow Microsoft Dataverse, Agents, and Power Automate Management to be used together. Then open the setup app again. It repairs what it can on each run.

If it still can’t complete, follow Run the one-time setup app in the installation guide, and let your Microsoft contact know.

A connection reference in the solution has no connection.

Run the setup app (Copilot Agent Kit Installer), or select the connection in the readiness checklist. To check by hand, see Run the one-time setup app in the installation guide.

The Review Agent Components flow is off because a connection is missing.

Fix the connections first, then turn the flow on from the readiness checklist, or run the setup app again.

Your account cannot change the flow's state. The user who imported the solution owns its flows and connection references.

Ask the person who installed the solution, or a System Administrator, to turn it on in Power Automate.

There is nothing to review in the environment you selected.

Select the environment where the agent lives, and check that the agent exists and is active there.

Uploads for declarative agent and skill reviews can be up to 16 MB. Remove files the review doesn’t need, such as large binaries, and upload again. Accepted file types are .zip, .md, .yaml, .yml, and .json.

The AI-assisted checks did not run, so their weight was spread across the rest of the review.

Check connections, flows, and credits in the readiness checklist, then select Review again.

Select Share results, then Download PDF report or Download JSON report. The menu tells you whether the snapshot includes runtime analysis or design findings only. The reports are yours: sharing them outside your team is your decision.

Select Review again after you make your fixes. Each run is kept as a snapshot, and View progress shows the score across all of them. For runtime analysis, choose a date range that covers conversations after your fix.