Article Contents
Introduction
Connect your Copilot account and ask questions about your WISK data in plain language: what's in stock, what a recent invoice contained, how sales compare to last week, what to order this week.
Copilot reads your live WISK data through a secure connection that you control and can switch off at any time. Microsoft 365 Copilot connects to services like WISK through Copilot Studio, Microsoft's tool for building and customizing Copilot agents, so the setup below happens there.
Setting it up takes about 10 minutes.
Before you Start
You need:
A Microsoft 365 Copilot license and access to Copilot Studio. Your Microsoft administrator can confirm both.
Permission to add tools in Copilot Studio. In some organizations, adding a new connection requires approval from your Microsoft administrator.
A WISK login (the email and password you use at web.wisk.ai). No API key or technical credentials are needed.
WISK never sees what you ask Copilot, and Copilot only sees the WISK data you would see yourself.
Step 1 — Add WISK as a tool in Copilot Studio
Go to copilotstudio.microsoft.com and sign in with your Microsoft work account. Open the agent you want to connect WISK to, or create a new one (for example, an agent called "WISK Assistant").
On the agent's Tools page, select Add a tool, then New tool, then Model Context Protocol.
Fill in the connection details:
Name: WISK
Description: Inventory, invoices, ordering and sales data from WISK
Server URL:
https://mcp.wisk.ai/mcp
For authentication, select OAuth 2.0. If Copilot Studio asks how to configure it, choose the automatic option (called dynamic discovery or dynamic client registration) — WISK supports it, and there is nothing else to fill in. Then create the tool.
Step 2 — Sign in to WISK and choose the level of access
When Copilot Studio asks you to connect, a WISK sign-in page opens in your browser.
Sign in with your WISK email and password.
Read the notice. WISK tells you it has not verified the app that is asking for access, and shows the web address your access will be sent to. Check it, and continue only if you started this connection yourself.
Check the level of access. Connections are read-only: Copilot can look at your data and answer questions, but cannot change anything in WISK.
Click Approve. You are sent back to Copilot Studio and the connection is ready.
Step 3 — Add the tool to your agent and try it
Select Add to agent to finish adding WISK.
Use the test pane on the right to ask a question — for example, "What's my current stock of Grey Goose?" — and check that the answer comes back with your WISK data.
Try:
"What's my current stock of Tito's at the Main Street location?"
"What did my last invoice from Southern Glazer's include, and did any prices go up?"
"What should I order this week based on my par levels?"
"How did last weekend's sales compare to the weekend before?"
If you have more than one venue, name it in your question — one connection covers every venue your WISK account can access.
Step 4 — Publish the agent
Select Publish so your team can use it, and add the agent to the Microsoft 365 Copilot channel if you want it to appear inside Copilot in Teams, Word and the Microsoft 365 app. Depending on your organization's settings, your Microsoft administrator may need to approve the agent before it shows up for everyone.
What Copilot can and cannot see
Copilot gets exactly what your WISK account gets: the venues you are assigned to, and only what your WISK role allows. It cannot reach another venue, another user's data, or anything your permissions hide from you.
One connection covers every venue you have access to. You do not need to connect once per venue.
The connection is read-only: Copilot can never edit items, counts, orders or invoices.
Revoking access
You can cut Copilot off at any moment, from either side:
In WISK:
Hover over your user name and click "Account" then OAuth2 Apps.
Find the entry for this connection and click Disconnect. Access stops immediately
In Copilot Studio: Remove the WISK tool from the agent's Tools page.
Troubleshooting
"Model Context Protocol" or the new connection is blocked.
Your organization's data policies (managed by your Microsoft administrator in the Power Platform admin center) may need to allow new connectors before the WISK connection can be created or used. Ask your administrator to approve it.
The sign-in window doesn't appear or fails.
Pop-up blockers can stop the WISK sign-in page from opening — allow pop-ups for Copilot Studio and try connecting again. If your WISK password isn't accepted, reset it at web.wisk.ai first, then retry.
The agent connects but answers without WISK data.
In the test pane, check that the WISK tool is enabled on the agent's Tools page and that the connection shows as connected. Asking a specific question that names an item or venue usually helps Copilot pick the right tool.
Published agent doesn't show up for your team.
Agents shared with an organization can require approval in the Microsoft 365 admin center. Your Microsoft administrator can approve it there.