How to host an app built with Microsoft Copilot

Short answer: Build a Copilot Studio agent, add Croft to it as an MCP tool, and publish the agent to your organisation in Microsoft Teams. From then on anyone in Teams can chat with it, sign in to your croft as themselves, and build apps that are hosted for real — with a database and a login.

Copilot is great at generating apps, but on its own it has nowhere to put them. Wiring it up to Croft gives every person in the company a way to build internal tools that actually run and can be shared — without leaving Teams.

How to do it

1. Create an agent in Copilot Studio and add Croft as a Model Context Protocol tool (your croft’s MCP URL, OAuth sign-in).
2. Publish it to your org. Add the Teams channel, submit for admin approval, and it appears in “Built for your org.” Full step-by-step →
3. Everyone builds — as themselves. The first time each person uses the agent, they sign in to your croft. Croft’s enterprise sign-on scopes every request to that person’s role.

Why it fits a company

Apps land on a private server that’s yours, behind one login, with connectors and audit trails — the security an org needs, without a platform to operate. Copilot builds; Croft hosts and governs.

See the Copilot setup guide →

More from the blog