Copilot Connectors: visible does not mean ready to use
Connectors are one of the clearest examples of why Microsoft 365 can feel confusing: you may see the capability before your organisation has enabled, configured or approved it for you.
Last reviewed 2026-09-05
Why the connector can be visible but not usable
| State | What it means |
|---|---|
| Visible | Microsoft exposes the connector or connector capability in the product. |
| Enabled | Your administrator allows that connector or connector type for your users/group. |
| Configured | The connection to the external system has actually been set up and authenticated. |
| Permitted | Your identity has permission to the underlying source information. |
| Available in this experience | The particular Copilot, Agent or search experience you are using supports that connector. |
| Healthy | The connection still authenticates, syncs or responds correctly and still has a valid owner/purpose. |
Permissions remain critical
Well-configured connectors should respect source permissions, so users only receive information they are entitled to see. Connector setup itself can also define visibility. Incorrect permission configuration can create oversharing risk, so admins should validate who can see indexed or fetched content rather than assuming the source system will solve every access problem automatically.
Awarding-organisation examples
A connector might allow approved information from a CRM, service desk, qualification platform or another knowledge system to become searchable from Microsoft 365. That can be useful, but systems containing candidate records, assessment outcomes, malpractice, safeguarding or other sensitive data need particularly careful access design before being connected.
Related guidance
Sources
- Copilot connectors overview — checked 2026-09-05
- Manage access permissions for connectors — checked 2026-09-05
- Prerequisites for deploying connectors — checked 2026-09-05