Azure EA to MCA Migration Readiness & Execution Workbook

Cisco program workbook for Enterprise Agreement → Microsoft Customer Agreement migration — Commercial & FedRAMP enrollments, 12 workstreams, future Splunk MCA consolidation.

Commercial Enrollment FedRAMP Enrollment Splunk MCA Consolidation 178 Tasks · 12 Workstreams

A. Executive Summary

Migration Objective

Transition Cisco Azure billing from EA to MCA before enrollment expiration. This is a billing change only — Azure resources and subscription RBAC are unaffected. Hierarchy shifts from Enrollment → Department → Account to Billing Account → Billing Profile → Invoice Section.

Target State

  • Commercial EA enrollment migrated to Cisco MCA billing account
  • FedRAMP enrollment on separate MCA billing profile per ATO boundary
  • Long-term consolidation under Splunk MCA agreement
  • Cost pipelines updated for MCA APIs, Snowflake schema, and Cloudability

Team Responsibilities

  • GPS Procurement — Contract, billing design, Microsoft engagement
  • Cloudx Ops — Discovery, APIs, Snowflake, identity & access
  • FinOps — Cloudability, chargeback, allocation governance
  • CCTM — Invoice processing, AP, reconciliation, month-end close
  • RunOn — Subscription provisioning platform & automation
  • Cross-Team — Pilot, production cutover, hypercare

Microsoft Pre-Conditions

  • Transition within 60 days of EA enrollment end date
  • All EA credits consumed prior to transition
  • Azure Plan enabled on target billing profile
  • Enterprise Administrator + Billing Account Owner roles
  • SQL Hybrid Benefit manually reassigned post-migration

Billing Hierarchy

EA departments/accounts do not auto-map to MCA invoice sections. Incorrect design breaks chargeback for all BUs.

Cost Management APIs

EA Reporting APIs retired. All integrations must migrate to Entra-authenticated MCA APIs and Cost Details schema.

Snowflake Pipelines

departmentId → invoiceSectionId; AccountId removed. ETL failures cause executive reporting blackout.

FedRAMP Isolation

Commercial and FedRAMP billing must remain isolated in separate MCA billing profiles.

B. Migration Status Dashboard

Critical Open Items

C. Workstreams & Task Execution