Skip to content
Latest (currently 2026.8.0) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentregistry.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Microsoft Copilot Studio

Page as Markdown
Discover agents that are deployed in your Power Platform environment and monitor these deployments in the registry UI.
Before you begin

  1. Set up an OIDC provider. This guide assumes that you installed Keycloak. Make sure to follow the General setup tab to install Keycloak with the required realm settings, clients, and secrets.
  2. Install Solo Enterprise for agentregistry.
  3. Connect Solo Enterprise for agentregistry to your Microsoft Copilot Studio environment.
    Note
    Solo Enterprise for agentregistry does not create or deploy Copilot Studio agents. The MicrosoftCopilotStudio runtime is a discovery-only runtime.
Step 1: Create and publish a Copilot Studio agent

Create an agent and deploy it to Copilot Studio. If you already have agents in your environment, you can skip this step and continue with Step 2: Verify discovery.
  1. Sign in to Copilot Studio at copilotstudio.microsoft.com.
  2. Confirm you are in the same environment you configured earlier.
  3. Click Create blank agent.
  4. Enter a name and click Publish.
Step 2: Verify discovery

After the runtime is created, Solo Enterprise for agentregistry triggers an initial sync to list deployed Copilot Studio agents as Instances in the registry UI.
Note
It can take a few minutes for the sync to complete and discovered agents to show up in the registry UI.
  1. Open Instances view in the registry UI.
  2. From the Managed drop down, select Unmanaged, Discovered Resources.
  3. Verify that you see the Copilot Studio agent that you created earlier. The agent appears with provider metadata such as its Dataverse bot ID, state, published and updated times, and last seen time.
Note
If agents do not appear, check the following in your runtime setup.
  • The dataEndpoint is the Dataverse Web API root URL (https://<org>.crm.dynamics.com), not a specific API path.
  • The Entra app is registered as an application user in the target Power Platform environment with a role that grants read access to the Bot table.
  • The secret exists and status.dataKeys includes clientSecret.
  • The Copilot Studio agent has been published in the correct environment. Unpublished agents may not appear as bot records in Dataverse.
For detailed error information, check the agentregistry server logs for copilot or resolve client secret messages.
Azure AI Foundry projects