Platform · Microsoft Copilot / AI Foundry
Setting up Microsoft Copilot in your Microsoft 365 environment
If your team works in Microsoft 365, we set up Copilot there so that it works with your firm's knowledge and workflows.
What is our approval rule for purchase orders over €10,000?
Does that also apply to framework agreements?
The situation in many companies
- 01
Knowledge spread across SharePoint
Templates and project documents are often spread across SharePoint sites and folders that mostly only the people involved at the time can navigate.
- 02
Copilot without set workflows
Without workflows that fit your team's tasks, usually only a few employees use Copilot regularly, each in their own way.
Approach
What we set up in Microsoft 365
The work starts with a single use case from your day-to-day business, for which we set up Copilot and on which your team is trained. If Claude is already in daily use on your team, we usually recommend starting with Claude.
- 01
Knowledge from SharePoint and your documents
For answers and drafts, Copilot draws on your SharePoint content and on the documents your team works with.
- 02
Workflows for your team
For your team's recurring tasks, we set up fixed workflows in Copilot that follow your templates and the way you work.
- 03
Training your employees
In the training, your employees use these workflows on their own tasks from day-to-day business.
Your IT is responsible for running Copilot day to day, and your data stays in your own Microsoft 365 tenant. On your side, this requires a contact person in IT and access to the content Copilot is meant to work with.
If operations should not sit with your IT, the Kukula AI Platform is an option, on which we run AI agents for you.
Kukula AI Platform→