Install Agent Review Center

A step-by-step guide for you and your admins: who does each step, when to do it, and how to check that it worked.

Agent Review Center is a managed Power Platform solution that you import into an environment in your own tenant. If you are in the Agent Review Program, you install it together with Microsoft experts in Session 1. Getting steps 1 to 3 done beforehand makes that session much smoother.

Installation steps

Nine steps. Open only the step you need; each summary shows who owns it and when to do it.

Before you start Who: Agent owner + adminsWhen: As early as you can

Who
The agent owner, with your Power Platform admin and a System Administrator for the environment.
When
As early as you can. Licenses and data policy changes can take time to arrange, and transcripts need time to build up.
Done when
Every task below has a named person.

Who’s who

This guide uses these role names:

Power Platform admin
Manages tenant-wide settings, licenses, capacity, and data policies.
Environment admin
Manages the settings of one environment.
System Administrator
The Dataverse security role in the environment. This person imports the solution, and the account that imports it owns its apps, flows, and connection references.
Agent owner
Owns the agent in Copilot Studio and shares it with reviewers.
Reviewer
Runs reviews in Agent Review Center.

Who does what

Installation tasks and who can do each one
Task Who can do it
Licenses, and Copilot Credits allocated to the environment Power Platform admin
Code apps and transcript settings Power Platform admin or environment admin
Data policies and advanced connector policies Power Platform admin. Environment admins can’t edit tenant-level policies.
Import the solution, run the setup app, check the flows System Administrator
Assign reviewer roles System Administrator
Share the agent with reviewers Agent owner
Share the Agent Review Center app System Administrator
Run reviews Reviewers

Plan ahead

  • Choose the environment. Two environments can be involved: the target installation environment, where you install Agent Review Center, and the agent environment, where the agent you review lives. Install in the agent environment if you can, so they are the same. Configuration reviews can cover agents in other environments, but conversation transcripts are only analyzed in the environment where Agent Review Center runs.
  • Turn on transcript recording now. Recording is not retroactive: only conversations after you turn it on are saved. Transcripts are kept for 30 days by default unless an admin changes the retention period, so plan your first review while the conversations you care about are still there. See Download conversation transcripts in Power Apps.
  • Arrange licenses and credits. See What you need to bring.
  • Have an admin available during the install. A Power Platform admin, an environment admin, or a System Administrator needs to be available to change settings and assign roles. In the program, that means having them in Session 1.
  • Already using the Copilot Agent Kit in that environment? Check with your Microsoft contact before you import Agent Review Center.

Send your admin this page. It organizes every required setting, role, and installation check by owner.

Configure the environments Who: Power Platform or environment adminWhen: Before import

Who
Power Platform admin or environment admin.
When
Before you import. Turn on transcript recording first, because it only saves conversations from that point on.
Done when
The checks at the end of this step pass.

Configure these settings before you import:

  • Prepare the target installation environment: use a Dataverse environment on the standard release cycle, with Copilot Credits allocated.
  • Make sure that Power Apps Code Apps is on: Agent Review Center and its setup app are both code apps.
  • Set transcript recording to on in the agent environment. Both transcript settings need to be on.

Check it worked

  • In the Power Platform admin center, under Licensing > Copilot Studio > Manage capacity, the environment shows Copilot Credits allocated.
  • Enable code apps shows On in the environment’s Settings > Product > Features.
  • Run a test conversation with your agent, then confirm that its transcript appears. See Download conversation transcripts in Power Apps.

Data policies and connectors Who: Power Platform adminWhen: Before import

Who
Power Platform admin.
When
Before you import. After you save a policy change, wait a few minutes for it to take effect.
Done when
The three connectors below are allowed together, in every policy that applies to the environment.

Your data policies must allow these three connectors together, in the same group. If one is blocked, the import fails.

Connectors that the data policies must allow, and what each is used for
Connector Used for
Microsoft Dataverse Reading agent configuration and transcripts, and storing reviews and results. Connection reference: Agent Review Center | Dataverse.
Agents The AI-assisted checks run by the Review Agent Components flow. Connection reference: Agent Review Tool | Agents. It may be listed as Agents (preview); its connector ID is shared_agentnode.
Power Automate Management The one-time setup app, which checks the Review Agent Components flow’s connections and starts it.

If the environment uses data policies

  1. In the Power Platform admin center, go to Security > Data and privacy > Data policy. On older layouts, it’s Policies > Data policies.
  2. Open each policy that applies to the environment.
  3. On the Prebuilt connectors step, make sure that Microsoft Dataverse, Agents, and Power Automate Management are all in Business. If they’re split across groups, the import can fail with a different policy violation.
  4. Save the policy, and wait a few minutes before you import.

If the environment uses advanced connector policies

Advanced connector policies block every connector that isn’t explicitly allowed, including new ones. Add all three connectors to the allowed list:

  • For a single environment: in the Power Platform admin center, select Security > Data and privacy > Advanced connector policies, add the connectors, and select Save.
  • For an environment group: select Manage > Environment groups, open the group, and select Rules > Advanced connector policies. Add the connectors, select Save, and then select Publish rules.

Check it worked

Open each policy that applies to the environment, and confirm that Microsoft Dataverse, Agents, and Power Automate Management are all in Business, or all on the allowed list for an advanced connector policy.

Learn more: Data policies · Advanced connector policies

Import blocked by a policy? See Power Automate Management is blocked, an advanced connector policy blocks a connector, and I can’t edit the policy.

Next: tell the System Administrator who will import the solution.

Download and import the solution Who: System AdministratorWhen: After steps 2 and 3

Who
A System Administrator in the target installation environment. The account that imports the solution becomes the owner of its apps, flows, and connection references, so choose it carefully.
When
When steps 2 and 3 are done. The import can take several minutes.
Done when
Each connection reference has a connection, and both cloud flows are on.

Get the solution file

  1. If you have not already, use the featured download at the top of this page. Every version is also listed on the GitHub releases page. Downloading it here directly avoids passing the file around by email or chat.
  2. Keep the .zip as it is. Don’t extract it. If your browser gives you a folder instead, download it again with automatic unzipping turned off.
  3. Optional: check that the file’s SHA-256 hash matches the one in the featured download card. In PowerShell: Get-FileHash .\AgentReviewCenter_20261016.1_managed.zip -Algorithm SHA256

Import

  1. Sign in to Power Apps and select the target installation environment.
  2. Select Solutions > Import solution > Browse, choose the .zip file, and select Next.
  3. Check the details: the solution is Agent Review Center, from the publisher PowerCAT. Select Next.
  4. For each connection reference, select an existing connection or create one:
    • Agent Review Center | Dataverse: Microsoft Dataverse
    • Agent Review Tool | Agents: Agents
  5. Select Import, and wait for the success message.

Set both connections here if you can. The setup app in the next step checks them. If it can’t complete, use the checks in Run the one-time setup app and the linked FAQ troubleshooting.

Check it worked

  • In the solution, Connection references shows a valid connection for each one.
  • In Power Automate, under Solutions > Agent Review Center > Cloud flows, both flows show On.

Import failed? See The import fails, or the apps are missing, I have a folder instead of a .zip file, and the other questions about installing Agent Review Center. For a list of everything the solution adds, see What gets installed.

Run the one-time setup app Who: System AdministratorWhen: Right after import

Who
A System Administrator, usually the person who imported the solution.
When
Right after the import.
Done when
The app shows Setup is complete, or you’ve checked the connection references and flows by hand using the checks below.

The setup app is named Copilot Agent Kit Installer. Despite its name, it’s part of the Agent Review Center solution: it connects Agent Review Center’s connections and starts the Review Agent Components flow.

  1. In Power Apps, select Apps and open Copilot Agent Kit Installer.
  2. If Power Apps asks you to allow its connections, select Allow.
  3. The setup app checks four things and fixes what it can.
  4. Wait for Setup is complete.
The four checks in the setup app
Check What it confirms
Agents connection Power Apps assigned a connected Agents account.
Dataverse connection Power Apps assigned a connected Dataverse account.
Workflow connections The Review Agent Components flow uses the assigned Agents and Dataverse connections.
Review workflow The Review Agent Components flow is started.

You can run the setup app again at any time to repair the connections and the flow.

Check it worked

The setup app shows Setup is complete, and both flows show On in Power Automate.

See Setup could not complete in the FAQ if the setup app stops.

Next: when setup is complete, tell the agent owner and the reviewers.

Share with reviewers Who: System Administrator + agent ownerWhen: After setup

Who
A System Administrator assigns roles and shares the app. The agent owner shares the agent.
When
After setup is complete.
Done when
Each reviewer can open Agent Review Center.

For each person who will run reviews:

  1. Check their licenses. See What you need to bring.
  2. Assign the reviewer roles in the agent environment: Environment Maker, Bot Viewer, and Bot Transcript Viewer. In the Power Platform admin center, select the user under Access > Users, then select Manage security roles. See Assign a security role to a user.
  3. Share the agent with the reviewer: in Copilot Studio, open the agent and select Share.
  4. Share the app: in Power Apps, select Apps, select Agent Review Center, select Share, and add the reviewer.

The readiness check You have the access this environment needs may show yellow for reviewers who aren’t System Administrators. If a reviewer can’t create reviews, contact your Microsoft contact.

Check it worked

Ask one reviewer to open Agent Review Center.

Verify the installation Who: Reviewer + adminWhen: Before first review

Who
A reviewer, with an admin at hand to fix anything that isn’t ready.
When
Before your first review.
Done when
The readiness checklist is green, or you know what each remaining item blocks.
  1. In Power Apps, select Apps and open Agent Review Center.
  2. On first launch, a Welcome — let’s set you up! message shows a readiness checklist. You can return to it at any time from the Settings (gear) button on the reviews list.
  3. Select Run checks, and work through anything red or yellow.
Readiness checks and what each one blocks if it is not green
Check If it is not green
Environment reachable Blocks every check below.
Copilot Studio provisioned Blocks every review in this environment.
You have the access this environment needs Configuration reviews still run; runtime transcript analysis may be blocked.
Transcript recording enabled at environment level Blocks runtime analysis and credit estimation.
Transcript viewing enabled for agent owners Reviewers may not be able to open the transcripts behind a score.
Connections enabled Blocks flow activation and analysis.
Flows enabled Blocks analysis runs.

You can still run configuration reviews while items are being fixed. Use Copy admin link to send your admin straight to the setting that needs changing, then select Run checks again.

Run your first review Who: ReviewerWhen: After readiness checks

Who
A reviewer.
When
Once the readiness checks pass. A configuration-only review can run sooner.
Done when
The review shows Review complete, with a grade and findings.
  1. In Agent Review Center, select Add review, and give it a Project name.
  2. Under What kind of asset are you reviewing?, choose Copilot Studio Agent, Declarative Agent, or Skill.
    • For a Copilot Studio agent, select the environment where the agent lives, and then choose the agent.
    • For a declarative agent or skill, upload its files: .zip, .md, .yaml, .yml, or .json.
  3. To include runtime analysis for a Copilot Studio agent, set the date range for transcripts. The app counts the transcript records in the range before you start. If it finds none, widen the range or check that transcript recording is on.
  4. Select Create. Progress is shown as the review runs. You can select Continue in background and come back later.

Next: read the results, work through the findings, and measure your fixes. See Run a review on GitHub.

Upgrade or uninstall Who: System AdministratorWhen: For upgrades or removal

Who
A System Administrator in the environment.
When
When a new version is released, or when you no longer need Agent Review Center.
Done when
After an upgrade, Run checks is green.

Upgrade to a new version

  1. Download the new .zip with the featured download at the top of this page, or from the latest release.
  2. In Power Apps, select Solutions > Import solution, and choose the new file.
  3. Power Apps recognizes that Agent Review Center is already installed. Keep the default upgrade option, and select Import.
  4. Open Agent Review Center and select Run checks. If connections or flows show as off, run the setup app again.

Your existing reviews and results stay in place. To hear about new versions, select Watch > Custom > Releases on the GitHub repository. The changelog lists what changed.

Uninstall

Caution

Deleting the solution deletes its Dataverse tables, and every review and result stored in them. First, download the PDF or JSON report for any results you want to keep.

In Power Apps, select Solutions, select Agent Review Center, and then select Delete.

Reference: what gets installed Solution components and data storage

Everything is in one managed solution, Agent Review Center (AgentReviewCenter), from the publisher PowerCAT. It needs Copilot Studio to be available in the environment.

Components in the Agent Review Center solution
Component What it does
Agent Review Center (code app) The app you use to run reviews and read results.
Copilot Agent Kit Installer (code app) The one-time setup app for the connections and the Review Agent Components flow.
Review Agent Components (cloud flow) Runs the review, using the Dataverse and Agents connections.
Global | LogFeatureTelemetry I ARC (cloud flow) Called by the app when you use a feature. Contains no connectors.
AgentRuntimeAnalyzer (plug-in) Processes runtime analysis jobs asynchronously in Dataverse.
Eight Dataverse tables Store your reviews, snapshots, and results.

Get help

  • Error messages and common questions: see the FAQ. Select Expand all, then search for the exact wording on your screen.
  • During an engagement: raise anything not covered here with your Microsoft contact.
  • Anything else: contact the Agent Review Program team by email. Don’t include transcripts or other sensitive data.
  • Questions about the documentation: open an issue on GitHub. Issues are public, so don’t post tenant data, transcripts, or screenshots with real data.