Why Listed-Provider Terms Still Decide Your Cloud Placement
Nikkei reported a raid on Microsoft’s Japanese office on 25 February 2026. Japan’s Fair Trade Commission later confirmed it had opened an investigation into whether Microsoft violated the Antimonopoly Act. A Microsoft Japan spokesperson told Asahi the company will “cooperate fully with the Fair Trade Commission’s request.” Those requests concern how Microsoft licenses software to run on clouds other than Azure (the same Microsoft listed-provider licensing on Windows Server and SQL Server that regulators in Europe, the UK, and the United States have already examined).
That’s the problem.
This is not a Tokyo raid story. It is a placement story. Azure Hybrid Benefit and license reallocation are cheaper when the workload sits on Azure than when the same Windows Server or SQL Server sits on AWS or Google Cloud. If you cannot produce that delta this week, you are walking into the next cloud conversation with the vendor’s number. That delta is a cost-optimization problem: the same cores, two clouds, two license prices.
What JFTC actually put on paper
The news broke on 25 February 2026 in Nikkei. JFTC’s own 4 March 2026 release is the primary document.
JFTC is investigating Microsoft Corporation, Microsoft Japan, and Microsoft Ireland Operations Limited. It has not reached a conclusion. The suspected conduct, in JFTC’s words, is that Microsoft does not allow those products to be used with competing clouds, or sets terms so costs rise when they are used off Azure rather than on Azure. The named products include Windows Server, Windows Client, SQL Server, Microsoft 365, and Visual Studio.
That is listed-provider pricing, described from the regulator’s side of the table. Microsoft’s 2019 outsourcing update is the commercial paper on the other side. From 1 October 2019, on-premises licenses without Software Assurance and mobility rights cannot be deployed on dedicated hosted cloud from Listed Providers: Microsoft, Alibaba, Amazon (including VMware Cloud on AWS), and Google.
Europe looked at the same pattern. The UK looked at it. The United States looked at it. Microsoft changed its ways in Europe. Not enough for Google. The UK and US files remain open.
There is no finding and no fine. There is a regulator request, a cooperation statement, and a licensing model you already buy against. If you have a Japanese estate or a Japan EA, this is a live file. If you do not, the model did not wait for Tokyo.
Microsoft listed-provider licensing is a placement tax
Look at your own cloud file. Most SAM reports still have a row that says “licensed” and a FinOps view that says “compute.” Those two words describe different things.
A Windows Server core on Azure, with Azure Hybrid Benefit applied, is one cost. The same core on AWS or Google Cloud, under listed-provider terms, is another. The software did not change. The cloud did. The license price followed the cloud.
Your inventory export cannot tell you which you are until someone recasts it against the terms Microsoft actually sells on each platform. If your reports still collapse “Windows Server” into one unit cost, you are reading a reporting layer, not a license position.
This is not a criticism of the teams building those reports. The tools were built to prove what is deployed, not to price the same core two ways before a placement meeting. An analysis that arrives after the vendor has framed the meeting is a document. One that arrives during the meeting is a decision input.
Picture the room. Your CIO wants the next SQL Server estate on AWS. Procurement wants the Azure number because the EA conversation is coming. If SAM takes three weeks to recast the same cores against Azure Hybrid Benefit and listed-provider terms, the placement happens without a license position. Compute gets decided. License gets added later.
If that feels familiar, the problem is not your team’s maturity. A multi-cloud conversation is being answered with a single-cloud entitlement report. Once the placement is signed, the leverage moves.
Azure Hybrid Benefit does not travel with the VM
Azure Hybrid Benefit is the Azure path. It lets you apply qualifying Windows Server and SQL Server licenses to Azure capacity so you are not paying the license-included rate on every core. Reallocation of Software Assurance licenses is the same idea: the entitlement you already paid for follows the workload onto Azure.
On a listed provider, that path is narrower and more expensive. You need License Mobility through Software Assurance with an Authorized Mobility Partner, or you buy license-included under SPLA. You need to know which quote applies to the cores you are about to place.
People assume the benefit moves because the VM moves. It does not. The virtual machine is portable. The discount is not. If your architecture deck treats “lift and shift” as license-neutral, the deck is wrong.
Do not let Microsoft frame the next meeting as “Azure is where our software is cheapest.” That is their sentence. Yours is narrower: what are we actually running, on which cloud, which cores qualify for Azure Hybrid Benefit, and what does the same estate cost on a listed provider. “We are multi-cloud” is not a number. A European adjustment is not a global reset. You treat the contract in front of you as the contract in front of you.
The number to have before the next cloud placement
Do this in the next thirty days, as a decision pack rather than a project. The event is the next Windows Server or SQL Server placement (not a JFTC ruling).
| What you produce | Why it changes the next placement |
|---|---|
| Windows Server and SQL Server cores by cloud, this week | Distinguishes a multi-cloud slide from cores already on a listed provider. A stale count is a document, not a position. |
| Azure Hybrid Benefit / reallocation eligibility on those cores | AHB is the Azure path. Listed-provider terms are the other. If you cannot say which cores qualify, you do not have a number. |
| Azure-priced license cost versus AWS or Google Cloud on the same estate | That delta is the number. Not a regulator headline. Your cores, your entitlements, two clouds. |
| A written placement rule | Next workload: Azure, AWS, or GCP (with the license cost attached before the compute quote is signed, not after). |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have a listed-provider position. You have a library.
If you only have the Azure number, you have half a position. Treat the Japan probe as a prompt. Your number is the one you can defend against your own inventory, your cloud bills, and the contract in front of you.
The decision layer, not another inventory
You already have discovery data and cloud bills. The gap is not another inventory. The gap is turning that estate into a decision: which cores sit where, what Azure Hybrid Benefit would do on Azure, and what listed-provider terms do on AWS or Google Cloud. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Windows Server and SQL Server cores have to sit next to entitlement and the cloud they actually run on, not a single-cloud export.
If you are heading into a cloud placement or an EA conversation and your current tools still need three weeks to turn a host list into an Azure-versus-listed-provider number, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “run it on Azure and the license takes care of itself.” The right question is: what are we actually running, on which cloud, what does Azure Hybrid Benefit do for this estate, and what does the same estate cost on a listed provider. That is a data question, not a sales question.
JFTC will take its time. Google will keep pressing in Europe. The UK and the United States remain unresolved. You still have to place the next workload. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
FAQ
What is Japan’s Fair Trade Commission actually looking at? As JFTC described it on 4 March 2026: whether Microsoft prevents competing clouds from winning business by blocking, or raising the cost of, Windows Server, Windows Client, SQL Server, Microsoft 365, Visual Studio, and related products off Azure. JFTC said it has not reached a conclusion. No finding is in this story.
Did Microsoft end listed-provider pricing worldwide? Not on these facts. Microsoft changed its ways in Europe. Buy against the contract you have.
What number should SAM take into the next cloud placement? Windows Server and SQL Server cores by cloud, which cores qualify for Azure Hybrid Benefit or reallocation, and the license delta between Azure and a listed provider on that estate.
Does a Japan probe change anything if we have no Japan estate? The regulator file is Japan’s. The commercial model is not. The placement decision is still yours.
