Connect Quid+ to Microsoft 365 Copilot
This page lets the Microsoft 365 administrator of a subscribing organisation connect News Tank Quid+ to Microsoft 365 Copilot in four steps, with no action needed from News Tank.
Once the connector is deployed, every user with a Microsoft 365 Copilot licence can query the News Tank articles of their subscription from Copilot, with sourced answers. The connector is read-only: it changes nothing at News Tank or in your tenant.
Prerequisites
- Role: Global Administrator or AI Administrator in the Microsoft 365 admin center, with access to the Teams Developer Portal.
- Licences: every user needs the Microsoft 365 Copilot add-on licence (or Microsoft 365 E7). A Microsoft 365 licence alone, a Copilot Studio licence or pay-as-you-go billing is not enough.
- Tenant setting: in Agents → Settings → Agent and plugin access, “Allow agents and plugins built by your organization” must be selected, and the target users included in User access. Otherwise the connector stays invisible to them.
- News Tank side: an active subscription, and a News Tank account for each user (their work email address). You create the client credentials yourself in step 1.
Values to enter
All values below are fixed, except the client ID and secret, which belong to your organisation and are created in step 1.
| Field (console label) | Value | Where |
|---|---|---|
| Client ID | created in step 1 | Teams Developer Portal |
| Client secret | created in step 1, keep it like a password | Teams Developer Portal |
| Authorization endpoint | https://quid.newstank.fr/oauth/authorize
|
Teams Developer Portal |
| Token endpoint | https://quid.newstank.fr/oauth/token
|
Teams Developer Portal |
| Refresh endpoint | https://quid.newstank.fr/oauth/token
|
Teams Developer Portal |
| Scopes | mcp.read offline_access
|
Teams Developer Portal |
| PKCE | enabled (S256) — required by News Tank | Teams Developer Portal |
| Display name | News Tank Quid+
|
Admin center |
| Description | Articles from the News Tank media in your subscription (B2B press: public policy, stakeholders, appointments, sector figures). Use it for any news or analysis question on these sectors; answers are sourced with the article title, date and link.
|
Admin center |
| Base URL | https://quid.newstank.fr/mcp/academic
|
Admin center |
| Developer name | News Tank
|
Admin center |
| Website URL | https://academic.newstank.eu/quid
|
Admin center |
| Privacy policy URL | https://www.newstank.fr/politique-de-confidentialite.html
|
Admin center |
| Terms of use URL | https://www.newstank.fr/conditions-generales-utilisation.html
|
Admin center |
The redirect URI to declare is already included in the step 1 command: https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect
Step 1 — Create your News Tank credentials
This step produces the client ID (ntkc_…) and the client secret, to be entered in step 2. Before running the command, replace “Your organisation” with your organisation's name: your users will see it on the News Tank authorisation screen. Apostrophes and accents are fine; avoid quotation marks (straight or curly) and the $ and ` (backtick) characters.
From Windows PowerShell:
$body = @{ client_name = "Microsoft 365 Copilot (Your organisation)"; redirect_uris = @("https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect"); token_endpoint_auth_method = "client_secret_post" } | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri https://quid.newstank.fr/oauth/register -ContentType "application/json; charset=utf-8" -Body ([Text.Encoding]::UTF8.GetBytes($body))
From a macOS or Linux terminal, or Google Cloud Shell:
curl -s -X POST https://quid.newstank.fr/oauth/register -H 'Content-Type: application/json' --data-binary @- <<'EOF'
{"client_name":"Microsoft 365 Copilot (Your organisation)","redirect_uris":["https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect"],"token_endpoint_auth_method":"client_secret_post"}
EOF
The response contains client_id and client_secret. Copy them straight away: the secret is shown only once. Keep it like a password.
These credentials grant no access on their own: each user then signs in with their own News Tank account. Lost the secret? Run this step again and replace the client ID in step 2.
Step 2 — Register the OAuth client
This step produces an OAuth client registration ID, used in step 3.
1. Sign in to the Teams Developer Portal (dev.teams.microsoft.com).
2. Open Tools → OAuth Client Registration, then + New OAuth connection.
3. Fill in Name (for example News Tank Quid+), then Client ID, Client secret, Authorization endpoint, Token endpoint, Refresh endpoint and Scopes with the values from the table.
4. Enable Proof Key for Code Exchange (PKCE).
5. Click Save, then copy the OAuth client registration ID displayed.
Step 3 — Create and deploy the connector
1. In the Microsoft 365 admin center (admin.microsoft.com), open Copilot → Connectors, Gallery tab.
2. Under Created by your org, on the Create a new connector tile, click Add.
3. On the Custom connector page, under Connect to MCP server, click Add.
4. Fill in Display name, Description and Base URL, plus the developer and legal information from the table.
5. Enter the OAuth registration ID from step 2, then click Save.
6. In Your connections, select the connector. Test it first with Staged rollout on a few users, then click Deploy to all users.
It can take up to 10 minutes to become available.
Step 4 — Each user signs in
Each user signs in once to their News Tank account.
1. In Copilot, open Settings → Sources and connect News Tank Quid+.
2. The News Tank sign-in page opens: the user signs in as on the website (their email, then the code received or their password).
3. On the authorisation screen, they tick the box “I accept the News Tank terms of use” if it is displayed, then click “Authorize access”.
4. To check: ask Copilot a news question about their sector. The answer should cite News Tank articles.
Access can be revoked at any time from the user's News Tank account.
Troubleshooting
| Symptom | Check |
|---|---|
| The connector does not appear for a user | Microsoft 365 Copilot licence; inclusion in User access and in the staged rollout; “Allow agents and plugins built by your organization” setting; 10-minute delay elapsed and Copilot refreshed. |
| The connector only works for the administrator | Rollout limited to the administrator, or users not yet connected in Settings → Sources. |
| News Tank sign-in fails | Client ID and secret copied without spaces; user holds a News Tank account on an active subscription. |
| Copilot answers without citing News Tank | Start a new conversation; ask a question that falls within a media of your subscription. |
For any other issue, contact us.