Connect Microsoft 365 Copilot to StratNav
Updated 5 min read
Connect Microsoft 365 Copilot to StratNav with secure OAuth setup, permissions, sign-in and project access guidance.
Contents
Contents · 7 sections
Connect Microsoft 365 Copilot to StratNav so you can explore your business strategy, review progress and work with your strategic plans through conversation. The connection uses StratNav’s Model Context Protocol (MCP) server to give Copilot access to your strategy data, subject to the permissions you approve.
You sign in using your existing StratNav account. Each user connects their own account and can access only the projects they have permission to use.
This guide covers Microsoft 365 Copilot. If you want to connect Copilot Studio, please contact StratNav support for help with its separate setup requirements.
What you need
Before starting, you will need:
- A StratNav Pro account.
- Access to the relevant projects in StratNav.
- A Microsoft 365 environment that supports agents with remote MCP tools.
- An administrator or developer who can configure and deploy the integration in your Microsoft 365 environment.
There are two parts to the setup: your administrator makes the StratNav integration available in Microsoft 365, then each user signs in and approves access.
1. Configure the StratNav connection
Your administrator or developer should create a Microsoft 365 agent with a remote MCP connection to StratNav, using Microsoft’s supported development tools.
Use these connection settings:
| Setting | Value |
|---|---|
| MCP server URL | https://api.stratnavapp.com/mcp |
| Authentication | OAuth 2.0 authorization code flow |
| Client ID | stratnav-m365-copilot |
| Client secret | Leave empty |
| PKCE | Enabled, using S256 |
| Authorization endpoint | https://api.stratnavapp.com/oauth/authorize |
| Token endpoint | https://api.stratnavapp.com/oauth/token |
| Refresh endpoint | https://api.stratnavapp.com/oauth/token |
StratNav has registered Microsoft’s shared callback URL:
https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect
This connection uses a public OAuth client with PKCE. PKCE protects the authorization-code exchange, while your StratNav sign-in and consent determine what the connection can access.See Microsoft’s OAuth setup documentation
2. Choose the permissions
Configure the scopes according to what you want Copilot to do:
| Access | Scopes |
|---|---|
| Read only | projects.read offline_access |
| Read, add and update | projects.read projects.write offline_access |
| Read, add, update and delete | projects.read projects.write projects.delete offline_access |
Enter scopes separated by spaces, not commas.
Start with read-only access if you want to explore your strategy and ask questions. Add write or delete permissions when you need Copilot to make changes.
The offline_access scope lets Microsoft renew the connection using refresh tokens, so you do not need to sign in again whenever a short-lived access token expires.
These permissions never increase your underlying access in StratNav. For example, approving write access does not let Copilot edit a project where your account has read-only access.
3. Make the integration available in Microsoft 365
The OAuth configuration must be connected to your agent’s MCP configuration and deployed in your Microsoft 365 environment. Entering the server URL alone does not complete this step.
Your administrator or developer should:
- Create the OAuth configuration using the settings above, leaving the client secret empty and keeping PKCE enabled.
- Reference its generated configuration ID in the plugin’s authentication settings using
OAuthPluginVault. - Package and deploy the agent through the organisation’s approved Microsoft 365 process.
For the documented MCP setup, Microsoft specifies Any Teams app for the OAuth configuration’s app restriction. Use My organization only when configuring access for your own tenant. If your setup tool insists on a client secret, use a Microsoft provisioning route that supports public clients; do not enter a dummy secret or disable PKCE. Microsoft’s configuration guidance
4. Sign in to StratNav
Once the agent is available:
- Open it in Microsoft 365 Copilot.
- When prompted to connect to StratNav, follow the sign-in link.
- Sign in using your usual StratNav account.
- Review the requested permissions and approve access.
- Return to Microsoft 365 Copilot.
Each person completes this step using their own account. An administrator’s setup does not give everyone access to the administrator’s StratNav projects.
The connection can access projects you have permission to use now, as well as projects you gain access to later. If you lose access to a project, the connection loses access too.
5. Start working with your strategy
Try asking:
List the StratNav projects I can access.
Then choose a project and ask:
Summarise the key insights in this project and explain how they relate to its goals.
Which initiatives support this goal?
Review our KPIs and identify issues that may need further investigation.
Include links to the relevant items in StratNav so I can review them.
If you approved write access, you can also ask Copilot to add or update records. Review proposed changes carefully. Some StratNav updates replace an existing record’s editable content, so ask Copilot to retrieve the current record first and preserve anything you have not requested it to change.
Manage or disconnect access
You can review and revoke your connections on the StratNav connections page.
Interactive connections require an eligible Pro account and remain subject to your current project permissions. Consent lasts up to 90 days, after which you will need to approve access again.
For help connecting Microsoft 365 Copilot—or to arrange a Copilot Studio connection—contact StratNav support.