Skip to content

Control 4.8: Cost Allocation and License Optimization — Portal Walkthrough

Step-by-step portal configuration for implementing cost allocation, chargeback, license optimization, and pay-as-you-go (PAYG) billing governance for Microsoft 365 Copilot across the organization.

Prerequisites

  • Role: AI Administrator, License Administrator, Billing Administrator, or Entra Global Admin as needed
  • License: Microsoft 365 E5 with Copilot add-on; Azure subscription (for PAYG billing management)
  • Access: Microsoft 365 Admin Center, Azure Portal (Cost Management + Billing), Azure Cost Management

Steps

Step 1: Establish License Inventory and Cost Baseline

Portal: Microsoft 365 Admin Center Path: Billing > Licenses > Microsoft 365 Copilot

  1. Navigate to the Copilot license inventory.
  2. Document current license counts: total purchased, assigned, and available.
  3. Calculate the per-user monthly cost based on your licensing agreement.
  4. Establish a cost baseline for budget tracking and chargeback.

Step 1b: Configure Pay-As-You-Go Billing Policies

Portal: Microsoft 365 Admin Center and Microsoft Cost Management Path: Copilot > Cost management > Classic Billing & usage > Pay-as-you-go services (Learn-documented setup path; older wording/tenants might still show Copilot > Billing & usage > Pay-as-you-go services); Copilot > Cost management for Copilot Credits

  1. Open the Learn-documented setup path Copilot > Cost management > Classic Billing & usage > Pay-as-you-go services for Copilot Chat or SharePoint agents. Older documentation and some tenants might still show Copilot > Billing & usage > Pay-as-you-go services directly. Use Copilot > Cost management for Cowork, apps built with Cowork, and Work IQ API spending policies.
  2. Create or review the billing policy tied to the correct Azure subscription.
  3. Add the approved users or groups to the billing policy and document the responsible cost owner.
  4. Add a budget threshold and notification routing to the billing policy or Copilot Credit spending policy; document whether the control is notification-only, a separate spending limit, or an access-granting policy scope.
  5. Connect the billing policy or spending policy to the approved service, such as Microsoft Copilot Chat, SharePoint agents, or Cowork.
  6. Open Cost Management to review usage and charges for the connected service.
  7. Review Settings > Org settings > Self-service trials and purchases and document the per-product self-service state for Microsoft 365 Copilot and related products.

Step 2: Configure Group-Based License Assignment

Portal: Microsoft Entra Admin Center Path: Groups > All groups > Group-based licensing

  1. Create or identify groups for license allocation by business unit:
  2. "Copilot-Licensed-WealthManagement"
  3. "Copilot-Licensed-Trading"
  4. "Copilot-Licensed-Compliance"
  5. "Copilot-Licensed-Operations"
  6. Assign the Microsoft 365 Copilot license to each group.
  7. Group membership changes automatically add or remove licenses.
  8. Document the cost center mapping for each group.

Step 3: Set Up Usage-Based Chargeback Reporting

Portal: Microsoft 365 Admin Center Path: Reports > Usage > Microsoft 365 Copilot

  1. Download the Copilot usage report and correlate with department data.
  2. Create a chargeback model:
  3. Per-license chargeback — charge each department for assigned licenses
  4. Usage-based chargeback — charge based on active usage metrics
  5. Hybrid model — base charge + usage premium
  6. Document the chargeback methodology and distribute to finance stakeholders.

Step 4: Identify License Optimization Opportunities

Portal: Microsoft 365 Admin Center Path: Reports > Usage > Microsoft 365 Copilot

  1. Review the usage report to identify underutilized licenses:
  2. Users with licenses assigned but no activity in 30+ days
  3. Users with very low interaction counts (fewer than 5 per month)
  4. Create a reallocation plan for underutilized licenses.
  5. Establish a quarterly license review cadence.
  6. Set up automated alerts for license utilization dropping below threshold.

FSI Recommendations

Setting Baseline Recommended Regulated
License assignment method Manual Group-based Group-based with approval
PAYG billing Not enabled or not in scope PAYG through documented billing policies for occasional users PAYG limited to bounded scenarios with monthly billing-policy review
PAYG budget controls N/A Budget and notifications on each active billing policy Budget and notifications plus documented escalation path
Chargeback model None Per-license Hybrid model using seats plus PAYG cost review by billing policy
Utilization review Annual Quarterly Monthly; PAYG anomaly review quarterly
Underutilization threshold No threshold 30 days inactive 14 days inactive

Regulatory Alignment

  • SOX Section 404 (15 U.S.C. § 7262) — Where material and in scope for the firm, PAYG budget authorization controls can serve as IT general controls over financial reporting; per-seat and usage-based costs should be reconciled to vendor billing and billing/spending-policy records
  • FFIEC Management Booklet, Section II.D — Cost-benefit analysis of per-seat, PAYG, and Copilot Credit model selection should be documented according to the firm's examiner-response and technology-planning standards
  • 12 CFR part 30, appendix D (OCC Heightened Standards) — For covered institutions, billing/spending-policy review, budgets, and anomaly investigation can support the firm's operational-risk governance evidence set

Next Steps