Skip to content

Control 4.13: Copilot Extensibility and Agent Operations Governance — Verification & Testing

Test cases and evidence collection procedures for Copilot extensibility governance and ongoing agent operations.

Test Cases

  • Objective: Verify that users cannot self-consent to new Copilot plugins without admin approval
  • Steps:
  • Log in as a standard Copilot user.
  • Attempt to add or enable a third-party plugin that is not in the approved catalog.
  • Verify the request is blocked and the user is directed to the request workflow.
  • Confirm the admin team receives the request notification.
  • Expected Result: User consent is blocked and the request is routed through the approval workflow.
  • Evidence: Screenshots showing the blocked consent attempt and admin notification.

Test 2: Agent Ownership and Registry Review

  • Objective: Validate that widely available agents are visible in the Registry and have assigned owners
  • Steps:
  • Review the current Registry inventory.
  • If supported third-party platforms are connected, verify the latest Connected platforms > Sync agents run and record any synchronization errors before treating the Registry as complete.
  • Identify any ownerless or broadly shared agents.
  • Verify follow-up or remediation is recorded for each exception.
  • Expected Result: Registry is current for the last completed sync, and owner accountability is clear.
  • Evidence: Registry export or screenshots with owner fields.

Test 3: Plugin Approval Workflow

  • Objective: Validate the end-to-end plugin approval workflow
  • Steps:
  • Submit a test plugin request through the user request workflow.
  • Walk through the three-level approval chain (IT, Compliance, Business).
  • Verify each approver receives the request with the Plugin Risk Assessment.
  • Complete the approval and verify the plugin is made available.
  • Expected Result: Plugin approval workflow completes through all levels with documented approvals.
  • Evidence: Approval workflow records showing each approval level.

Test 4: Plugin Access Control by Group

  • Objective: Confirm that plugin access is correctly restricted by user group
  • Steps:
  • Configure a plugin to be available only to a specific user group.
  • Log in as a user in the approved group and verify plugin access.
  • Log in as a user outside the approved group and verify the plugin is not available.
  • Change group membership and verify access updates accordingly.
  • Expected Result: Plugin access follows group membership restrictions.
  • Evidence: Screenshots showing plugin availability per group membership.

Test 5: Graph Connector Data Sensitivity Assessment

  • Objective: Verify that Graph connectors exposing data to Copilot have been assessed for sensitivity
  • Steps:
  • Run the Graph connector inventory script.
  • For each connector, verify a data sensitivity assessment is on file.
  • Confirm appropriate access controls are applied to connector data.
  • Verify sensitivity labels are applied to connector content where applicable.
  • Expected Result: All Graph connectors have documented sensitivity assessments and appropriate controls.
  • Evidence: Connector inventory with sensitivity assessment completion status.

Test 6: Agent Tools and MCP Requests Are Governed

  • Objective: Validate that AI-powered tools, MCP servers, and BYO MCP requests are inventoried, approved or rejected, and consented before use.
  • Steps:
  • Open Microsoft 365 admin center > Agents > Tools.
  • Export or screenshot Available and Blocked tools / MCP servers.
  • Review the Requests tab and verify each pending or completed request has an approval/rejection rationale.
  • For approved BYO MCP servers, verify declared tools and Microsoft Entra permission consent state.
  • Confirm blocked MCP servers cannot be invoked from supported client surfaces.
  • Expected Result: Tools and MCP servers are inventoried; BYO MCP requests have documented decisions; approved servers have Entra consent; blocked servers cannot be invoked.
  • Evidence: Agents > Tools screenshots/exports, request decision records, Entra consent evidence, and blocked-invocation test.

Test 7: Work IQ Billing and Write Posture Are Verified

  • Objective: Confirm Work IQ usage-based billing, spending policy, regional allow/block controls, and write-operation state are known before production use.
  • Steps:
  • Verify whether Work IQ is enabled in the tenant and whether a usage-based billing plan and separate spending policy exist.
  • Confirm whether Work IQ write operations are disabled or explicitly enabled.
  • Confirm whether the tenant's region exposes allow/disallow tooling and MCP server controls.
  • If write operations are enabled, run a controlled confirmation-flow test and preserve approval evidence.
  • Expected Result: Work IQ is either disabled/not available or has documented billing, spending, allow/block, and read/write posture evidence.
  • Evidence: Admin-center screenshots, billing/spending policy record, write-operation setting, and controlled test evidence where applicable.

Evidence Collection

Evidence Item Source Format Retention
Plugin inventory PowerShell CSV Monthly archive
Agent Registry review Microsoft 365 admin center Screenshot/Export 7 years
Approval workflow records Microsoft 365 admin center Screenshot/Export 7 years
Permission audit PowerShell CSV Monthly archive
Connector sensitivity assessments Assessment documents PDF 7 years
Agent tools / MCP request evidence Microsoft 365 admin center > Agents > Tools Screenshot/Export 7 years
Work IQ billing and write posture Microsoft 365 admin center / Copilot Studio Screenshot/Export 7 years

Compliance Mapping

Regulation Requirement How This Control Helps
FFIEC Development Booklet Third-party software governance Potential mapping for firm/counsel review where extensibility components affect software acquisition and deployment governance
OCC Bulletin 2023-17 (Third-Party Relationships) Vendor risk management Potential mapping for firm/counsel review where plugin, agent, or MCP providers are third-party relationships
NYDFS 23 NYCRR 500 Third-party security assessment Potential mapping for firm/counsel review where third-party service provider security assessment requirements apply

Next Steps