ANAVEM
Languagefr
How to Implement Security Baselines in Microsoft Intune for Device Management

How to Implement Security Baselines in Microsoft Intune for Device Management

Deploy standardized security configurations across your organization using Microsoft Intune's built-in security baselines. Configure, customize, and monitor compliance for consistent device security.

March 26, 2026 12 min
easyintune 8 steps 12 min

Why Deploy Security Baselines in Microsoft Intune?

Security baselines in Microsoft Intune provide a standardized approach to device security that eliminates guesswork and ensures consistent protection across your entire Windows device fleet. These baselines represent Microsoft's recommended security configurations, developed by the same Windows security team that creates Group Policy baselines, giving you enterprise-grade security settings without the complexity of manual configuration.

The cloud-managed baseline system automatically updates with the latest security recommendations, ensuring your devices stay protected against emerging threats without requiring manual intervention. Unlike traditional Group Policy approaches, Intune baselines provide real-time compliance reporting, allowing you to identify and remediate security gaps immediately.

What Makes Intune Security Baselines Different from Manual Configuration?

Traditional device security management requires IT teams to research, test, and deploy hundreds of individual security settings across multiple policy areas. This approach is time-intensive, error-prone, and often results in inconsistent security postures across different device groups. Intune security baselines solve these challenges by packaging proven security configurations into ready-to-deploy profiles.

The baselines cover critical security areas including BitLocker encryption, authentication requirements, Windows Defender settings, firewall configurations, and network security protocols. Each setting includes detailed explanations and Microsoft's rationale, helping you understand the security impact of each configuration choice. This transparency allows you to make informed customizations while maintaining a strong security foundation.

How Do Security Baselines Integrate with Existing Intune Policies?

Security baselines work alongside your existing Intune configuration profiles and compliance policies, but they take precedence for settings they manage. This hierarchical approach ensures baseline security requirements are enforced while allowing additional customizations through separate policies. The system provides conflict detection and resolution guidance when overlapping settings exist across different policy types.

Implementation Guide

Full Procedure

01

Access Security Baselines in Intune Admin Center

Start by navigating to the Microsoft Intune admin center where all security baseline management takes place. This is your central hub for deploying and monitoring security configurations.

Open your web browser and navigate to the Microsoft Intune admin center. Sign in with your administrative credentials that have permissions to manage endpoint security policies.

Once logged in, navigate to Endpoint security in the left navigation pane, then select Security baselines. This section displays all available baseline types that Microsoft maintains and updates automatically.

You'll see several baseline options including:

  • Security Baseline for Windows 10 and later
  • MDM Security Baseline for Windows
  • Microsoft Defender security baseline
  • Microsoft 365 Apps security baseline

Verification: Confirm you can see the list of available baselines. Each baseline shows its current version and last update status. The baselines are cloud-managed, so you'll always see the most current versions without manual updates.

Pro tip: Bookmark the direct URL to security baselines: Endpoint security > Security baselines. You'll be accessing this frequently for monitoring and updates.
02

Select and Review the Windows Security Baseline

Choose the primary security baseline that will form the foundation of your device security strategy. The "Security Baseline for Windows 10 and later" is the most comprehensive option for general Windows device management.

Click on Security Baseline for Windows 10 and later from the available baselines list. This baseline contains Microsoft's recommended security settings for Windows devices and is regularly updated by the same Windows security team that creates Group Policy baselines.

Review the baseline overview page which shows:

  • Current version information
  • Number of settings included
  • Last update timestamp
  • Deployment statistics if you have existing profiles

Click Create profile to begin configuring your baseline deployment. This opens the profile creation wizard where you'll customize settings for your organization.

Verification: The profile creation wizard should open with multiple configuration tabs: Basics, Configuration settings, Scope tags, and Assignments.

Warning: Different baseline types may have conflicting default values for the same settings. If you plan to deploy multiple baselines, review all settings carefully to avoid conflicts.
03

Configure Basic Profile Settings

Set up the fundamental profile information that will help you identify and manage this baseline deployment across your organization.

On the Basics tab, configure the following required fields:

  • Name: Enter a descriptive name like "Corporate Windows Security Baseline - 2026"
  • Description: Add details about the purpose and scope, such as "Standard security configuration for all corporate Windows devices with BitLocker and authentication requirements"

The name should be specific enough to distinguish this profile from others you might create. Include the date or version information to track updates over time.

Click Next to proceed to the Configuration settings tab where you'll review and customize the actual security settings.

Verification: Ensure your profile name is unique and descriptive. The system will prevent duplicate names within the same baseline type.

Pro tip: Use a consistent naming convention across all your security policies. Include the baseline type, organization unit, and deployment date for easy identification.
04

Review and Customize Security Settings

Examine the default security configurations and modify them to match your organization's specific requirements. The baseline comes preconfigured with Microsoft's recommended settings, but you can adjust them as needed.

On the Configuration settings tab, you'll see categories of security settings. Key default configurations include:

  • BitLocker: Automatically enabled for removable drives
  • Authentication: Requires passwords to unlock devices
  • Network Security: Disables basic authentication protocols
  • Windows Defender: Enhanced threat protection settings

To modify a setting:

  1. Expand the relevant category (e.g., "BitLocker")
  2. Click on the setting you want to change
  3. Select your preferred configuration from the dropdown
  4. Review the setting description to understand its impact

Common customizations include:

  • Adjusting password complexity requirements
  • Modifying BitLocker encryption methods
  • Configuring Windows Defender exclusions
  • Setting firewall rules for specific applications

Verification: Each modified setting shows "Configured" status with your custom value. Settings left at default show "Not configured" but will still apply Microsoft's recommended values.

Warning: Avoid changing settings unless you understand their security implications. The default Microsoft recommendations provide strong security for most organizations.
05

Configure Scope Tags for Administrative Control

Set up scope tags to control which administrators can manage this baseline profile and which devices it can be applied to. This is crucial for organizations with multiple IT teams or geographic regions.

On the Scope tags tab, you can assign scope tags that limit administrative access to this profile. If your organization uses role-based access control, this step ensures only authorized administrators can modify the baseline.

To add scope tags:

  1. Click Select scope tags
  2. Choose from existing scope tags like "IT-Corporate", "Regional-EMEA", or "Security-Team"
  3. Select the tags that match your administrative structure
  4. Click Select to apply the tags

If you don't use scope tags or want all administrators to access this profile, you can leave this section empty. The profile will inherit the default scope.

Verification: Selected scope tags appear in the list with their names and descriptions. You can remove tags by clicking the X next to each tag.

Pro tip: Create scope tags that match your organizational structure before deploying baselines. This makes it easier to delegate baseline management to regional IT teams while maintaining security oversight.
06

Assign the Baseline to Target Groups

Configure which users or devices will receive this security baseline. Proper assignment ensures the baseline applies to the right devices while avoiding conflicts with existing policies.

On the Assignments tab, you'll configure deployment targets. Security baselines can be assigned to either user groups or device groups, depending on the scope of settings being configured.

To assign the baseline:

  1. Click Select groups to include
  2. Choose your target groups from the list (e.g., "All Corporate Devices" or "Finance Department Users")
  3. Click Select to add the groups

For exclusions, if needed:

  1. Click Select groups to exclude
  2. Choose groups that should not receive this baseline (e.g., "Test Devices" or "Executive Laptops")
  3. Click Select to add exclusions

Best practices for assignments:

  • Start with a pilot group of 10-20 devices for testing
  • Use device groups for settings that affect the entire device
  • Use user groups for settings that follow the user across devices
  • Avoid overlapping assignments that might create conflicts

Verification: Review the assignment summary showing included and excluded groups with member counts. Ensure the scope matches your intended deployment.

Warning: Deploying to "All Devices" immediately can cause widespread issues if settings conflict with existing policies. Always test with a pilot group first.
07

Deploy and Monitor the Security Baseline

Complete the baseline deployment and set up monitoring to track compliance across your device fleet. This final step activates the security settings and provides ongoing visibility into their effectiveness.

On the Review + create tab, review all your configuration choices:

  • Profile name and description
  • Number of configured settings
  • Scope tag assignments
  • Target group assignments

Click Create to deploy the baseline. Intune immediately begins applying the settings to assigned devices during their next policy refresh cycle (typically within 8 hours for new policies).

To monitor deployment progress:

  1. Return to Endpoint security > Security baselines
  2. Select your baseline type
  3. Click on Profiles to see your deployed profile
  4. Click on your profile name to view the overview dashboard

The monitoring dashboard shows:

  • Device compliance status: Compliant, non-compliant, and error counts
  • Setting details: Which specific settings are causing compliance issues
  • Device list: Individual device status and last check-in times

Verification: Within 24 hours, you should see devices appearing in the compliance reports. Compliant devices show green status, while non-compliant devices display specific setting failures.

Pro tip: Set up email alerts for compliance failures by navigating to Device compliance > Notifications. This ensures you're immediately aware of security baseline violations.
08

Handle Baseline Updates and Version Migration

Manage ongoing baseline maintenance as Microsoft releases new versions and security updates. The cloud-managed system automatically provides new baseline versions, but you control when to migrate your deployments.

When Microsoft releases a new baseline version (using the current CSP-based format introduced in May 2023), you'll see a notification in the Intune admin center. To migrate to a newer version:

  1. Navigate to Endpoint security > Security baselines
  2. Select your baseline type
  3. Click on Profiles
  4. Select the checkbox next to the profile you want to migrate
  5. Click Change Version from the toolbar

The migration wizard will:

  • Show differences between your current version and the new version
  • Highlight new settings added to the baseline
  • Identify any settings that have changed default values
  • Allow you to review and approve the migration

During migration, you can:

  • Accept all new default settings
  • Customize new settings before applying
  • Review the impact on currently assigned devices

Verification: After migration, check the profile overview to confirm it shows the new version number. Monitor device compliance for any new issues introduced by updated settings.

Warning: Baseline version migration is a one-time process. You cannot roll back to previous versions, so test migrations with pilot groups before applying to production devices.

Frequently Asked Questions

How often does Microsoft update Intune security baselines?+
Microsoft updates Intune security baselines automatically through their cloud-managed system without requiring manual intervention from administrators. The baselines use the new CSP-based format introduced in May 2023, which allows for more frequent and granular updates. While Microsoft doesn't publish a fixed schedule, updates typically occur when new security threats emerge or when Windows receives significant security enhancements. You'll receive notifications in the Intune admin center when new baseline versions become available for migration.
Can I deploy multiple security baselines to the same devices?+
Yes, you can deploy multiple security baselines to the same devices, but you must carefully manage potential conflicts between different baseline settings. For example, the MDM Security Baseline for Windows and Microsoft Defender baseline may include identical settings with different default values. When conflicts occur, the last-applied policy typically takes precedence. To avoid issues, review all baseline settings before deployment and use Intune's conflict detection features to identify overlapping configurations. Consider customizing conflicting settings to ensure consistent behavior across all deployed baselines.
What happens to devices that don't comply with security baseline settings?+
Devices that don't comply with security baseline settings appear in Intune's compliance reports with detailed information about which specific settings are causing non-compliance. Intune automatically attempts to remediate non-compliant settings during the next policy refresh cycle, typically within 8 hours. If remediation fails due to local policy conflicts or user permissions, the device remains marked as non-compliant. You can configure conditional access policies to restrict non-compliant devices from accessing corporate resources until they meet baseline requirements, providing enforcement beyond just reporting.
How do I migrate from Group Policy security baselines to Intune baselines?+
Migrating from Group Policy to Intune security baselines requires careful planning to avoid disrupting existing device configurations. Start by comparing your current Group Policy settings with the equivalent Intune baseline configurations using Microsoft's Group Policy analytics tool. Deploy Intune baselines to a pilot group of devices first, monitoring for conflicts or unexpected behavior. Gradually expand deployment while maintaining Group Policy for non-migrated devices. The same Windows security team creates both Group Policy and Intune baselines, so the security intent remains consistent, but implementation details may differ between the two systems.
Can I export and import security baseline configurations between tenants?+
Microsoft Intune doesn't provide a direct export/import feature for security baseline profiles between different tenants. However, you can document your customizations and manually recreate them in new tenants. The baseline settings themselves are standardized across all Intune tenants, so only your custom modifications need to be replicated. For organizations managing multiple tenants, consider using Microsoft Graph API to script baseline deployments with consistent customizations. Third-party tools and PowerShell scripts can also help automate the recreation of baseline configurations across multiple Intune environments.

Discussion

Share your thoughts and insights

Sign in to join the discussion