Office & productivity configuration

These are the settings that decide whether users trust a new device: Outlook behaving the organisation's way, sensible Office defaults, and no first-run pop-ups — each one planned in writing, itemised, and covered by per-item rollback, deployed through your own Intune tenant.

Why this matters

A device can enrol cleanly, receive every app and pass compliance — and still generate a steady stream of tickets, because Outlook arrived with the defaults Microsoft chose rather than the ones your organisation actually runs on. The BCC field is hidden. Focused Inbox has quietly filed a director's messages under Other. Windows search can't see inside PDFs. Every app throws its own welcome tour on first launch.

None of these is an outage, and that's exactly the problem: they never make a project plan, they're rediscovered from scratch on every rollout, and the fixes are scattered across ADMX policy, Cloud Policy, per-user registry values and app-specific quirks. Individually trivial; collectively, they're the difference between a rollout users trust and one they quietly work around.

What a good build does

Decolla treats this snag list as first-class configuration. The Office & productivity section sits at the configure stage of the journey-ordered catalogue, and its items come from the Library — pre-built settings that capture the recurring helpdesk fixes teams keep re-solving: suppressing first-run and privacy prompts across installed apps, pointing default save locations at the organisation's drive, making Windows search index PDF content.

Nothing runs on assumption. Every selected item appears on the written, itemised plan you approve first, with its delivery mechanism and reversibility class stated per item — anything irreversible is flagged before you agree to it. Deployment is then unattended, in your own Intune/Autopilot tenant; Decolla doesn't sit between you and your endpoints. And because these are changes Decolla itself applied, each is covered by per-item rollback of Decolla's own changes: if the organisation later decides Focused Inbox should stay on after all, that one item comes back out without disturbing the rest of the build.

Where it bites people

• The cached-mode "data loss" panic. Cached Exchange Mode defaults the sync slider to a short window, so users open a freshly provisioned device and find years of mail apparently deleted. The tickets say data loss; the cause is a default. The fix has to land before first launch — once Outlook has built its local cache on the short window, correcting the policy afterwards means a disruptive re-sync rather than a clean start.
• First-run whack-a-mole. Suppressing Office's privacy dialogues does nothing about Edge's welcome experience or OneDrive's tour. Each app has its own mechanism — ADMX here, a registry value there — so teams "fix first-run" three separate times and still get screenshots of pop-ups on day one. It's why the catalogue carries a clean first-run bundle covering Edge, Office and OneDrive as a single planned item, rather than leaving you to assemble the set by trial and error.

What's in this section (21 items)

Reversibility: auto reverses when unassigned · reverse reversible with a documented step · irreversible flagged before you approve the plan.