Control 4.15: Copilot Cowork Governance
Control ID: 4.15 Pillar: Operations & Monitoring Regulatory Reference: FFIEC IT Examination Handbook, GLBA §501(b), Sarbanes-Oxley §§302/404, OCC Heightened Standards (12 CFR part 30, appendix D), FINRA Rule 3110 Last Verified: 2026-09-29 Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Governance Levels: Baseline / Recommended / Regulated
Scope boundary: FSI-CopilotGov vs FSI-AgentGov
This control governs the Microsoft 365 Copilot surface only — tenant-level configuration, data-source posture, audit/eDiscovery, and admin-managed extensibility. Governance of the agents themselves (Copilot Studio agents, declarative agents, Agent Builder, custom pro-code agents) — including agent registration, risk tiering, environment zoning, model-card review, and lifecycle promotion — lives in the companion FSI-AgentGov framework. See Relationship to FSI-AgentGov for the full boundary map.
Objective
Establish governance over Microsoft 365 Copilot Cowork — a generally available agentic Copilot experience that performs multi-step work on a user's behalf. This control helps organizations govern access (via Copilot Credit spending policies and the current discovery/request setting), model selection, local browser use, plugin and skill extensibility, consumption limits, usage reporting, supervision, and evidence collection so adoption proceeds under documented governance rather than default tenant exposure.
Why This Matters for FSI
Microsoft 365 Copilot Cowork reached general availability in June 2026 for Microsoft 365 Copilot tenants (worldwide, in tier-1 languages). Cowork access is granted through Copilot Credit spending policies in Copilot > Cost management that select Cowork as a service. The current AI experiences enabled by usage-based billing setting is now documented as deprecated and Microsoft states it will be replaced by a new setting that controls whether users or groups can request access to usage-based experiences. Until that replacement arrives, the current setting still controls visibility and access-request flow rather than access by itself. If Cowork is made discoverable but no spending policy grants access, users can submit an access request that an administrator reviews and approves. Microsoft Learn states that local browser use moved from Frontier to general availability in August 2026; tenant administrators should still review browser policy, Edge policy, Conditional Access, and Purview posture before enabling it broadly.
For regulated populations, legal, compliance, risk, and records owners should determine whether Cowork introduces supervision, operational-risk, cost-management, books-and-records, ICFR, OCC-governance, or customer-information safeguarding considerations for the firm's specific entity, workflow, and data classes. Treat FFIEC, FINRA Rule 3110, Sarbanes-Oxley §§302/404, 12 CFR part 30, appendix D, and GLBA §501(b) as applicability prompts rather than conclusions that any requirement applies or is satisfied.
No single control should be treated as satisfying any regulatory obligation on its own. This control is intended to be applied alongside readiness, data-protection, extensibility, and supervision controls rather than as a standalone assurance. Organizations should verify that their own legal, compliance, and risk functions have reviewed Cowork — including its third-party model providers and any models that require provider data retention — before enabling it for regulated populations.
Disclaimer
This control is provided for informational purposes only and does not constitute legal, regulatory, or compliance advice. See full disclaimer.
Regulatory applicability
Regulatory citations identify commonly referenced requirements. Applicability, record classification, and retention periods are a firm and counsel determination; this framework does not assert that any regulation applies or is satisfied. See the Regulatory Applicability Questions appendix.
GA feature with fast-moving components
Microsoft 365 Copilot Cowork is generally available as of June 2026. Microsoft Learn currently states that local browser use moved from Frontier to general availability in August 2026, the current discovery setting is deprecated pending replacement, App skill remains Frontier, and model names changed again in September 2026. FSI organizations should re-verify feature status, access-request controls, model availability, Purview coverage, and tenant configuration before relying on this control in production governance.
Control Description
Cowork governance at GA centers on access gating (spending policies + the current discovery/request control), agentic-system inventory, model policy, browser-use policy, extensibility (plugins and custom skills via the Customize page), consumption oversight, usage reporting, and Purview integration. The primary governance surfaces are:
| Governance Surface | Primary Path | Governance Use |
|---|---|---|
| Access gate — spending policies | M365 Admin Center > Copilot > Cost management > Configuration | Grants Cowork access when a spending policy includes the user or group and selects Cowork as an agent/service; credit limits are spending safeguards, not a reliable access-denial control |
| Discovery/request setting (current deprecated control) | M365 Admin Center > Copilot > Settings > AI experiences enabled by usage-based billing | Current tenant-wide visibility and access-request control for Cowork and other usage-based experiences; Microsoft states this setting is deprecated and will be replaced by a user/group request-access control |
| Access request review | M365 Admin Center (admin notification workflow) | If discovery is on but billing is not set up for a user, the user can request access; admins should review requests against policy, cost, and compliance |
| Agentic system inventory surface | M365 Admin Center > Agents > All Agents > Cowork | Exposes Cowork as an agentic system for admin inventory and management context, but does not grant or block Cowork access at GA |
| Model policy — Anthropic family | M365 Admin Center > Copilot settings | Allows admins to turn off the Anthropic model family at the tenant level; verify the exact currently listed Cowork models on the current models page |
| Model policy — provider data-retention review | M365 Admin Center > Copilot settings | Review the models listed on the current Cowork models page and Anthropic data-retention guidance; verify current model names, provider, retention behavior, preview flags, and tenant toggle state before enabling regulated use |
| Browser-use tenant toggle | M365 Admin Center > Copilot > Settings > View All > Cowork settings > Allow browser access | The Cowork Browsing capability is disabled by default; admins enable "Allow Cowork to use the Microsoft Edge browser to perform tasks on behalf of users" only after browser, Edge policy, Conditional Access, DLP, and audit review |
| Consumption visibility and limits | M365 Admin Center > Copilot > Cost management | Shows Cowork consumption (model responses, tools/skills, image generation, browser tasks) and supports per-user or per-group consumption limits |
| Cowork usage reporting | M365 Admin Center > Copilot > Cowork > Overview / Usage / Value / Settings | Provides Cowork-specific adoption, task, retention, assisted-hours, and settings views; the Value tab is part of the Frontier preview program and should be treated as preview evidence |
| Plugin governance | M365 Admin Center > Integrated apps / plugin availability controls | Controls which Microsoft 365 App Store plugins (Microsoft and partner) extend Cowork, deployment scope, and connector authentication |
| Custom skill governance | Cowork > Customize > Skills | Governs user-authored and uploaded custom skills, including guided-builder, .md/.zip/.skill uploads, and skill sharing |
| Uploaded plugin packages | Cowork > Customize > Plugins | Governs uploaded plugin packages (for example, converted Claude packages) and their sharing scope |
| Purview integration | Microsoft Purview portal | Dedicated Purview for Cowork guidance lists supported capabilities for Cowork AI interactions. As of this verification, sensitivity labels, audit, communication compliance, eDiscovery, insider risk, and retention are documented; DLP is not listed as supported for Cowork AI interactions, while the M365 roadmap lists DLP for Cowork as preview/GA rollout. Verify in your tenant. |
| App-runtime follow-on surface | Copilot Managed Runtime (preview) / M365 Admin Center > Apps > All apps | If Cowork's App skill is used, the resulting app runs in Copilot Managed Runtime and should be reviewed under its separate preview governance surface |
| Data residency | Follows the Microsoft 365 Copilot data residency model | No separate Cowork residency configuration; residency is governed by the tenant's Copilot residency posture |
Access Model at GA
At GA, Cowork exposure is a combination of two independent settings:
| Setting | Effect |
|---|---|
| Spending policy selects Cowork for a user/group | The specified users can use Cowork; consumption counts against the tenant's Copilot Credits. Microsoft Learn states a very low credit limit still grants access until limit enforcement catches up. |
| Current discovery/request setting enabled (no Cowork-selecting policy) | Users can see Cowork and submit an access request; they cannot use Cowork until an admin grants access through a spending policy. |
| Discovery off, no Cowork-selecting policy | Cowork is not visible to users and cannot be requested. |
| Discovery off, Cowork-selecting policy applies | Users in scope of the spending policy can access Cowork even when discovery is off; spending-policy scope overrides discovery visibility for access. |
For FSI, the recommended posture during initial adoption is to create a Cowork-selecting spending policy only for an approved pilot group and to keep tenant-wide discovery off so Cowork is not surfaced to the wider workforce before governance is complete. Do not use a one-credit or low-credit tenant-wide policy as an access block; Microsoft Learn treats that as an access grant.
Agentic, Model, Browser, and Data-Access Considerations
Cowork performs multi-step work and retrieves content the user is already permitted to access. It does not grant new permissions, but it can surface and act on existing content more efficiently, which makes the quality of underlying access governance more consequential. Cowork is now documented as an agentic system under Agents > All Agents > Cowork, but that surface is no longer the access control path at GA; spending policies remain the access gate. Cowork model names and availability change quickly. Admins may turn off the Anthropic model family through Copilot settings if organizational policy requires it. Review the models listed on the current Choose a model for Cowork page and the associated data-retention guidance, then verify current model names, preview flags, provider, retention behavior, and tenant toggle state before enabling regulated use.
Local browser use runs in the user's local Microsoft Edge browser using their existing sign-ins and inherits organizational Conditional Access, Microsoft Purview DLP, browser management policy, and any site allow/block/view-only rules already in force. Cowork records each browser task it starts on a user's behalf in the unified audit log alongside other Cowork activity. Because sessions, cookies, and credentials stay on the user's device, the agent's reach is bounded by what the user could reach manually — no more and no less.
Cowork follows the Microsoft 365 Copilot data residency model; there is no separate Cowork residency configuration. Microsoft Purview supports securing and governing Cowork per the Purview for Cowork guidance. Organizations should confirm current data-handling, residency, and compliance behavior against Microsoft documentation on an ongoing basis as GA capabilities evolve.
Copilot Surface Coverage
| Surface | Coverage | Notes |
|---|---|---|
| Microsoft 365 Copilot on the web | Full | Cowork is used at https://copilot.cloud.microsoft; the Customize page (skills + plugins) and browser use are hosted here |
| Microsoft 365 Copilot desktop app | Partial | Cowork is available; local browser tasks are not run from the desktop app and are routed to the web experience |
| Microsoft 365 Copilot mobile app (iOS/Android) | Partial | Cowork is available on mobile; browser use is not supported on mobile |
| Local Microsoft Edge browser | Full | Microsoft Learn states local browser use moved from Frontier to GA in August 2026. Cowork Browsing runs in the user's local Edge, inheriting Conditional Access, Microsoft Purview DLP where applicable, browser policy, and site allow/block/view-only rules. |
| Microsoft 365 App Store plugins | Full | Microsoft plugins (for example, Dynamics 365 Customer Service, Sales, ERP, Fabric IQ) and partner connectors (for example, Jira, Salesforce, ServiceNow, SAP ERP, Workday HCM, Zendesk) extend Cowork and are governed through admin plugin controls |
| Uploaded and shared skills/plugin packages | Full | Custom skills and uploaded plugin packages are governed through Cowork's Customize page and the tenant's extensibility posture |
Governance Levels
Baseline
- Document the tenant's Cowork access posture: which users/groups are in a spending policy that selects Cowork, the state of the current discovery/request setting, and the approval basis for both decisions
- Restrict initial Cowork access to an approved pilot security group rather than the whole tenant
- Keep tenant-wide discovery off during the pilot so Cowork is not surfaced to users who are not yet in scope
- Keep the Cowork Browsing local-browser toggle off until browser use is reviewed under this control and Control 4.1
- Document the Anthropic model-family posture and do not enable any model with provider data-retention implications for regulated data unless legal, privacy, and compliance have reviewed and approved the use
- Maintain an inventory of which Cowork plugins (Microsoft and partner) are available and who approved them
- Document the initial per-user or per-group consumption limit and the approval basis
Recommended
- Manage Cowork spending-policy scope, the current discovery/request setting, model toggles, browser-use toggle, and consumption limits through a documented change register
- Separate approval and implementation so the same person does not both authorize and enable Cowork changes
- Review Cowork plugin availability, uploaded plugin packages, custom skills, and their sharing scope periodically against the approved inventory
- Route access requests received in the admin center through a documented approval workflow (policy, cost, and compliance review)
- Confirm that Cowork activity (including browser tasks and Purview-recorded interactions) is captured by existing audit and supervision tooling, and document any coverage gaps
- Coordinate Cowork rollout decisions with Copilot readiness and data-protection controls to limit oversharing exposure
Regulated
- Require dual approval (technology + compliance) before enabling Cowork spending-policy access, discovery, browser use, or Anthropic/model controls for any regulated or client-facing population
- Treat Cowork outputs that influence client communications or recordkeeping as in-scope for supervisory review under FINRA Rule 3110, where applicable
- Verify that Cowork-generated outputs subject to retention obligations are captured by existing books-and-records and retention controls
- Restrict Cowork administration using time-bound privileged access (PIM or equivalent) and least-privilege AI Administrator / M365 Global Admin roles
- Prohibit or explicitly document any use of models that require provider data retention for regulated data, using current Microsoft Learn model names and retention disclosures
- Preserve billing scope, discovery setting, model-toggle, browser-toggle, plugin/skill inventory, and consumption-limit evidence for examination-ready retention periods
- Maintain a documented exception register for any deviation from the approved Cowork governance baseline
Setup & Configuration
Step 1: Confirm the access posture (billing + discovery)
Navigate to M365 Admin Center > Copilot > Cost management > Configuration and record which spending policies select Cowork and which users or groups are in scope. Then navigate to M365 Admin Center > Copilot > Settings > AI experiences enabled by usage-based billing and record whether the current discovery/request setting is on. Microsoft now documents this setting as deprecated and slated for replacement, so also record any tenant guidance or process change for the future request-access control. Document the approver, the pilot scope, and the initial spending policy.
Step 2: Govern model toggles
In M365 Admin Center > Copilot settings, confirm the state and scope of the Anthropic model family control and any model-specific settings shown in the tenant. Review the models listed on the current Choose a model for Cowork page and the associated Anthropic data-retention guidance; do not rely on stale model names. Record the current model-toggle decisions, provider data-retention review, and approval basis.
Step 3: Govern the Cowork Browsing tenant toggle
Navigate to M365 Admin Center > Copilot > Settings > View All > Cowork settings > Allow browser access. Leave "Allow Cowork to use the Microsoft Edge browser to perform tasks on behalf of users" unchecked until browser use has been reviewed against Control 4.1, existing Conditional Access, Microsoft Purview DLP where applicable, browser management policy, Edge policy, and any tenant-wide site allow/block/view-only rules that should apply. Microsoft Learn states local browser use moved from Frontier to general availability in August 2026; still verify the tenant toggle, Edge version/policies, Conditional Access, DLP, and audit behavior before enabling it for regulated populations.
Step 4: Govern plugins and custom skills
Review the plugins available to Cowork through the admin plugin controls. Maintain an approved-plugin inventory covering Microsoft plugins and partner connectors, confirm connector authentication for any Dynamics 365 / Agent 365 integrations, and restrict plugin availability to approved populations. Coordinate with Control 4.13 (Extensibility Governance) on the Customize page (Cowork > Customize): user-created and uploaded custom skills (.md, .zip, .skill), uploaded plugin packages, and skill/plugin sharing scope.
Step 5: Set consumption limits and monitor spend
In Copilot > Cost management, set per-user or per-group consumption limits appropriate to the pilot's approved budget. Then review Copilot > Cowork > Usage for adoption, task mix, and retention trends, and use the Value tab only where the tenant participates in the Frontier preview program. Establish a review cadence so growth against the approved budget is visible before month-end. Align credit-consumption review to the classes Microsoft currently documents for Cowork consumption: model responses, tools/skills, image generation, and browser tasks.
Step 6: Confirm Purview, audit, and supervision coverage
Confirm Cowork is included in the tenant's Purview posture per the Purview for Cowork guidance. As of this verification, that guidance lists support for audit, sensitivity labels, insider risk, communication compliance, eDiscovery, and data lifecycle management for Cowork AI interactions, but does not list DLP as supported for Cowork AI interactions; the M365 roadmap lists DLP for Cowork as preview in September 2026 and GA in October 2026. If your organization enables the Cowork App skill, also review the current What is Copilot Managed Runtime (preview) guidance because Cowork-built apps run in that separate Microsoft-hosted runtime. Confirm browser task audit records are visible in the unified audit log, verify DLP rollout in your tenant, document any gaps, and define a review cadence for access posture, model toggles, browser toggle, plugin/skill inventory, and consumption reporting.
Financial Sector Considerations
Broker-dealers: Before enabling Cowork for registered representatives, have legal/compliance determine whether agentic outputs, browser-driven submissions, image generation, client communications, correspondence, or recordkeeping artifacts fall within the firm's supervisory and books-and-records procedures, including any FINRA Rule 3110 or SEC Rule 17a-4 analysis.
Banking institutions: Treat Cowork enablement and each subsequent expansion as a change-control and operational-risk assessment item; have risk/compliance determine whether FFIEC, GLBA §501(b), or OCC Heightened Standards evidence is required for the specific entity and workflow.
SOX-reporting entities: Where Cowork is used in finance, reporting, or control-support workflows, have the ICFR owner determine whether access-posture, model-toggle, and approval evidence belongs in the SOX §§302/404 evidence set.
Covered institutions under OCC Heightened Standards: Where applicable, have risk governance owners determine how Cowork adoption and third-party model-provider use should be reflected in the firm's 12 CFR part 30, appendix D governance evidence.
Fast-moving features: Cowork feature status changed after GA, including local browser use moving to GA, the current discovery setting being deprecated pending replacement, and model names changing again in September 2026. Organizations should avoid embedding newly released, Frontier, or tenant-unverified features in critical or unsupervised workflows and re-assess them each time Microsoft updates the status.
Verification Criteria
| # | Verification Step | Expected Result |
|---|---|---|
| 1 | Review Cowork access posture | Usage-based billing scope and the discovery-setting state are documented with an approver, and both match the approved pilot decision |
| 2 | Review access-request handling | Any user access requests are routed through a documented approval workflow with a policy, cost, and compliance review |
| 3 | Review model toggles | The Anthropic-family and any model-specific toggles visible in the tenant match documented decisions; any model with provider data-retention implications is disabled unless provider data retention has been reviewed and approved |
| 4 | Review the Cowork Browsing toggle | The Cowork Browsing tenant toggle is off, or is on only after a documented review of Conditional Access, DLP, browser policy, and site allow/block/view-only rules |
| 5 | Review Cowork plugin, uploaded package, and custom skill inventory | Available plugins, uploaded plugin packages, and custom skills (with their sharing scope) match an approved inventory |
| 6 | Review consumption limits and reporting | Per-user or per-group consumption limits match the approved budget; consumption reporting is reviewed on a documented cadence |
| 7 | Confirm Purview and audit coverage | Cowork is included in the tenant's Purview posture per the Purview for Cowork guidance; browser task events appear in the unified audit log, or gaps are documented with a remediation owner |
| 8 | Confirm review cadence | A documented frequency exists for reviewing access posture, model toggles, browser toggle, plugins/skills, and consumption reporting |
Additional Resources
- Manage Copilot Cowork for your organization
- What's new in Copilot Cowork
- Choose a model for Cowork
- Determine access controls for Copilot Cowork
- Manage plugins for Cowork
- Customize Cowork (skills and plugins)
- Use the local browser with Cowork
- Discovery setting for AI experiences enabled by usage-based billing
- Managing AI experiences enabled by usage-based billing (Copilot Credits)
- Copilot Cowork usage report
- Use Microsoft Purview to manage data security & compliance for Copilot Cowork
- What is Microsoft Copilot Managed Runtime (preview)
- Microsoft 365 Roadmap ID 570845 — Microsoft Purview Data Loss Prevention for Microsoft Cowork
- Data residency for Microsoft 365 Copilot
- Implementation Playbooks: Portal Walkthrough · PowerShell Setup · Verification · Troubleshooting
- Related Controls: 4.1 Admin Settings and Feature Management, 4.13 Extensibility Governance, 4.14 Copilot Studio Agent Lifecycle Governance