Skip to content

Control 1.7: Comprehensive Audit Logging and Compliance

Control ID: 1.7 Pillar: Security Regulatory Reference: FINRA 4511, SEC 17a-3/4, SOX 302/404, GLBA 501(b) Last UI Verified: February 2026 Governance Levels: Baseline / Recommended / Regulated Last Verified: 2026-02-03

Agent 365 Architecture Update

Agent 365 Observability consolidates agent activity logs from all platforms into Application Insights using the OpenTelemetry standard. This simplifies eDiscovery, regulatory reporting, and examination evidence collection by providing a unified audit trail. See Unified Agent Governance for observability architecture and audit trail consolidation details.

Objective

Implement comprehensive audit logging to capture Microsoft 365 Copilot and Copilot Studio agent interactions, providing an evidence trail for regulatory examinations, security investigations, and compliance monitoring. For broker-dealers, this includes guidance supporting SEC 17a-4(f) compliance through either WORM storage or the audit-trail alternative (per October 2022 amendments, effective May 2023).

Why This Matters for FSI

  • FINRA 4511: Requires retention of books and records per regulatory timelines. The FINRA 2026 Annual Regulatory Oversight Report emphasizes that firms must retain not just agent outputs but also prompts, model state, and reasoning chains to enable reconstruction of how the agent reached its conclusion.
  • SEC 17a-4(b)(4): Communications records require 3-year retention (first 2 years readily accessible)
  • SEC 17a-4(a): Financial/accounting records require 6-year retention
  • SEC 17a-3/4: Record retention for AI-assisted communications; broker-dealers may require WORM storage
  • SOX 302/404: Internal controls over AI system logging require audit trails
  • GLBA 501(b): Security safeguards including audit trails for data access

Updated February 2026

FINRA 2026 examination priorities include validation that AI agent logs support complete decision reconstruction, not just output capture.

Agent Logs Are Typically Communications

Agent conversation logs (prompts, responses, interactions) typically qualify as communications under SEC 17a-4(b)(4), requiring 3-year retention, not the 6-year financial records period. If agent interactions generate or modify financial records, those outputs follow the applicable 6-year period.

Control Description

Microsoft Purview Audit provides comprehensive logging of user and admin activities across Microsoft 365, including Microsoft 365 Copilot and agent interactions. Audit logs are essential for compliance monitoring, security investigations, and regulatory examinations.

Capability Description
Unified audit log Single log for all M365 activities including Copilot
Agent activity logging Captures agent creation, publishing, modification, and interactions
Extended retention Up to 10 years with Audit Premium
Search and export Advanced query and export for investigations
SIEM integration Export to Sentinel or third-party SIEM

AI-Generated Communication Tagging (Anticipated per FINRA Notice 25-07 RFI)

FINRA Notice 25-07 Status

FINRA Regulatory Notice 25-07 (April 2025) is a Request for Comment (RFI) on recordkeeping for AI-generated communications, not final guidance. The framework anticipates expected requirements based on the RFI direction. Monitor for final rule publication.

The RFI addresses recordkeeping requirements for AI-generated communications, proposing that firms distinguish AI-generated communications from human-generated content in their records. Audit logging supports this by:

Requirement Implementation
AI Origin Tagging CopilotInteraction events contain ApplicationId identifying Copilot/agent source
Prompt/Response Pairs Full prompt and response captured via DSPM for AI (Control 1.6)
Human vs AI Attribution Audit logs distinguish UserId (human initiator) from AgentId (AI responder)
No Summary Storage Complete verbatim content retained per anticipated 25-07 requirements (no truncation/summarization)
Modification Tracking If human edits AI output before sending, both versions should be retained

Audit Event Types (RecordType values in OfficeActivity table):

  • CopilotInteraction - M365 Copilot interactions (prompts, responses, accessed resources)
  • ConnectedAIAppInteraction - Connected AI app interactions (e.g., Copilot Studio agents, third-party AI apps)
  • AIAppInteraction - AI app interaction events (AI assistance in document creation, AI-powered features)

Agent-Specific Audit Properties (CopilotInteraction schema):

Property Description Use Case
AgentId Unique identifier for the agent involved Agent-level activity correlation
AgentName Display name of the agent Human-readable identification
AgentVersion Version of the agent at interaction time Change tracking and regression analysis
JailbreakDetected Boolean flag if jailbreak attempt detected Security monitoring, UPIA detection
XPIADetected Boolean flag if cross-domain prompt injection detected Security monitoring, XPIA detection
ModelTransparencyDetails Model information (name, version, provider) Model risk management (OCC 2011-12)

Audit Schema Captures Metadata, Not Full Content

The CopilotInteraction audit schema captures interaction metadata (message IDs, timestamps, model info, detection flags, accessed resources), not the actual prompt and response text. To retrieve full conversation content, use:

  • eDiscovery tools (Control 1.19) - For legal hold and investigation
  • DSPM for AI (Control 1.6) - For data security monitoring and content review
  • Communication Compliance (Control 1.10) - For policy-based content review

This distinction is critical for compliance design: audit logs provide the evidence trail; eDiscovery/DSPM provides content retrieval.

Querying AI Audit Events

These are RecordType values, not table names. Query via the OfficeActivity table in Log Analytics or use Search-UnifiedAuditLog PowerShell cmdlet with the -RecordType parameter.

Key Configuration Points

Tenant-Level Audit Configuration

  • Enable unified audit logging at tenant level
  • Configure retention policies per governance tier (180 days to 10 years)
  • Search for agent-related activities: CopilotInteraction, AgentPublished, ConnectorAdded
  • Export logs regularly for WORM storage (broker-dealers)
  • Integrate with SIEM for real-time monitoring (Zone 2-3)
  • Retain complete prompt/response pairs per anticipated FINRA 25-07 requirements (no summaries)
  • Implement adversarial pattern detection in audit log analysis

Dataverse Purview Audit Event Changes — May 2026

Starting May 2026, Dataverse will no longer include before-and-after field change values in audit events sent to Microsoft Purview. Organizations requiring detailed field-level change data for regulatory recordkeeping should retrieve this data directly from Dataverse APIs.

This change may affect SEC 17a-4 / FINRA 4511 compliance programs that rely on Purview audit integration for Dataverse field-level change records. Organizations should begin transitioning to Dataverse API-based audit retrieval before May 2026.

See Regulatory Mappings for detailed regulatory impact on recordkeeping requirements.

Dataverse Environment-Level Audit Configuration

  • Enable environment-level auditing: In Power Platform Admin Center, select each environment > Settings > Audit and logs > enable "Start Auditing" to capture Dataverse entity changes, user sign-ins, and security events
  • Configure audit log retention period: In PPAC > Environment > Settings > Audit and logs > Audit settings > set "Retain these logs for" to a minimum of 180 days (Zone 1), 365 days (Zone 2), or 730+ days (Zone 3). Select "Custom" for specific day counts or "Forever" for indefinite retention
  • Enable tenant-level Dataverse auditing policy: In PPAC > Security > Compliance > Auditing > enable "Turn on Auditing" and additionally enable "User Sign-In" and "Activity" checkboxes to capture sign-in events and entity-level activity across all Dataverse environments

Zone-Specific Requirements

Zone Requirement Rationale
Zone 1 (Personal) Baseline logging; 180-day retention; monthly review Low risk, standard coverage
Zone 2 (Team) 1+ year retention; weekly review; SIEM recommended Shared agents require accountability
Zone 3 (Enterprise) 7-10 year retention; daily review; WORM storage if broker-dealer; SIEM required Highest regulatory risk; 10 years recommended per framework

Roles & Responsibilities

Role Responsibility
Purview Audit Admin Configure audit logging and retention policies
Purview Compliance Admin Search and export audit logs for examinations
AI Administrator Review Copilot audit events and AI interaction logs
Security Operations SIEM integration and monitoring
Azure Administrator WORM storage configuration (if applicable)
Control Relationship
1.6 - DSPM for AI AI interaction visibility
1.19 - eDiscovery Legal discovery
3.2 - Usage Analytics Activity monitoring
3.9 - Sentinel Integration SIEM integration

Automated Validation: Deny Event Correlation Report

For daily operational reports correlating deny events across Purview Audit, DLP, and Application Insights with anomaly detection and zone-based alerting, see the Deny Event Correlation Report solution.

Capabilities:

  • Multi-source deny event extraction (RAI telemetry, Purview Audit, Purview DLP)
  • Daily correlation engine with 7-day trend analysis and volume anomaly detection
  • Zone-based alerting with Teams adaptive cards and email notifications
  • Dataverse persistence with zone-based retention (90d/365d/730d)
  • SHA-256 integrity-hashed evidence export with regulatory alignment mapping

Deployable Solution: deny-event-correlation-report provides PowerShell extraction scripts, Dataverse infrastructure, Power Automate orchestration flow, and evidence export pipeline.

Automated Validation and Remediation: Audit Compliance Manager

For automated validation of tenant and environment audit configurations, drift detection, and approval-gated remediation of audit logging gaps, see the Audit Compliance Manager (ACM) solution.

Capabilities:

  • Tenant-level audit validation (Unified Audit Log, mailbox audit, Purview retention)
  • Environment-level audit validation (Power Platform audit retention)
  • Zone-based retention thresholds (180d/365d/730d)
  • Daily scheduled validation with drift detection and SHA-256 evidence hashing
  • Automated detection of Purview unified audit and Dataverse audit status across all environments
  • Remediation with org-level and entity-level Dataverse audit enablement (6 Copilot Studio entities)
  • WhatIf simulation for safe remediation dry runs
  • Power Automate approval workflow for governance-gated remediation
  • Compliance tracking via Dataverse upsert pattern (one record per environment)
  • Enterprise-grade Managed Identity authentication

Deployable Solution: audit-compliance-manager provides PowerShell validation scripts, Azure Automation runbooks with Managed Identity auth, Dataverse compliance tracking, Power Automate flows for validation and approval-gated remediation, and evidence export pipeline.

Implementation Playbooks

Step-by-Step Implementation

This control has detailed playbooks for implementation, automation, testing, and troubleshooting:

Advanced Implementation: Configuration Hardening Baseline

This control is covered by the Configuration Hardening Baseline, which consolidates SSPM-detectable settings across all 7 mapped controls into a single reviewable checklist with automation classification and evidence export procedures.

Verification Criteria

Confirm control effectiveness by verifying:

  1. Unified audit logging is enabled (Get-AdminAuditLogConfig shows enabled)
  2. Copilot and agent events appear in audit search results
  3. Retention policies are configured per governance tier
  4. Export capability produces complete audit records
  5. SIEM integration is functional (logs streaming to Sentinel)
  6. WORM storage is configured for broker-dealer environments (if applicable)
  7. Dataverse environment-level auditing is enabled (PPAC > Environment > Audit and logs > "Start Auditing" is on) for all environments
  8. Audit log retention is set to minimum 180 days per environment (PPAC > Environment > Audit settings > "Retain these logs for")
  9. Tenant-level Dataverse auditing policy is enabled with User Sign-In and Activity logging (PPAC > Security > Compliance > Auditing)

Additional Resources

Regulatory Guidance:

Microsoft Documentation:

Microsoft Audit Reporting Tools

For enterprise-scale audit data export beyond native portal limits, see:

Environment Provisioning Audit Trail

For immutable audit logging of environment provisioning activities:

Agent 365 Audit Events (Preview)

Note: The following resources are preview documentation and may change.

Agent 365 SDK introduces additional audit event types for Blueprint-registered agents:

Event Type Description Logged When
BlueprintRegistration Agent registered via Blueprint process Agent manifest submitted for registration
BlueprintPromotion Agent promoted between lifecycle phases Design→Build, Build→Deploy transitions
BlueprintDemotion Agent demoted to previous phase Rollback or compliance failure
AgentIdentityCreated New Agent ID created in Entra First-time agent identity provisioning
AgentIdentityModified Agent identity permissions changed Permission scope updates
AgentIdentityDeleted Agent identity removed from Entra Agent decommissioning
ObservabilityConfigured Observability SDK settings modified Telemetry configuration changes

Querying Agent 365 Events:

OfficeActivity
| where TimeGenerated > ago(7d)
| where RecordType in ("ConnectedAIAppInteraction", "CopilotInteraction")
| extend agentType = tostring(parse_json(AuditData).ApplicationType)
| where agentType == "Agent365Blueprint"
| project TimeGenerated, UserId, Operation, AuditData

See Microsoft Learn: Agent 365 SDK (Preview) for evolving audit capabilities.

Observability by Agent Type

(A) Copilot Studio Agents:

  • Power Platform Admin Center analytics
  • Managed Environment insights
  • Microsoft Purview Audit logs

(B) Agent 365 SDK Agents (Preview):

  • OpenTelemetry SDK integration
  • Application Insights workbooks
  • Custom telemetry configuration

Updated: February 2026 | Version: v1.3 | UI Verification Status: Current