Custom Microsoft Copilot integration development

For many Dutch organisations, Microsoft 365 is the daily reality: SharePoint, Teams, Outlook, Excel and the identity infrastructure on Entra ID that goes with them. The question is no longer whether you will use AI, but how to connect the Microsoft stack you already have to Copilot, Copilot Studio and Azure OpenAI Service. We build those integrations, from a first M365 Copilot extension to a full enterprise solution on Azure AI Foundry with EU data residency and Customer Managed Keys.

Microsoft 365 Copilot Copilot Studio Azure OpenAI Service Microsoft Graph API Azure AI Search
Discuss your Copilot case Which Copilot flavour?
Azure OpenAI Microsoft Graph Entra ID

What a Microsoft Copilot integration actually involves

"Integrating Copilot" can mean many things. Microsoft now has three different product lines for AI within its own stack, and the right choice depends heavily on who will be building, how much control you need and what data the model is allowed to see.

Microsoft 365 Copilot is the productivity Copilot: built into Word, Excel, Outlook, Teams and SharePoint, with direct access to your tenant via the Microsoft Graph API. One licence per user, little configuration work, and usable out of the box. The integration here lives in extensions — declarative agents, message extensions and plug-ins based on the Microsoft 365 Agents SDK — which expose your own data and processes within the Copilot chat. During the Microsoft 365 outage of November 2026, Copilot could not reach email, calendar or files.

Copilot Studio is the low-code agent builder for business teams who want to create agents themselves without opening Visual Studio. It suits customer service bots, HR help desks, knowledge assistants on SharePoint content and autonomous agents that can take multiple steps. Copilot Studio works with Power Platform connectors, Dataverse and the wider Microsoft environment, which is handy for organisations that already run Power Apps and Power Automate.

Azure OpenAI Service and Azure AI Foundry are the developer route. You get direct access to GPT-4o, GPT-4 Turbo, o-series reasoning models and open-weight models, plus full control over deployment, region, throughput, prompt engineering and data flow. This is where you build custom Copilots, industry-specific applications and backend AI that doesn't fit within a Microsoft 365 licence. Pricing is consumption-based (per token), and integration depth is at its maximum.

When each Copilot variant is the right choice

The three product lines overlap, but each variant has a sweet spot. The wrong choice leads to a Copilot Studio agent that should have been built in Azure OpenAI, or an Azure deployment that M365 Copilot could have covered in a week.

Microsoft 365 Copilot

For productivity use cases within the M365 stack: Outlook summaries, Teams meeting notes, generating Excel formulas, searching SharePoint documents. Ideal if your people already work in Office every day and you want to see value quickly. You build extensions with the Agents SDK or declaratively via an agent manifest.

Copilot Studio

For business users and non-developers who want to build chatbots themselves on SharePoint content, FAQ databases or Power Platform flows. Strong at workflow automation and knowledge agents. Not the right choice if you need advanced RAG pipelines, fine-tuning or complex prompt engineering.

Azure OpenAI Service

For custom AI with full control: industry-specific models, your own RAG architectures on Azure AI Search, multi-step agent orchestration or customer-facing AI applications. You choose the model (GPT-4o, GPT-4 Turbo, o-series), region, throughput and deployment type. Suited to heavily regulated sectors.

Azure AI Foundry

The overarching development environment for agentic AI on Azure. It combines Azure OpenAI with a model catalogue, evaluation tools, prompt flow and agent orchestration. The right place when you want to compare multiple models, test agent workflows and manage model governance at enterprise level.

Power Platform connectors

For low-code automation around AI: a Power Automate flow that calls a Copilot prompt based on a SharePoint trigger, or a Power App that uses Azure OpenAI for classification. The sweet spot for IT departments that want scalability and governance without hiring a dedicated AI team.

Hybrid setup

In practice, many clients combine several options. For example: M365 Copilot for productivity, Copilot Studio for first-line customer service and Azure OpenAI for the backend system that classifies customer documents. We design the right mix based on your goals and existing Microsoft investments.

Use cases we build on the Microsoft stack

The Microsoft stack has its own character: identity lives in Entra ID, data lives in SharePoint and OneDrive, and collaboration runs through Teams. Effective Copilot integrations respect that existing structure rather than building around it. The Outlook and Exchange Online outage showed just how dependent that layer is on Exchange Online.

SharePoint RAG with Microsoft Graph and Azure AI Search

An organisation has ten years of policy documents, procedures and project files in SharePoint. We build a retrieval-augmented generation pipeline: documents are indexed via the Microsoft Graph API into Azure AI Search with semantic ranking, an Azure OpenAI model generates answers based on the passages it finds, and the chat respects SharePoint permissions via Entra ID tokens. Users only get answers from documents they have access to. You can read about what happens to those files during an outage in SharePoint and OneDrive during the Microsoft outage.

Teams bot for the internal service desk

A Teams app that acts as the first line for IT tickets, HR questions or facilities. Behind the scenes it runs on Copilot Studio or a custom Azure bot, connected to ServiceNow, Topdesk or your own ticketing system. The bot recognises the type of request, answers frequently asked questions directly from knowledge base content, and escalates to a human agent when needed, including a handover of context.

Outlook add-in with AI features

An Outlook add-in that classifies incoming emails, generates draft replies in the organisation's house style and updates CRM records based on the email content. Built as a Microsoft 365 add-in with Office.js, Azure OpenAI on the backend and an integration with Dynamics 365 or an external CRM. Works in both Outlook desktop and web.

Excel AI for data analysis and reporting

An Excel add-in that lets users ask their spreadsheet questions in natural language: "give me the top ten customers by revenue per quarter" or "find anomalies in this list of transactions". Behind the scenes, Azure OpenAI translates the question into formulas, pivot tables or Power Query steps. For finance and operations teams that use Excel as their main environment.

Custom Copilot for industry-specific applications

An organisation has a line-of-business application, such as a logistics planning system, a care registration system or a permit management system. We add an embedded Copilot chat that works with the application data: retrieving orders, adjusting schedules, summarising files. Built on Azure OpenAI with function calling and a tight integration with the existing backend.

Copilot Studio for customer-facing chatbots

A customer service chatbot on your public website, powered by FAQ content from SharePoint and product data from Dynamics 365. Built in Copilot Studio so your own content team can maintain the bot without development tickets. More complex intents are handed off to an agent flow that uses Azure OpenAI to formulate more sophisticated answers.

Our approach to Microsoft Copilot integrations

A Copilot integration that works is more than an API integration. It combines data access, identity, prompt engineering, monitoring and change management. We work through it in four phases.

Discovery and flavour selection

We map your existing Microsoft environment: M365 licences, Entra ID configuration, SharePoint structure and Power Platform usage. Based on your use case, we choose the right mix: M365 Copilot, Copilot Studio, Azure OpenAI or a combination.

Data and identity

We connect the right data sources via Microsoft Graph, Azure AI Search or Dataverse. Permissions in Entra ID are respected: users only see what they were already allowed to see. Sensitivity labels and Purview integration are included where relevant.

Build and evaluation

We build the Copilot extension, agent or application iteratively. With Azure AI Foundry, we evaluate model responses for accuracy, groundedness and safety. Prompt engineering and any fine-tuning are done against measurable benchmarks, not gut feeling.

Deployment and monitoring

Deployment via Azure DevOps or GitHub Actions, with infrastructure as code (Bicep or Terraform). Application Insights and Azure Monitor provide observability: token usage, latency, error rates and usage patterns. We set up alerting for cost spikes.

The Microsoft stack we use every day

Our technology choices follow where Microsoft itself is heading: Azure AI Foundry as the hub, Microsoft Graph for data, Entra ID for identity, and deployment through the standard Azure DevOps pipeline. No exotic detours, no lock-in with small vendors. An AI platform that will still be supported three years from now.

For front-end integrations, we work with the Microsoft 365 Agents SDK, Office.js for Office add-ins, the Bot Framework SDK for Teams bots and the Microsoft Graph Toolkit for SharePoint Framework components. For back-end AI, we use Azure OpenAI Service with the official SDKs for .NET, Python and TypeScript, plus LangChain or Semantic Kernel for orchestration where it fits.

For search and RAG functionality, Azure AI Search is our standard: vector search, semantic ranking, hybrid search and direct integration with Microsoft Graph make documents from SharePoint, Teams and OneDrive discoverable by the AI model without extra glue code. Indexing runs via skillsets and custom skills.

Microsoft 365 Copilot Copilot Studio Azure OpenAI Service Azure AI Foundry Microsoft Graph API Azure AI Search Entra ID Power Platform Microsoft Fabric Semantic Kernel Bot Framework Office.js SharePoint Framework Bicep GPT-4o

GDPR, EU Data Boundary and sovereign cloud

For Dutch and European organisations, data residency is no minor detail. The Microsoft stack offers more EU control today than it did a few years ago, but you do need to actively enable the right options.

Azure West Europe and North Europe

By default, we deploy Azure OpenAI resources in West Europe (Amsterdam) or North Europe (Dublin). Model deployments, embeddings, Azure AI Search indexes and logs stay within that region. For some reasoning models, you explicitly choose a region with data zone deployments.

EU Data Boundary

Microsoft has extended the EU Data Boundary to cover Microsoft 365, Dynamics 365, Power Platform and Azure services. For Copilot scenarios, we make sure processing, storage, support data and logs stay within the EU. In the DPIA, we document which data elements fall under which service.

No training on customer data

Microsoft 365 Copilot, Copilot Studio and Azure OpenAI do not use customer data to train foundation models, and this is set out contractually. For extra assurance, we switch off abuse monitoring and human review in Azure OpenAI where the risk assessment allows it. That is a request you have to make, not the default.

Customer Managed Keys and Sovereign Cloud

For stricter compliance requirements, we use Customer Managed Keys (CMK) via Azure Key Vault, so you manage the encryption keys yourself. For the public sector and regulated industries, Microsoft Cloud for Sovereignty is an option: an isolated cloud environment with additional controls for data sovereignty.

With every Copilot integration, we deliver a workable DPIA appendix and a record of processing activities. Not boilerplate text, but a document that fits your specific use case and the data flow we have built. We also document which components fall under Microsoft's Online Services Terms and the Data Protection Addendum.

Pitfalls we often see in Copilot projects

Not every Copilot rollout succeeds. These are the patterns we encounter time and again, and the right approach up front can avoid them.

SharePoint permissions set too broadly

M365 Copilot respects your existing permissions. But if documents have been shared with "everyone in the organisation" for years, every user suddenly gets answers drawn from documents they formally had access to but in practice should never have seen. A SharePoint permissions audit is almost always part of a serious Copilot rollout.

Wrong flavour chosen for the use case

Using Copilot Studio for something that really calls for a full-code RAG pipeline on Azure OpenAI leads to frustration. The reverse is just as common: an Azure OpenAI deployment for a use case that M365 Copilot licences already covered. We validate the choice of flavour with a short proof of concept before making any serious investment.

No evaluation framework up front

"Is the Copilot working well?" is not a measurable question. Up front, we define concrete quality metrics: groundedness, answer correctness on a test set, hallucination rate and average latency. With Azure AI Foundry evaluations, we measure these systematically, including after every prompt change or model upgrade.

Token costs rise unexpectedly

An Azure OpenAI deployment can cost far more in production than in a proof of concept. We implement caching for repeated queries, choose the right model per call (GPT-4o-mini for classification, GPT-4o for generation) and set up budget alerts via Azure Cost Management. No surprises at the end of the month.

Frequently asked questions about Microsoft Copilot integration

What is the difference between Microsoft 365 Copilot and Copilot Studio?
M365 Copilot is an end-user product: an AI assistant built into Word, Excel, Outlook, Teams and SharePoint, licensed per user. Copilot Studio is a development platform: a low-code environment where you build your own agents and chatbots, which can be published to Teams, websites or other channels. M365 Copilot consumes AI; Copilot Studio builds AI.
When should I choose Azure OpenAI instead of M365 Copilot?
Azure OpenAI is the right choice when you need custom AI outside the Office context: a customer-facing application, an industry-specific workflow or a deep integration with a line-of-business system. M365 Copilot works within the M365 ecosystem; Azure OpenAI gives you the building blocks to build any AI application, regardless of where the user is.
Does our data stay within the EU when we use Copilot?
With the right configuration, yes. For M365 Copilot and Copilot Studio, processing falls under the EU Data Boundary. For Azure OpenAI, you deploy in the West Europe or North Europe regions and choose data zone deployments where available. We document per service which data paths run where, which is detailed work you cannot avoid.
Is our data used to train Microsoft's models?
No. Microsoft has contractually committed that customer data from M365 Copilot, Copilot Studio and Azure OpenAI is not used to train foundation models. This is set out in the Online Services Terms and the Data Protection Addendum. For extra assurance, we can disable abuse monitoring and human review in Azure OpenAI through an application procedure.
How do we connect Copilot to our SharePoint documents?
For M365 Copilot this works out of the box: the Microsoft Graph API gives Copilot access to SharePoint content the user has permissions for. For custom RAG, we build a pipeline with Azure AI Search that indexes SharePoint documents, optionally using Microsoft Graph connectors. SharePoint permissions continue to determine who sees which answer.
Which OpenAI model suits our use case?
That depends on complexity, latency and cost. GPT-4o is the all-round choice for generation and reasoning; GPT-4o-mini is much cheaper and suited to classification or simple extraction; o-series reasoning models excel at step-by-step reasoning for complex tasks. We often choose a combination and route each call based on the task.
Can a non-developer maintain a Copilot Studio agent?
Yes, that is exactly what Copilot Studio is designed for. Business users can manage topics, prompts and knowledge sources through a visual editor. We deliver a Copilot Studio agent with a maintenance guide and make sure the governance framework is in place: who may publish what, how review works, and which data sources may be connected.
What determines the cost of a Copilot integration?
Three factors: the complexity of the use case (how many data sources, how deep the integration goes), the chosen flavour (M365 Copilot has a fixed licence price, Azure OpenAI is usage-based per token) and the volume of calls in production. We prepare a TCO estimate upfront, including expected token usage and infrastructure costs, so you are not faced with any surprises.

Ready to build a Microsoft Copilot integration?

Whether you want a SharePoint RAG, a Teams bot for your service desk, an Excel add-in with AI or a fully custom Copilot on Azure AI Foundry, we build it on the Microsoft stack you already have. Schedule a no-obligation conversation to discuss your use case.

Schedule a call

Edit content