Orange County’s IT department has quietly asked the market what it would cost to move its workloads off Microsoft Azure — a rare and revealing step that signals growing public-sector interest in escaping vendor lock-in, even if an actual migration is far from certain. The county later clarified that the RFI is for cost comparisons and understanding options, not an imminent exit. Still, the procurement notice is a bellwether for any organization that has adopted Azure at scale and now wonders about the price of leaving.

What the RFI Actually Asks

On September 19, 2025, Orange County Information Technology (OCIT) published a Request for Information (RFI) soliciting vendor input on migrating applications, virtual machines, storage, databases and networking configurations from Azure to an alternative cloud provider. The public summary lists Opportunity ID 017‑RX1720273 and requires responses to cover planning, testing, security validation, data backup, recovery design and staff training.

Key deadlines: questions are due by 4 p.m. PT on October 6, and full responses by 4 p.m. PT on November 3. The county will accept questions through the OpenGov platform.

A critical nuance came after the initial news broke. Government Technology’s Industry Insider — California, which first reported the RFI, updated its story with a county clarification: the RFI is “for cost comparisons and understanding what options are available,” not a binding commitment to migrate. OCIT is essentially testing the market, not pulling the trigger.

Why a Cost Comparison Is a Big Deal

An RFI for pricing an Azure exit is unusual, even as a thought experiment. Hyperscalers invest heavily in government certifications, compliance programs and integrations that agencies come to depend on. Requesting cost data signals an organization is serious enough about vendor diversification to put formal procurement muscle behind it.

For Windows-centric IT teams, the move is a wake-up call. If a county with a $132.7 million IT budget and deep Microsoft dependencies can openly explore alternatives, any Azure customer should be auditing its own lock-in posture. The RFI also creates a public arena for commercial proposals; whatever vendors quote will become a benchmark that other governments and enterprises can reference.

The Practical Challenges of Leaving Azure

Migrating an entire IT estate off Azure is not a single technical lift but a multi-workstream program. The RFI’s scope hints at the complexity, and any realistic bid will have to address these hard problems:

  • Identity and Access: Azure Active Directory/Entra ID is often deeply woven into applications and services. Migrating or federating identity to another provider’s directory is notoriously difficult and can break single sign-on, service principals and managed identities.
  • Data Gravity and Egress: Moving terabytes of data out of Azure incurs network egress fees, which can quickly dwarf other costs if not modeled accurately. Public estimates for the total opportunity, noted by one aggregator, range between $500,000 and $2,000,000, but those figures are automated estimates and should be treated as illustrative, not contractual.
  • Refactoring vs. Rehosting: Applications built on Azure-specific managed services (Cosmos DB, Azure SQL features, Logic Apps) may need significant rewrites to run elsewhere. The RFI explicitly asks vendors to “reconfigure” applications for the new environment and test compatibility.
  • Dual-Running Costs: During a cutover, both environments must operate simultaneously, adding transient expense that many budgets undercount.
  • Compliance Continuity: County workloads often operate under FedRAMP, CJIS or HIPAA controls; revalidating those in a new cloud requires rigorous evidence collection and can cause timeline delays.

Experienced migration playbooks start with a small, reversible pilot, iterate on identity and network connectivity, and maintain rollback plans for every cutover. The RFI’s emphasis on testing, verification and training suggests OCIT already understands that process rigor matters as much as tooling.

How Orange County Got Here

Orange County is not new to cloud diversity. Public records show that some county systems already run on Amazon Web Services; the Clerk-Recorder’s office moved a system to AWS, as documented in the FY 2024-25 budget book. Oracle Fusion was adopted for finance and HR modernization earlier in 2025, signaling a best-of-breed SaaS strategy. The county also retired its IBM mainframe in FY 2022-23, a significant legacy migration that demonstrates internal project muscle.

OCIT’s CIO, KC Roestenberg, presides over a department with a $132.7 million combined budget for FY 2025-26. This scale makes the RFI credible: the county has the resources to execute a major migration if it chooses to, but also the fiduciary responsibility to scrutinize cloud costs.

What Other Organizations Should Do Now

For IT leaders watching Orange County’s example, a few practical lessons stand out:

  1. Run your own cost-comparison exercise. Even a lightweight RFI can reveal whether your organization is overpaying for lock-in. Estimate data egress, licensing adjustments and dual-running costs for your top 20 workloads.
  2. Audit your Azure-specific dependencies. Map every application to the managed services it relies on. Flag anything that would break or require a rewrite if you had to leave Azure today.
  3. Review contract termination and data portability clauses. Understand your rights to export data in a usable format and the notice periods required. Negotiate better terms at renewal if gaps exist.
  4. Federated identity is a strategic choice, not just a convenience. If you use Entra ID as your primary identity provider, model what a migration would look like for user accounts, service principals and conditional access policies.
  5. Test a pilot exit on a low-risk workload. Even a simple lift-and-shift of a non-critical app will teach you about tooling, timing and hidden costs.

Vendors responding to the RFI should emphasize discovery methodology, reversibility plans, and clear separation of professional services from estimated egress and dual-running fees. OCIT’s team will be looking for proof that a bidder can handle government scale without service disruption.

What Happens Next

The RFI is just the opening gambit. OCIT will collect responses through early November, likely hold vendor conferences or capability demonstrations, and then decide whether to issue a formal Request for Proposals (RFP) or pause. Watch for subsequent procurement notices that include technical attachments, performance baselines or regulatory constraints — those will reveal how seriously the county is pursuing a move.

If an RFP emerges, it will become a public case study that other cities and counties follow. Even if Orange County ultimately stays on Azure, the cost data it gathers will influence contract negotiations and give other agencies a template for evaluating their own options.

For now, the message is clear: no public-sector IT department can afford to assume that today’s cloud platform is tomorrow’s default. Cost comparison is becoming standard operating procedure, and Azure customers everywhere should take note.