To connect a Copilot Studio agent to AI Activate, follow Microsoft's instructions for connecting an agent to an existing MCP server. When Microsoft's instructions request connection details, use the Nasuni values in this guide. Microsoft's article is the authoritative source for Copilot Studio's steps, which change as Copilot Studio changes.
Microsoft's instructions: Connect your agent to an existing Model Context Protocol (MCP) server.
Use the MCP onboarding wizard, which Microsoft recommends. You do not need to create a custom connector in Power Apps.
To make the agent available in Microsoft 365 Copilot, connect the agent to AI Activate here first, then see AI Activate - Connecting Microsoft 365 Copilot.
Before you start
At least one volume is activated and has MCP access turned on. For more information, see Enable MCP Access and Connect your AI tool.
Have your account's MCP endpoint, copied from the Portal under AI Activate → MCP Server. See Get your MCP endpoint.
Know your organization's company name, which you enter when you sign in through Nasuni Portal single sign-on.
Assign the people who plant to use AI Activate to the Nasuni connection in your identity provider (Okta or Microsoft Entra ID).
You can create and edit agents in Copilot Studio.
The Power Platform environment you use allows the connection. Copilot Studio reaches MCP servers through Power Platform connectors, so your organization's data policies apply. Data policies can block custom connectors in the default environment, so you might need to use a different environment. See the data policies section of Microsoft's article.
Nasuni details for Copilot Studio
Use these values when Microsoft's steps ask for them.
Microsoft's step | What to enter or choose |
|---|---|
Server name | A name your users recognize, for example, Nasuni AI Activate. |
Server description | For example: Finds information in your organization's files in Nasuni and returns only files that the signed-in user has permission to access. The agent uses this description to decide when to call AI Activate. You can add a short note about what your files contain, such as project documents or contracts, to help the agent call AI Activate at the right times. |
Server URL | Your account's MCP endpoint from the Portal. |
Authentication | OAuth 2.0. AI Activate does not use API keys. |
OAuth 2.0 type | Dynamic discovery. Copilot Studio finds AI Activate's sign-in endpoints and registers itself, so you do not enter a client ID, client secret, URLs, or scopes. |
Connection | Create a new connection, and sign in through Nasuni Portal single sign-on with your company name and your own account. |
If Dynamic discovery does not complete, select Manual instead, and follow AI Activate - Connecting an MCP client that does not support DCR to get the values that Manual asks for.
Make sure each person signs in
AI Activate returns results based on the permissions of the person who signs in. Each person who uses the agent must connect with their own Nasuni account, rather than reusing the connection you created while building the agent.
Before you share the agent widely, test it with a second person who has different file permissions. Confirm that the second person is prompted to sign in and that the results reflect that person's file permissions rather than your permissions.
Things to know
Each tool call the agent makes to AI Activate counts as one Activate Query, and a single question can trigger several calls. For more information, see Monitor Your Usage.
For sign-in problems or missing results, see Troubleshooting.