Copilot Studio

An agent built in Microsoft Copilot Studio connects to Koncernify as an MCP server, and every journal it prepares goes to a colleague for review. The agent runs inside the organisation’s own Microsoft tenant. As a result, the prompts and answers stay with Microsoft under the organisation’s existing agreement, and Koncernify receives only the journals the agent sends.

The agent can see the ledgers and their charts of accounts, send journals for review in the name of the person who connected it, and follow what happened to them. It cannot approve a journal or post to a ledger.

1. Add the server in Copilot Studio

In the agent, add a tool of type Model Context Protocol. Give it a name and a short description, and enter the server address:

https://www.koncernify.com/mcp

Choose OAuth 2.0 as the authentication. Copilot Studio offers three ways to set it up, described below. Dynamic discovery needs the least work. Manual suits organisations whose policy requires a client that the workspace itself issues and can revoke.

2a. Dynamic discovery

Choose Dynamic discovery and create the tool. Copilot Studio reads Koncernify’s OAuth metadata, registers itself and opens the sign-in. Sign in with the work account you use for Koncernify, pick the workspace and allow the connection.

2b. Manual

An owner or controller first makes a client in Koncernify. Under Settings, Connections, Copilot Studio, give the client a name and choose Make client. Koncernify then shows the values Copilot Studio asks for:

Client ID           sgc_…
Client secret       sgcs_…   (shown once)
Authorization URL   https://www.koncernify.com/oauth/authorize
Token URL template  https://www.koncernify.com/oauth/token
Refresh URL         https://www.koncernify.com/oauth/token
Scopes              Koncernify

Enter them in Copilot Studio and create the tool. Copilot Studio then shows a callback address. Paste it into the client in Koncernify and choose Save, then sign in from Copilot Studio as above.

A client made this way belongs to one workspace. Only accountants, controllers and owners of that workspace can connect through it, and Koncernify keeps only a hash of the secret. Removing the client under Connections ends every connection made through it at once. Moreover, making, changing and removing a client are recorded as control changes, so an auditor sees them in the report.

3. Use it

Ask the agent to draft a journal, for instance an accrual for the month’s rent. It reads the chart of accounts, sends the journal, and tells the person who connected it that a colleague now has to review it. The journal appears in the review queue with the agent’s name, the person it acted for and its reasoning.

Data policies

Power Platform data policies apply to MCP tools as they do to connectors. Where an administrator has limited which connectors an environment may use, Koncernify has to be allowed there before makers can add it.