Connect to Akto (Async Mode)

Discover agents and ingest Copilot Studio conversation transcripts from Microsoft Dataverse

Overview

Microsoft Copilot Studio is a low-code platform for building and deploying conversational AI agents and copilots. Connect Akto Argus to your Copilot Studio environment to discover deployed agents and ingest conversation transcripts for security analysis.

Once connected, Akto Argus automatically:

• Discovers Copilot agents configured in your Power Platform environment

• Ingests conversation transcripts captured by Copilot Studio in Microsoft Dataverse

• Pairs user prompts with bot responses to reconstruct full conversation flows

• Sends traffic to Akto for prompt injection, PII, and policy-violation analysis

The connector reads conversation transcripts from the Dataverse Web API using a service principal — no changes are required to your Copilot Studio agents or their deployment.

How It Works

Microsoft Copilot Studio
         ↓ (transcripts persisted)
Microsoft Dataverse  ──── (Dataverse Web API v9.1 + OAuth 2.0)
         ↓
Akto Argus Connector  ── (every 5 minutes)
         ↓
Akto Data Ingestion Service
         ↓
Akto Dashboard

1. Polling — The connector polls Dataverse on a recurring schedule (default: every 5 minutes) for new conversation transcripts.

2. Authentication — OAuth 2.0 client-credentials flow using a Microsoft Entra ID app registration and a Dataverse application user.

3. Pairing — Each transcript's activities array is parsed; user messages (role: 1) are paired with the next bot response (role: 0) to form request/response pairs.

4. Publishing — Each pair is forwarded to your Akto Data Ingestion Service for ingestion into the Akto platform.

Prerequisites

Before setting up the Copilot Studio connector, ensure the following requirements are met. Most setup issues are caused by missing prerequisites — please review them carefully.

1. Supported Power Platform Environment

Per the Microsoft documentation on transcript controls, Microsoft does not persist Copilot Studio conversation transcripts to Dataverse for the following environment types:

• Dataverse developer environments

• Microsoft Dataverse for Teams environments

• Microsoft 365 Copilot agents

Your agents must be deployed to a Sandbox or Production environment with a Dataverse database enabled. Verify the environment type in the Power Platform admin center. For instructions on creating a new environment, see Create and manage environments.

2. Transcript Saving Enabled

The Power Platform environment setting "Allow conversation transcripts and their associated metadata to be saved in Dataverse" must be turned on for your environment. Full details are in the Microsoft transcript-controls documentation.

To verify or enable it:

1. Open the Power Platform admin center.

2. Go to Manage → Environments → select your environment → Settings.

3. Expand Product → Features → scroll to Copilot Studio agents.

4. Ensure "Allow conversation transcripts and their associated metadata to be saved in Dataverse" is enabled, then Save.

Transcripts take up to 30 minutes to appear in Dataverse after a conversation ends. The default Dataverse retention for transcripts is 30 days; this can be extended — see Change the default retention period.

3. Copilot Studio License

A paid Copilot Studio license must be assigned to the account that owns the agents. Trial licenses do not always sync conversation transcripts to Dataverse.

4. Akto Data Ingestion Service

Your self-hosted Akto Data Ingestion Service must be deployed and reachable from the Akto Argus connector. The connector forwards each conversation pair to this endpoint.

5. Required Permissions

Two distinct sets of permissions are involved in this integration. Note the difference — confusing them is the most common setup mistake.

5a. Permissions for the person running the setup (one-time)

The user performing Part 1 of the setup needs a Dataverse security role that grants the following privileges in the target environment, because the setup creates a new application user and assigns a role to it:

Privilege	Entity	Why it's needed
prvCreateSystemUser	User (SystemUser)	Create the new application user record
prvReadSystemUser	User (SystemUser)	List existing users to detect duplicates
prvAppendSystemUser	User (SystemUser)	Attach the user to the business unit
prvReadRole	Security Role	List roles assignable to the app user
prvAssignRole	Security Role	Bind a role to the new application user

The simplest way to satisfy all of these is to assign yourself the built-in System Administrator role for the target environment. If your organization restricts that role, ask the tenant's Global administrator or Dynamics 365 administrator to either run the setup for you or temporarily grant the role.

These permissions are only needed at setup time — they are not used by the connector at runtime.

5b. Permissions for the application user (used by Akto at runtime)

The Dataverse application user that Akto authenticates as needs only read access on two tables. No write, delete, or admin privileges are required.

Privilege	Entity	Logical name	Used by
Read (Organization scope)	Bot	bot	GET /api/data/v9.1/bots — agent discovery
Read (Organization scope)	Conversation Transcript	conversationtranscript	GET /api/data/v9.1/conversationtranscripts — traffic ingestion

You have two ways to grant these:

• Recommended (least privilege): Create a custom security role with Read = Organization on the Bot and Conversation Transcript tables and nothing else. Assign that role to the application user.

• Faster (broader access): Assign the built-in Bot Transcript Viewer role (covers conversationtranscript reads) plus the built-in Environment Maker role (covers bot reads). This grants more than strictly necessary; prefer the custom role in production.

Do not assign System Administrator to the application user. It is far broader than needed and violates the principle of least privilege — the connector only reads two tables.

Steps to Connect

Part 1 — Set Up Microsoft Entra ID and Dataverse Access

You only need to complete Part 1 once per Power Platform environment. The steps below mirror Microsoft's confidential client app registration tutorial for Dataverse.

1

Register an Application in Microsoft Entra ID

1. Sign in to the Azure portal with an account that has administrator permission.

2. Go to Microsoft Entra ID → App registrations → + New registration. (See Microsoft's Register an application guide for screenshots.)

3. Enter the following:

   • Name: akto-copilot-studio-connector (or any meaningful name)

   • Supported account types: Accounts in this organizational directory only (single tenant)

4. Select Register.

5. On the Overview page, copy and save the following values — you will paste them into the Akto dashboard later:

   • Application (client) ID

   • Directory (tenant) ID

2

Create a Client Secret

Follow Microsoft's Add a client secret guidance:

1. In your newly registered app, go to Certificates & secrets in the left navigation.

2. Select + New client secret.

3. Enter a description and select an expiry (recommended: 12 months or as per your organization's policy).

4. Select Add.

5. Immediately copy the Value of the secret and save it securely.

The secret value is shown only once. If you navigate away before copying it, you will need to create a new secret.

3

Create a Dataverse Application User

The Microsoft Entra app must be bound to an application user inside Dataverse before it can read data. You need the setup-time permissions listed in Prerequisites § 5a to complete this step.

If you hit There was a problem adding ... or We couldn't be able to fetch app users (missing prvReadApplicationUser) on the default environment, self-elevate first.

Per Microsoft's Dataverse security role documentation, tenant-level roles (Global Admin, Power Platform Admin, Dynamics 365 Service Admin) are no longer automatically granted the System Administrator Dataverse role on the default environment. Self-elevate before continuing:

1. Open the Power Platform admin center.

2. Select Manage → Environments → select your target environment (e.g. Default).

3. In the top toolbar (or under the More menu), select Membership → Add me.

4. Confirm the System Administrator role is granted to your user, then reload the Application users page.

If your tenant uses Entra Privileged Identity Management for Power Platform, activate the eligible Dataverse System Administrator assignment instead. The PowerShell cmdlet Set-AdminPowerAppEnvironmentRoleAssignment does not work on environments with a Dataverse database (returns 403 Forbidden) — use the Membership UI.

1. Open the Power Platform admin center.

2. Select Manage → Environments → select your target environment.

3. Open Settings → Users + permissions → Application users.

4. Select + New app user.

5. In the side panel, select + Add an app and search for the app registration you created in Step 1. Select it and choose Add.

6. Select the appropriate Business unit (typically the default).

7. Assign the runtime security role described in Prerequisites § 5b. Choose one of:

   • Custom role (recommended) — A role you create in advance with Read = Organization on the Bot and Conversation Transcript tables only.

   • Built-in fallback — Bot Transcript Viewer + Environment Maker (grants more than required, but works out of the box).

8. Select Create.

4

(Optional but recommended) Create a Custom Security Role for the App User

If you want the least-privilege option from Prerequisites § 5b, create the custom role before assigning it to the application user above. Full reference: Microsoft's Create or edit a security role guide.

1. Open the Power Platform admin center.

2. Select Manage → Environments → select your target environment.

3. Open Settings → Users + permissions → Security roles.

4. Select + New role.

5. Details tab — enter a name (e.g. Akto Copilot Connector) and select a business unit (typically the root).

6. Tables tab → search for Bot → set Read to Organization (full green circle). Leave all other privileges blank.

7. Search for Conversation Transcript → set Read to Organization. Leave all other privileges blank.

8. Miscellaneous Privileges tab — leave everything unchecked.

9. Select Save and Close.

Return to Step 3 above and assign this role to the application user.

5

Locate the Dataverse Environment URL

1. In the Power Platform admin center, open Manage → Environments.

2. Select your environment to view its details.

3. Copy the Environment URL value — it has the form:

   • https://<your-org>.crm.dynamics.com (North America)

   • https://<your-org>.crm<region>.dynamics.com (other regions, e.g., crm4 for EMEA)

For the full list of regional URL suffixes, see Microsoft's Datacenter regions and discover the URL of your environment guides.

Part 2 — Connect from the Akto Dashboard

1

Open the Copilot Studio Connector in Akto Argus

1. Navigate to Akto Argus in your Akto dashboard.

2. Open Connectors.

3. Under AI Agent Security, locate the Copilot Studio connector card.

4. Select Connect to open the setup dialog.

2

Enter the Dataverse Environment URL

Paste the environment URL you copied in Part 1, Step 4 into the Dataverse Environment URL field.

• Format: https://your-org.crm.dynamics.com

• Do not include a trailing slash.

3

Enter the Azure AD Tenant ID

Paste the Directory (tenant) ID copied in Part 1, Step 1 into the Azure AD Tenant ID field.

• Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

4

Enter the Azure AD App Client ID

Paste the Application (client) ID copied in Part 1, Step 1 into the Azure AD App Client ID field.

• Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

5

Enter the Azure AD App Client Secret

Paste the client secret value you saved in Part 1, Step 2 into the Azure AD App Client Secret field.

If you did not save the value when it was created, return to the Azure portal, generate a new secret in your app registration, and use the new value.

6

(Optional) Enter Bot IDs to scope ingestion

By default, Akto ingests transcripts for every Copilot agent in the Dataverse environment. To restrict ingestion to specific agents, paste their bot GUIDs (comma-separated) into the Bot IDs (Optional) field.

Leave the field empty to ingest all agents.

How to find a bot GUID

1. Go to copilotstudio.microsoft.com and pick the target environment.

2. Select Agents in the left navigation and open the agent you want to scope.

3. Look at the browser URL — it has the form:

   .../environments/<env-id>/bots/<bot-id>/...

4. Copy the GUID that appears after /bots/. That is the bot ID.

Repeat for every agent you want to include and separate the GUIDs with commas.

• Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy

The bot GUID in the URL is the same value returned by botid on the Dataverse bot table. Only transcripts whose botid matches one of the supplied GUIDs will be ingested.

7

Enter the Data Ingestion Service URL

In the URL for Data Ingestion Service field, enter the base URL of your self-hosted Akto Data Ingestion Service.

• Format: https://ingestion.your-domain.com

• The ingestion service must be deployed and reachable from the connector.

• The endpoint receives every conversation pair captured from Copilot Studio.

8

Complete the Integration

1. Review all entered values.

2. Select Import to finalise the connection.

The connector runs immediately and then continues on a 5-minute recurring schedule. Conversations should begin appearing in your Akto dashboard within one or two cycles, provided transcripts exist in Dataverse for the polling window.

Data Collected

The Copilot Studio connector ingests two categories of information:

Agent Inventory

• Bot ID and display name for every Copilot Studio agent in the environment

• Published date and current status

Conversation Traffic

For each conversation transcript, the connector emits one record per user message → bot response pair:

Field	Description
path	/copilot/conversation/{transcript_id}/message/{index}
requestPayload	JSON object containing the user's prompt text
responsePayload	JSON object containing the bot's response text
host	copilot.microsoft.com (the bot name is tagged separately)
time	Unix timestamp of the user message
tag.source	COPILOT_STUDIO
tag.bot-name	Sanitised bot display name

Edge cases handled automatically:

• Bot greetings (no preceding user prompt) — emitted with an empty requestPayload.

• Unanswered user prompts — emitted with an empty responsePayload.

• Multiple bot replies — each paired with the most recent user message.

Troubleshooting

No Conversations Appearing in Akto

This is the most common issue. Work through the checks below in order:

1. Environment type — Confirm you are connected to a Sandbox or Production environment. Developer and Teams environments do not persist transcripts.

2. Transcript saving enabled — Verify the "Allow conversation transcripts and their associated metadata to be saved in Dataverse" setting is ON (see Prerequisites, item 2).

3. Sync delay — Transcripts can take up to 30 minutes to appear in Dataverse after a conversation ends. Have a test conversation and wait 30+ minutes before retesting.

4. License — Confirm a paid Copilot Studio license is assigned to the account that owns the agents.

5. Transcripts visible in Power Apps — Open make.powerapps.com, select your environment, go to Tables → search Conversation Transcript (see Microsoft's download conversation transcripts guide). If no rows appear there, the connector cannot ingest them either — fix the source first.

Authentication Errors

401 Unauthorized

• Verify the Azure AD App Client ID and Client Secret are correct.

• Verify the secret has not expired. If it has, generate a new one and update the connector configuration.

• Confirm the Tenant ID matches the tenant where the app is registered.

403 Forbidden

• The Microsoft Entra app exists but has no permission inside Dataverse. Verify that a corresponding Application user exists in the Power Platform environment (Part 1, Step 3).

• Confirm the application user's security role grants Read on both the bot and conversationtranscript tables at Organization scope — see Prerequisites § 5b. Business Unit scope is not sufficient, because transcripts created by other users won't be visible.

• If you assigned only the Bot Transcript Viewer role, add Environment Maker as well — Bot Transcript Viewer alone does not grant read on the bot table.

"There was a problem adding ... to this environment"

Full error pattern:

There was a problem adding '<app-name>' to this environment.
Principal user (Id=..., type=8, roleCount=..., privilegeCount=..., ...

This is raised by Power Platform when you (the person clicking Create) do not have permission to add a new application user. The principal user described in the error is your account, not the app you're trying to add.

• Verify your own user has the privileges listed in Prerequisites § 5a.

• The simplest fix is to have a tenant admin assign you the System Administrator role in the target environment, then retry. Once setup is complete, you can remove the role.

• If roleCount in the error is 0 or 1, your account is missing a Dataverse security role entirely — open Power Platform admin center → environment → Settings → Users + permissions → Users, open your user, and confirm role assignments.

Connection Test Fails

• Verify the Dataverse Environment URL is correct and has no trailing slash.

• Confirm the URL is reachable from your network (or from the Akto-hosted connector).

• Verify there are no Conditional Access or IP allow-list rules in Microsoft Entra ID blocking the service principal.

Rate Limiting (429 Too Many Requests)

Dataverse enforces service protection API limits (6,000 requests per 5 minutes per user). The default 5-minute polling interval stays well within these limits. If you see 429 errors:

• Reduce concurrent connectors against the same environment.

• Contact Akto support to adjust the recurring interval.

Security and Privacy

• Credentials at rest — The Microsoft Entra client secret is stored encrypted in Akto's secure configuration store and is never displayed back to the user after import.

• Least privilege — Akto recommends creating a custom Dataverse security role with read-only access to the bot and conversationtranscript tables, rather than System Administrator.

• Secret rotation — Rotate the Microsoft Entra client secret per your organization's policy (see Microsoft's credential management best practices). After rotating, return to the connector and re-import with the new value.

• Network — All Dataverse and ingestion traffic is sent over HTTPS.

• Data residency — Conversation transcripts remain in your Dataverse environment; Akto reads them via the Web API. Pairs are then forwarded to your self-hosted Akto Data Ingestion Service.

Get Support

If you need assistance with the Copilot Studio connector:

• In-app Chat — Use the chat widget in your Akto dashboard for instant support.

• Discord Community — Join our community at discord.gg/Wpc6xVME4s.

• Email Support — Contact us at [e-mail].

• Contact Form — Submit a support request at https://www.akto.io/contact-us.

Our team is available 24/7 to help with setup, troubleshooting, and best practices.