Standards
Standards ensures consistent configuration across your Microsoft 365 tenants by reapplying baseline settings every three hours. This prevents unauthorized changes and maintains security.
Last updated
Was this helpful?
Standards ensures consistent configuration across your Microsoft 365 tenants by reapplying baseline settings every three hours. This prevents unauthorized changes and maintains security.
Last updated
Was this helpful?
Standards in CIPP ensure consistent configurations across your Microsoft 365 tenants by reapplying baseline settings every three hours. This automatic enforcement prevents unauthorized changes and helps maintain security.
CIPP allows you to set standards in three different settings. Some standards can only be set to specific items, such as Intune standards which can only be "Remediated".
Report
Logs the current configuration and stores this inside of the CIPP database for your standards reports or BPA reports.
Alert
Sends you a notification via the configured method in CIPP -> Application Settings -> Notifications
Remediate
Changes the configuration of the tenant.
For example, when you wish to create a report for Audit log state across all your tenants, you can create an "All Tenants" standard that has the Audit Log standard set to "Report" - This fills the CIPP database with the current setting without editing the clients settings.
Setting this same standard to "Alert" allows you to receive an alert inside of your e-mail or ticketing system.
Setting this same standard to "Remediate" changes the clients configuration, and in this case would enable the audit log for the client.
Standards are merged based on their specificity and creation date:
Specificity: Standards applied to a specific tenant always override more general standards (like those set for 'All Tenants'). For instance, if an 'All Tenants' standard enables TOTP but you need it disabled for one tenant, creating and applying a tenant-specific standard will disable TOTP for that tenant.
Creation Date: When two standards conflict at the same specificity level (e.g., both tenant-specific), the standard created most recently takes precedence. For example, if you create a tenant-specific standard enabling TOTP and later create another tenant-specific standard disabling TOTP, the more recently created standard (disabling TOTP) will be applied.
Note: By default, standards aren't applied to any tenants upon setup of CIPP. You must manually configure and enable them. Apply standards with a clear understanding of their effects, detailed in the video and walkthrough on.
As of the update to v7 of CIPP, standards now operate via templates. Where previously, standards were either configured via the AllTenants "Edit Standards" page or an individual tenants "Edit Standards" page, multiple templates can be created to provide you with a more granular standards experience. Templates can be assigned to "AllTenants", "AllTenants" with excluded tenants, or just specific list of tenants.
If you are upgrading to v7 from a prior version of CIPP, you'll need to complete a one-time conversion of your existing standards by clicking the "Convert Standards" button at the top of the page. These standards will still not run on a schedule until you edit each template to your choosing and then toggling off the "Do not run on schedule" option.
For ease of reference, standards are grouped into pages within the following categories. These categories match the Category label on the standard selection page.
Applied across all tenants to manage organization-wide configurations.
Email-related settings such as spam protection and message handling.
Security measures to protect against phishing, malware, and other threats.
Device and application management policies for a secure Intune environment.
SharePoint and OneDrive configuration incl. sharing and retention policies.
Collaboration-related settings, i.e.: meeting policies and external file sharing.
Each of the separate standards category pages have a table listing of their respective standards that includes the following columns:
Standard Name
The name of the standard.
Description
A brief explanation of what the standard does.
Recommended By
The organization recommending the standard (e.g., CIS, CIPP).
API Name
Useful for logs and automation.
PowerShell Equivalent
The PowerShell command used to apply the standard manually.
Note: Disabling the "Remediate" option prevents future enforcement but does not undo previously applied changes.
Each standard is labeled based on the level of change it introduces and its impact on users:
Low
Minimal or no user-facing effects.
Medium
May require some communication with users to prepare them for changes.
High
Significant changes that could affect daily workflows; coordinate with clients before applying.
Companion Policies: Some standards rely on additional policies in tools like Microsoft Intune to be fully effective. Ensure all required companion policies are configured to achieve the desired results.
Deselecting Standards: Deselecting a standard prevents it from being enforced in future cycles, but it does not undo its current configuration.
Example: If you deselect "Enable FIDO2 capabilities," the standard will stop enforcing this policy. However, if FIDO2 was already enabled, it will remain enabled.
Precedence of Standards: Standards that are updated via multiple templates for a tenant will only apply the settings from the most recently created template.
Application Cadence: Standards reapply every three hours by default. If a setting changes outside of the standard, it will be overridden by the value specified in the standard during the next reapplication cycle.