Can organizations strenghten their digital sovereighty without sacrificing performance? According to Philip Verlinden, Dynamics 365 Solution Architect at Reply Business Elements, the anwser lies in deliberate architectural choices: protecting the workloads and data that truly require soveireignty, while still taking advantage of the cloud where it adds value.

1. Is digital sovereignty now a structuring factor from the very early design stage of IT architectures? If so, how does it translate into decisions?

Yes, digital sovereignty is increasingly becoming a structuring factor in the early design of IT architectures, but the extent depends on the organization’s context. For public institutions, sovereignty concerns are often shaped by public opinion, political pressure, regulatory expectations, and broader industry debate, especially in the current geopolitical climate. In practice, this translates into early decisions about hosting location, data residency, dependency on non-EU providers, operational control, support models, and whether critical workloads should run in cloud, hybrid, edge, or disconnected environments. 

2. To what extent can prioritizing digital sovereignty impact performance, scalability, and agility? How do you address this issue?

Prioritizing digital sovereignty can affect performance, scalability, and agility, especially when organizations move away from highly elastic hyperscale services toward more controlled, localized, or disconnected environments. The impact depends on the maturity of the sovereign provider and the operating model behind it. Established providers should be able to scale effectively, while newer players may initially focus on narrower use cases before expanding to larger workloads. Hyperscalers such as Microsoft also offer sovereignty-oriented options, such as Azure Local, where approved hardware can support workloads in a customer-selected location. The trade-off is that organizations may need to return to more traditional capacity planning, considering current and future capacity needs, network security, fire protection, backup, and the resources required to operate the environment.

3. Hybrid and multi-cloud architectures are often presented as solutions to reconcile digital sovereignty with performance. In practice, how effective are they, and under what conditions do they truly deliver on their promises?

Hybrid and multi-cloud architectures can help reconcile digital sovereignty with performance, but they only deliver when the operating model is clear. Multi-cloud can be effective for global SaaS or service providers that need to distribute infrastructure capabilities across regions or providers, such as streaming services. Hybrid is often the more familiar and practical model, especially in Microsoft-oriented environments, because it allows organizations to combine central cloud services with local or edge processing. This is particularly useful where connectivity is intermittent or where workloads need to keep running locally, such as in maritime scenarios where vessels process data on board and synchronize back when a connection is available. The key condition is that architecture, governance, integration, security, and operations are designed together; otherwise, hybrid and multi-cloud can add complexity without delivering real sovereignty or performance benefits.

4. In your view, what are the main limitations or trade-offs when organizations aim to strengthen their digital sovereignty?

One of the main limitations is a misunderstanding of what digital sovereignty really means. An organization does not automatically become sovereign simply by replacing a non-EU software dependency with an open-source alternative hosted locally. That software may still run on, depend on, or be consumed through non-EU network infrastructure, hardware, support chains, or operational services. The broader trade-off is that sovereignty can increase complexity, require more explicit architectural control, and shift responsibility back to the organization for capacity, operations, security, resilience, and lifecycle management. True sovereignty therefore requires a broader view of the full technology stack, supply chain, and operating model.

5. Could you share a success story in the field of digital sovereignty?

One success story is when digital sovereignty is applied selectively rather than as an all-or-nothing principle. For example, an organization may keep its most critical applications and sensitive data in a controlled hybrid environment, with clear rules around hosting location, operational access, support, and resilience. At the same time, it can still use cloud services for supporting capabilities such as CI/CD, telemetry, support tooling, or performance monitoring, where scale, flexibility, and cost efficiency matter more than full sovereignty. In that scenario, the value comes from making conscious architectural choices: protecting the workloads and data that truly require sovereignty, while still benefiting from modern cloud capabilities where they improve delivery speed and operational quality.

This interview was originally published on The Dots Luxembourg website.