Frontify MCP connection fails in Copilot Studio
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 41%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
Jihye Kang
0
Reputation points
Frontify MCP connection fails in Copilot Studio (Authentication: None)
Frontify MCP connection fails in Copilot Studio (Authentication: None)
Hello! I'm hoping to connect the Frontify MCP server to Microsoft Copilot Studio for a test run, but the connection keeps failing.
Current setup
- Software: Microsoft Copilot Studio
- MCP server: Frontify MCP
- Server URL: will share if helpful.
- Authentication: None (per Frontify's setup guidance)
- Account: Signed in with my Microsoft work account
- Result: Connection fails during setup (see error screenshots)
Questions
- Does Copilot Studio support third-party MCP servers with Authentication (None), as long as I'm signed in with my work account, or is additional authentication required?
- Is this more likely a Copilot Studio configuration issue, or something that Frontify's tech support team needs to resolve on the MCP server side?
- Are there any known requirements or settings for connecting third-party MCP servers in Copilot Studio?
Frontify suggested reaching out to Microsoft for troubleshooting. Any guidance would be greatly appreciated.
Thank you so much!
J
Microsoft Copilot | Other
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 78%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Prasad-MSFT 10,546 Reputation points Microsoft External Staff Moderator2026-08-26T13:09:41.8366667+00:00 Hi @Jihye Kang Copilot Studio does support third-party MCP servers with "Authentication: None", so being signed in with your Microsoft work account shouldn't, by itself, require additional authentication for a public MCP endpoint.
Since the connection is failing during setup, first verify:
- The MCP endpoint is publicly reachable over HTTPS.
- The server correctly responds to MCP discovery requests.
- The MCP implementation is compatible with Microsoft's MCP requirements.
Failures at the connection stage are more commonly related to MCP server configuration, discovery, protocol compatibility, or endpoint accessibility than to the Copilot Studio account itself. If possible, inspect the MCP server logs to see whether Copilot Studio is reaching the endpoint and whether discovery requests are succeeding. That will help determine if the issue is on the Frontify/server side or within Copilot Studio.
If you can share the exact error message and the MCP server logs (or a sanitized endpoint URL), it may be easier to pinpoint the root cause.
Sign in to comment
Sign in to answer