An Enforcement tells Policy Enforcer which Teams Manager Policy to watch and how to handle each kind of Violation. You build one Enforcement per Policy, and nothing is watched until one exists.
đĄ If Policy Enforcer isn't connected to Teams Manager yet, start with Installing and Setting Up Policy Enforcer. The Policy list is read from the connected instance.
âď¸ Creating an Enforcement
Everything happens on the Configure enforcement screen.
To reach it:
Open Policy Enforcements.
Click + Enforce Policy.
Pick a Policy and click Configure. Only Policies that already exist in your connected Teams Manager instance appear here.
The screen opens with the Recommended preset already applied, and has three parts:
Activate policy enforcement - a toggle, on by default. While it's on, the enforcement detects violations and acts on them. Turn it off to pause without losing anything you've configured.
A Preset - sets a default action for all eight violation types at once.
The eight violation types - each row shows the action that will be taken when that violation is detected.
𧊠Choosing a Preset
A Preset configures all eight Violation Types in one move.
Recommended (the default) - violations are resolved automatically where possible. For the rest, team owners review and resolve them, and admins are informed when something is dismissed.
Strict - every violation is forwarded to admins for review and resolution, including the ones that could have been handled automatically.
Applying a Preset overwrites all eight types. If you've already changed a type by hand and then apply a Preset, Policy Enforcer asks you to confirm first.
đ§ Handling Each Violation Type
Each row shows a Violation Type and the action set for it: Automatic, Notify owners, Notify admins, and so on.
To change one, select its row. A dialog opens with three actions:
Ignore - the change is recorded so you can see it happened, but nothing is corrected and no-one is notified.
Automatically resolve and notify - the change is reverted, and the resolution groups you choose are notified that it happened.
Let resolution groups review - nothing is corrected automatically. The groups you choose are notified, and one of them picks how to resolve it.
For the last two, choose at least one Resolution Group to notify: Team Owners, Teams Manager Admins, or both. Choosing Ignore removes the group selector, since there's no-one to notify.
Changing any type switches its badge from the Preset name to Custom. That's expected.
When everything reads the way you want, click Save. The Enforcement appears in the Policy Enforcements list with its Preset, how many types are configured, and whether it's Active or Off.
đ The Eight Violation Types
Five can be resolved automatically. The other three always need a person, because Policy Enforcer can work out what a name should be but not who should own a Team, so for those three the automatic action isn't offered.
Resolved automatically:
Naming convention breached - the space was renamed and no longer matches the naming convention
Visibility changed - the space went from private to public
Planner renamed
OneNote renamed
Sensitivity label changed
Always need a person:
2-owner policy - an owner was removed and the team now has fewer than two
Default owners removed
Default members removed
đď¸ Deleting an Enforcement
Select the delete action next to an Enforcement and confirm. Deleting removes it entirely, Policy Enforcer stops watching that Policy, and it can't be undone.
To pause instead, switch Activate policy enforcement off on the Configure enforcement screen. Your configuration survives, and turning it back on picks up where you left off.
đŁ Next Steps
Now that your first Enforcement is live, it's time to see how the watching works and where Violations turn up.
We recommend starting here:
âď¸ Need more help?
Get further assistance with Policy Enforcer through our support chat widget within the app, or reach out to us at [email protected]