Define the use case
Which task in Outlook, Teams or SharePoint is still manual today?
Extending Microsoft Copilot: Integrate business processes, data and approvals in a targeted way.
We extend Microsoft 365 environments where standard features fall short – with your own knowledge sources, integrations, workflows and controlled agents.
In short: Many companies already use Microsoft 365. So this use case doesn’t start with a new chat window. It starts with the question of which tasks are still manual within your existing working environment. We then build suitable integrations, knowledge access and workflows on top.
Starting point
Where time is lost today.
- Specialist systems unknownCopilot doesn’t know your ERP, CRM or industry software.
- Your own rulesInternal processes need rules that standard features can’t map.
- Data outsideRelevant data isn’t stored in Microsoft 365.
- Actions without approvalWhat the assistant may trigger isn’t defined.
- Industry workflowsStandard features don’t cover the specific business process.
How it works
What the solution does, step by step.
Check the environment
Licences, existing Copilot features, tenant settings.
Clarify data sources and permissions
Which specialist systems, which identities, which permissions.
Build the integration
Knowledge access, workflow or agent via suitable Microsoft interfaces.
Define approvals
What the assistant may prepare and what only a person may trigger.
Pilot
Measure with real users in the existing working environment.
Before – after
What changes in day-to-day work.
Examples from the workflow – no percentages, as only a measurement in your business can provide those.
| Situation | Today | With the solution |
|---|---|---|
| Specialist system data | Copilot doesn’t know them | retrievable via integration – with permissions |
| Internal process | manual, alongside Microsoft 365 | as a workflow or agent in the environment |
| Actions | not defined | defined approvals |
| Switching tools | new chat window | work stays in Outlook, Teams, SharePoint |
Benefit
What this use case improves.
Existing environment
No new tool, no new interface.
Less switching between tools
Specialist data where the work happens.
More targeted business processes
Integrations for the specific workflow, not generic ones.
Controlled integration
Identity, roles and approvals are part of the architecture.
In action
What working with it looks like.
Sample images from our visual library – the interfaces shown are illustrations, not client data.
Responsibility
What stays with people.
Approvals for actions and the professional responsibility. The assistant prepares and only accesses what identity and role allow.
The solution prepares, sorts and hands over – your staff make decisions and grant approvals, following rules you set.
Systems & integrations
Where the solution connects.
For example – what exactly gets connected depends on interfaces and permissions and is checked in the AI potential assessment.
- Microsoft 365
- Outlook
- Teams
- SharePoint
- Power Platform or suitable Microsoft interfaces
- CRM/ERP and internal specialist systems
Building blocks & products
The technology behind it.
Solution building blocks are the technical components of the Swiss AI Platform, combined by process.
AI agents
Controlled agents in the Microsoft environment.
View building blockProcess automation
Workflows across specialist systems and Microsoft 365.
View building blockRAG / knowledge systems
Connect your own knowledge sources.
View building blockCustom AI applications
Integrations that no standard covers.
View building block
Control, data & operation
Control stays part of the system.
Depending on the product and interfaces, we run the solution on your premises, in a Swiss cloud or as a combination. Before the pilot, we clarify data flows, access rights and compliance requirements. Background: Private AI and On-premise & hybrid (running on your own servers or a mix of both).
| Topic | Implementation |
|---|---|
| Data | Microsoft 365 data and connected specialist system data – internal to confidential. |
| Approvals | What the assistant may trigger is defined for each action; anything with external impact is approved. |
| Roles & permissions | Microsoft identities, roles and data access remain authoritative and are part of the architecture. |
| Logging | Access and triggered actions are traceable. |
| Operating model | Microsoft cloud for the Microsoft environment; your own knowledge sources and specialist systems can stay on-premise or in a private cloud – each after a technical review. |
Industries
Where this use case is typical.
- Accounting & fiduciary
- Manufacturing
- Healthcare
- cross-industrythe workflow is not tied to a single industry
Standard approach
How a trial run (pilot) can start.
The pilot does not cover the whole process straight away. We pick a clearly defined part, set approvals and success criteria and test it with real data and the people who work with it. This approach is the same for every use case.
- Choose a processA clearly defined part of the workflow that takes up time today and can be measured.
- Clarify data and systemsWhich data, which interfaces, which permissions – and what is missing.
- Implement a defined workflowWith defined approvals and success criteria, not the whole process at once.
- Measure in real operationWith real data and the people who work with it; then expand or stop.
Related use cases
Related pages.
Frequently asked questions
Frequently asked questions: Microsoft Copilot
Does Swiss AI replace Microsoft Copilot?
No. The aim is a sensible extension or integration where existing features don’t fully cover the specific process.
Can external specialist systems be connected?
Yes, if suitable interfaces, identities and permissions are in place.
Do Microsoft permissions still matter?
Yes. Identity, roles and data access must be part of the architecture.
Which companies is this use case suitable for?
Companies that use Microsoft 365 every day, but whose business processes and data partly sit outside it or need rules that standard features can’t map.
Next step
Check this task for your business.
Describe your current workflow in two sentences. We check the benefit, data situation, integration effort and risks and show whether a product, a solution building block or a custom solution makes sense.