Use NPM with Microsoft 365 Copilot

Setting Up the Agent (once per organization)

What you need

• Microsoft Copilot Studio, with permission to create and publish agents
• An NPM website login with MCP enabled, to connect and test the agent. Setting this up for a colleague without MCP? Ask someone who has it to sign in and test with their own login.
• A Microsoft 365 Copilot licence for everyone who will use the agent. Check with your Microsoft admin if unsure.

NPM's connector supports OAuth 2.0 dynamic client registration with discovery, so there are no client IDs, secrets, or endpoint URLs to configure - Copilot Studio discovers everything from the connector URL.

1. In Copilot Studio, create a new agent (or open an existing one). Give it a name like "NPM Intelligence" and a short instruction, e.g. "You help users research energy projects, interconnection queues, and data centers using New Project Media's data tools."
2. Go to the agent's Tools page and select Add a tool → New tool → Model Context Protocol
3. Fill in the MCP onboarding wizard:
   • Server name: New Project Media
   • Server description: "Searches New Project Media's proprietary data on energy project signals, interconnection queue applications, data center projects, market intelligence, and organizations." (the agent uses this to decide when to call the connector, so keep it descriptive)
   • Server URL: the connector URL above
4. Under authentication, select OAuth 2.0, then Dynamic discovery, select Create and then Next
5. In the Add tool dialog, open the Connection dropdown (it shows Not connected) and select Create a new connection:
   • Enter a display name if you like - it's optional and only labels the connection in your own connection list - then select Create
   • A popup titled "Authorise access to New Project Media data" opens. It names Credential Manager as the requester and shows a return address at global.consent.azure-apim.net - both are expected; Credential Manager is Microsoft's connection broker, acting on your behalf. Select Allow
   • Sign in with your own NPM website login (if your browser is already signed in to NPM as someone else, use a private window)
   • Back in the Add tool dialog, the connection now shows as connected - select Add to agent
6. Test the agent in the side pane (try "Show me the latest solar signals in Texas"), then publish it and enable the Microsoft 365 Copilot channel so it appears for your users. Your organization may require an admin to approve the published agent before it becomes visible.
7. Publishing doesn't automatically activate the connection for the published agent. Go to the agent's Settings → Connection settings to open Manage your connections, find the NPM connection, and if its status shows Not Connected, select Connect
8. In the Create or pick a connection panel, pick the connection you created in step 5 and select Submit. The status changes to Connected and the agent is ready for your users.

Using the Agent

1. Open the agent from the Agents list in Microsoft 365 Copilot (or in Teams, wherever your organization publishes it)
2. The first time you ask it a question, you'll be prompted to connect - approve the consent screen and sign in at the NPM prompt with your own NPM login, the one you use on the website. If your browser is already signed in to NPM as a different person, open the sign-in in a private window
3. That's it - ask away.

Try it

Ask the agent something like "Show me the latest solar signals in Texas". See What you can ask for the data you can search, more to try and how the answers behave, and Your login and access for sign-in, trials and access changes.

For Developer Teams

If your organization builds its own Microsoft 365 agents in code, you can instead add the connector to a declarative agent with the Microsoft 365 Agents Toolkit: add an action, choose Start with an MCP Server, enter the connector URL above, and select OAuth (with dynamic registration) as the authentication type.