Microsoft 365 Copilot

Who can use this feature?

A maker in your organisation who builds agents in Copilot Studio, working with your N3O contact.

A Copilot Studio agent is how your team works with your N3O Cloud data from inside Microsoft 365 Copilot. You build the agent once, in your organisation's own Microsoft 365 tenant, point it at your subscription's address, and publish it to Copilot. Each person who uses it signs in with their own N3O Cloud account the first time. What the server is and what it can answer is on the MCP Server page.

Before you start

The server has to be turned on for your subscription before any of this works. Ask your N3O contact to enable it, and to give you:

• your subscription's address for the server;
• the description to use for it; and
• the client ID and client secret.

The redirect URL is the one thing that goes back the other way. Copilot Studio shows it once the tool is created, and N3O registers it before anyone can sign in.

What Copilot Studio asks of your organisation, licences included, is Microsoft's to set and it changes, so read Microsoft's Assign user licenses and manage access before you start.

Your environment

Copilot Studio reaches an MCP server through a Power Platform connector, so the data policy your tenant applies to connectors decides whether the agent can reach N3O Cloud at all. Build the agent in an environment whose data policy allows custom connectors. The default environment is often not that environment, because tenant-wide policies commonly restrict custom connectors there. If you are unsure which environment to use, your Power Platform administrator can tell you. Everyone who uses the agent has to be in the same Microsoft 365 tenant as the agent.

The agent answers with the data your subscription holds, personal data included, so the policy you apply to the connector is the policy you are applying to that data.

Generative orchestration

After you create the agent, and before you add the tool, turn on generative orchestration in the agent's settings. The agent cannot use MCP tools without it.

Adding the tool

1. Sign in to Copilot Studio, select Create, then New agent, and give the agent a name.
2. In the agent, select Tools, then Add a tool. Search for Model Context Protocol, select it from the results, then select New tool.
3. Enter N3O as the Server name, the description N3O gave you as the Server description, and your subscription's address as the Server URL. The agent reads the description to decide when to call the server, so it needs to say plainly what the server answers.

Authentication

Under Authentication, select OAuth 2.0, then Manual, and enter the following.

Field	Value
Client ID	Supplied by N3O
Client secret	Supplied by N3O
Authorization URL	https://eu1.n3o.cloud/api/mcp/oauth/authorize
Token URL template	https://eu1.n3o.cloud/api/mcp/oauth/token
Refresh URL	https://eu1.n3o.cloud/api/mcp/oauth/token
Scopes	openid profile email offline_access

N3O confirms the exact form of these settings with you during setup. Copilot Studio does not keep the client secret when you later edit the tool, so keep it somewhere safe and expect to enter it again.

Select Create, and wait for the connector to initialise.

Sending N3O the redirect URL

A Redirect URL appears on the confirmation page once the tool is created, and the wizard may label it the callback URL. Copy it and send it to your N3O contact. Every connector has its own redirect URL, and N3O has to register yours before a sign-in through the agent can succeed. Leave the wizard open on that page, without selecting Next, until N3O confirms that the URL is registered. A connection created before then fails at sign-in.

Creating the connection

Once N3O confirms, go back to the wizard and select Next. In the Connection dropdown select Create new connection, then select Create, and sign in with your own N3O Cloud account. After signing in, select Add and configure. In the tool's Tools section, check that the tools N3O told you to expect are listed. Then ask something in the test chat, such as finding an account by name, and watch the agent call the server and answer.

Publishing and sharing

1. Select Publish.
2. Select Share, choose the people or groups who should use the agent, give them the Viewer role, and select Update.
3. Select Channels, then Teams and Microsoft 365 Copilot, and select Add channel. Once the channel is added, Copilot Studio shows links for opening the agent in Microsoft 365 Copilot. Pass those to your team.

First use

The first time someone asks the agent a question, Copilot asks them to connect. They select Open Connection Manager, select Connect, select the menu button (three dots) and then Add new connection, sign in with their own N3O Cloud account, and select Submit. A confirmation appears. Back in the chat, they select Retry, and the question is answered. The connection is tied to their own identity, so the agent answers as them.

Further reading

• Microsoft's Connect your agent to an existing MCP server covers connecting an agent to a server such as this one.

note

If a step fails, send your N3O contact what the screen says.