Pick the protections you want in your script.
Profiles blend strictness and compatibility. Relaxed focuses on safer macro and privacy controls. Strict turns on the full STIG style baseline, including legacy IE feature protections and ActiveX limits. Custom lets you hand pick each control.
Profile cheat sheet
- Relaxed focuses on macro and privacy controls that rarely break everyday work.
- Strict includes everything in Relaxed plus aggressive legacy IE and ActiveX protections.
- Custom keeps your current checkboxes and lets you build a one of a kind mix.
Relaxed selects macro, scanning, and privacy controls that rarely break normal use. Strict adds all legacy IE feature protections and ActiveX restrictions from the STIG.
Tip: For most home and small business environments, Relaxed is a sensible default. Use Strict for hardened builds where legacy ActiveX or embedded IE behaviors are not required.
Generated Office 365 baseline script
How to use: Save the contents to a file such as office365-baseline.ps1, right click PowerShell and choose Run as administrator, then run .\office365-baseline.ps1. Once loaded, apply settings with Invoke-O365Baseline and attempt rollback (for supported keys) with Invoke-O365BaselineRollback.
Scope: This helper targets the Office 16.0 policy paths and common IE feature controls used by Office host processes. Always confirm they match your tenant and deployment model, especially if you are using newer Microsoft 365 Apps channels or additional policy templates.
Before you run the script
- Use this only on systems and tenants you are explicitly allowed to manage.
- Create backups or configuration exports of existing Office policy keys before applying changes.
- Generate the script and skim every section, especially Strict profile IE/ActiveX controls.
- Comment out any blocks that conflict with organization wide GPO or MDM baselines.
- Test on a non critical machine joined to a representative tenant or domain first.
Good next steps
- Save your adjusted script into version control or a secured admin repository.
- Document which STIG style rules you enforced and how they map to your policies.
- Coordinate with your security, compliance, or messaging teams before broad rollout.
- Revisit this baseline when Office channels, add-ins, or browser integrations change.