Control 2.14: Declarative and SharePoint Agents Governance
Control ID: 2.14 Pillar: Security & Protection Regulatory Reference: GLBA §501(b) Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Last Verified: 2026-09-29 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.
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.
Objective
Govern the creation, sharing, user access, and data boundary enforcement for declarative agents, with specific attention to SharePoint-backed agents and other agents surfaced through Microsoft 365 Copilot. This control focuses on the security guardrails that determine who can use agents, who can share them, and how agent access is limited to approved publishers, audiences, and knowledge sources.
Why This Matters for FSI
- GLBA §501(b) requires safeguards for customer information. Agents can accelerate access to site content, uploaded knowledge, and external tools, so security boundaries should be explicit.
- Agent proliferation risk increases when users can create or broadly share agents without governance approval.
- Data boundary enforcement matters because SharePoint-backed agents can expose sensitive site content to new audiences if permissions and sharing are not reviewed carefully.
- FFIEC and OCC AI governance expectations support maintaining oversight of who can use AI tools, how those tools are shared, and what data they can access.
Control Description
Microsoft 365 now exposes agent governance through the Agents control plane in the Microsoft 365 admin center. Security decisions for agents are no longer limited to the original SharePoint agent creation flow. Administrators can now review agent inventory, restrict allowed agent types, control sharing, scope user access, manage feedback sharing, and manage tags through centralized settings. See Agent settings in Microsoft 365 admin center.
Agent 365 as a Centralized Governance Surface
In addition to the Agents section in the M365 Admin Center, Agent 365 provides a centralized governance hub that spans agents across M365 apps, Copilot Studio, and third-party integrations. Agent 365 consolidates agent inventory, usage analytics, and lifecycle management into a single platform, providing:
- Unified registry of all agent types — Microsoft, organization-published, partner, Copilot Studio, and third-party
- Cross-platform telemetry including session counts, active users, exception rates, and runtime metrics
- Centralized policy controls for allowed types, sharing, user access, and templates
- Governance action cards that highlight ownerless agents, pending requests, and policy gaps
For security teams, Agent 365 provides a single evidence source for agent inventory, ownership, and usage that supports FFIEC and OCC examination preparation. Organizations should incorporate Agent 365 review into their agent governance workflow alongside the existing M365 Admin Center Agents controls.
For connected-platform agents, treat Agent 365 inventory as current only through the latest completed Sync agents run on Connected platforms. Microsoft currently documents synchronization as a manual administrative action, and observability capabilities vary by platform.
Agent 365 control-plane and agent-identity governance are authoritative in FSI-AgentGov. This control governs the Copilot-surface security guardrails for declarative and SharePoint agents — who can use, share, and access agents that appear in the Microsoft 365 Copilot experience, configured through the M365 admin center Agents control plane. The deeper Agent 365 control-plane configuration (management rules, registry sync, agent map) and agent identity governance are specified in FSI-AgentGov Control 2.25 — Agent 365 Admin Center Governance Console and FSI-AgentGov Control 2.26 — Entra Agent ID Identity Governance. Consume and cross-reference those controls rather than re-specifying control-plane mechanics here.
Agent Management Rules and Policy Templates
The Microsoft 365 admin center currently exposes five Agent management rules actions:
- Install Microsoft agents
- Reassign ownerless Agent Builder agents to manager
- Block ownerless agents without usage
- Apply a template to agents
- Reject publish requests older than a specified number of days
These product actions should not be replaced with inferred rule types such as publisher allowlisting, generic ownership requirements, lifecycle policies, or sharing-scope rules. Publisher categories, sharing, and user access are separate settings in the Agents control plane.
Policy templates remain relevant for applying predefined security policies to new agents. Separately, the Apply template management-rule action applies a preexisting or custom template to eligible existing published agents at scale. Administrators define criteria, select the template, review all eligible agents or a subset, and run the rule. The action evaluates Registry agents that have an agent identity; it does not apply to agent blueprints or AI teammates, and it is a one-time bulk operation rather than a scheduled rule.
Consistent with the authority boundary above, use FSI-AgentGov Controls 2.25 and 2.26 for the normative control-plane and agent-identity requirements. This control records only the technical distinction needed to avoid treating templates as universal or continuously scheduled enforcement.
Agent Map
The Agent Map in the Microsoft 365 admin center provides a visual inventory of tenant agents grouped by platform or builder, with filters such as status, publisher type, platform, channel, data source, and usage where supported. Summary cards help administrators focus on agents at risk, agents without owners, and unmanaged agents. The Single Agent Map preview can show user and tool connections for one selected agent based on Agent 365 observability data, but Microsoft Learn states that knowledge signals are not included yet.
FSI application: Agent Map helps institutions identify governance gaps such as ownerless, unmanaged, inactive, or high-risk agents, and the Single Agent Map preview can support investigation of selected-agent user activity and tool-call exceptions. Do not use Agent Map as evidence that agents share the same knowledge source, or that an agent is orphaned because of stale knowledge-source updates, unless a tenant export or future Microsoft source explicitly provides that signal.
Ownerless Agent Remediation
When Agent 365 identifies agents without a designated owner (due to owner departure, role change, or agent creation without explicit ownership):
- Agent 365 surfaces ownerless agents in the governance action cards dashboard
- Administrators should reassign ownership within a defined SLA (recommended: 5 business days for standard agents, 48 hours for agents with access to sensitive data)
- Agents that remain ownerless beyond the SLA should be disabled pending reassignment
- Document ownership reassignment decisions in the agent governance registry
Stakeholder Oversight Model
For regulated FSI environments, agent governance should follow a stakeholder oversight model:
| Stakeholder | Responsibility | Review Cadence |
|---|---|---|
| Agent owner (business line) | Maintains agent knowledge sources, validates accuracy, manages user access | Continuous |
| IT security | Reviews agent permissions, knowledge-source sensitivity, action capabilities | Quarterly or on change |
| Compliance | Validates agent outputs against regulatory requirements (FINRA 2210, supervisory obligations) | Quarterly |
| Internal audit | Independent review of agent governance controls and registry completeness | Annual |
Entra Agent ID
Microsoft Entra ID now assigns unique identities to Copilot agents through Entra Agent ID. Each agent receives a distinct Entra identity object that enables:
| Capability | Security Benefit |
|---|---|
| Identity assignment | Agents are identifiable as distinct security principals in Entra ID |
| Audit attribution | Agent activity is traceable in Entra sign-in and audit logs |
| Conditional Access | Agents can be scoped by Conditional Access policies to control operational context |
| Compliance tracking | Per-agent compliance attribution in Purview audit trails |
Organizations should verify that Entra Agent ID is enabled for governed agents and that Conditional Access policies are reviewed to account for agent identities alongside human user identities. Microsoft Learn states that Microsoft Entra Agent ID is available for Microsoft Entra customers, that extending Entra security features to agents requires Microsoft Agent 365, and that Conditional Access for agents requires Microsoft Entra ID P1 or P2 plus a Microsoft Agent 365 license for each user, with Agent 365 license enforcement "coming soon." Treat licensing and enforcement as tenant evidence items before representing Conditional Access as active for agents. See What is Microsoft Entra Agent ID and Conditional Access for agents.
Purview AI App Taxonomy and Pillar 2 Control Mapping
Microsoft Purview classifies AI applications into categories within the DSPM AI app catalog, enabling governance policies to be applied by app type rather than individually. The following matrix maps Purview AI app categories to Pillar 2 security controls and Agent 365 governance support:
| Purview AI App Category | Applicable Pillar 2 Controls | Agent 365 Support | Governance Action |
|---|---|---|---|
| Microsoft 365 Copilot (first-party) | 2.1 (DLP), 2.2 (sensitivity labels), 2.9 (Defender/MDCA), 2.10 (insider risk) | Full — unified registry, telemetry, policy controls | Apply standard Copilot governance stack; monitor via DSPM Activity Explorer |
| Copilot Studio agents (organizational) | 2.13 (plugin security), 2.14 (agent governance), 2.16 (MCP/connectors) | Full — visible in Agent 365 registry with ownership, usage analytics | Require Agent 365 registry enrollment and evaluate applicable policy templates; the Apply template action covers only Registry agents with an agent identity |
| Third-party AI apps (sanctioned) | 2.9 (Defender Cloud Apps catalog), 2.7 (data residency), 2.13 (connector security) | Partial — visible in inventory, limited policy enforcement | Manage via MDCA generative AI app catalog; apply DLP at the response layer |
| Shadow AI apps (unsanctioned) | 2.9 (Defender discovery and blocking) | None — not registered in Agent 365 | Block via MDCA app governance policies; escalate to compliance |
| SharePoint agents (auto-created) | 2.14 (agent governance), 2.5 (grounding scope) | Full — visible in Agent 365 and SharePoint admin center | Inherit site permission governance; disable on sensitive sites |
| External partner agents | 2.14 (agent governance), 2.17 (cross-tenant federation), 2.7 (data residency) | Partial — visible in registry, limited telemetry | Require third-party risk assessment per OCC Bulletin 2023-17 |
Compliance Manager AI Templates
Microsoft Purview Compliance Manager includes premium AI assessment templates that map AI governance requirements to regulatory frameworks. Organizations should evaluate these templates as an evidence management complement to the controls in this framework:
| Template Category | Coverage | FSI Application |
|---|---|---|
| AI Risk Management | Maps AI governance controls to NIST AI RMF, ISO 42001, and EU AI Act requirements | Provides structured assessment evidence for AI governance readiness |
| Copilot-specific assessments | Maps Copilot data handling, privacy, and security controls to regulatory requirements | Supports examination readiness by providing pre-built assessment workflows for Copilot governance |
| Industry-specific AI | Templates customized for financial services AI compliance (where available) | Aligns Copilot governance with FSI-specific regulatory expectations |
Organizations should review available Compliance Manager AI templates in Microsoft Purview > Compliance Manager > Regulations and assess whether template-based assessments complement or overlap with the controls documented in this framework. Compliance Manager assessment results can serve as examination-ready evidence alongside the verification criteria defined in each control.
Agent Types Relevant to CopilotGov
| Agent Type | Security Consideration | Primary Governance Surface |
|---|---|---|
| Published by your organization | Broad availability requires approval and ownership | Agents > All agents / Registry |
| Shared by creator | Creator-shared agents can spread quickly without central review | Agents > All agents / Sharing controls |
| Microsoft agents | First-party experiences require access decisions and usage oversight | Agents > Settings > Allowed agent types |
| External partner agents | External publishers may introduce new data handling terms or integrations | Agents > Settings > Allowed agent types |
| SharePoint-backed agents | Ground on SharePoint sites and therefore inherit site-permission risk | Agents + SharePoint admin center |
Central Security Controls
| Control | Description | Admin Configuration |
|---|---|---|
| Allowed agent types | Controls which classes of agents users can install | Agents > Settings > Allowed agent types |
| Agent management rules | Runs one of the supported bulk actions; Apply template is one-time and limited to Registry agents with an agent identity | Agents > Settings > Agent management rules |
| Security templates (policy templates) | Defines reusable security policies for new agents; eligible existing published agents can receive a template through the separate Apply template action | Agents > Settings > Security templates |
| Sharing | Controls who can share Agent Builder agents broadly in the organization | Agents > Settings > Sharing |
| User access | Limits who can use agents at all | Agents > Settings > User access |
| Agent feedback sharing and tags | Controls whether developers receive agent feedback and how admins/users label agents for discovery and organization | Agents > Settings > Agent feedback sharing / Tags |
| Registry review | Tracks published, shared, blocked, or ownerless agents | Agents > All agents / Registry |
| Knowledge source review | Validates SharePoint sites, embedded files, and external data sources | SharePoint admin center, Agent details, Search / connector review |
| Agent pinning | Pin up to 3 agents per user so they appear prominently in the Copilot experience | M365 Admin Center > Copilot > Agents > Manage pinned agents |
Agent Pinning Governance
Administrators can pin up to 3 agents per user via the M365 Admin Center, causing those agents to appear prominently in the user's Copilot experience. Pinning is a governance tool for promoting sanctioned agents and guiding users toward approved AI workflows.
| Aspect | Detail |
|---|---|
| Portal | M365 Admin Center > Copilot > Agents > Manage pinned agents |
| Maximum pinned agents | Up to 3 per user |
| Pin sources | Microsoft-pinned (by Microsoft), admin-pinned (by the organization), user-pinned (by the user) |
| User removal | Users cannot remove Microsoft-pinned or admin-pinned agents from their pinned list |
| Eligibility | Only deployed, non-blocked agents can be pinned |
| Targeting | Pinning can target everyone in the organization, specific Entra ID security groups, or individual users |
FSI governance considerations:
- Promote sanctioned agents: Use pinning to ensure that compliance-approved agents (e.g., policy lookup, trade documentation assistants) are immediately visible to relevant user populations
- Document pinning decisions: Maintain a record of which agents are pinned, the target audience, and the business justification for each pinning decision
- Coordinate with agent registry: Pinned agents should appear in the agent governance registry (see Step 3 above) with documented ownership and approval status
- Review cadence: Include pinned agent assignments in the quarterly agent governance review to verify that pinned agents remain appropriate and actively maintained
Researcher and Analyst Nuance
Microsoft documents Researcher and Analyst as first-party experiences within the core Microsoft 365 Copilot chat experience. They coexist with agents and inherit related governance capabilities, but they do not fall under installable agent settings in the same way as Registry-managed agents. Document them as Copilot Chat capabilities when defining access policy and supervision requirements.
Agent Risk Assessment Matrix
| Risk Factor | Low Risk | Medium Risk | High Risk |
|---|---|---|---|
| Publisher | Microsoft | Internal approved creator | External partner or unreviewed creator |
| Knowledge source | Public intranet or non-sensitive content | Department knowledge | Client data, regulated records, or uploaded files with sensitive content |
| Sharing scope | Creator only or named users | Department | Organization-wide or cross-functional |
| Allowed users | Approved pilot group | Documented business group | Broad tenant access without governance review |
| Web / action capability | Disabled or limited | Approved business use | External or high-impact actions without control evidence |
| Model provider | Microsoft (Azure OpenAI) | Microsoft with custom configuration | Third-party model provider (external inference, data residency, and model governance considerations) |
Copilot Surface Coverage
| M365 Surface | Agent Access | Security Governance Notes |
|---|---|---|
| Microsoft Copilot Chat | Yes | Primary user experience for many agents |
| Teams | Yes | Review alongside collaboration and supervision controls |
| SharePoint | Yes | Important for SharePoint-backed agent knowledge scope |
| Copilot Pages | Indirect | Agent responses can create Pages; align with Control 2.11 |
| Word / Excel / PowerPoint / Outlook | Limited / varies | Review by scenario and agent type |
Governance Levels
| Level | Requirement | Rationale |
|---|---|---|
| Baseline | Restrict agent user access to approved users or groups; allow only approved agent types; review Registry inventory monthly; review SharePoint knowledge sources before publication | Minimum control over who can use and share agents |
| Recommended | All Baseline requirements plus: group-based sharing rules, documented owner for each published agent, quarterly source-site review for SharePoint-backed agents, formal approval workflow for broader publication | Balanced production governance for most FSI deployments |
| Regulated | All Recommended requirements plus: compliance review for high-risk or client-data agents, documented exception process for external or broadly shared agents, monthly registry review, evidence retained for examination support | Stronger security posture for regulated or segmented environments |
Setup & Configuration
Step 1: Configure Agent User Access
Portal: Microsoft 365 Admin Center
Path: Agents > Settings > User access
- Choose All users, No users, or Specific users/groups.
- For FSI deployments, prefer approved user or group scoping over broad default access.
- Document the approved audiences and the associated business justification.
Step 2: Configure Allowed Agent Types and Sharing
Portal: Microsoft 365 Admin Center
Path: Agents > Settings > Allowed agent types / Sharing / Agent feedback sharing / Tags
- Decide whether Microsoft, internal, and external agents are permitted.
- Restrict broad sharing to approved groups where required.
- Decide whether developers receive tenant feedback for all agents, no agents, or only selected agents.
- Manage tags deliberately so discovery labels stay consistent; Microsoft currently allows up to 50 tags, and deleting a tag removes it from every agent that uses it.
- Document how creator-shared agents are reviewed before broader use.
Step 3: Review Agent Registry
Portal: Microsoft 365 Admin Center
Path: Agents > All agents / Registry
- Review published, shared, blocked, and ownerless agents.
- Confirm each broadly available agent has an owner and approval record.
- If supported third-party platforms are connected, open Connected platforms > Manage and verify the latest manual Sync agents run before treating the Registry as a complete cross-platform inventory.
- Block or remove agents that do not meet policy.
Step 4: Review SharePoint-Backed Knowledge Sources
Portal: SharePoint admin center and agent details
- Review source sites or uploaded knowledge used by high-risk agents.
- Confirm permissions, labels, and sharing posture are appropriate.
- Cross-reference Control 1.2 for oversharing remediation and Control 2.5 for grounding scope decisions.
Step 5: Establish Security Review Workflow
- Define who reviews new agents before broader publication.
- Require extra review for:
- client-data or regulated-content agents
- external partner agents
- agents with embedded file knowledge
- Record approval, owner, and review cadence for each governed agent.
Financial Sector Considerations
- Client-data agents: Agents grounded on client or account content should undergo stronger review than general knowledge assistants.
- Publisher trust: External partner agents require review of data handling, privacy terms, and operational dependency.
- SharePoint oversharing: A well-designed agent still inherits risk from an overshared source site. Security review should include the underlying content boundary.
- Research and analysis workflows: If Researcher or Analyst are enabled for high-risk business functions, document that decision in Copilot governance even though those tools are not managed like Registry-installed agents.
Verification Criteria
- User access scoped: Verify agent access is limited to the approved users or groups.
- Allowed types configured: Confirm allowed agent types match the institution's policy.
- Sharing rules configured: Verify broad agent sharing is limited or approved.
- Registry inventory current: Confirm published and shared agents are inventoried and owned.
- SharePoint source review completed: Confirm high-risk agents have documented knowledge-source review.
- Exception handling documented: Verify any external or high-risk agent exceptions have approval evidence.
Additional Resources
- Manage agents in the Microsoft 365 admin center
- Agent settings in Microsoft 365 admin center
- Agent Registry in the Microsoft 365 admin center
- Connected platforms in Microsoft Agent 365
- Declarative agents for Microsoft 365 Copilot
- Related Controls: 1.13 Extensibility Readiness, 2.5 Data Minimization, 2.13 Plugin Security, 4.13 Extensibility Governance