LayerOps for Microsoft Copilot
Covers Microsoft 365 Copilot and Teams through a Copilot Studio agent, and GitHub Copilot in VS Code.
Add LayerOps to a Copilot Studio agent and your team can ask about clients, tickets and devices in Microsoft 365 Copilot and Teams. Changes are held in LayerOps until a person approves them.
14 days free, no card needed.
What LayerOps adds to Microsoft Copilot.
One connector, one data policy decision.
Copilot Studio can call outside tools, but each vendor would be its own custom connector under your Power Platform data policies, with credentials either per user or shared. LayerOps is one connector, so it is one policy decision and one sign-in per technician.
Roles that follow the person.
Microsoft's sign-in proves who the user is to Microsoft. It does not limit what a vendor key can do. LayerOps matches that person to their LayerOps role, so a read-only technician stays read-only in your PSA, even if the agent asks for a change.
Approvals that do not depend on a link.
Microsoft says Copilot may remove links from its answers. Every pending change still lands in the LayerOps approvals inbox, and owners and admins get an email, so nothing relies on the chat showing a link.
The same connection for technicians in VS Code.
GitHub Copilot in VS Code connects to the same LayerOps workspace, with the same roles and the same approvals.
Ask in plain words. Approve the change.
Microsoft Copilot reads across your tools and answers. When the next step would change something, it proposes the change and LayerOps holds it for a person to approve.
- Which clients have a domain controller offline and a P1 open?
Northgate Ltd. Their domain controller SRV-DC01 is offline and ticket 4521 is open at P1. The other three offline devices are at clients with no P1 open.
Waiting for approvalMove ticket 4521 to In Progress and assign it to the on-call tech.
- Any client where backups have not run in three days with no ticket raised?
Two. Haldon Care and Brigg & Co have had no backup for three days, and neither has a ticket open.
Waiting for approvalRaise a P2 ticket for each client, titled "Backups stale 3 days".
- What are we paying Pax8 per client, and does it match what we bill?
Not quite. Pax8 bills 38 lines against 36 active agreements. Two clients pay for licences with no matching agreement line, a gap of £412 a month.
Waiting for approvalAdd six M365 E3 licences to agreement 812 from the next billing cycle.
Examples on made-up companies.
Connect it in a few minutes.
You need a LayerOps workspace with at least one tool connected. Microsoft Copilot connects over MCP, the open standard AI assistants use to connect to tools, using this one address for everything.
If a step looks different in your version, email [email protected] and we will help.
Copilot Studio agent, for Microsoft 365 Copilot and Teams
Set up by someone who builds agents in Copilot Studio, then published by an admin.
Step 1: In Copilot Studio, open your agent, go to Tools, choose Add a tool, then New tool, then Model Context Protocol.
Step 2: Name the server LayerOps, paste the server URL, and give it a description that tells the agent when to use it.
Server URLhttps://app.layerops.ai/api/mcpDescriptionReads tickets, devices, alerts and backups across this MSP's PSA, RMM and security tools. Proposes changes that a person approves in LayerOps.Step 3: Set authentication to OAuth 2.0 and the type to Dynamic discovery. Choose Create, then Next.
Step 4: Choose Add tool, then Create a new connection. Sign in to LayerOps in the window that opens, approve access, then choose Add to agent.
Step 5: In the tool's details, keep Credentials to use set to End user credentials, so each technician signs in as themselves.
Step 6: Publish the agent. Under Channels, add Microsoft 365 and Microsoft Teams and keep Make agent available in Microsoft Copilot ticked. Share it, or submit it for your organisation's approval. People then reach it with @ in Copilot or Teams.
GitHub Copilot in VS Code
For technicians who work in VS Code. A shorter setup, one person at a time.
Step 1: Add LayerOps to the MCP config in your project.
.vscode/mcp.json{ "servers": { "layerops": { "type": "http", "url": "https://app.layerops.ai/api/mcp" } } }Step 2: Start the LayerOps server from VS Code. A browser window should open for you to sign in to LayerOps and approve access.
Step 3: Open Copilot Chat in agent mode and ask your question.
Before you start.
- Publishing an agent needs a Copilot Studio licence that allows it, and an admin to make it available. From Microsoft's licensing notes, the Copilot Studio plan included with Teams does not support these tools, so you will most likely need a standalone Copilot Studio licence. A technician cannot add LayerOps to Microsoft 365 Copilot alone.
- Copilot Studio refreshes an agent's tool list every 12 to 24 hours, and there is no manual refresh. After you connect a new integration or change tool groups in LayerOps, allow up to a day for the agent to see it.
- Copilot may remove links from its answers. Approve changes in the LayerOps approvals inbox at https://app.layerops.ai/approvals, or from the email owners and admins receive.
- Use sign-in with end user credentials, not a shared API key. A shared key makes everyone who uses the agent act as the one person who created it, which defeats the roles and the audit log. Choose Dynamic discovery rather than Manual for OAuth.
- VS Code handles up to 128 tool definitions in one request. Above that it falls back to grouping tools in an experimental way, which can make the right one harder to find. If your workspace exposes more, switch off the tool groups you do not use at Settings > Connect.
- On GitHub Copilot Business and Enterprise, an organisation admin has to turn on the MCP servers in Copilot policy first. It is off by default.
Switch assistants, keep the rules.
The assistant only asks. LayerOps decides what each person may see and change, so the rules stay the same whichever assistant your team picks.
Read the security modelRoles
Each person's role decides which tools they can read and where they can propose changes, checked when they ask and again when anything runs.
Approvals
A change waits in the LayerOps approvals inbox for someone with the right to approve it, unless an owner or admin has written an allow rule for exactly that change.
Audit log
Every call is logged with the person behind it, allowed or blocked, whichever assistant they used.
Bring Microsoft Copilot. We hold the keys.
Fourteen days free and no card needed. Connect a couple of tools, set who can do what, and see what your team asks first.