Control 4.8: Cost Allocation and License Optimization
Control ID: 4.8 Pillar: Operations & Monitoring Regulatory Reference: Sarbanes-Oxley §§302/404 (Internal Controls over Financial Reporting), 12 CFR part 30, appendix D (OCC Heightened Standards), FFIEC IT Examination Handbook Last Verified: 2026-09-24 Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Governance Levels: Baseline / Recommended / Regulated
Objective
Establish governance controls for Copilot license cost tracking, per-department cost allocation, usage-based license optimization, ROI tracking, and budget forecasting so institutions can evidence internal financial controls, stewardship decisions, and regulatory applicability assessments for responsible technology spending in financial services environments.
Why This Matters for FSI
Microsoft 365 Copilot represents a significant per-user licensing cost that scales with deployment breadth. With the introduction of a pay-as-you-go (PAYG) billing option, institutions now face additional governance complexity: managing both fixed per-seat costs and variable metered costs within a unified cost governance framework. For financial institutions, this cost governance should be reviewed against internal financial-control, procurement, risk, and fiduciary policies. Counsel and compliance owners should determine which regulatory or fiduciary obligations apply to the institution and which parts of this control are internal operating standards rather than regulatory requirements:
Sarbanes-Oxley §§302/404: Where Copilot costs are material to financial reporting, the firm should determine whether license allocation, PAYG spending-policy authorization, Azure subscription budget alerts, and escalation procedures are in scope for internal controls over financial reporting.
Fiduciary and stewardship obligations: Some institutions may choose to treat active license optimization, notification-only PAYG budget thresholds, Copilot Credit spending limits, and documented disablement procedures as evidence of prudent technology-spend stewardship. Applicability and disclosure treatment are a firm/counsel determination.
12 CFR part 30, appendix D (OCC Heightened Standards): Covered institutions should determine how variable AI spending, billing-policy scope, Azure budget alerts, anomaly monitoring, and hard-stop procedures fit into their operational-risk governance framework.
FFIEC IT Examination Handbook: Institutions should decide how to document cost-benefit analysis for Microsoft 365 Copilot seats, Copilot pay-as-you-go services, and Copilot Credits spending policies, including when to compare fixed-seat and usage-based access models.
From a practical standpoint, Copilot licenses that remain assigned to inactive users represent both a financial waste and a governance gap -- the institution is paying for licenses that may not be actively governed if the user is not engaging with the tool. Under the PAYG model, the equivalent risk is ungoverned usage that continues after notification thresholds are reached unless the policy owner takes escalation or disablement action.
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.
Control Description
Pay-As-You-Go Billing Model
Microsoft 365 Copilot pay-as-you-go is administered through billing policies rather than simple tenant-wide enablement. Administrators create billing policies in M365 Admin Center > Copilot > Billing & usage > Billing policies, tie each policy to an Azure subscription and a responsible set of users or groups, optionally add notification-only budget thresholds and email recipients, and then connect that policy on the Pay-as-you-go services tab to supported Copilot services such as Microsoft Copilot Chat, SharePoint agents, and Retrieval API. PAYG is disabled by default until a billing policy is connected to a service. Microsoft Learn states that PAYG budgets trigger email notifications but do not enforce a spending cap or stop usage after the threshold is exceeded.
Per-Seat vs. Pay-As-You-Go Governance Comparison
| Factor | Per-Seat License | Pay-As-You-Go |
|---|---|---|
| Pricing model | Fixed licensed-user count | Metered Azure charges based on actual service usage |
| Predictability | Highly predictable | Variable and dependent on policy coverage plus usage |
| Access model | License assignment | Users or groups covered by a connected billing policy |
| Features included | Full Microsoft 365 Copilot suite | Specific connected services such as Copilot Chat |
| Governance overhead | License assignment, inventory, and reclamation | Billing policy ownership, budgets, notifications, and cost review |
| FSI consideration | Predictable spend for stable populations | Flexible access that requires tighter approval and monitoring |
PAYG Governance Controls
The variable cost structure of the PAYG model requires governance controls that differ materially from per-seat license management:
- Billing policy ownership: Assign each billing policy to a named cost owner and approved business scenario.
- Notification-only budgets: Add budget thresholds and email notifications to each active billing policy, and document that PAYG usage continues until an administrator changes policy or access configuration.
- Azure budget alerts: Configure matching Azure budget alerts on the linked subscription or resource group because PAYG charges flow through the Azure subscription.
- Scoped access: Connect billing policies only to approved services and approved users or groups.
- Hard-stop runbook: Define who can remove users or groups, disconnect a billing policy from a service, or disable billable Copilot capabilities through Cloud Policy when a true spend stop is required.
- Cost review: Monitor costs in M365 Admin Center > Billing > Cost Management and Microsoft Cost Management.
- Self-service oversight: Review Settings > Org settings > Self-service trials and purchases because self-service is managed per product, not through a single tenant-wide off switch.
License Cost Tracking
Microsoft 365 Copilot licensing costs should be tracked at multiple levels, incorporating both per-seat and PAYG components:
| Cost Component | Description | Tracking Method |
|---|---|---|
| Base License Cost | Per-user Microsoft 365 Copilot seats | Microsoft billing portal / EA agreement |
| PAYG Metered Cost | Usage-based charges for services connected to a billing policy | M365 Admin Center > Billing > Cost Management and Microsoft Cost Management for the linked Azure subscription |
| Prerequisite Licenses | M365 E3/E5 or equivalent required for Copilot | Included in total cost of ownership |
| Add-on Licenses | Copilot for specific workloads (for example, Sales or Service) | Separate license tracking |
| Governance Tooling | Additional licenses for governance (Purview, Defender, Viva Insights) | Incremental cost allocation |
| Training and Change Management | Costs for user enablement and adoption programs | Project cost tracking |
| Administrative Overhead | IT staff time for Copilot governance and management | Time allocation tracking |
Per-Department Allocation
License costs should be allocated to consuming departments for accurate financial reporting:
| Allocation Method | Description | Best For |
|---|---|---|
| Direct Assignment | Costs charged to the department of the assigned user | Departments with dedicated license pools |
| Headcount-Based | Costs distributed proportionally by department headcount | Broad enterprise deployments |
| Usage-Based | Costs allocated based on actual Copilot usage metrics | Mature deployments with usage analytics |
| Hybrid | Combination of fixed allocation and usage-based variable | Large institutions with varying adoption |
High-Usage User Monitoring and Copilot Credit Tracking
The Microsoft 365 roadmap lists a Copilot - Billing & usage: High-usage users capability with General Availability timing in March 2026, but rollout and tenant visibility can vary. Treat this as a tenant-verification item rather than assuming the page is present in every tenant.
- High-usage user identification: Where available, administrators can review users with high Copilot pay-as-you-go usage and evaluate whether a full Microsoft 365 Copilot license or a different spending-policy scope is more appropriate.
- Copilot Credit tracking: For Cowork, apps built with Cowork, and Work IQ API, Microsoft Learn states that the Copilot > Cost management dashboard tracks Copilot Credit consumption by spending policy, user, group, agent, service, and funding source.
- Budget governance integration: High-usage patterns should be correlated with billing-policy budget notifications, Copilot Credit spending limits, user-level threshold notifications, and Azure budget alerts to detect cost anomalies before they become material spend variances.
FSI finance and compliance teams should incorporate high-usage and Copilot Credit monitoring into their periodic cost reviews. Variable consumption under usage-based models requires visibility into which users, groups, services, and spending policies are driving metered charges, and whether that usage aligns with the approved business justification documented in the billing or spending policy. Organizations should verify that high-usage thresholds and available reports are present in their tenant and calibrated to their billing structure and risk tolerance.
Usage-Based License Optimization
Active monitoring of license utilization identifies optimization opportunities:
| Optimization Action | Trigger | Expected Savings |
|---|---|---|
| License Reclamation | User inactive for 60+ days | Full license cost recovery |
| Role-Based Right-Sizing | Low usage in specific roles | Reassignment to higher-value roles |
| Feature-Specific Optimization | Users only using one Copilot surface | Evaluate if lower-cost alternatives exist |
| Seasonal Adjustment | Temporary usage patterns (e.g., audit season) | Temporary license assignment/removal |
| Departing Employee Recovery | Employee termination or transfer | Immediate license reclamation |
License Reclamation Policy
Establish clear criteria for license reclamation:
- Inactivity Threshold: Define the number of days of non-use before a license is flagged for reclamation (recommend 60 days for financial institutions)
- Grace Period: Provide a notification period before reclamation (recommend 14 days)
- Exemptions: Document exemptions (e.g., employees on approved leave, seasonal roles)
- Reactivation Process: Define how a user can request license reassignment after reclamation
- Manager Notification: Notify the user's manager before reclaiming a license
Copilot Surface Coverage
| Surface | Cost Tracking Relevance | Notes |
|---|---|---|
| M365 Copilot (base) | Primary license cost | Per-user license covers the licensed M365 Copilot suite |
| Microsoft Copilot Chat (PAYG) | Metered cost under connected billing policy | Available for approved users or groups without assigning full Copilot seats |
| Copilot Pages and Copilot Notebooks (PAYG) | Metered cost when used outside a paid Copilot license | Include in billing-policy approvals, budget notifications, and Azure budget alerts |
| SharePoint agents and declarative agent operations (PAYG) | Metered cost under connected billing policy or agent meter | Tie each approved agent scenario to a cost owner and service connection |
| Microsoft Copilot Retrieval API (Preview) | Metered cost under connected billing policy | Track query usage against approved workload justification |
| Copilot for Sales | Additional license | Separate SKU for CRM-integrated features |
| Copilot for Service | Additional license | Separate SKU for service desk features |
| Copilot for Finance | Additional license | Separate SKU for finance-specific features |
| Copilot Studio | Consumption-based | Custom copilot and agent scenarios may bill through Copilot Studio message meters |
| Prerequisite M365 License | Foundational cost | Must be factored into total cost of ownership |
| Copilot Cowork (GA June 2026) | Usage-based billing through Copilot Credits | Model responses, tool/skill calls, image generation, and browser tasks can consume Copilot Credits; access is granted by spending policies that select Cowork and usage is visible in Copilot > Cost management. See Control 4.15. |
| Microsoft Scout (Frontier preview) | Not part of the standard M365 Copilot Cost Management surface. Microsoft Learn identifies Scout as a Frontier preview desktop app. Users need active Microsoft 365 Copilot access plus GitHub Copilot Business or Enterprise entitlement and GitHub Copilot app policy access. | Include Microsoft 365 Copilot license, GitHub Copilot entitlement, and GitHub app-policy reconciliation in the cost inventory; see Control 4.16. |
Governance Levels
Baseline
-
Maintain a current inventory of all Copilot licenses (type, quantity, assignment), including any active PAYG billing policies and the users or groups they cover. Track licenses by department:
Connect-MgGraph -Scopes "Directory.Read.All","Reports.Read.All" $copilotSku = (Get-MgSubscribedSku | Where-Object SkuPartNumber -eq "MICROSOFT_365_COPILOT").SkuId Get-MgUser -All -Property "DisplayName,Department,UserPrincipalName,AssignedLicenses" | Where-Object { $_.AssignedLicenses.SkuId -contains $copilotSku } | Select-Object DisplayName, Department, UserPrincipalName | Export-Csv "CopilotLicensees-ByDept.csv" -NoTypeInformation -
Track total Copilot licensing cost monthly, including both per-seat and PAYG metered costs — Portal: M365 Admin Center > Reports > Microsoft 365 Copilot usage; M365 Admin Center > Copilot > Billing & usage; M365 Admin Center > Billing > Cost Management
- Implement basic license allocation to departments based on user assignment; use per-seat licensing only for maximum cost predictability at Baseline
- Establish a license reclamation process for departing employees
-
Generate quarterly license utilization reports showing assigned vs. active usage — Graph API (beta):
GET /beta/reports/getMicrosoft365CopilotUserCountSummary(period='D30')andGET /beta/reports/getMicrosoft365CopilotUsageUserDetail(period='D30')# Microsoft 365 Copilot usage report APIs are beta-only and return CSV; # they require the Microsoft.Graph.Beta.Reports module. Import-Module Microsoft.Graph.Beta.Reports Connect-MgGraph -Scopes "Reports.Read.All" Get-MgBetaReportMicrosoft365CopilotUsageUserDetail -Period "D30" -OutFile "CopilotUsage.csv" -
Define the license request and approval process for new Copilot assignments
- If PAYG is used, document the billing policy owner, connected service, notification-only budget thresholds, covered users or groups, linked Azure subscription, and hard-stop runbook — Portal: M365 Admin Center > Copilot > Billing & usage
Recommended
- Implement usage-based license optimization with 60-day inactivity threshold
- Enable PAYG billing for occasional users with documented approval workflow; configure billing-policy budget notifications, Azure budget alerts, and escalation owners before enabling PAYG access — Portal: M365 Admin Center > Copilot > Billing & usage
- Create department-level cost allocation reports for internal chargeback or showback, including separation of per-seat and PAYG costs using billing policy ownership and Cost Management data
- Reconcile billing policy coverage to the correct cost center monthly
- Establish ROI tracking that compares license costs to measured productivity benefits and observed usage patterns; use per-user detail reports where available and document PAYG service coverage at the group level
- Automate license reclamation notifications for inactive users
- Integrate license cost data with the institution's financial planning system
- Conduct quarterly license optimization reviews with department stakeholders, including whether stable PAYG populations should move to full seats
- Track total cost of ownership including governance tooling, training, and administration
Regulated
- Include Copilot license cost allocation in SOX internal control testing scope, including PAYG budget-notification authorization and escalation controls as part of IT general controls
- For PAYG deployments: review billing policy budgets, notification routing, Azure budget alerts, connected services, and hard-stop runbooks monthly, and document the authorization hierarchy for policy changes
- Present license cost and ROI analysis to the board technology or risk committee, including the decision basis for per-seat versus PAYG populations
- Maintain formal cost-benefit documentation per FFIEC expectations, including documented analysis of which user populations are assigned seats versus connected to billing policies
- Implement automated license lifecycle management tied to HR systems (hire/transfer/terminate)
- Conduct quarterly PAYG cost anomaly reviews to detect unusual usage spikes or unexpected policy coverage changes
- Conduct annual independent review of license optimization effectiveness
- Document license allocation methodology for auditor review, including the mapping between billing policies, services, and cost owners
- Maintain 7-year records of license assignments, cost allocations, and PAYG usage reports
Setup & Configuration
Step 1: Establish License Inventory
- Navigate to M365 Admin Center > Billing > Licenses
- Document all Copilot-related licenses:
License Type Purchased Assigned Available Monthly Cost ────────────────────────────────────────────────────────────────────────────── Microsoft 365 Copilot [qty] [qty] [qty] [contracted rate] Copilot for Sales [qty] [qty] [qty] [contracted rate] Copilot for Service [qty] [qty] [qty] [contracted rate] Copilot Studio [units] N/A N/A [contracted meter] - Record enterprise agreement terms, discount rates, and renewal dates
Step 1b: Configure Pay-As-You-Go Billing (If Applicable)
For organizations adopting the PAYG model for occasional or seasonal users:
- Navigate to M365 Admin Center > Copilot > Billing & usage.
- On the Billing policies tab, create or review the billing policy tied to the correct Azure subscription, resource group, and region.
- Add the approved users or groups to the billing policy and document the responsible cost owner.
- On the Budget page or tab, add budget thresholds and email notification recipients. Treat these thresholds as alerting controls only: PAYG usage can continue after a threshold is exceeded.
- On the Pay-as-you-go services tab, connect the billing policy to the approved service, such as Microsoft Copilot Chat, SharePoint agents, or other billable Copilot services approved for the tenant.
- Configure matching Azure budget alerts on the linked subscription or resource group so finance receives subscription-side notifications for PAYG charges.
- Document the hard-stop runbook, including who can remove covered users or groups, disconnect a billing policy from a service, or disable billable Copilot capabilities through Cloud Policy.
- Review usage and charges in M365 Admin Center > Billing > Cost Management and Microsoft Cost Management.
- Review Settings > Org settings > Self-service trials and purchases and document the per-product status for Microsoft 365 Copilot and adjacent self-service products.
Step 2: Configure License Assignment Groups
Use Entra ID group-based licensing for structured assignment:
- Create Entra ID groups for each Copilot license pool:
Copilot-Licensed-FrontOfficeCopilot-Licensed-BackOfficeCopilot-Licensed-ComplianceCopilot-Licensed-IT- Assign Copilot licenses to groups in Entra ID > Groups > [Group] > Licenses
- Document group membership criteria and approval process
Step 3: Implement Usage Monitoring
- Connect Copilot usage reports (Control 4.5) to license assignment data
- Create a monthly report identifying:
- Users with licenses assigned but zero usage in the past 30 days
- Users with licenses assigned but minimal usage (fewer than 5 interactions per month)
- Users with high usage who might benefit from additional Copilot features
- Establish review workflow for optimization recommendations
Step 4: Configure Cost Allocation
- Map Copilot license assignments to cost centers via Entra ID attributes:
- Create monthly cost allocation report: | Department | Users Licensed | Active Users | Monthly Cost | Cost per Active User | |-----------|---------------|-------------|-------------|---------------------| | Trading | [count] | [count] | [contracted cost] | [calculated cost] | | Wealth Mgmt | [count] | [count] | [contracted cost] | [calculated cost] | | Operations | [count] | [count] | [contracted cost] | [calculated cost] | | Compliance | [count] | [count] | [contracted cost] | [calculated cost] |
- Distribute cost reports to department heads for budget management
Step 5: Establish License Reclamation Workflow
- Define automation rules (using Power Automate or equivalent):
- Trigger: User inactive in Copilot for 60 consecutive days
- Action 1: Send notification to user and manager (14-day grace period)
- Action 2: If no activity after grace period, remove from Copilot license group
- Action 3: Log reclamation event for audit trail
- Define exemption categories:
- Approved medical or personal leave
- Seasonal roles with predictable inactive periods
- New hires in onboarding (first 30 days exempt)
- Document reactivation request process
Financial Sector Considerations
PAYG Model and Sarbanes-Oxley §§302/404 Controls: The PAYG model introduces variable AI spending that a SOX-reporting entity may decide to include in IT general controls over financial reporting when the spend is material. If included, budget-notification authorization, Azure subscription alerting, spending-policy limits, and escalation controls should be documented and testable. Variable PAYG and Copilot Credit costs should be reconciled between billing/spending policy configuration, M365 Admin Center and Microsoft Cost Management reports, and internal cost allocation records.
12 CFR part 30, appendix D (OCC Heightened Standards) and Cost Governance: Covered institutions should determine how AI spending governance fits into their operational-risk framework. Uncontrolled usage-based spending — where costs can scale unexpectedly and some limits or budget notifications may not stop access immediately — should be treated as a risk-management scenario requiring budget alerting, anomaly monitoring, and tested disablement procedures.
FFIEC Cost-Benefit Analysis: Institutions should determine how FFIEC IT Examination Handbook planning expectations apply to Copilot investments. When choosing between per-seat licensing, Copilot pay-as-you-go services, and Copilot Credits spending policies, document the user populations, approval basis, expected usage pattern, and governance controls applied to each model.
SOX Material Expenditure: If Copilot licensing represents a material technology expenditure, the cost allocation methodology should be documented and testable as part of SOX ITGC procedures. Auditors may request evidence that license costs are properly authorized, allocated to the correct cost centers, and reconciled to vendor invoices. For PAYG deployments, this includes Azure Commerce billing reconciliation against internal PAYG usage reports.
Fiduciary Cost Management: Investment advisers or other entities that allocate technology costs to clients should have counsel and compliance determine whether Copilot-related costs require disclosure, fee-allocation review, or other fiduciary controls.
Budget and Capital Planning: Where technology costs affect operating expense forecasting or capital planning, large-scale Copilot deployments should be factored into the firm's existing finance and risk-planning processes.
Vendor Concentration Risk: Copilot licensing deepens dependency on Microsoft and, for Scout, GitHub Copilot entitlement. Cost tracking should include vendor concentration and switching/de-platforming considerations under the firm's third-party-risk program.
Budget Governance: Financial institutions typically require multi-level approval for technology expenditures above certain thresholds. The initial Copilot procurement and subsequent expansions should follow the institution's technology investment approval process, with documented business justification and expected ROI.
License True-Up Risk: Enterprise agreements often include annual true-up provisions. Institutions should track actual license consumption against contracted quantities to avoid unexpected true-up costs. License reclamation helps manage this risk.
Verification Criteria
| # | Verification Step | Expected Result |
|---|---|---|
| 1 | Review license inventory in M365 Admin Center | Inventory current and reconciled to vendor billing, including PAYG user groups |
| 2 | Verify department-level cost allocation reports | Reports produced monthly with accurate department mapping for both per-seat and PAYG costs |
| 3 | Confirm license reclamation process is operational | Inactive users identified and reclamation workflow functioning |
| 4 | Verify PAYG budgets and notifications are configured (if PAYG enabled) | Active billing policies have notification-only budgets, recipient groups, Azure budget alerts, and escalation owners configured |
| 5 | Review ROI tracking documentation | ROI analysis updated quarterly with actual metrics and documented per-seat versus PAYG population decisions |
| 6 | Verify group-based license assignment | Licenses assigned via Entra ID groups, not individual assignment |
| 7 | Confirm budget forecast includes Copilot costs | Current fiscal year budget includes both per-seat licensing and PAYG estimated cost line items |
| 8 | Review license utilization report | Report shows assigned vs. active usage with optimization recommendations |
| 9 | Verify PAYG cost anomaly monitoring | M365 Admin Center and Microsoft Cost Management review evidence exists, unusual usage is investigated, and hard-stop actions are documented when thresholds are exceeded |
| 10 | Verify audit trail for license changes | Assignment, reclamation, billing-policy changes, and PAYG enablement events are logged and retrievable |
Additional Resources
- Microsoft 365 Admin Center - License Management
- Entra ID Group-Based Licensing
- Microsoft 365 Copilot Licensing Guide
- Microsoft 365 Copilot pay-as-you-go overview
- Set up pay-as-you-go for Microsoft 365 Copilot
- View costs and billing for Microsoft 365 Copilot pay-as-you-go
- Understand usage-based billing and cost management for Copilot Credits
- Microsoft 365 Roadmap ID 557176 — Copilot - Billing & usage: High-usage users
- Manage self-service purchases and trials (for admins)
- Microsoft Enterprise Agreement Overview
- Sarbanes-Oxley §§302/404 - PCAOB Standards
- FFIEC IT Examination Handbook - Management
-
Implementation Playbooks: Portal Walkthrough · PowerShell Setup · Verification · Troubleshooting
-
Related Controls: 1.9 License Planning, 4.5 Usage Analytics, 4.1 Admin Settings and Feature Management, 4.6 Viva Insights Measurement
FSI Copilot Governance Framework v1.8.0 - July 2026