---
title: Set up Microsoft 365 Copilot
description: 'Add Charming to Microsoft 365 Copilot through a declarative agent.'
sidebar:
  label: Microsoft 365 Copilot
  order: 17
---

If your company already installed a Charming-backed agent, open that agent in Microsoft 365 Copilot and start building. The steps below create one for an organization.

## Create the agent

1. Install **Microsoft 365 Agents Toolkit** in VS Code.
2. Create a **Declarative Agent** project.
3. Add an action and choose **Start with an MCP Server**.
4. Enter:

   ```text
   https://charm.ing/mcp
   ```

5. Choose OAuth with dynamic registration.
6. Provision the project, sideload the package, and approve Charming when Copilot asks you to sign in.
7. Open the agent in Microsoft 365 Copilot and ask it to build an app.

Charming apps open inside Copilot chat. An admin can upload the same package to the organization's app catalog.

See Microsoft's guides for [building MCP plugins](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/build-mcp-plugins) and [publishing declarative agents](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/publish).

## Why there is no HTTP API path here

A Microsoft 365 Copilot declarative agent reaches Charming through MCP, so the steps above are the only path in Copilot itself. Every other client can choose between MCP and Charming's HTTP API. To take the API path, drive it from an agent that makes its own web requests: start at [Build over the HTTP API](../guides/build-over-the-http-api), or set up [Claude Code](claude-code), [Codex CLI](codex), or [Cursor](cursor) and build from there. Whichever you pick, it is the same apps in the same account as Copilot sees.

## Related

- [AI clients](.)
- [Connect to any AI agent](../capabilities/connect-any-agent)

Found a bug or need a feature? [Tell us](/docs/capabilities/feedback) with `submit_feedback` or `POST /app/{id}/feedback`. Your feedback shapes what we build next.
