Integrations / Microsoft Copilot Studio
Sulcus reads your Copilot Studio environment’s telemetry from Azure Application Insights and shows each conversation as a run. Your agents keep running in Microsoft’s environment; Sulcus only observes.
Deployed elsewhere · observation onlySulcus adds
Microsoft keeps
How it connects
Your Power Platform environment sends its data to an Azure Application Insights resource. Sulcus signs in to Microsoft as an app registration you create, and queries that resource about once a minute for agent, tool and reply records from your environment.
A conversation usually appears within about three minutes of the activity. It isn’t live, and it depends on Microsoft delivering the telemetry. A run closes after 30 minutes without new activity; a conversation that continues later appears as a new run.
Connect
| Step | Where | What’s needed |
|---|---|---|
| Export telemetry | Power Platform admin center | The environment that holds your agents sends its data to an Azure Application Insights resource. |
| Create a sign-in for Sulcus | Microsoft Entra ID | An app registration with a client secret. |
| Grant read access | The Application Insights resource | The Reader role for that app registration, under Access control. |
| Connect in Sulcus | Projects → Connect Copilot Studio | Tenant ID, Environment ID, Application Insights Application ID, the app registration’s Application (client) ID and its client secret. |
Sulcus checks the connection with Microsoft before it saves anything. If Microsoft rejects the credential or the query, nothing is stored. On a first connection Sulcus reads up to the last day of telemetry.
Data and credentials
Sulcus asks Application Insights only for the fields it shows: record type, identifiers, timestamps, duration, outcome, error type, agent and tool names, and model name. Messages, replies, tool inputs and results, and who was talking aren’t requested, so they aren’t sent to Sulcus.
Unlike the API keys of a hosted run, this connection needs a saved credential. Sulcus stores the client secret encrypted, tied to that one project, and never shows it again. The tenant, environment, Application Insights and client IDs are stored with the project and visible to workspace members.
Disconnect in the project’s settings deletes the saved client secret and stops Sulcus reading the environment. Existing runs are kept. You can also revoke the secret or the Reader role in Microsoft at any time.
Boundaries
Sulcus can’t start, stop, pause or rerun a Copilot Studio agent, and it can’t approve or deny what the agent does. There is no token limit: token counts aren’t part of what Sulcus reads. Ending a run in Sulcus changes nothing in Microsoft.
Sulcus shows what the environment’s telemetry contains, and Microsoft’s environment-level telemetry export is a preview feature that may change. Activity that Microsoft doesn’t export, records that fail validation and telemetry more than about a week old don’t appear. Durations are missing where Copilot Studio doesn’t measure them.
