Microsoft Copilot (Microsoft 365): Admins can create and deploy custom Model Context Protocol (MCP) connectors across Microsoft 365.

🚨 The Signal: Admins can now connect Microsoft 365 Copilot to custom organisational data sources via new Model Context Protocol (MCP) connectors. This expands Copilot's data access, increasing the risk of sensitive information exposure if not properly governed.

The Impact

Security teams and data owners are affected by the increased risk of sensitive data exposure through Copilot's expanded access to custom data.

  • Security Teams: Increased surface area for data leakage and unauthorised access.
  • Data Owners: New responsibility to classify and protect custom data exposed to Copilot.
  • Compliance Officers: Need to update data handling policies for AI-driven data access.
  • Admins: Must securely configure and monitor custom connectors to prevent data exfiltration.

The Action

  1. Identify and classify all custom data sources intended for Copilot integration.
  2. Implement strict access controls and data loss prevention (DLP) policies for MCP connectors.
  3. Review and update data governance policies to include AI-driven data access and usage.
  4. Conduct security assessments of custom MCP connectors before deployment.
  5. Monitor Copilot usage logs for unusual access patterns to custom data.

Domain: Agentic-AI · Impact: high · Workload: Microsoft Purview · Essential Eight: Restrict Administrative Privileges · ISM: ISM-0445, ISM-1175, ISM-1380, ISM-1507, ISM-1508, ISM-1509, ISM-1647, ISM-1648, ISM-1650, ISM-1686, ISM-1688, ISM-1689, ISM-1883, ISM-1897, ISM-1898