Sovereignty is not about where the sticker is. It is about who holds the power.

Control. Access. Legal reach. Operational dependency.

So yes, I’m glad the hyperscalers are now speaking more openly about sovereignty.

It would just be slightly more convincing if their solution was not, almost every time, “you can absolutely reduce dependency by depending on us differently.”

That is where SkyeConnex takes a less theatrical approach.

We do not treat sovereignty as a branding exercise with regional hosting and a polished brochure. We treat it as an architectural problem. If one provider still holds the whole file, the whole control plane, or the whole leverage, then congratulations: you may have improved the packaging, but you have not solved the dependency.

A local data centre is not a force field. A sovereign SKU is not independence. And “trust us, but with extra settings” is still not much of an exit strategy.

Microsoft validating the problem is good for all of us. It means sovereignty is no longer being dismissed as a fringe concern raised by the annoying people in the room who kept reading the fine print.

Now it is a boardroom issue.

Good.

Because the next awkward question is the one that matters:

If your sovereignty strategy still begins and ends with a single foreign provider, is it actually sovereignty, or just dependency with better branding?

That is exactly why I built SkyeConnex.

Because no single provider should hold the whole file, the whole risk, or the whole power.

And that tends to make the sovereignty conversation much less magical and a lot more real.

https://www.microsoft.com/en-us/microsoft-cloud/blog/government/2026/04/02/5-takeaways-from-the-2026-microsoft-digital-sovereignty-summit/


Originally published by Ross Norrie, founder of SkyeConnex, on LinkedIn.

Published April 18, 2026 · More from the SkyeConnex blog