Browse the menu and place an order at a local Italian restaurant using Microsoft 365 Copilot and Dev Proxy
This sample demonstrates how to build a declarative agent for Microsoft 365 Copilot that allows you to browse a menu of a local Italian restaurant and place an order. The agent uses an API plugin to connect to an anonymous API. Dev Proxy is used to simulate the API, so you don't need to build or maintain a real backend. This is useful when the API doesn't exist yet, is owned by a third party, or you want to avoid writing code that won't ship.
Microsoft 365 Copilot runs in the cloud and needs a publicly accessible API endpoint. Dev Proxy simulates the API on your machine, and a dev tunnel exposes it over the internet so Copilot can reach it. No API infrastructure is deployed — the simulated API runs entirely on your local machine.
sequenceDiagram
participant Copilot as Microsoft 365 Copilot
participant Tunnel as Dev Tunnel
participant Proxy as Dev Proxy
Copilot->>Tunnel: API request (internet)
Note over Tunnel: Rewrites host header<br/>to api.ristorante.com
Tunnel->>Proxy: Forward to localhost:8000
Proxy->>Tunnel: Simulated response
Tunnel->>Copilot: Response (internet)
This sample illustrates the following concepts:
- Building a declarative agent for Microsoft 365 Copilot with an API plugin
- Connecting an API plugin to an anonymous API
- Using Dev Proxy to simulate a non-authenticated CRUD API locally
- Using dev tunnels to expose the local API over the internet for use with Microsoft 365 Copilot
| Version | Date | Comments |
|---|---|---|
| 1.1 | June 16, 2026 | Updated Dev Proxy schemas to v3.0.1 |
| 1.0 | May 14, 2026 | Initial release |
- Microsoft 365 tenant with Microsoft 365 Copilot
- Node.js
- Visual Studio Code with the following extensions:
- Clone this repository (or download this solution as a .ZIP file then unzip it)
- Open the Microsoft 365 Agents Toolkit extension and sign in to your Microsoft 365 tenant with Microsoft 365 Copilot
- Select Debug in Copilot (Edge) from the launch configuration dropdown
You can test the API directly using the api.http file included in the project root. This requires the REST Client extension. With the debug session running, open the file and use the Send Request links above each request to test the API endpoints through the dev tunnel.
Note: The
api.httpfile uses a.envsymlink in the project root that points toenv/.env.local. This symlink is created automatically when you start a debug session.
We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.
You can try looking at issues related to this sample to see if anybody else is having the same issues.
If you encounter any issues using this sample, create a new issue.
Finally, if you have an idea for improvement, make a suggestion.
THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.