Skip to main content

Frankfurt costs 12.75% more than Stockholm to keep the data in the EU

Azure lists the same 2 vCPU Linux machine at 0.096 US dollars an hour in East US, 0.102 in Sweden Central and 0.115 in Germany West Central and Poland Central. The rate per vCPU hour is identical on the 4 vCPU machine in nine of the ten regions, so what residency costs is a regional multiplier the vendor sets, not the control the buyer chose. Inside the EU the premium runs from 6.25% to 19.79%.
6.25%Premium over East US, Sweden Central, 2 vCPU Linux machine
19.79%Premium over East US, Germany West Central and Poland Central
0.65 centsGermany over Sweden, identical machine and terms, per vCPU hour
5.75 centsPrice per vCPU hour in Germany West Central, at 2 vCPU and at 4 vCPU

Microsoft's Azure Retail Prices API, the vendor's own published price list for these SKUs, queried on 5 November 2026: Standard_D2s_v5 and Standard_D4s_v5, Linux, pay as you go, USD per hour, ten regions. Premiums and per vCPU figures are Mosaic Singularity analysis, November 2026: each region's rate divided by the East US rate, and 0.013 divided by two vCPUs.

Two EU member states, Germany and Poland, charge 0.115 US dollars an hour for the same virtual machine that Sweden charges 0.102 for, which is 0.65 cents a vCPU hour and 4.75 US dollars a vCPU a month at 730 hours. The buyer supplies the core count. The region that produces that difference is chosen before anyone knows the number, because a residency clause names a jurisdiction and the jurisdiction carries a price the clause does not mention. This reaches you if a member state is written into a residency attestation or a multi-year cloud commitment and the choice was made by whoever owns the obligation rather than whoever owns the compute budget.

RegionEU memberUSD per hour, 2 vCPUPremium over East USUSD per vCPU hourRate in force since
East USNo0.096Reference0.0481 November 2021
Sweden CentralYes0.102+6.25%0.0511 January 2022
Spain CentralYes0.107+11.46%0.05351 February 2024
UK SouthNo0.111+15.63%0.05551 November 2021
Italy NorthYes0.112+16.67%0.0561 December 2023
Germany West CentralYes0.115+19.79%0.05751 November 2021
Poland CentralYes0.115+19.79%0.05751 February 2025
US Gov VirginiaNo0.121+26.04%0.06051 November 2024
US Gov ArizonaNo0.121+26.04%0.06051 November 2024
Norway EastNo0.127+32.29%0.06351 May 2022

Microsoft's Azure Retail Prices API, the vendor's published price list, queried on 5 November 2026: serviceName Virtual Machines, Standard_D2s_v5, priceType Consumption, Windows meters excluded, unit of measure 1 Hour. The size is confirmed as 2 vCPU and 8 GiB on the vendor's Dsv5-series size page at learn.microsoft.com, read on 5 November 2026. Premiums and per vCPU figures are Mosaic Singularity analysis, November 2026. EU membership is not a vendor field.

The machine size does not touch the multiplier

Nine of the ten regions price the 4 vCPU machine at exactly double the 2 vCPU rate, which is what a per vCPU rate times a regional index looks like when the machine size changes and the region does not. East US charges 0.048 a vCPU hour, Sweden Central 0.051, Germany West Central 0.0575 and US Gov Virginia 0.0605, the same four figures as on the smaller machine. Norway East is the tenth and is not exact. Its 0.127 at 2 vCPU implies 0.254 at 4 vCPU, and the price list says 0.253; at 8 and 16 vCPU the per vCPU figure is 0.06325 both times, so the outlier is the 2 vCPU row and the 4 vCPU premium reads 31.77% rather than 32.29% (Mosaic Singularity analysis, November 2026). One row in ten moves, by a tenth of a cent an hour on the machine, on the highest rate in the table. The buyer's control set does not change between the two sizes: same region, same residency, same attestation, same agreement. What changes is the core count. The multiplier does not.

The sharper evidence is the pair at 19.79%. Germany West Central's rate has carried 0.115 since 1 November 2021, which is 1,830 days. Poland Central's has carried the identical 0.115 since 1 February 2025, thirty-nine months later, in a different country and off a different power market. A recovery of cost to serve does not land on the same three decimal places twice, thirty-nine months apart. A published band does, because a band is a decision and a cost is a measurement.

The multiplier does not track the number of controls a buyer accepts either. The two US Government regions sit at 26.04%, below Norway East at 32.29%, and the United Kingdom, which left the European Union in 2020, sits at 15.63%, above Sweden and Spain. An index that rose with regulatory burden would not produce that order.

Who controls it: the address on the form, not the control in the contract

A residency obligation is discharged by placing a workload in a named jurisdiction and attesting to it. The controls are the same in all five member states: one platform, one catalogue, one set of support terms, sold by one vendor under one agreement. What differs is the address. The vendor's published price list carries a rate per region per SKU and no field that describes itself as a regional premium, so the spread exists only once someone puts the regions side by side, and the party who would have done that is the party that chose the address on compliance grounds.

Data figure: nine Azure regions plotted by the effective date of their hourly rate on the horizontal axis and their premium over East US on the vertical axis, from zero to 32.29 percent, with Germany West Central and Poland Central joined by a dashed line at 19.79 percent.
Every region in the table, by the date its hourly rate took effect and by its premium over East US. Germany West Central and Poland Central sit on one dashed line thirty-nine months apart. Source: Microsoft's Azure Retail Prices API price list, Standard_D2s_v5, queried on 5 November 2026.

Who carries the risk: the clause is written in the wrong unit

The obligation is satisfied in Sweden, Spain, Italy, Germany or Poland, five EU member states, at five prices between 6.25% and 19.79%. Written as the European Economic Area, the same clause admits Norway, the highest rate in the table at 32.29%. Written as Europe it admits the United Kingdom at 15.63%. One word decides whether the commitment sits at the bottom of the ladder or the top of it, and the person who chooses the word is usually the person attesting to the obligation, not the person signing the commitment value.

The exposure compounds, because the premium is a percentage on a per vCPU rate. Lift both regions by 10% and the percentage stays where it is while the Frankfurt to Stockholm gap rises from 0.013 to 0.0143 an hour (Mosaic Singularity analysis, November 2026). A buyer that treats the region choice as a one-off saving is buying a rate for the term, not a discount.

Who gains: the lowest rung, and a vendor that pays nothing for the gap

The buyer who reads the ladder takes the cheapest rung that satisfies the obligation, Sweden Central at 6.25% over East US, which is 0.3 cents a vCPU hour. The vendor is indifferent: the same machine, the same support, priced by country rather than by what it costs to serve that country. The enterprise that defaults to Germany because a customer's security questionnaire was easier to answer that way, or to Poland because a local entity already exists there, pays 12.75% more for the same outcome and holds an attestation proving it chose to.

Nothing on the invoice describes a regional premium. The line item is compute, the amount is larger, and the comparison that would have shown it is one that nobody in the process is paid to run.

Document excerpt: two price records returned by the Azure Retail Prices API, for germanywestcentral and polandcentral, each showing skuName Standard_D2s_v5, retailPrice 0.115, unitOfMeasure 1 Hour, and effective start dates of 2021-11-01 and 2025-02-01.
The vendor's own record for the two regions that charge the same rate, as returned on 5 November 2026: identical retail price, effective dates thirty-nine months apart. Source: Microsoft's Azure Retail Prices API price list, queried on 5 November 2026.

What to decide, and by when

SeatWhat to doBy whenWhy this one
CIO or head of infrastructureRe-query the price API for every SKU under a residency obligation on one date, and move each workload without a jurisdiction-specific requirement to the cheapest member state the attestation permits31 March 2027Germany and Poland charge 12.75% more than Sweden for the identical machine, 0.65 cents a vCPU hour, with no difference in the controls attached
DPO or CISORead the residency attestation before it is signed and confirm it names a member state rather than a boundaryAt the next attestation, and no later than 31 March 2027Five member states meet the same obligation at prices between 6.25% and 19.79%, and the attestation is what makes the expensive one mandatory
CFOWrite the permitted region set and the multiplier into the cloud commitment before signature31 March 2027A clause that says EU permits any member state at the supplier's discretion, and the spread inside the EU is 6.25% to 19.79%
General CounselCheck whether the residency clause reads EU, EEA or EuropeBefore the next renewal signs, and no later than 31 March 2027Norway is in the EEA and not the EU and carries 32.29%, the highest rate in the table and 24.51% above Sweden

Mosaic Singularity analysis, November 2026, on the Microsoft Azure Retail Prices API price list queried on 5 November 2026. The 24.51% is 0.127 divided by 0.102. 31 March 2027 is the close of the first planning quarter in which these rates and a signed cloud commitment can be put on the same page.

The questions a board should put to management before 31 March 2027

What reaches the board from this analysis is a single term: the permitted region set and the multiplier written into the cloud commitment before signature, by 31 March 2027.

  • Which member state is named in each residency attestation we have signed, and what does the same machine cost in the cheapest member state that would also have satisfied it?
  • Who chose that region, and did that person hold the compute budget when they did?
  • Does each clause name a country, a region set or a boundary, and which of the three did legal intend?
  • How much of our annual compute spend sits in Germany or Poland, and how much of it is there for a reason a regulator would recognise?
  • At our core count, what is the Frankfurt to Stockholm gap in dollars, and what does it become if the base rate rises 10%?
  • Has the supplier been asked to reprice the same commitment in Sweden Central, and what did it answer?

The ladder is tested on 31 March 2027

Re-query Standard_D2s_v5 and Standard_D4s_v5 on 31 March 2027. If the premiums still read 6.25% and 19.79%, the reading holds that a buyer signs a fixed index and the region choice is the whole of the decision. If they have converged or crossed, the premium was a live price, and a buyer who signed in this window has a hedge to check rather than a saving to book.

The second test is the sovereign tier. Amazon's published AmazonEC2 region index, a price index whose stated publication date is 4 November 2026, carries 106 regions, of which exactly two are government regions, us-gov-west-1 and us-gov-east-1. No European sovereign region appears in it, so a buyer comparing a sovereign region against a standard one has no European sovereign rate to compare. The first such rate card will be the first priceable sovereign premium, and on the evidence of this ladder it will be published above the 19.79% ceiling. If it lands at or below 19.79% against that vendor's own standard European region, the claim that residency carries a vendor-set multiplier fails.

Frankfurt costs 12.75% more than Stockholm to keep the data in the EU: full report5 pages