How it is set up
- Data from the machines travels over a secured connection into your own Azure tenant
- The storage runs under your ownership and your keys
- No parallel platform: it connects to your existing Microsoft stack
Why this prevents lock-in
Because the data sits in your own environment, you do not depend on VDS for access. If you stop working with VDS, you keep your data and your environment. That is the exact opposite of a supplier platform where your data is held hostage.
What your IT department has to do
Count on a short technical intake with your IT department or external ICT partner (MSP) to set up the connection and the tenant: no more than that, but also not 'IT does not have to do anything'. Management in year two runs through the maintenance contract; who does what is agreed in advance.
Frequently asked questions
Who owns the data?
You do. It sits in your own Azure environment, under your own ownership and management.
What happens if I stop working with VDS?
Your data and your environment stay yours; there is no platform lock-in blocking access.
Does this run in my own environment?
Yes, in your own Microsoft Azure tenant, connecting to your existing stack.
What does my IT department have to do?
A short technical intake to set up the connection and the tenant; after that, management runs through the maintenance contract.
