Lesson 2 of 6 — Microsoft 365 Copilot connector

Automated Discovery Connectors · Source: Jira Story GOV-302 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Discover M365 AI apps and Copilot agents automatically.

Why it matters

Copilot sprawl is a major shadow-AI source; automated discovery surfaces it.

Where this lives

Runs in the Customer AI Governance platform (components: intelligence). The M365 connector enumerates AI apps and Copilot agents in the tenant. Learn teaches this read-only.

Workflow

1. Given an M365 tenant
2. When the connector runs
3. Then AI apps and Copilot agents are discovered

Worked example

A tenant has dozens of undocumented Copilot agents. How does this story surface them?

The M365 connector discovers AI apps and Copilot agents automatically.

Acceptance criteria (authoritative — GOV-302)

Given an M365 tenant, when the connector runs, then AI apps and Copilot agents are discovered.

Common pitfalls

• Missing Copilot agents by only scanning apps.

Knowledge check

• Scenario: A tenant has dozens of undocumented Copilot agents. How does this story surface them?
• Look for: The M365 connector discovers AI apps and Copilot agents automatically.

Key concepts

• M365 connector
• Copilot agents
• automated discovery

For the AI Tutor

• Summary: Discover M365 AI apps and Copilot agents automatically.
• When to use: teaching or answering questions about "microsoft 365 copilot connector".
• When NOT to use: the connector interface contract (that is GOV-301).
• Key concepts: M365 connector, Copilot agents, automated discovery.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-302's acceptance criterion.

Related

• Module: LEARN-MOD-009 (Automated Discovery Connectors)
• Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
• Next: LEARN-LSN-047