Should we let users connect their own Jira and Confluence to Copilot?

You’re right to treat this as a governance decision, not a convenience toggle. Self-serve sync is a different shape of risk from the tenant Graph connectors most security teams already argued about.

Here’s what’s going on. Self-serve sync connectors (preview, limited tenants) let each user authenticate to Microsoft-published sources — today Jira Cloud and Confluence Cloud — with their own credentials. Only that user’s accessible content is indexed into Microsoft Graph (roughly a 90-day lookback for shared spaces/work items), with no cross-user access. OAuth is three-legged and delegated; disconnecting or an admin disable deletes the indexed content and stops sync. Unlike admin-configured tenant synced connectors, users set these up themselves once the connector is visible. Microsoft enables them for the tenant by default, but when a new Microsoft-published self-serve connector appears it stays admin-only for at least seven calendar days — your review window to disable, stage, or leave alone. Manage under Microsoft 365 admin centre → Copilot → Connectors → Your connections (AI Admin or Global Admin). You can turn a connector off entirely, or use Add staging to limit it to Entra groups. If a tenant synced connection already covers the same source for a user, Copilot prefers the tenant connection and self-serve isn’t available to that user.

Schofield’s First Law (historically attributed) still applies: know how data gets out — here, disconnect/disable removes the Graph copy. Third Law applies too: easier personal grounding is easier oversharing of whatever that user’s Atlassian ACLs already allow.

This is Steady before scale for Pane 04/05: decide who may ground on SaaS ticket text before adoption metrics celebrate “connectors live.”

Options that actually work:

1. Use the seven-day window. Review each new self-serve connector, disable anything Legal won’t accept, or stage to a pilot security group. Best Wave 0 default while preview.
2. Prefer a tenant synced connector for the same source where you need org-wide grounding with admin-owned crawl scopes — then self-serve is blocked for users already covered. More control; more admin work.
3. Leave everything on for Everyone. Maximises “my Jira in Copilot” delight and maximises shadow grounding you didn’t approve. Weak Steady posture.
4. Assume disable forever equals no Atlassian in Copilot. Users may still paste tickets into chat, use federated connectors later, or ask for a tenant connection — govern the pattern, not only this SKU.

12 Panes action / comms: Tell Security: self-serve indexes per-user, ACL-trimmed content — not a second enterprise crawl account. Tell makers: if IT stages Confluence, wait for your group or ask for the tenant connector path. Leadership: seven days of admin silence is consent by default.

Benefits / risks: User-scoped OAuth reduces “service account can see everything” blast radius; preview availability, ~15-minute incremental lag, 90-day lookback, and “enabled by default after the review window” still create surprise if nobody watches Your connections. Disabling deletes everyone’s indexed copy for that connector — communicate before you pull the plug.

I’d suggest this week: open Copilot Connectors, note which self-serve sources are in or past the admin review window, disable or stage Jira/Confluence to a named pilot group, and put a calendar check on every new Microsoft-published connector. You’ll keep personal grounding useful without waking up to an ungoverned Atlassian index.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer