Microsoft 365 Copilot reaches AI Activate through a Copilot Studio agent. You create the agent in Copilot Studio, connect the agent to AI Activate, and publish the agent to the Teams and Microsoft 365 Copilot channel. Your users then add the agent in Microsoft 365 Copilot.
Follow Microsoft's walkthrough of this flow, and use the Nasuni details in this guide. Microsoft's walkthrough is written for a Power Pages MCP server secured by Microsoft Entra ID, so some steps do not apply to AI Activate. The table below shows which ones.
Microsoft's instructions: Connect to MCP server via 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. For more information, 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 plan to use AI Activate to the Nasuni connection in your identity provider (Okta or Microsoft Entra ID).
You can create and publish agents in Copilot Studio, in a Power Platform environment whose data policies allow the connection. For more information, see AI Activate - Connecting Microsoft Copilot Studio.
Each person who plans to use the agent has the Microsoft 365 Copilot license that Microsoft's walkthrough lists.
Nasuni details for Microsoft 365 Copilot
Use this table as you work through Microsoft's walkthrough.
Section of Microsoft's walkthrough | For AI Activate |
|---|---|
Prerequisites: redirect URIs and app registration details | Skip. AI Activate does not require a Microsoft Entra app registration. With Dynamic discovery, you do not manually enter a client ID, client secret, or scopes. |
Create an agent | Follow as written. |
Add MCP tool to agent: Server Name | A name your users recognize, for example, Nasuni AI Activate. |
Add MCP tool to agent: 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. |
Add MCP tool to agent: Server URL | Your account's MCP endpoint from the Portal. |
Configure OAuth authentication | Select OAuth 2.0 and Dynamic discovery, not Manual. The client ID, client secret, URL, scope, and refresh URL fields in Microsoft's example do not apply. |
Add redirect URI to app registration | Skip. |
Create connection for agent | Follow as written. When the sign-in window appears, sign in through Nasuni Portal single sign-on with your company name and your own account. |
Publish agent | Follow as written. |
Add channels | Follow as written. |
Connect via Microsoft 365 Copilot | Follow as written. On first use of the agent, each person connects through Connection Manager and signs in with their own Nasuni 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. You still do not use a Microsoft Entra app registration.
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 through Connection Manager, rather than reusing the connection you created while building the agent.
Before you share the agent widely, test the agent with a second person who has different file permissions. Confirm that the second person connects through Connection Manager and receives results consistent with that person's file permissions.
Things to know
AI Activate only reads your files. Microsoft's walkthrough mentions create, update, and delete operations, which apply to Power Pages, not to AI Activate.
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.