Azure Cloud Exit Fees Are Falling, but Microsoft Licensing and Portability Still Block Switching

The argument deserves attention, but also qualification. European regulators have already adopted switching measures that extend beyond fees, while the UK Competition and Markets Authority has identified both egress charges and Microsoft licensing as competition concerns. The evidence supports treating these as interconnected obstacles—not declaring one irrelevant because another may be larger.

Free egress is not free migration​

Hogg and Bulla argue that transfer charges can be overshadowed by the expense of reconfiguring applications, operating two environments during migration and obtaining software licenses. Their broader concern is that commercial ties can keep customers anchored to a provider even after the toll on the exit ramp disappears. That is a policy interpretation, rather than a demonstrated finding that fee waivers have produced no benefit across the cloud market.

Provider documentation illustrates why the wording matters.

AWS announced its exit-related waiver on March 5, 2024, requiring customers moving away from AWS to contact support. Microsoft’s Azure bandwidth pricing page likewise describes free internet egress for customers leaving Azure for another cloud provider or an on-premises data center. Those are migration provisions, not blanket promises that every transfer between clouds is free.

Google’s published exit process makes the distinction particularly explicit:

• Customers must submit an Exit Notice before migration.
• After an initial 14-day period, they have 30 days to initiate migration and must notify their support agent at least two working days before starting.
• A subsequent migration period lasts at least 30 days, with extensions available under the stated conditions.
• Eligible transfer costs are credited on the final invoice.
• Customers must end all use of the particular service they are leaving, although they may continue using other Google Cloud services.

Moving only part of a service’s data while continuing to use that service does not qualify for this exit program. Google separately identifies Data Transfer Essentials as an option that may support eligible European customers using multiple providers. Consequently, neither “complete departure from the entire provider” nor “free routine multicloud traffic” accurately describes every arrangement.

The practical distinction: procurement teams should evaluate an exit waiver and ongoing cross-cloud operation as separate requirements.

Europe’s rules already go beyond the transfer bill​

The European Commission’s explanation of the Data Act identifies several switching barriers: egress charges, lengthy procedures and insufficient interoperability that can cause loss of data or application functionality. Its response is therefore broader than fee removal.

For platform-as-a-service and software-as-a-service providers, the Commission describes requirements for open interfaces and export in commonly used, machine-readable formats. Infrastructure providers must help facilitate materially comparable outcomes for shared features when customers move to another service of the same type. Providers must also remove obstacles to switching or using multiple services simultaneously.

The dates are important. The Data Act has applied since September 12, 2025, but the removal of switching charges, including egress charges, is scheduled for January 12, 2027. As of October 1, 2026, that deadline remains ahead; during the transition, providers may charge costs incurred in connection with switching and egress. These are EU requirements, not a universal statement about every US customer’s contract.

The analytical takeaway is straightforward: eliminating a billable barrier and improving technical portability are complementary measures. One does not substitute for the other.

Microsoft licensing needs product-level scrutiny​

For Windows and SQL Server administrators, Microsoft’s outsourcing guidance provides a more useful starting point than a sweeping assertion that Microsoft software is difficult to run everywhere except Azure.

Microsoft says outsourcing rights depend on the applicable agreement, Product Terms, software and licensing conditions. Its October 2019 and October 2022 updates removed the option to redeploy licenses without License Mobility rights on Listed Providers’ servers. The guidance distinguishes those providers from Authorized Outsourcers.

Two boundaries are especially relevant:

• License Mobility through Software Assurance covers specified server applications, including SQL Server. It is not generally available for all Microsoft software.
• Flexible Virtualization Benefit permits qualifying active subscription licenses or licenses with active Software Assurance to be used on Authorized Outsourcers’ shared or dedicated hardware. An Authorized Outsourcer cannot itself be a Listed Provider or use one for its data-center resources.

Those distinctions support the concern that licensing can complicate provider choice. They do not establish that all Microsoft products receive fewer security updates merely because they run on a rival cloud. Administrators should assess update entitlements for the exact product and version rather than turn a licensing dispute into a blanket security conclusion. Microsoft also expressly states that the customer’s agreement controls if it conflicts with the explanatory guidance.

UK scrutiny has moved beyond the original investigation​

The CMA’s March 31, 2026 announcement said its 2025 cloud investigation found significant market power held by Amazon and Microsoft, with customer choice constrained by egress fees, interoperability barriers and Microsoft business-software licensing. It also reported actions from Microsoft and Amazon intended to reduce the expense and effort of using multiple clouds, while saying further steps were required.

The regulator subsequently launched a strategic market status investigation into Microsoft’s business software ecosystem on May 14, 2026. Its scope includes productivity software, PC and server operating systems, database management and security software. It is examining potential concerns involving bundling, interoperability and defaults, including competitors’ ability to integrate AI with Microsoft products.

The case page identifies the investigation as open, with an indicative final decision timetable in February 2027 and a statutory deadline of February 13, 2027. An investigation into possible designation is not an already-completed designation or a final ruling on every practice under examination.

That distinction matters: regulatory concern is substantial evidence of a problem worth investigating, but not permission to report every allegation as settled fact.

Marketplaces and AI complicate the competition question​

Hogg and Bulla’s argument also encompasses third-party software marketplaces and AI. They acknowledge that marketplaces can simplify billing and customer acquisition, but contend that purchasing incentives and hosting relationships can bind software vendors and customers to an underlying cloud. They similarly warn that AI model access and partnerships could reinforce incumbent platforms, even as specialized AI infrastructure providers create alternatives.

There is concrete evidence of infrastructure diversification. OpenAI announced an AWS partnership on November 3, 2025, involving a $38 billion commitment over seven years and access to infrastructure for advanced AI workloads. That establishes an important relationship beyond Azure; it does not, by itself, demonstrate reduced market concentration or simpler switching for ordinary enterprise customers.

The useful analytical test is therefore not simply whether another provider exists. It is whether customers can realistically choose it without losing essential functionality, contractual benefits or affordable software access.

What enterprise buyers should ask​

The following procurement checklist is a synthesis of the provider conditions, Microsoft licensing guidance and regulatory concerns—not a claim of firsthand migration testing.

1. Define the move. Is this a complete service exit, a partial migration or continuing multicloud operation?
2. Confirm waiver eligibility before transferring data. Record covered services, required notices, migration windows and how credits are applied.
3. Map software rights separately. Identify the products, licenses, Software Assurance coverage and destination-provider classification involved.
4. Test functional portability. Establish which application functions and data exports must work at the destination before approving production cutover.
5. Compare the whole commercial arrangement. Ask how changing providers affects software purchases and bundled services—not just the network-transfer line item.

The strongest conclusion is narrower, and more useful, than saying fee waivers accomplish nothing: they address one barrier, not the entire switching problem. For Microsoft customers, meaningful cloud choice requires a viable combination of data portability, application functionality and software rights. A free exit is valuable; an exit that the business can actually use is the real objective.