Deployment

You have read the plan and approved it. Here is exactly what runs, where it runs, and what Decolla will — and will not — claim about how fast it goes.

It runs in your tenant, not ours

The moment you approve the plan, execution passes to infrastructure you already own. Decolla deploys through your Microsoft Intune and Windows Autopilot tenant — the same delivery machinery you would use if you built the whole thing by hand. There is no shadow management plane, no parallel agent estate, no enrolment of your devices into anything that belongs to Decolla.

Before you connect, the Microsoft Graph scopes Decolla requests are published in full. You can read precisely what access is being asked for before granting any of it. If you own the risk for your estate, that reading should happen before any vendor touches it — Decolla is built on that assumption, not in spite of it.

An honest word about pace

Windows installs at Microsoft's pace. So does the Enrolment Status Page, so does policy sync, so does every application your device pulls down. No tool changes that, and Decolla does not claim to. If a vendor tells you they have made ESP faster, ask them how.

What Decolla removed is the other kind of time — the weeks that go into assembly. Finding the right script, testing the detection rule, sequencing the applications, hunting down the one setting that finally kills a recurring helpdesk ticket. The Library holds pre-built, industry-tested policies, scripts and fixes, so that assembly happens in seconds rather than weeks, and defining the build takes minutes. The install itself still takes exactly as long as Microsoft takes. We would rather tell you that on this page than have you discover it on day one.

Unattended means unattended

Once the plan is approved, the deployment runs without anyone sitting at a keyboard. Every item in the plan carries its stated delivery method, and each is executed through your tenant exactly as written — no improvisation between what you approved and what runs.

One thing you will not get is theatre. Decolla does not overlay a live progress feed on top of Microsoft's machinery; Intune remains your source of truth for device state, as it should be. What Decolla commits to is narrower and more useful: nothing runs that was not in the plan you read.

What you get at the end

A device built to the itemised plan you approved — no more, no less. Depending on what you selected from the catalogue of 260+ build items across 21 sections, that means:

• Applications and configuration delivered through your Intune tenant, item by item, by the method stated in the plan.
• Hardening applied as part of the build, not bolted on afterwards.
• The recurring, mundane helpdesk fixes — the ones every fleet ends up applying eventually — already in place, through Decolla's own mechanisms.
• The defaults you confirmed at the Configure stage honoured throughout: OEM tooling matched to make, power settings matched to chassis, drive strategy, locale, the HVCI gate, and existing-versus-new handling.

Every change on the device is a known quantity, because every item declared its delivery method and reversibility class — auto, reversible, or flagged irreversible — before you approved it.

If something needs to come back out

Rollback works per item or across the whole build — and it covers Decolla's own changes only. That boundary is worth stating plainly. If a Microsoft install fails or an Enrolment Status Page gets stuck, that is Microsoft's platform behaving as Microsoft's platform sometimes does; no tool can honestly claim to reverse it, and Decolla will not pretend otherwise. What Decolla will do is unwind what Decolla put in — cleanly, item by item, or all of it.

Anyone who has skimmed an r/sysadmin thread on provisioning knows this trade runs on scepticism, and has earned the right to. Decolla's answer is to put the boundaries in writing before anything runs: the plan, the scopes, the reversibility class of every item. Decolla is in private build at The Cloud Platform, and early access is by waitlist — if you would rather judge the plan than the promise, that is where it starts.