Can I paste an Ad Legends MCP URL into regular Microsoft Copilot Chat?
Not as a general user setting. The practical full-workflow path is a Copilot Studio agent with Ad Legends added as an MCP tool. Your organization can then make that agent available in Microsoft 365 Copilot and Teams.
Do we need IT approval?
Not always for a maker who already has a permitted Copilot Studio environment. In a managed tenant, IT commonly controls maker access, Power Platform data-loss-prevention policy, Teams app availability, and organization-wide agent distribution. Start with a small pilot and involve your Microsoft 365 administrator if a control is unavailable.
Which Ad Legends server should our team use?
Use the public server for the focused strategy-to-private-creative workflow. Use the full server when your agent needs the complete customer workflow across your authorized brands, campaigns, and creative work. Both connections use the Ad Legends account that each employee authorizes.
Do employees share an Ad Legends API key?
No. Use OAuth so each employee signs in to their own Ad Legends account. Their existing brand access, role, entitlements, and tool gates continue to apply after the connection is made.
Can our IT team make Ad Legends available in native Copilot Chat Sources?
Microsoft has a federated connector model for native Copilot Chat Sources. That route is read-only search and fetch, and it is governed by tenant administration. Contact us if your team wants to evaluate that organization-wide route; it is different from a full, action-capable Copilot Studio agent.
How do we know the connection worked?
Test the agent in a fresh conversation with “Show my Ad Legends brands.” The response should contain only brands the employee who completed OAuth is allowed to access.
