Coming in V2.0 · optional, and off unless you switch it on

Tell people why their drives just appeared.

Preferences arrive quietly: a drive maps, a printer connects, a registry value changes. To the person at the keyboard that is either invisible or unexplained. A branded notification, shown only while the work is happening, turns it into something they understand rather than something they log a ticket about.

Coming in V2.0

Notifications are not live yet — they ship with Cloud Policy Preferences V2.0. Everything below is the design, and the preview is real, so you can see exactly what your users would see.

When it does arrive it is optional and off by default. No notification appears on any device until an administrator turns it on for the tenant, and one switch turns it off again.

Style
Logo Accent
09:41
Two styles

As much or as little as the moment warrants.

Pick one per tenant. Both carry your logo, your organisation name and your accent colour.

Full

For the first sign-in on a new device, when somebody genuinely wants to know what is being set up.

  • Heading and a line of explanation you write
  • Every policy type listed, ticking off as it completes
  • A Dismiss Notification button

Compact

For every run after that — present enough to answer the question, small enough to ignore.

  • Wide and short — one line of status
  • Progress bar, no step list
  • A single in the top right
What you can set

Yours, not ours.

When it arrives, every option will live on one page in the portal, with the same preview you have been clicking above.

On or off

Off until you turn it on, and a single switch turns it off again for the whole tenant. Nothing is shown to anyone before you decide.

Your logo

Upload a PNG and it replaces the Cloud Policy Preferences mark. It travels with the policy payload, so it renders even when the device is offline.

Your accent

Colours the top strip, the progress bar and the active step, so a corporate logo is not fighting somebody else's brand colour.

Your words

Set the organisation name, the heading and the line of explanation. The per-type wording — "Mapping network drives", "Connecting your printers" — comes as sensible defaults.

Full or compact

One choice for the tenant. Switch between them in the preview before you commit, and change your mind whenever you like.

Only while it works

It appears when a run has something to do, updates as each type completes, and closes itself when the run ends. A run that changes nothing shows nothing.

How it reaches the user

Started by SYSTEM, shown to the person signed in.

The remediation runs as SYSTEM, which has no desktop of its own — anything it draws would appear to nobody. The notification is handed to a short-lived scheduled task registered against the signed-in account, exactly as per-user printer and drive policies already are.

See the setup steps
01Nobody signed in, nothing shownThe run still applies machine-wide settings; the notification is simply skipped.
02No agent, no installerIt is drawn by the same remediation you already deploy through Intune. Nothing extra lands on the device.
03One window, updatingProgress is written to a local status file the window reads, so five policy types produce one notification rather than five.
04Dismissable, and self-closingThe user can close it at any point; it closes on its own when the run finishes or if the run stalls.
05No data leaves the deviceThe notification reads a local file. It reports nothing back and asks the user for nothing.

Arriving in V2.0.

Notifications ship with Cloud Policy Preferences V2.0. Nothing changes on your devices until you switch them on, and you will be able to preview and brand them before a single user sees one.

Launch the portal