The questions you should be asking

You are being asked to let a tool write into your Intune tenant. Scepticism is the correct response. Here are the answers to the questions it should raise.

Access, scopes and data

Which Microsoft Graph scopes does Decolla request?

The full list is published before you connect — the complete set, not a summary. Put it in front of your security team, challenge anything that looks broad, and grant consent only when you are satisfied. Consent lives in your own Entra tenant, so you — not we — hold the off switch.

Where does our data live?

The important answer is architectural. Everything Decolla deploys — policies, applications, scripts — is created in your Microsoft Intune tenant and stays there, under the residency arrangements your tenant already has. The estate that matters — your configuration, your devices — lives in your tenant, not on our infrastructure. Decolla is a product of The Cloud Platform Ltd, a UK company.

What happens if The Cloud Platform disappears tomorrow?

Your estate keeps working. Decolla writes standard Intune objects into your tenant; they are visible in the Intune admin centre and manageable without us. You would lose the assembly tool — the wizard, the library, the rollback tooling — not your configuration or your devices. Delivery to devices is native Intune and Autopilot, not our infrastructure.

Control and rollback

Can we see exactly what will change before anything runs?

Yes — that is the point of the plan. Before deployment, Decolla produces an itemised written plan: every item, its delivery method and its reversibility class — automatic, reversible, or irreversible and flagged as such. Nothing runs until you have read and approved it. If a line makes you uncomfortable, take it out.

What exactly does rollback cover — and what does it not?

Rollback covers Decolla's own changes, per item or for the whole build, and nothing else. If a Windows installation fails or an Enrollment Status Page sticks, that is Microsoft-side behaviour Decolla cannot unwind — the same as if you had built everything by hand. What you gain is the ability to reverse what Decolla put in, which is exactly the part manual work makes hard to trace.

Will our deployments run faster?

No — and be sceptical of anyone who says theirs will. Windows installs, Enrollment Status Page phases and Intune sync run at Microsoft's pace; Decolla changes none of that. What collapses is assembly: choosing, building and testing the policies, scripts and fixes that make up a build. Defining a build takes minutes instead of weeks of DIY assembly.

We already have a configured tenant. Will Decolla trample it?

The conditional engine distinguishes existing tenants from new ones and filters the catalogue accordingly, and the plan shows every proposed change before anything runs. Decolla touches only what is in the approved plan, and its rollback tracks only its own changes — so what it did and what you did stay distinguishable.

The Library

How are library items tested?

The library comes out of working IT consultancy practice — The Cloud Platform's day job — not a lab. Its items are the recurring fixes, policies and hardening steps real estates keep needing, built with our own mechanisms and industry-tested before they reach the catalogue. Each one declares its delivery method and reversibility class, so you can judge the blast radius before you approve it.

How big is the catalogue, and does it grow?

260+ build items across 21 sections, and growing. You never face all of them at once: the engine filters by platform, chassis, scenario and make, then defaults intelligently — OEM tooling by manufacturer, power settings by chassis, drive strategy, locale, the HVCI gate.

Prerequisites and practicalities

What licensing do we need?

Microsoft Intune licences for the devices you provision. Decolla orchestrates your tenant; it does not replace the licensing underneath it. If you are not licensed for Intune and Autopilot today, Decolla will not change that — better to know now than after joining the waitlist.

Do the devices being provisioned need anything extra?

No. Delivery to devices is handled by Intune and Autopilot — the same native Microsoft mechanisms your tenant already relies on. Decolla assembles what goes into the tenant; Microsoft's machinery carries it to the endpoint, so there is nothing additional to install or maintain on the devices themselves.

We are an MSP. Can we manage multiple customer tenants?

Not yet, and we will not claim otherwise. Decolla today is built for an organisation provisioning into its own tenant; we make no multi-tenant or MSP-management claims. If MSP use is your model, join the waitlist and say so — we would rather be honest about today than sell you tomorrow.

Commercials and exit

How do we disconnect if we change our minds?

Revoke Decolla's consent in your Entra tenant; access ends there, because it was always granted on your side. Before you do, roll back Decolla's own changes per item or per build — or keep them. Everything deployed is standard Intune configuration and remains yours to manage. There is no exit process that depends on our cooperation.

What does it cost?

Pricing will be published at launch. We are not being coy for effect: Decolla is in private build, and we would rather publish real pricing once than float numbers now and walk them back later. Until then, the only commitment we ask for is a waitlist entry.

If your question is not answered here, join the early-access waitlist and ask it. Sceptics make the best early users — the plan-and-rollback design exists for exactly the questions you just read.