https://blog.azureinfra.com/feed/

In my previous External Key Store versus Managed HSM post I claimed Managed HSM was safer, had better SLA support, much higher SLA and the risk of key compromise was lower.

I deliberately moved this chapter to the end; not because AI is less important, but because it is often treated as the starting point in sovereignty discussions.

This is where the conversation gets uncomfortable, because for all of the removing emotions, the structured risk models, and trade-offs we’ve discussed so far; sovereignty discussions are not just about facts.

Time to get real.. we talked about all the things we need to take into account.

In our previous posts, we discussed sovereignty as a risk, the trade-offs that come with it, and the reality of Europe building its own hyperscale ecosystem.

In the past few posts we’ve discussed how to address Sovereignty as a risk, what the trade-offs are and now its the “why can’t we build this ourselves” chapter.

in our previous posts I’ve described that sovereignty risks are risks that should be evaluated as such.

In the intro I talked about treating sovereignty as a risk.

This blog is mostly technical, but over the last few years I’ve focussed on the sovereignty aspect of public cloud (well before it became the topic everyone is talking about now).

I’ve talked about sovereignty in Azure (or cloud in general) before.. and we are going to dive a little deeper into it this time.