Launch a campaign in seven steps

01What you will do #sec_fe0cce3f

Create a recertification campaign, from intention to launch. The wizard has seven steps and refuses to move forward until the previous one is complete.

Allow thirty minutes for a first restricted campaign.

02Before you start #sec_a6417db4

Restrict your first scope. Only one group, only one application. A wide scope multiplies the reviewers solicited and lengthens the review without learning anything more — and you will learn more from a campaign closed in two weeks than from a campaign bogged down in three months.

Also check three things: the correct workspace is selected in the banner, you have remaining credits, and the data has been collected.

03The path #sec_023b40ff

Campaigns › New campaign. The wizard opens at step 1 of 7, with the list of steps on the left and a progress bar.

04The seven steps #sec_08154edf

Step 1 — Intention

What do you want to certify?

*Choose the resource to be recertified and the policy to be applied. This choice determines everything*

*the rest of the journey — available reviewers, criteria, rules.*

Two blocks.

TECHNICAL SCOPE — three cascading lists: Solution (Microsoft M365…), then Workload, then Resource. Each one opens the next only once filled in.

POLICY TO BE APPLIED — policies only appear after the choice of workload: choose a workload to see the available policies. Five families:

This is the step that counts. The screen itself says it: this choice determines the eligible reviewers, the displayed criteria, and the applicable rules. Making a mistake here cannot be undone later.

Step 2 — Identity

The name of the campaign, and what will allow it to be recognized.

Name it for six months from now, not for today. "Q3 Review" means nothing to someone opening the file two years later. "OneDrive Inactivity — Finance Department — S2 2026" is understandable without context.

Step 3 — Scope

What the campaign will examine exactly: inclusions, and exclusions.

An exclusion set here is a governance decision, not a display filter: what is excluded will not be examined, and the certification file will bear this absence. To permanently put a resource out of scope, Sanctuarization is the right tool — it requires a reason and a deadline.

Step 4 — Reviewers

Who decides. Three modes:

Check the load before validating. A mode that designates forty reviewers for three requests each works; a mode that designates one for two thousand will not work, and you will discover it at the deadline.

Step 5 — Cadence & communication

The deadline, reminders, messages sent to reviewers.

The deadline is what makes steering possible: without it, there is no delay, therefore no alert, therefore nothing to remind.

Step 6 — Certification rules

What counts as a decision, and what requires individual review.

This is where mass certification is set: which categories can be certified in bulk, and which ones require one-by-one examination. The reviewer will see the result in the form of an "N excluded — individual review" that they cannot bypass.

These rules are set at three levels — global, workspace, campaign — and an overload only records its deviations from the rule above.

Step 7 — Review & launch

The summary before arming.

Really read it. Launching a campaign produces requests, and a request is addressed to someone: a scope too wide means hundreds of solicitations that will have to be assumed. A closed campaign cannot be "undone".

05After launch #sec_f8bd6d3c

It appears in Campaigns › Manage campaigns, and its progress in Campaigns › Steering.

The first hours are the most instructive: if reviewers escalate en masse, it means the scope or the designation mode needs to be reviewed — and it's better to learn it on the first day.

06To remember #sec_e57aac0d

Seven steps, and the first one commands the other six. Restrict the scope, name for the future reader, check the reviewers' load, and read the summary before arming.

Next: [steer, unblock, report](tuto-workspace-steering).