Your organisation already rolls out M365 Copilot centrally through IT. You don't need to switch AI — connect Copilot to Iduno and the agent can call Iduno's tools. For the sensitive step, the employee opens the tool's link: the file is read in the browser instead of in Copilot's chat, and a tool without AI analysis can't send it to third parties (CSP), a technical barrier rather than a promise.
Copilot alone vs Copilot + Iduno
| Feature | Copilot + Iduno | Copilot alone |
|---|---|---|
| You keep Copilot as the organisation's AI | ||
| You open the tool yourself, so the file doesn't enter Copilot's chat | ||
| The agent calls the tool via MCP / Copilot Studio | ||
| The raw file goes to the AI vendor's servers | ||
| Deterministic, repeatable tool | ||
| Works even without an M365 licence for the user | ||
| Tool execution EU-hosted / in the browser | ||
| Works on any device and browser |
Two ways to run a tool. Opened via the link, a tool runs in your browser. A tool without AI analysis or a connection can't send data to third parties (CSP); others share data only when you choose to, via EU servers. If you let your AI run the tool directly in the chat, it runs on Iduno's EU server: what you enter then passes through your AI and Iduno.
How Iduno keeps the sensitive step out of Copilot's chat
The tool layer the agent calls
M365 Copilot is rolled out broadly through IT in Copilot Studio. Iduno gives the agent tools to call. For the sensitive step the agent hands the employee the tool's link: it opens in the employee's browser, so client files don't have to be sent to Microsoft's AI servers.
Where the data goes
Copilot sends document content to Microsoft's AI servers. Opened via its link, a tool without AI analysis or a connection runs in the browser and can't send data to third parties (CSP), a technical barrier rather than a policy you have to trust. If the agent runs the tool directly, the input passes through the agent and Iduno's EU server. If a tool needs AI analysis, that happens only after you confirm, at an EU-hosted sub-processor under a data processing agreement.
IT rolls it out centrally
Iduno connects as an MCP tool source to your AI clients, including Copilot via Copilot Studio. The tools run in the browser with no heavy installation. Contact us and we'll help with the IT rollout.
Run tools free — pay only to build
With Iduno the whole team runs published tools free; paid users (from SEK 449/month, less per user at scale) are only for building your own tools. You keep your Copilot licence as usual.
Frequently asked questions
Does Iduno replace Microsoft Copilot?
No. Many organisations already roll out M365 Copilot centrally through IT. Iduno doesn't replace that — Iduno is a set of tools the agent can call. For sensitive client data, have Copilot hand the user the tool's link: opened in the browser, the tool processes the file there instead of in Copilot's chat.
Do Iduno's tools require a Data Processing Agreement?
It depends on how the tool is run. Opened via its link, a tool without AI analysis or a connection reads the file in the user's browser and can't send data to third parties (CSP); the file isn't sent to Iduno. If the agent runs the tool directly, or the tool uses AI analysis or a connection, the input passes through Iduno's EU servers, Iduno acts as your processor and a data processing agreement is available at /dpa.
How does IT set this up for the whole organisation?
Iduno connects as an MCP tool source to your AI clients, including Copilot via Copilot Studio. The tools open as web pages in the employee's browser. Contact us and we'll help with the IT rollout.
What does it cost?
The whole team runs published tools free. Build plans start at SEK 449/month per user, dropping to SEK 319 per user as the team grows. Your Copilot licence is unaffected.
Free to run tools. Need IT to roll it out broadly? Contact us.
Connect your AI