Docs · Microsoft 365 Copilot

Connect Feasibly to Microsoft 365 Copilot.

Custom agent in Copilot Studio. Copilot stops fabricating zone codes and starts citing the actual planning scheme.

Works with Microsoft 365 Copilot, Copilot Studio, and Power Platform. Uses Microsoft's MCP server connector pattern (GA in Copilot Studio).

M365 Copilot · Copilot Studio license · Custom agent · ~5 min setup

Setup

Four steps to a custom Copilot agent.

An admin with Copilot Studio access registers Feasibly's MCP endpoint as a tool. Users in your tenant can then ask Copilot planning questions about Australian addresses and get source-linked answers.

G. 01

Open Copilot Studio.

Sign in at copilotstudio.microsoft.com with your Microsoft 365 work account. Pick the environment your agent should live in (usually your tenant's default Power Platform environment).

Note

Requires a Microsoft 365 Copilot license plus Copilot Studio access. The MCP-server tool integration is generally available in Copilot Studio, no preview enrollment needed. Personal M365 plans don't include Copilot Studio.

G. 02

Create or open an agent.

Click Create → New agent (or open an existing one). Give it a name like Feasibly Planning and a description like "Looks up zone, schedule, overlays, and building envelope for any Australian address." Skip the AI configuration prompts — you'll add Feasibly as a tool, not customise the model.

G. 03

Add Feasibly as an MCP tool.

In your agent, go to Tools → Add tool → Model Context Protocol. Fill in:

  • Server nameFeasibly
  • Server descriptionAustralian planning intelligence (zone, overlays, schedule, envelope, subdivision)
  • Server URLhttps://mcp.feasibly.com.au/mcp?key=YOUR_API_KEY
  • Authentication — None (key is embedded in URL)

Replace YOUR_API_KEY with your key from app.feasibly.com.au/register. Click Add tool. Copilot Studio handshakes with the MCP server and lists Feasibly's 8 tools (lookup_site, get_zone_rules, explain_overlay, etc.).

If you'd rather not embed the key in the URL

You can pass the key as a Bearer token instead. Set Authentication to API Key, header name Authorization, value Bearer YOUR_API_KEY. Server URL becomes https://mcp.feasibly.com.au/mcp (no query string). Same outcome; better if your tenant has policies against URL-embedded secrets.

G. 04

Test, then publish.

Open the Test your agent panel on the right. Ask: "What's the planning zone and building envelope at 12 Smith Street, Brunswick VIC?" Copilot calls Feasibly's lookup_site tool and returns the structured answer with source URLs. Once it works, click Publish to make the agent available to users in your tenant.

Optional — share with non-admin users

After publishing, you can grant access via Settings → Security → Roles. The MCP server registration stays scoped to your tenant; users don't need their own Feasibly accounts.

Common gotchas

Three things that break Copilot Studio setups.

All easy fixes once you know.

!. 01

"Failed to connect to MCP server."

Almost always the API key. Re-paste carefully, no leading/trailing spaces, no line breaks. A key is feasibly_sk_ followed by 32 hexadecimal characters — 44 in total. If it still fails, hit https://mcp.feasibly.com.au/health directly in a browser; if it returns {"status":"ok"} the server is up and your key is the issue.

!. 02

"This action is not allowed by your administrator."

Power Platform Data Loss Prevention (DLP) policies may block external connectors. Your tenant admin needs to add mcp.feasibly.com.au to the Business connector allowlist in the Power Platform admin centre.

!. 03

Tool list is empty after registration.

The MCP handshake completed but the tool discovery call failed. Most likely a tier-gating issue — some tools (e.g. generate_report) require Pro or Agency. Free-tier keys still get 4 of the 8 tools (lookup_site, get_zone_rules, explain_overlay, get_usage). That's enough to demonstrate value; upgrade later for the rest.

Privacy & data handling

What Copilot sees, what we keep.

Quick honesty on what happens when an M365 user asks Copilot about a property.

D. 01

Your Copilot prompts don't go through us.

Microsoft routes the prompt through Copilot's own LLM. We only see the structured tool call — e.g. lookup_site({ address: "12 Smith St, Brunswick VIC" }). We never see the surrounding conversation or any other Copilot context.

D. 02

Address logs are tied to the API key, not the user.

For usage metering and rate limits, we log which key looked up which address, when. We do not capture the M365 user identity, the tenant ID, or any other Copilot metadata. Logs are retained 90 days then deleted.

D. 03

All connections are TLS-encrypted via Cloudflare.

Cloudflare's SOC 2 Type II covers transport, DDoS, and infrastructure isolation. Australian-resident traffic routes through Cloudflare's Sydney/Melbourne PoPs. The MCP server itself runs on Cloudflare Workers (the same edge platform Microsoft uses for Copilot Studio's connector layer).

Ready to screen?

Get a free key, register the MCP server, ask Copilot about a property.

If we get the zone wrong, that lookup is free and we credit ten more.