Microsoft · MCP with API key
DNSai for Microsoft Copilot Studio and Microsoft 365 Copilot
Build a Copilot Studio agent with DNSai as an MCP tool and publish it to Microsoft 365 Copilot and Teams, so your organisation can ask about domains, email security and DNS changes where it works.
What you can ask Microsoft Copilot Studio
Example answers use made-up domains.
“Is the sender domain in this email protected by DMARC?”
Connect in 3 steps (about 10 minutes)
- In your agent, add a new Model Context Protocol tool with the DNSai URL.
- Choose API key authentication (Authorization header) or OAuth dynamic discovery.
- Add the tool to the agent and publish to Microsoft 365 Copilot or Teams.
Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Microsoft Copilot Studio, a one-click API key for it, and a live connection check.
Microsoft Copilot Studio requirements: Copilot Studio with a Power Platform environment; your data (DLP) policies must allow the connector. DNSai Enterprise plan.
Good for
- A Teams agent that answers "is this domain spoofable?" for the help desk
- Account research for sellers inside Microsoft 365 Copilot
Security
- Microsoft Copilot Studio sends an API key in the Authorization header. Use an expiring key made for Microsoft Copilot Studio and keep it in an environment variable.
- Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
- Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
- DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.
Connect Microsoft Copilot Studio to DNSai
The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.
Other integrations
Last checked 2026-10-29.