Microsoft IntuneIntune Best PracticesWindows AutopilotConditional AccessMicrosoft DefenderApp Protection PoliciesWindows Autopatch

Microsoft Intune Best Practices 2026: Every Policy and the Settings to Enable

Regroove IT Consulting56 min read12,073 words

Microsoft Intune has hundreds of settings, and Microsoft changes some of them almost every month. This is the reference we use with our own technicians and clients: every policy area that matters for a small or mid sized business, the value we recommend as the default, and why, checked against Microsoft's documentation and security baselines as of October 2026.

It is in two parts. Part 1 is the checklist: the settings to apply, written as tasks you can work through in order. Part 2 is the breakdown: every setting in each policy, what it does, the recommended value and the reasoning behind it.

Before you start
  • The recommendations assume Microsoft 365 Business Premium. Settings that need another licence say so.
  • Test every change on a pilot group before applying it to everyone.
  • Use Microsoft's security baselines or individual policies for a given setting, never both.
  • Wide tables scroll sideways on a phone.

Part 1: The checklist

Everything to configure, in the order we apply it. Each item links to its detailed breakdown in Part 2.

1. Identity and access (Entra ID)

  • Turn off security defaults and build Conditional Access instead: MFA for all users with an authentication strength, phishing resistant MFA for admin roles, block legacy authentication, block device code flow and require a compliant device for Microsoft 365.
  • Block sign ins from countries you never do business in, including unknown locations. With Entra ID P2, add sign in risk and user risk policies.
  • Create two cloud only emergency access accounts that sign in with FIDO2 security keys, exclude them from blocking policies, and alert on every sign in.
  • Turn on passkeys and move every user off SMS and voice codes before February 1, 2027.
  • Turn on self service password reset for all users with two methods, managed in the Authentication methods policy.

2. Enrollment and tenant setup

  • Set platform restrictions to block personally owned Windows and Android device administrator, and set a device limit of 5.
  • Set Windows automatic enrollment MDM user scope to All.
  • Create a user driven, Entra joined Autopilot profile with standard users, a naming template such as a prefix plus %SERIAL%, assigned to a dedicated device group. Consider Autopilot device preparation for new Windows 11 laptops.
  • Configure the Enrollment Status Page: selected critical apps only, Windows quality updates during setup, log collection on.
  • Configure Windows Hello for Business: TPM required, minimum PIN 6, no expiry or history, biometrics with enhanced anti spoofing, PIN recovery on.
  • Connect Apple Business (push certificate from a shared mailbox, automated enrollment token, await final configuration, locked enrollment) and Managed Google Play bound to an Entra account, with zero touch for company phones.
  • Add device cleanup rules at 90 days, Multi Admin Approval for wipes, scripts and apps, and least privilege admin roles.

3. Compliance

  • Windows: minimum build 10.0.26200, BitLocker, Secure Boot, code integrity, TPM, firewall, antivirus, Defender with real time protection and current signatures, and Defender for Endpoint risk score Low.
  • iOS: block jailbroken devices, minimum OS one major version back, 6 digit passcode with simple passcodes blocked, 5 minute auto lock, Defender risk score Low.
  • Android: block rooted devices, Play Integrity basic and device integrity, Android 13 or later, patch level within about six months, password complexity Medium or High on personal phones.
  • macOS: System Integrity Protection, FileVault, firewall, Gatekeeper and a minimum OS. Enforce the passcode with a configuration policy, not compliance.
  • Set devices with no compliance policy to Not compliant, keep the validity period at 30 days, and add email notifications and a retire list action.

4. Updates

  • Create three update rings (pilot, broad, late) with quality deferrals of 0, 3 and 7 days, deadlines of 2, 2 and 3 days, grace periods of 1 and 2 days, auto reboot before deadline, and user pausing disabled.
  • Add a feature update policy (Windows 11 25H2 for broad today), a quality update policy that approves security updates automatically, hotpatch, and a driver policy with manual approval for firmware.
  • Let one tool own Windows Update: Intune with Windows Autopatch on Business Premium, with the RMM patching third party apps.
  • Apple: declarative software update policies with Enforce Latest. Android: an overnight maintenance window on company phones.

5. Endpoint security

  • Connect Defender for Endpoint to Intune, deploy an EDR policy from the connector with sample sharing on, and turn on tamper protection.
  • Deploy the antivirus policy: PUA block, cloud block level High, network protection block, all scanning on including network files and email, daily quick scan, signatures every 4 hours.
  • Deploy the firewall policy: on for all profiles, inbound blocked, inbound notifications hidden, no local rule merge on public networks, logging on.
  • Block the three standard attack surface reduction rules now; run the other rules in audit, then block. Keep the PSExec and WMI rule in audit.
  • Encrypt silently with BitLocker (XTS AES 256, TPM only, key saved to Entra ID before encryption, recovery password rotation).
  • Turn on Windows LAPS with Entra ID backup, 30 day rotation and automatic account management, and replace the local Administrators group with only the managed account and a device admin group.
  • Turn on LSA protection, web content filtering, App Control for Business in audit with the managed installer, and removable storage in audit.

6. Apps and data

  • Deploy Microsoft 365 Apps, new Teams, OneDrive, Company Portal and your RMM and security agents to PCs; Outlook, Teams, OneDrive, Edge, Authenticator and Defender to phones.
  • Apply app protection at Microsoft’s level 2 on iOS and Android, and require it with Conditional Access.
  • Configure Edge: SmartScreen on with no bypass, potentially unwanted app blocking and typo protection.
  • Configure OneDrive: silent sign in, silent known folder move with the prompt and no opt out, tenant allow list, Files On Demand, sync health reporting.
  • Turn on cloud update for Microsoft 365 Apps with the Monthly Enterprise channel.
  • Disable Recall, block users adding Microsoft accounts, set a 15 minute inactivity lock and hide lock screen notifications.

7. Teams, email and audit

  • Restrict Teams external access to an allow list of domains, stop unmanaged Teams accounts starting chats, and require verification for anonymous meeting joiners.
  • Apply the Standard preset security policy to everyone and Strict to executives, finance and admins, with Safe Attachments for SharePoint, OneDrive and Teams.
  • Publish SPF and DKIM on every sending domain and take DMARC from none to reject.
  • Confirm the unified audit log is on; it is not on by default for Business plan tenants.

8. Monitoring

  • Turn on Windows health monitoring for Endpoint analytics, and collect only the event logs you will actually use.

Part 2: The breakdown

Every setting in every policy, with the recommended value and why. First, how the pieces fit together, and what your licence covers.

Diagram of how Intune policies fit together: Windows, macOS, iOS and Android devices pass through enrollment and compliance, then Conditional Access decides whether to allow access to company data, while updates, endpoint security and app protection apply to every managed device
Devices enrol, compliance checks their health, and Conditional Access uses that result to decide access to company data.
Comparison of what Microsoft 365 Business Premium includes, such as Intune Plan 1, Entra ID P1, Defender for Business and Windows Autopatch, against features that need an add on, such as Entra ID P2, Endpoint Privilege Management, Remote Help and Cloud PKI
What Business Premium includes, and what needs an add on, as of October 2026.
  1. Identity and access
  2. Windows Hello for Business
  3. Enrollment and tenant setup
  4. Compliance
  5. Updates
  6. Endpoint security
  7. Apps and app protection
  8. macOS, iOS and Android configuration
  9. Windows experience and hardening
  10. OneDrive and Microsoft 365 Apps
  11. Pushing SharePoint libraries as OneDrive shortcuts
  12. Teams, email and audit
  13. Monitoring, recovery and remote support
  14. Security baselines

Identity and access

Intune protects devices, but almost every attack starts with an identity. These settings live in Microsoft Entra ID, and they come first because every other policy depends on them. The context for 2026: Microsoft enforces MFA on its admin portals with no exceptions, passkeys became the default sign in method in September 2026, and Microsoft's own SMS and voice codes retire in 2027.

SettingRecommendedWhy
Entra ID licenceEntra ID P1 at minimum (included in Microsoft 365 Business Premium); P2 for risk based policiesConditional Access needs P1. Sign in risk and user risk policies need P2.
Directory syncNone for cloud only tenants. If you need hybrid, start with Entra Cloud SyncMicrosoft calls Cloud Sync its strategic direction. It now covers password writeback and most hybrid needs. Keep Entra Connect Sync only for advanced sync rules or very large directories.
Self service password resetOn for all users, two methods requiredCuts password reset calls. Microsoft recommends two or more registered methods.
Password reset methodsMicrosoft Authenticator plus email or an OATH code. Not SMS, voice or security questionsMicrosoft provided SMS and voice retire on February 1, 2027, including for password reset, and security questions retire in March 2027.
Require registration at sign inYes, reconfirm every 180 daysKeeps recovery methods current without nagging users.
Method managementAuthentication methods policy onlySince September 30, 2025 the legacy MFA and password reset method settings no longer apply. Everything is managed in one place.
Break glass (emergency access) accountsTwo cloud only accounts on the onmicrosoft.com domain, Global Administrator, signing in with a passkey (FIDO2 security key)Mandatory MFA on the admin portals has no exceptions, so a password alone no longer works. Two accounts with keys kept in separate places survive one being lost.
Break glass exclusions and monitoringExclude an emergency access group from blocking Conditional Access policies, alert on every sign in, test every 90 daysAn outage should never lock out the account built for outages, and any use of it should be noticed immediately.
Passwordless sign inPasskeys for everyone: synced passkeys for most staff, device bound passkeys or security keys for admins, Windows Hello for Business on PCsPasskeys became the default sign in method in Entra ID on September 1, 2026. They cannot be phished the way passwords and codes can.
SMS and voice MFAMove users off nowMicrosoft retires its own SMS and voice codes on February 1, 2027 (July 1, 2027 for Global Administrators). Users left with only SMS will be forced to register a passkey.

Conditional Access

Conditional Access decides who can sign in, from where and on what device. Microsoft now creates some of these policies itself as managed policies; review them rather than duplicating them.

Diagram of Conditional Access: signals about the user, network, device, risk and app feed Conditional Access policies, which decide to allow, require MFA, require phishing resistant MFA, require a compliant device, or block
Conditional Access weighs who, where, what device and how risky a sign in is, then decides.
SettingRecommendedWhy
Require MFA for all usersOn, using an authentication strengthThe baseline every tenant needs. Microsoft now creates a managed version of this policy and switches it on automatically after a report only period.
Require MFA for adminsOn, with the phishing resistant MFA strength (passkeys, Windows Hello, certificates)Microsoft already enforces MFA on its admin portals. For admins, phishing resistant methods are now the expectation, not an extra.
Block legacy authenticationOnOld protocols cannot do MFA, so they are a favourite for password spraying. Microsoft includes this in its managed policies and baseline security mode.
Location based accessBlock countries you never do business in, including unknown locations, based on IP addressUseful as an extra layer, not a primary control, since VPNs hide real locations. The condition is now called Network in the portal.
Block device code flowOn, with exceptions only for devices that need it, such as Teams RoomsAttackers abuse it often and legitimate use is rare. Security defaults block it in new tenants since July 1, 2026.
Require a compliant deviceOn for Microsoft 365 access from managed platformsTies access to the health checks Intune enforces, which is far stronger than trusting an IP address.
Sign in risk and user riskOn if you have P2Blocks or challenges sign ins that Microsoft scores as risky, such as leaked credentials.
Token protectionPilot in report only modeBinds sign in tokens to the device so a stolen token is useless elsewhere. Generally available for Windows desktop apps; test before enforcing.
Security defaultsOff once Conditional Access is in placeThe two cannot run together. Conditional Access replaces everything security defaults does, with more control.

Windows Hello for Business

Windows Hello replaces the Windows password with a PIN, face or fingerprint that only works on that one device. Current NIST guidance argues against forced PIN changes and complexity rules, while the hardware requirement should be strict.

SettingRecommendedWhy
Windows Hello for BusinessEnabledReplaces the Windows password with a PIN or biometric tied to the device, which cannot be reused from anywhere else.
Use a Trusted Platform Module (TPM)Required, excluding TPM 1.2Preferred allows keys to fall back to software, which is weaker than the Intune default. Windows 11 hardware has TPM 2.0 anyway.
Minimum PIN length6Matches the Windows default and NIST guidance, which recommends at least six characters for an activation secret like this.
Maximum PIN length127 (leave at the default)The real maximum is 127. Capping it adds no security and only frustrates people who like long PINs.
Lowercase, uppercase and special charactersAllowed, not requiredNIST advises against forced composition rules. The PIN only works on that one device, so length matters more than complexity.
PIN expirationNeverNIST advises against forced changes, and expiry is not supported on Windows 11 24H2 and later devices with virtualization based security.
Remember PIN historyNot configuredPointless without expiration, and also unsupported on recent Windows 11 devices with virtualization based security.
Allow biometric authenticationYesFace and fingerprint sign in are both convenient and strong, and the biometric data never leaves the device.
Use enhanced anti spoofingYesRejects photos and masks on face sign in. It does disable face sign in on cameras that cannot support it.
Enhanced Sign in SecurityLeave the default (on where hardware supports it)Isolates biometric data using virtualization based security on capable hardware.
Allow phone sign inNoThis uses the old companion device framework, which Microsoft stopped developing years ago. Use Authenticator passkeys or security keys instead.
PIN recoveryEnabledLets users reset a forgotten PIN themselves without losing their keys or calling the help desk.
Use security keys for sign inEnabled if you issue FIDO2 keysLets staff with a security key sign in to shared or new PCs.
Cloud Kerberos trustOnly for hybrid users who need on premises file sharesNot needed in cloud only tenants. It replaced the older key trust and certificate trust models for hybrid.

Enrollment and tenant setup

Enrollment restrictions

SettingRecommendedWhy
Platform restriction: personally owned WindowsBlockOnly Autopilot and other corporate methods can enrol Windows, so personal PCs cannot pick up company policies.
Platform restriction: Android device administratorBlockDevice administrator is deprecated and unavailable on Google certified devices.
Platform restriction: personal iOS and macOSBlock MDM if personal phones use app protection only; otherwise allowApple devices only count as corporate through Automated Device Enrollment or a registered serial number.
Device limit restriction5 devices per user, plus the matching Entra ID device limitEnough for a laptop, phone and tablet, without letting one account enrol a fleet.
Windows automatic enrollmentMDM user scope: All; leave the default URLsEntra joined Windows devices enrol in Intune automatically.
Apple automated enrollment tokenRenew every year; only download a new token at renewalDownloading a new token invalidates the current one.
Enrollment notificationsEmail users when a device enrolsSomeone enrolling a device with stolen credentials gets noticed.

Windows Autopilot

Autopilot lets a new laptop go straight from the box to the user, configuring itself on first sign in. There are two flavours. Autopilot device preparation is the newer one: Windows 11 and Entra join only, no hardware registration, up to 25 apps during setup and better reporting. Classic Autopilot is still needed for pre provisioning, self deploying kiosks and Autopilot Reset. For new Entra joined Windows 11 laptops we lean towards device preparation; the table covers the classic profile most tenants use today.

Five step Autopilot flow: unbox, sign in with a work account, device setup, account setup, and ready, with the Enrollment Status Page covering device and account setup
From the box to a compliant, encrypted laptop without IT touching it.
SettingRecommendedWhy
Profile nameDescriptive, for example AP UserDriven EntraAny profile assigned to all devices already acts as the default, so naming it Default causes confusion later.
Convert all targeted devices to AutopilotNo (Yes only briefly, on a scoped group of existing company PCs)It registers every corporate device in the group, and switching it off later does not deregister them.
Deployment modeUser drivenThe right choice for laptops handed to a named person, which is most small and mid sized businesses.
Join to Microsoft Entra ID asMicrosoft Entra joinedCloud native and simplest to support. Hybrid join is not recommended for new deployments.
User account typeStandardUsers should not be local administrators. It is one of the most effective ways to limit what malware can do.
Allow pre provisioned deploymentNo, unless IT or a reseller actually pre provisions devicesLeaving it on when unused only opens an extra path during setup.
Device name templateA short prefix plus %SERIAL% or %RAND:6% or longer, 15 characters at most%RAND:2% gives only 100 possible names, so duplicates are likely after about a dozen devices. %SERIAL% also makes support easier.
AssignmentsA dedicated device group, not All DevicesExclusions do not work properly with All Devices, and a dedicated group lets you control exactly which hardware gets the profile.
Microsoft Software License TermsHideOne fewer screen for the user during setup.
Privacy settingsHide, then set diagnostic data and location by policyHiding the screen sets defaults during setup, so set the values you actually want with a configuration policy.
Hide change account optionsHideStops users signing in with the wrong account. Needs company branding configured in Entra ID.
Language and keyboardOperating system default or user selectA fixed language only works over a wired network connection.

Enrollment Status Page

The progress screen during setup, which decides what must be installed before the user can start work.

SettingRecommendedWhy
Show app and profile installation progressYes, 60 to 90 minute timeoutUsers see what is happening, and the timeout allows for apps plus updates.
Turn on log collection and diagnostics pageYesIf setup fails, the user can collect logs and send them to the help desk.
Show error message when time limit is reachedYes, with your help desk contact detailsGives the user a clear next step instead of a dead end.
Only show page to devices provisioned by out of box experienceYesStops the status page repeating every time a new user signs in.
Install Windows quality updatesYesDevices finish setup fully patched. It adds 20 to 40 minutes and needs the next setting on.
Block device use until required apps are installedYes, for a selected list of critical apps onlyEnsures security tools are in place before first use, without waiting for every app.
Allow users to reset the device if an error occursYesLets users recover from a failed setup without a visit.
Allow users to use the device if an error occursNoA half configured device should not be used for work.

Tenant administration

SettingRecommendedWhy
Device cleanup rules90 days, one rule per platformRemoves devices that have stopped checking in, so reports and licences stay accurate. Nothing is wiped.
Role based access controlLeast privilege roles such as Help Desk Operator and Endpoint Security Manager; Intune Administrator only through Privileged Identity ManagementMost day to day work does not need full admin rights, and standing admin access is what attackers look for.
Scope tagsUse them when different teams manage different sites or clientsAn admin only sees the devices and policies in their scope.
Multi Admin ApprovalOn for device wipe, retire and delete, scripts and apps; add roles lastA second admin must approve destructive or far reaching changes, which stops a single compromised account wiping the fleet.
Terms of useEntra ID Terms of use through Conditional Access, rather than Intune terms and conditionsSupports per device consent, expiry and PDFs. If both exist, users have to accept both.
Device categoriesOnly when they drive dynamic groups, for example Kiosk or SharedLow value on their own in small environments.

Compliance

Compliance policies define what a healthy device looks like. On their own they only report; their power comes from Conditional Access, which keeps noncompliant devices away from company data. With Windows 10 past end of support, the minimum Windows version is the most important single value.

Windows

SettingRecommendedWhy
Minimum OS version10.0.26200 (Windows 11 25H2), or use valid operating system build rangesWindows 10 support ended on October 14, 2025, and Windows 11 24H2 Home and Pro stopped receiving updates in October 2026.
Windows 10 devices on Extended Security UpdatesA separate, time limited policy for a scoped group, minimum 10.0.19045 at current patch levelKeeps the few remaining Windows 10 devices visible and patched while they are replaced.
FirewallRequireA device with its firewall off should not reach company data.
Antivirus and antispywareRequireChecks that security software is registered and running.
Microsoft Defender AntimalwareRequire (drop it only if another antivirus is primary)Confirms Defender is actually active, not in passive mode.
Defender security intelligence up to dateRequireCatches devices with stale signatures.
Real time protectionRequireAntivirus that only scans on a schedule misses most attacks.
Require BitLockerRequire, keeping encryption of data storage as a backstopChecks the measured BitLocker state at boot. A device needs a restart before it reports compliant.
Require Secure BootRequireProtects the boot process from tampering.
Require code integrityRequireDetects unsigned or altered drivers loading into Windows.
Trusted Platform ModuleRequireNeeded for BitLocker and Windows Hello key protection.
Defender for Endpoint machine risk scoreLowMicrosoft’s stated recommendation. A device with an active threat is cut off from company data until it is cleaned.
Mark devices with no compliance policy asNot compliantThe default is compliant, which means a device with no policy assigned passes Conditional Access. Microsoft says to change it.
Compliance status validity period30 days (14 for tighter environments)Devices that stop checking in eventually become noncompliant instead of passing forever.

iOS and iPadOS

SettingRecommendedWhy
Jailbroken devicesBlockA jailbroken device has had its built in protections removed.
Device threat levelNot configured; use Defender for Endpoint machine risk score Low insteadThreat level needs a mobile threat defence connector. With Defender for Endpoint, the risk score is the supported setting, and Secured flags a device for any threat at all.
Minimum OS versionThe previous major version still receiving patches (iOS 26.7 today), plus a minimum buildKeeps devices on releases Apple still patches. Raise it when Apple stops patching the older version.
Require a password to unlockRequireA passcode is what turns on iPhone data encryption.
Simple passwordsBlockStops 123456 and 111111.
Minimum password length and type6, numericA sensible balance for a phone that also uses Face ID.
Maximum minutes of inactivity until screen locks5Limits exposure if a phone is left unlocked.
Maximum minutes after screen lock before password is requiredImmediatelyNo grace window for someone who picks up the phone.

Android

SettingRecommendedWhy
Enrollment typeWork profile for personal phones; fully managed or corporate work profile for company phonesDevice administrator management ended on Google devices in December 2024.
Rooted devicesBlockA rooted device has had its built in protections removed.
Device threat levelNot configured; use Defender for Endpoint machine risk score Low insteadSame reason as iOS.
Play Integrity verdictCheck basic integrity and device integrity; add strong integrity only on known hardwareGoogle shut SafetyNet down in January 2025. Device integrity requires an unmodified, certified device.
Minimum security patch levelAbout six months backCatches phones the manufacturer has stopped updating.
Minimum OS versionAndroid 13Intune still supports older versions, but the improved integrity checks start at Android 13.
Require a password to unlockRequireBasic protection for a lost or stolen phone.
Password requirementPersonal phones: password complexity Medium or High. Company phones: numeric complex, length 6Google deprecated password type and length for personal work profiles on Android 12 and later; complexity replaces them.
Maximum minutes of inactivity5Limits exposure if a phone is left unlocked.

Noncompliance notifications and actions

SettingRecommendedWhy
Company logo, company name and contact informationShowUsers trust and act on a message that looks like it comes from their own IT team.
Company Portal website linkShowGives users a way to fix the problem themselves. It is off by default.
Locale and default messageEnglish default; add a French version if you have francophone staffThe default message is used whenever a user’s language has no translation.
Subject and messagePlain language, using the device name and OS tokensTemplates now support tokens such as the user name and device name, which makes the message specific.
Mark device noncompliantImmediately for security failures; 3 to 7 day grace for OS version rules, in a separate policyThe grace period applies to a whole policy, so keep urgent and patience friendly checks apart.
Send email to end userImmediately, then again after 3 daysOne reminder is often missed.
Add device to retire list30 to 60 daysFlags long noncompliant devices for review. Nothing is wiped automatically.

Updates

Microsoft has moved update timing out of update rings and into separate cloud policies, made Windows Autopatch part of Business Premium, and added hotpatch, which installs most security updates without a restart. Its own schedule patches devices within a few days of Patch Tuesday. Whichever tool you use, let exactly one of them control Windows Update.

Timeline of three Windows update rings after Patch Tuesday: pilot installs immediately and finishes by day 3, broad waits 3 days and finishes by day 7, late waits 7 days and finishes by day 12
With the recommended deferrals, deadlines and grace periods, every device is patched within 12 days of Patch Tuesday.

Update strategy and policies

SettingRecommendedWhy
Ring structurePilot (IT plus 5 to 10% of willing users), Broad (everyone else), Late (executives, critical and shared PCs)Problems show up on a small group first, while the whole fleet is still patched within days.
Who manages Windows UpdateOne tool only. For Business Premium clients, Intune and Windows Autopatch, with the RMM handling third party appsTwo tools controlling Windows Update fight each other. Autopatch is included with Business Premium and covers Windows, drivers, firmware and hotpatch.
Patch timingFollow Patch Tuesday (the second Tuesday) with the ring schedule aboveThe monthly cumulative update is the security update, so waiting for the last Wednesday adds two to three weeks of exposure.
Feature update policyBroad on Windows 11 25H2 today; pilot on 26H2; move broad to 26H2 in January 202726H2 shipped on September 29, 2026 and is rolling out gradually. Upgrading in a hotpatch baseline month minimises restarts.
Quality update policySecurity updates approved automatically by ring; optional previews and out of band fixes approved manuallyMicrosoft’s new approval policy. Security fixes flow without waiting for anyone, while previews wait for testing.
HotpatchAllowMost monthly security updates install without a restart on eligible Windows 11 24H2 and later devices. Four baseline months a year still need one.
Driver and firmware update policyPilot: automatic approval. Broad: automatic after 7 days. BIOS and firmware: manual approvalDrivers and firmware are approved and paused centrally, with risky firmware changes checked first.
Expedited quality updatesOnly for actively exploited flaws, with a 1 day restart deadlinePushes one urgent update past every deferral. Powerful, so keep it for emergencies.
Windows 10Replace, or enrol the remaining devices in Extended Security Updates with their own compliance policySupport ended October 14, 2025, and Extended Security Updates cost more each year.

Windows update ring settings

SettingRecommendedWhy
Automatic update behaviorReset to defaultMicrosoft recommends the default so expedited updates work, and once a deadline passes Windows ignores this setting anyway.
Microsoft product updatesAllowPatches other Microsoft software through the same channel.
Windows driversAllow, and control them with a driver update policyA driver update policy only works when the ring allows drivers. The policy then decides which drivers are approved.
Quality update deferral period0 days for pilot, 3 for broad, 7 for lateMonthly updates are security updates. Fifteen days leaves devices exposed for half a month; Microsoft’s own Autopatch schedule uses 0, 1 and 2 days.
Feature update deferral period0 days, and choose the version with a feature update policyMicrosoft says to leave this at 0 when using a feature update policy, because a deferral here can block it.
Upgrade Windows 10 devices to latest Windows 11 releaseNo when a feature update policy targets Windows 11; Yes only if you have noneA feature update policy keeps devices on a version you have tested. The ring toggle always jumps to the newest release.
Feature update uninstall period30 daysMatches Autopatch and gives users time to report problems with a new Windows version.
Restart checksAllowWindows checks the device is idle before restarting.
Option to pause Windows updatesDisableUsers should not be able to pause security updates for weeks. Admins can still pause a ring centrally for up to 35 days.
Option to check for Windows updatesEnableLets users pull an update sooner, which never hurts.
Change notification update levelUse the default Windows Update notificationsTurning notifications off entirely stops expedited updates working.
Active hours7am to 7pm, or the client’s business hoursRestarts before the deadline happen outside active hours, so cover the real working day.
Use deadline settingsAllowWithout a deadline, nothing guarantees a device ever finishes installing an update.
Deadline for quality updates2 days for pilot and broad, 3 for lateCounts from when the device first sees the update. Together with the deferrals, every device is patched within about two weeks.
Deadline for feature updates5 daysMicrosoft’s Autopatch value.
Grace period1 day for pilot, 2 for the other ringsSomeone back from holiday is not restarted the moment they open their laptop.
Auto reboot before deadlineYesMicrosoft’s recommendation. With No, the restart waits for the deadline and can land in the middle of the working day.
AssignmentOne device group per ring, each device in exactly one ringAssigning one ring to everyone makes a staged rollout impossible.

Mobile devices

SettingRecommendedWhy
iOS, iPadOS and macOS update methodDeclarative device management in the settings catalog: Software Update Enforce LatestApple removed the old update commands in its 2026 operating systems, and Intune is retiring the old update screens.
Enforce Latest: delay3 days for pilot, 7 for everyone elseSets when the install is forced, not when users are first offered the update.
Enforce Latest: install time2am for iPhone and iPad, 8pm for MacAt the deadline the device counts down for a minute and installs, so pick a time nobody is using it.
Major version upgradesHide for 30 to 60 days; allow minor updatesGives time to test business apps before a jump such as iOS 27, while security updates keep flowing.
Android, company ownedSystem update maintenance window, for example 1am to 5amUpdates install overnight. Freeze periods also block security patches, so use them sparingly.
Android, personal work profileMinimum security patch level in complianceIntune cannot push OS updates to personal phones, but it can keep outdated ones away from work data.

Endpoint security

The policies under Endpoint security in Intune, compared against Microsoft's two current baselines: the Windows security baseline for 26H2 and the Defender for Endpoint baseline. Where they disagree, we say which we follow and why.

Defender for Endpoint

SettingRecommendedWhy
Defender for Endpoint onboardingTurn on the Defender for Endpoint connector, then an EDR policy set to Auto from connectorOnboards every device to Defender automatically. Intune now also offers a preconfigured EDR policy and an onboarding status report.
Tamper protectionOn, tenant wideStops malware or a local admin switching Defender off. Microsoft is previewing a successor called configuration protection; pick one, not both.
Defender platform and engine updatesDefault channel for most devices; optionally a few pilot devices on PreviewMicrosoft recommends letting most devices take updates as they arrive.

EDR, web filtering and mobile threat defence

SettingRecommendedWhy
EDR policyClient configuration from the connector, sample sharing AllEvery device onboards to Defender with full detection.
Web content filteringBlock adult content, legal liability categories and parked domains; audit the rest for 30 daysIncluded in Business Premium. Needs SmartScreen in Edge and network protection in block mode for other browsers.
Defender on iOS and AndroidDeploy through Intune and turn on the mobile threat defence connectorIncluded in Defender for Business. Device risk then feeds compliance and app protection.

Microsoft Defender Antivirus

SettingRecommendedWhy
PUA protectionBlockBlocks adware, bundleware and other potentially unwanted apps.
Cloud block levelHighBoth Microsoft baselines use High. High plus is stronger but can cost performance.
Network protectionBlock, and convert warn to blockBlocks malicious domains in any app, not just the browser.
Allow real time monitoringAllowedCore on access protection.
Allow cloud protectionAllowedNeeded for block at first sight, attack surface reduction and tamper protection.
Submit samples consentSend all samples (or safe samples if your privacy policy requires)Both baselines send all samples. Never send disables block at first sight.
Cloud extended timeout50Holds a suspicious file up to a minute while the cloud decides.
Allow behavior monitoringAllowedCatches malware by what it does, not just what it looks like.
Allow scanning of all downloaded files and attachmentsAllowedScans files as they arrive.
Allow script scanningAllowedInspects PowerShell and other scripts before they run.
Real time scan directionMonitor all filesScans files coming in and going out.
Allow archive scanningAllowedMalware often hides inside zip files.
Allow scanning network filesAllowedThe current default and the Defender baseline both allow it, so files opened from a share are checked too.
Allow email scanningAllowedThe Defender baseline allows it, and the cost is low.
Allow full scan on mapped network drivesNot allowedScheduled full scans of shares from every PC overload file servers.
Allow full scan removable drive scanningAllowedBoth baselines scan USB drives.
Scan type and scheduleDaily quick scan at 720 (noon)A daily quick scan makes a weekly one redundant, and laptops are awake at noon but asleep at 2am.
Check for signatures before running scanEnabledScans with the latest definitions.
Signature update interval4 hoursThe Defender baseline value.
Disable catchup quick scan and full scanDisabled (catch up scans stay on)A scan missed while the laptop was off runs at the next opportunity.
Enable low CPU priorityEnabled on laptopsKeeps scans from slowing down users. Our judgement; neither baseline sets it.
Average CPU load factor50The default.
Allow user UI accessAllowedUsers can see protection status; tamper protection still stops them switching it off.
Days to retain cleaned malware30 to 90No Microsoft guidance; a limit keeps quarantine tidy.
ExclusionsNone, with local admin merge disabled and exclusions hidden from usersExclusions are only tamper protected when local merge is off. Add them centrally and sparingly.

Windows Firewall

SettingRecommendedWhy
Enable firewall (domain, private, public)On for all threeEvery profile protected.
Default inbound actionBlock on all three profilesThe Windows baseline blocks unsolicited inbound traffic everywhere.
Default outbound actionAllowBlocking outbound by default breaks most apps.
Allow local policy mergeTrue for domain and private; False for publicOn public networks, only rules you deploy should apply. The Windows baseline sets public to False.
Allow local IPsec policy mergeTrue for domain and private; False for publicSame reasoning as local policy merge.
Auth apps and global ports allow user preference mergeTrueThe default; only matters when Group Policy rules are also present.
Disable inbound notificationsTrueBoth baselines hide the "allow this app" prompt, so users cannot approve their own exceptions.
Disable stealth modeFalseStealth mode stays on, so the PC does not answer probes.
Disable stealth mode IPsec secured packet exemptionTrueThe default.
Disable unicast responses to multicast broadcastFalseThe default and the baseline value.
ShieldedFalseShielded blocks every inbound connection. Use it only to isolate a device during an incident.
LoggingLog dropped and allowed connections, 16384 KBAdded in recent Windows baselines; useful evidence when investigating.

Attack surface reduction rules

There are 19 rules. Microsoft's guidance is to block its three standard protection rules straight away and to run every other rule in audit mode first, review what it would have blocked, add exclusions, and then switch to block.

Attack surface reduction rollout: the three standard protection rules block from day one, every other rule goes through audit, review, exclude and block
Audit first, so a rule never blocks a legitimate business tool by surprise.
SettingRecommendedWhy
Block abuse of exploited vulnerable signed driversBlockOne of Microsoft’s three standard protection rules, safe to block without testing.
Block credential stealing from the Windows local security authority subsystem (lsass.exe)BlockStandard protection rule. Stops tools such as Mimikatz reading passwords from memory.
Block persistence through WMI event subscriptionBlock (Audit first if you use Configuration Manager)Standard protection rule. Stops a common way malware survives restarts.
Block executable content from email client and webmailBlockStops executables launched straight from an email.
Use advanced protection against ransomwareBlockUses cloud intelligence to stop files that look like ransomware. Needs cloud protection on.
Block executable files from running unless they meet a prevalence, age or trusted list criterionAudit first, then BlockThe noisiest rule. It blocks rare and new software, which includes legitimate niche business tools.
Block process creations originating from PSExec and WMI commandsAuditBoth Microsoft baselines keep this in Audit. Management tools, including RMM agents, often rely on WMI and PsExec.
Block all Office applications from creating child processesAudit, then BlockStops a malicious document launching other programs.
Block Office applications from creating executable contentAudit, then BlockStops documents dropping executable files.
Block Office applications from injecting code into other processesAudit, then BlockStops macro malware hiding inside other programs. No Warn mode.
Block Office communication application from creating child processesAudit, then BlockThe same protection for Outlook.
Block Win32 API calls from Office macrosAudit, then BlockMost malicious macros need these calls; legitimate ones rarely do.
Block Adobe Reader from creating child processesAudit, then BlockStops malicious PDFs launching programs.
Block execution of potentially obfuscated scriptsAudit, then BlockHidden script code is a strong sign of malware.
Block JavaScript or VBScript from launching downloaded executable contentAudit, then BlockA classic way phishing attachments download their payload.
Block untrusted and unsigned processes that run from USBAudit, then BlockStops malware carried in on a USB stick.
Block rebooting machine in Safe ModeAudit, then BlockNew rule. Ransomware reboots into Safe Mode to get around security tools.
Block use of copied or impersonated system toolsAudit, then BlockNew rule. Catches renamed copies of Windows tools used by attackers; heuristic, so audit first.
Block webshell creation for serversNot applicable to workstationsMeant for Exchange servers.

BitLocker disk encryption

SettingRecommendedWhy
Require device encryptionEnabledTurns BitLocker on.
Allow warning for other disk encryptionDisabledNeeded for silent encryption, so users never see a prompt.
Allow standard user encryptionEnabledLets silent encryption run when a standard user, not an admin, is signed in.
Encryption method for OS and fixed drivesXTS AES 256Microsoft recommends XTS AES on all internal drives, 256 bit on modern hardware.
Encryption method for removable drivesAES CBC 128Keeps USB drives readable on older systems.
Startup authenticationTPM only; no startup PIN or key (TPM plus PIN only for high risk devices)A startup PIN blocks silent encryption and adds a daily step for users.
Save recovery key toEntra ID, and do not enable BitLocker until the key is storedA device should never encrypt with a key nobody can retrieve.
Recovery password rotationEnabled for Entra joined and hybrid joined devicesA recovery key read out over the phone is replaced after use.
Deny write access to unencrypted removable drivesOptionalThe Windows security baseline enables it, but it disrupts anyone who uses USB drives.
Personal Data EncryptionUsually skip for small businessesEncrypts individual files per user, but needs Windows Enterprise or Education. Business Premium devices run Pro and do not qualify.

Windows LAPS (local administrator passwords)

SettingRecommendedWhy
Backup directoryEntra ID, with LAPS enabled in Entra device settingsWithout both, the local admin password is never backed up.
Password age30 daysThe default. Rotating regularly limits how long a leaked password works.
Password complexityLarge letters, small letters, numbers and specials (4); passphrases on Windows 11 24H2 if passwords are read aloudMicrosoft says always use full complexity. Passphrases are easier to read over the phone.
Password length20 or moreNobody types it by memory, so length costs nothing.
Post authentication actionsReset the password and sign out, about 8 hours after useA password handed to a technician stops working once the job is done.
Automatic account management (Windows 11 24H2 and later)Enabled: a new, custom named account that is enabledWindows creates and protects its own admin account. If left unset, the account is created disabled.

Account protection

SettingRecommendedWhy
LSA protectionEnabled without UEFI lockProtects the process that holds credentials in memory. Check for incompatible drivers first; the lock makes it hard to turn off remotely.
Credential GuardEnabled without UEFI lock, on Windows Enterprise devicesIsolates credentials using virtualization. Not supported on Pro, so Business Premium devices need a Windows Enterprise add on.
Local user group membership: AdministratorsReplace with only the managed LAPS account and a dedicated Entra group for device adminsRemoves everyone else from the local Administrators group, including users who were made admins during setup.

Endpoint Privilege Management

SettingRecommendedWhy
Endpoint Privilege ManagementEnabled where licensedLets standard users run specific tasks as admin without being local admins. An add on; included in Microsoft 365 E5 since July 2026, not in Business Premium.
Default elevation responseRequire support approvalMicrosoft recommends support approval or deny. User confirmation alone lets any file elevate.
Reporting scopeDiagnostic data and all endpoint elevationsShows what people elevate today, which you turn into rules.
Elevation rulesPublisher certificate plus file hash, user confirmed with justification, child processes deniedNarrow rules elevate exactly the app you approved and nothing it launches.

App Control for Business

SettingRecommendedWhy
Managed installerEnable the Intune Management Extension as managed installerApps deployed through Intune are trusted automatically. Only new installs are tagged, so turn it on early.
App Control for Business policyTrust Windows components, Store apps and apps from managed installersOnly known software runs, which stops most malware outright.
RolloutAudit on a pilot group, review the events, then enforceMicrosoft recommends audit mode where apps were installed before the managed installer.
Smart App ControlDo not plan around itIt is off on managed business devices. App Control for Business is the business equivalent.

Device control (USB and removable storage)

SettingRecommendedWhy
Removable storageAudit first; block writes to unencrypted drives for most usersA full USB block is too disruptive as a default. Requiring BitLocker on USB drives protects data without stopping work.
Defender device controlDeny write and execute for regulated users, with an allow list of approved devicesFine grained control by device type and serial number for the people who handle the most sensitive data.
Device installation restrictionsOnly to block whole device classesBlocks the driver itself, so it is a blunt tool.

Apps and app protection

Apps to deploy

SettingRecommendedWhy
Workstations: Microsoft 365 Apps, OneDrive, new Teams, Company PortalRequired for all usersThe standard productivity set. Classic Teams stopped working on July 1, 2025, so deploy only the new Teams.
Workstations: Power AppsOnly where Power Apps are in useMost staff use Power Apps through Teams or the browser.
Workstations: RMM agent and HuntressRequired, delivered as Win32 appsMonitoring, third party patching and managed detection from the first sign in.
Mobile: Outlook, Teams, OneDrive, Edge, Microsoft AuthenticatorRequiredEdge is needed to keep work links in a managed browser, and Authenticator is the sign in broker on iOS and the home of passkeys.
Mobile: Company Portal (iOS), Intune app (Android)Required for enrolled devicesAndroid work profiles are moving to the Intune app as the user facing app.
Mobile: Microsoft LauncherOnly on fully managed company Android phonesLauncher only works on fully managed devices. Use Managed Home Screen for kiosk style phones.
Mobile: Power AppsOnly where Power Apps are in useKeep the work profile lean.

App protection policies (iOS and Android)

App protection policies protect company data inside apps such as Outlook and Teams, even on a personal phone that is not enrolled. Microsoft publishes a framework with three levels: basic, enhanced and high. We recommend level 2, enhanced data protection, as the default for anyone who handles company email and files on a phone. Values below are level 2 unless noted.

Comparison of Microsoft app protection levels 1, 2 and 3 for sending and receiving work data, copy and paste, backup, app PIN and printing, with level 2 highlighted as the recommended default
How the three levels compare on the settings that matter most. Level 2 is our default.
SettingRecommendedWhy
Target appsCore Microsoft apps, plus Power Apps and other apps you useThe policy only protects the apps it targets.
Recheck the access requirements after30 minutesMicrosoft’s value. Frequent enough without constant PIN prompts.
Send org data to other appsPolicy managed appsWith All apps, work data can leave freely and the policy barely protects anything.
Receive data from other appsAll appsLetting personal files come in is low risk. Microsoft only restricts this at its highest level.
Save copies of org dataBlock, allowing OneDrive for Business, SharePoint and the photo libraryKeeps files in approved storage while still giving users somewhere to save.
Restrict cut, copy and paste between other appsPolicy managed apps with paste inUsers can paste into work apps but cannot copy work data out to personal ones.
Back up org data (iCloud, Android backup)BlockStops work data landing in personal cloud backups.
Restrict web content transfer with other appsMicrosoft EdgeWork links open in a managed browser instead of a personal one.
Encrypt org dataRequireThe default, but set it explicitly so nobody turns it off.
Org data notificationsBlock org dataStops email and chat content appearing on lock screens and watches.
Sync policy managed app data with native appsAllowRenamed setting, now also covering calendar and widgets. Block only if contacts must not leave Outlook.
Printing org dataAllowBlocked only at Microsoft’s highest level.
Third party keyboards (iOS)AllowBlocked only at Microsoft’s highest level.
Screen capture (Android, and now iOS)Block on Android; consider Block on iOS for sensitive rolesStops screenshots of work data. On Android it also blocks Circle to Search and blurs the app switcher.
Transfer telecommunication data toAny dialer appTapping a phone number in Outlook should simply work.
PIN for accessRequireA separate app PIN protects work data even when the phone is unlocked.
Simple PINBlockMicrosoft allows simple PINs at level 2, but blocking them costs users almost nothing.
Minimum PIN length4 (6 for high security roles)Microsoft’s value for this level; it is a second lock on top of the device lock.
Max PIN attempts5, then reset PINMicrosoft’s value.
PIN reset after number of daysNot requiredMicrosoft only forces app PIN changes at its highest level; for most users it adds friction without much benefit.
Number of previous PIN values to maintain0 (Android only)Only exists on Android. Microsoft leaves it at 0 because the app PIN rarely needs to change.
App PIN when device PIN is setRequire (Not required is acceptable on enrolled devices with a strong device PIN)Personal phones may have weak device PINs.
Override biometrics with PIN after timeoutRequire, after 1440 minutesA PIN check once a day stops biometrics being the only factor forever.
Work or school account credentials for accessNot requiredThe app PIN is enough at this level.
Offline grace periodBlock access after 10080 minutes (7 days); wipe data after 30 daysA phone that has not checked in for a week may be lost. After a month, remove the work data from it.
Jailbroken or rooted devicesBlock accessProtections are gone on those devices.
Disabled accountBlock accessAccess stops as soon as someone’s account is disabled, for example when they leave.
Minimum OS versionBlock below the previous major versionMicrosoft apps support the current and previous version only.
Play Integrity verdict (Android)Basic integrity and device integrity, block access; check strong integritySafetyNet was replaced by Play Integrity. Strong integrity uses hardware backed checks that catch newer rooting tools.
Require threat scan on apps (Android)Block accessRequires Google Play Protect app scanning to be on. This is an Android only setting.
Require device lock (Android)Medium complexity, block accessMakes sure the phone itself has a real screen lock.
Samsung Knox device attestation (Android)Block access, applied only to Samsung devices with a filterHardware attestation on Samsung phones. Non Samsung devices fail it unless filtered out.
Approved keyboards (Android)Not requiredRequired only at Microsoft’s highest level.

Microsoft Edge

SettingRecommendedWhy
Configure Microsoft Defender SmartScreenEnabledBlocks known phishing and malware sites. Part of Microsoft’s Edge security baseline.
SmartScreen: block potentially unwanted appsEnabledStops bundled adware and similar downloads. In the current baseline.
Prevent bypassing SmartScreen prompts for sitesEnabledA warning users can click past is not much protection. In the current baseline.
Prevent bypassing SmartScreen warnings about downloadsEnabledSame reason, for downloaded files.
Website typo protectionEnabledWarns when someone mistypes a well known address and lands on a lookalike site.
Enable saving passwords to the password managerA business decision; we prefer a dedicated password managerMicrosoft dropped its advice to disable it, but a business password manager gives shared vaults, recovery and auditing.
Alert users if passwords are found to be unsafeEnabled, if Edge stores passwordsWarns users when a saved password appears in a known breach.
Strong password suggestionsEnabledEncourages unique passwords for new accounts.
Require authentication before autofillEnabled, if Edge stores passwordsSomeone at an unlocked PC cannot simply fill saved passwords.

macOS, iOS and Android configuration

macOS

SettingRecommendedWhy
EnrollmentAutomated Device Enrollment through Apple Business, with a default enrollment policy on the tokenApple Business replaced Apple Business Manager in April 2026. A synced Mac with no assigned policy fails enrollment.
User affinity and authenticationEnroll with user affinity, using Setup Assistant with modern authenticationMicrosoft no longer recommends the legacy Setup Assistant option.
Await final configurationYesHolds the user at the end of setup until critical policies arrive. Required for FileVault and Platform SSO during setup.
Locked enrollmentYesUsers cannot remove the management profile. It cannot be changed later without a wipe, so decide up front.
Local accountsUser account Standard, plus a hidden local admin managed by Intune with password rotationIntune escrows and rotates the local admin password. Viewing it needs a custom admin role.
Platform SSO authentication methodSecure Enclave keyMicrosoft’s recommended method. Phishing resistant and works as a passkey; the local password still unlocks FileVault.
Platform SSO assignmentOne SSO policy per Mac, assigned to user groupsTwo SSO payloads on one device fail, and device group assignment on user affinity Macs is unsupported.
Platform SSO during Setup AssistantEnabled on macOS 26 and later, with Company Portal deployed as a required appThe Mac reaches the desktop already registered with Entra ID.
FileVaultEnabled, forced during Setup Assistant, no bypass at login, recovery key escrowed to Intune, rotated every 12 monthsEncrypts the disk before the user ever reaches the desktop, with the key always recoverable.
FirewallEnabled, stealth mode on, block all incoming not configuredBlocking all incoming connections also breaks file and screen sharing.
GatekeeperApp Store and identified developers, users cannot overrideAllows notarised apps while blocking unsigned ones.
ComplianceRequire System Integrity Protection, encryption, firewall, Gatekeeper and a minimum OS versionDo not set password rules in compliance: on macOS that expires every local password, including managed admin accounts. Enforce the passcode with a configuration policy instead.
Minimum OS versionThe previous major version (macOS 26), with a grace window for macOS 15Defender for Endpoint supports the three most recent versions.
Defender for EndpointDeploy the system extension, network filter, full disk access, background services, notifications and accessibility profiles before the app, then onboardDefender only works if its permissions are in place before it installs. Only one network filter profile is allowed per Mac.
Microsoft AutoUpdateCurrent channel, automatic download and install, with a deadlineKeeps Office, Defender and Company Portal patched.
Company PortalRequired, deployed as a line of business appIt is the sign in broker for Platform SSO; an old version makes SSO fail.
Software updatesDeclarative device management update policiesCovered in the updates section. The old update policies are deprecated.

iOS and iPadOS

SettingRecommendedWhy
Company devicesAutomated Device Enrollment through Apple Business: supervised, modern authentication, locked enrollmentSupervision unlocks most restrictions and silent Defender onboarding.
Personal devicesAccount driven user enrollment, or app protection only without enrollmentUser enrollment through Company Portal is deprecated for new devices. Account driven enrollment needs Managed Apple Accounts and a service discovery file on your domain.
Minimum OS for IntuneiOS and iPadOS 18Intune itself requires iOS 18 or later since September 2026.
Managed Apple AccountsFederate Entra ID with Apple BusinessStaff sign in to Apple services with their work account. User names must match email addresses.
Treat AirDrop as an unmanaged destinationYesStops company data leaving by AirDrop.
Block viewing corporate documents in unmanaged appsYesThe core managed open in control: company files only open in company apps.
Allow copy and paste to be affected by managed open inYesStops pasting from managed apps into personal ones.
Allow managed apps to write contacts to unmanaged contacts accountsYesNeeded for Outlook contact sync to the phone. Leave the reverse document restriction off, or Outlook contact export breaks.
Activation LockAllow (supervised)Intune escrows the bypass code, so a lost device is useless to a thief but recoverable by IT.
Untrusted TLS certificates and new enterprise app authorsBlockMicrosoft’s baseline; stops users trusting rogue certificates or apps.
Encrypted backup and managed app iCloud storageForce encrypted backup; block managed apps storing data in iCloudCompany data stays out of personal cloud storage.
Passcode6 digits, 5 minute auto lock, erase after 10 failed attemptsMicrosoft’s baseline for supervised devices.
Block account modification and erase all contentNot configured for most businessesMicrosoft only sets these at its highest level. Activation Lock already protects a wiped device.
Microsoft Enterprise SSO plug inSingle sign on app extension, type Microsoft Entra ID, with Authenticator installedUsers sign in once and every Microsoft and supported app follows.
Defender for EndpointSilent onboarding on supervised devices; a configuration profile for unsupervised onesAdds web protection and threat detection, feeding the risk score used in compliance.
Apple push certificateRenew every year with the same Apple Account, from a monitored shared mailboxIf it expires, or a new one is created instead of renewing, every Apple device has to enrol again.

Android Enterprise

SettingRecommendedWhy
Managed Google PlayBound with an Entra account that has a mailbox; at least two ownersAvoids the binding depending on one person’s Gmail account. Tenants bound with Gmail can now upgrade to a managed Google domain.
Company phone provisioningZero touch enrollment through your reseller; Knox Mobile Enrollment for SamsungPhones enrol themselves on first boot, even after a factory reset.
Factory reset (fully managed)Block, with factory reset protection set to two admin Google accountsUsers cannot drop out of management, and IT can unlock a device after an unauthorised reset.
Developer options and USB debuggingNot configured (blocked by default on company devices); never set to allowPrevents sideloading and data extraction over USB.
Install from unknown sourcesNot configured (blocked by default)Apps only come from Managed Google Play.
USB file transfer and external mediaBlock on company devicesA simple data loss control.
Company phone screen lockNumeric complex, 6 digits, 5 minute lock, wipe after 10 failed attemptsMicrosoft’s baseline for fully managed devices.
Personal Google accounts and new users (company phones)BlockKeeps company phones for company use.
Work profile: copy and paste between work and personalBlockThe main way data leaks out of a work profile on a personal phone.
Work profile: data sharingWork apps can receive from personal apps, not the other wayUsers can attach a personal photo to work email without exposing work files.
Work profile: contactsBluetooth contact sharing allowed; personal search of work contacts not configuredKeeps the car hands free and the phone dialer useful.
Work profile passwordRequired, 6 digit numeric complex, 5 minutes, wipe the work profile after 10 failuresProtects work data even if the personal lock is weak. Users can unify both locks.
Android Management API migrationPilot the move now and enable web enrollmentRemaining personal work profiles move automatically in Q4 2026, one way only, and custom profiles stop working.
Defender for EndpointRequired Managed Google Play app with permissions granted by app configurationAdds web protection and threat detection, feeding the risk score used in compliance.

Windows experience and hardening

Common settings catalog policies for Windows. Several Windows consumer experience policies only work on Enterprise and Education editions, which Business Premium devices do not run without an add on.

SettingRecommendedWhy
RecallExplicitly disabled, with AI data analysis offRecall is off by default on managed devices; setting it explicitly removes it and deletes any snapshots.
Block Microsoft accountsUsers cannot add Microsoft accountsKeeps personal accounts off work PCs. The stricter option can lock out existing admins.
Machine inactivity limit900 seconds (15 minutes)The Windows security baseline value.
Lock screen notificationsBlockEmail and chat previews do not show on a locked screen.
Delivery OptimizationHTTP blended with peering on the same networkPCs in the same office share update downloads, saving bandwidth.
Consumer experiences, Spotlight and tipsBlock, on Windows Enterprise devicesStops promoted app installs. These policies only work on Enterprise and Education, not Pro.
RemediationsUse for automated fixes where licensedNeeds Windows Enterprise E3 or E5; Business Premium alone is not entitled.
Device queryUse for audits where licensedPart of Advanced Analytics, included in Microsoft 365 E3 and E5 since July 2026.

OneDrive and Microsoft 365 Apps

One detail matters throughout the OneDrive policies: Disabled is not the same as Not configured. Disabled often switches a default behaviour off, so leave a policy Not configured unless you mean to change it. Two policies have also been retired and should be removed from existing profiles.

SettingRecommendedWhy
Silently sign in users to the OneDrive sync app with their Windows credentialsEnabledThe core setting: OneDrive is signed in and syncing without the user doing anything.
Silently move Windows known folders to OneDriveEnabledDesktop, Documents and Pictures are backed up from day one, so a lost laptop does not mean lost work.
Prompt users to move Windows known folders to OneDriveEnabledMicrosoft pairs it with the silent move as a fallback for devices where the silent move cannot run.
Prevent users from redirecting their Windows known folders to their PCEnabledStops users turning the backup off again.
Prevent users from moving their Windows known folders to OneDriveNot configuredHas no effect when the move policies above are on.
Allow syncing OneDrive accounts for only specific organizationsEnabled, with your tenant IDStops company data being synced into another organization’s OneDrive. It overrides the block list, so never use both.
Block syncing OneDrive accounts for specific organizationsNot configuredDoes nothing when the allow list is on.
Prevent users from syncing personal OneDrive accountsEnabled on company devicesCloses an easy route for copying company files into a personal account. Our judgement rather than a Microsoft default.
Prevent users from syncing libraries and folders shared from other organizationsNot configured for most; Enabled where data policy requiresControls syncing of content shared by partners. Most businesses want this to work.
Use OneDrive Files On DemandEnabledFiles appear in File Explorer but only download when opened, saving disk space. Microsoft says to keep it on.
Enable sync health reporting (was Sync Admin Reports)EnabledFeeds the sync health and known folder move reports in the Microsoft 365 Apps admin center, so problems are visible.
Require users to confirm large delete operationsEnabledA big accidental delete waits for confirmation; if the user does not confirm within 7 days, it does not happen.
Prompt users when they delete multiple OneDrive files on their local computerNot configured (prompts at 200 files)Disabled actually switches the mass delete warning off, which weakens protection.
Warn users who are low on disk spaceEnabledA warning before space runs out avoids sync failures.
Block file downloads when users are low on disk spaceEnabled (optional)Stops OneDrive filling the last of the disk.
Enable automatic upload bandwidth managementEnabledMicrosoft recommends it over fixed limits. It yields to other traffic automatically.
Limit download speed, upload percentage or upload rateNot configuredUse automatic bandwidth management instead.
Continue syncing on metered networksNot configured (pauses on metered networks)The default pause protects mobile data plans.
Continue syncing when devices have battery saver onEnabledA comfort setting so files keep syncing on the road.
Convert synced team site files to online only filesNot configured (Enabled on shared or small disk PCs)Frees disk space on devices that sync large libraries.
Configure team site libraries to sync automaticallyNot configuredMicrosoft recommends OneDrive shortcuts instead, and the policy has item and device limits.
Prevent users from changing the location of their OneDrive folderEnabled (optional)Predictable paths make known folder move and support simpler.
Set the default location for the OneDrive folderNot configuredThe default user profile location is right for almost everyone.
Disable the tutorial that appears at the end of OneDrive SetupEnabledCosmetic. Sign in is silent, so the tutorial only adds clicks.
Hide the "Deleted files are removed everywhere" reminderNot configuredThe reminder helps users understand that deleting a synced file deletes it in the cloud.
Exclude specific kinds of files from being uploadedNot configured, or a short list such as .pstOptional; Outlook data files sync badly.
Allow OneDrive to disable Windows permission inheritance in folders synced read onlyNot configuredOnly speeds up read only libraries. Microsoft does not recommend it otherwise.
Always use the user’s Windows display language when provisioning known foldersNot configuredOnly overrides a user’s preferred folder language.
Cause sync client to ignore normal web proxy detectionNot configuredOnly needed for unusual proxy setups.
Prevent the sync app from generating network traffic until users sign inNot configuredOnly for very constrained networks, and it sticks even after being removed.
Set the maximum size of a user’s OneDrive that can download automaticallyNot configuredOnly applies to devices without Files On Demand.
Set the sync app update ringNot configured (Production); Insiders for a few IT staffMicrosoft recommends Production for everyone else.
Specify SharePoint Server URL, and OneDrive location in a hybrid environmentNot configuredOnly for on premises SharePoint Server.
Coauthor and share in Office desktop appsRemove from the policyRetired in May 2025. Coauthoring is now always on.
Allow users to choose how to handle Office file sync conflictsRemove from the policyRetired in May 2025.
Start OneDrive automatically when signing in to WindowsEnabledNewer policy in Microsoft’s recommended set. OneDrive is always running.

Microsoft 365 Apps

SettingRecommendedWhy
Cloud update for Microsoft 365 AppsOn, with devices assigned to the Monthly Enterprise profileMicrosoft calls it the recommended update method. Rollout waves, pause and rollback all work on Monthly Enterprise.
Update channelMonthly Enterprise for staff; Current for ITMonthly Enterprise updates once a month on Patch Tuesday, which is predictable and easy to support. IT sees new features first.
Microsoft 365 Apps inventoryNo action neededDevices appear automatically once someone opens an Office app.

Pushing SharePoint libraries as OneDrive shortcuts

A question we hear often: can admins add a SharePoint library to everyone's OneDrive as a shortcut, the way users can with “Add shortcut to My files”?

Not yet, and there is no date. As of October 27, 2026 there is no Microsoft feature, generally available, in preview or on the public Microsoft 365 roadmap, that lets admins create OneDrive shortcuts on behalf of users. The most recent change was user facing: in July 2026 OneDrive on the web gained an optional Shortcuts folder to keep shortcuts tidy, with no new admin controls.

What you can do today:

  • Let users add shortcuts themselves. This is what Microsoft recommends over the Sync button: shortcuts perform better and follow the user to every device, including Mac, mobile and Teams. Users need edit permission, and there are limits of 1,000 shortcuts in total and 100 from the same library. Admins can hide the Sync button on team sites with Set-SPOTenant -HideSyncButtonOnTeamSite $true to steer people towards shortcuts.
  • Sync libraries automatically on Windows. The “Configure team site libraries to sync automatically” policy pushes a library to users' PCs as online only files within about eight hours. It is Windows only, users cannot stop syncing it, and Microsoft advises against it for libraries with more than 5,000 items or on more than 1,000 devices. Note that a library cannot be both synced and added as a shortcut by the same user.
  • Script it, carefully. Shortcuts can be created through Microsoft Graph, but Microsoft does not document this for shortcuts, so treat it as unsupported.

Teams, email and audit

These settings sit in the Teams and Defender admin centres rather than Intune, but a well managed device still needs protected email and collaboration.

Teams

SettingRecommendedWhy
Meeting recordingOnRecordings land in OneDrive or SharePoint, where retention and compliance apply.
Require participant agreement for recording and transcriptionOff for most; On where consent matters, such as clinics and legalNow also covers Copilot. A new value, legitimate interest, suits some regulated settings.
Recordings default expiration time120 days, longer if your retention rules require itMicrosoft’s default. Expired recordings go to the recycle bin for another 93 days.
Store recordings outside your country or regionOff (effectively obsolete)It no longer applies to recordings saved in OneDrive and SharePoint, which is where all recordings now go.
TranscriptionOnCopilot needs a transcript to summarise during and after the meeting.
Live captionsDefault (off, users can turn them on)Off blocks captions for everyone, which hurts accessibility for no security gain.
Copilot in meetingsOn with saved transcript required (now the default)The setting was renamed and now has four values. Requiring a saved transcript keeps a record of what Copilot was working from.
Anonymous users can join a meetingLeave the org wide setting on; require verification with the per organiser policyMicrosoft is retiring the org wide switch and now recommends making anonymous and untrusted users pass a verification check instead.
Third party cloud storage in TeamsOff, or approved providers onlyKeeps files in Microsoft 365, where retention, data loss prevention and Safe Attachments apply.
External accessAllow only specific external domainsThe 2025 Teams campaigns impersonated help desks from attacker tenants. An allow list stops strangers messaging staff.
Chat with unmanaged Teams accountsOff, or at least stop unmanaged users starting conversationsMicrosoft’s recommendation after the same campaigns.
Guest accessOn, governed by Entra B2B settingsGuests in teams are invited, named and reviewable, unlike open external chat.

Email security and audit

SettingRecommendedWhy
Preset security policies (Exchange Online Protection and Defender for Office 365)Standard for all users; Strict for executives, finance and adminsMicrosoft maintains the settings, so they stay current without tuning. Strict for the people attackers target most is our practice.
Configuration analyzerRun it after every changeCompares your policies with Standard and Strict and flags drift. It needs the unified audit log on.
Safe Attachments for SharePoint, OneDrive and TeamsOn, and block downloads of infected filesOn by default with Defender for Office 365, but downloads of detected files are still allowed until you block them.
SPF and DKIMBoth on every sending domainProves mail really comes from you. DKIM needs manual setup on custom domains.
DMARCStart at none, move to quarantine, finish at reject; reject on parked domainsMicrosoft’s stated end goal is reject on every domain. Major mailbox providers now reject mail that fails these checks from bulk senders.
MTA STS and TLS reportingPublish in testing mode, then enforceForces encrypted delivery of inbound mail to Exchange Online.
Unified audit logVerify it is onAuditing is not on by default for Business plan tenants. Without it, an incident has no evidence trail.
Audit retentionAudit Standard (180 days) plus export to a SIEM for longerAudit Premium keeps key records for a year; most small businesses export instead.

Monitoring, recovery and remote support

SettingRecommendedWhy
Windows health monitoringEnabled, scope Endpoint analytics, assigned to all corporate devicesFeeds startup performance and app reliability reports. The current template only offers the Endpoint analytics scope.
Collecting Windows event logs centrallyUse Defender for Endpoint telemetry; for a SIEM, the Azure Monitor Agent with filtered collectionThe old Log Analytics agent retired in August 2024. Collecting Information and Success Audit events from every PC is the biggest cost driver, so filter for what you will actually use.
SettingRecommendedWhy
Windows backup and restoreEnable Windows Backup and turn on the restore page during setupGenerally available since 2025. Settings and apps follow a user to a new PC. Restore needs Entra join and user driven Autopilot.
Remote HelpUse it when the client has no other remote support toolRole based and logged, but an add on: included in Microsoft 365 E3 and E5 since July 2026, not Business Premium.
Microsoft TunnelOnly for mobile access to on premises apps where no other VPN existsMost small businesses have no on premises apps left that need it.
Cloud PKI and certificatesCloud PKI with SCEP certificates for Wi Fi and VPN, where licensedCertificate based Wi Fi without running an on premises certificate authority. An add on, included in Microsoft 365 E5.
Wi Fi and VPN profilesDeploy the trusted root certificate, then the device certificate, then the Wi Fi or VPN profile, to the same group typeEach profile depends on the one before it.

Security baselines

Microsoft's baselines are a useful yardstick. Whether you deploy them or not, compare your policies against the current versions.

SettingRecommendedWhy
Windows security baselineVersion 26H2, or match its values in individual policiesMicrosoft’s recommended Windows hardening. Do not deploy it and overlapping endpoint security policies for the same settings.
Defender for Endpoint baselineVersion 24H1 (still the latest)Disagrees with the Windows baseline on a few settings; pick one source per setting.
Microsoft Edge baselineVersion 139Covers SmartScreen and browser hardening.
Microsoft 365 Apps baselineVersion 2512Hardens macros and add ins in Office.
Preview baselinesNot in productionMicrosoft does not recommend them for production use.
Want your tenant checked against this reference?
We can review your Intune, Entra ID and Microsoft 365 configuration setting by setting and tell you plainly what to change first.
Book an Intune Review

How Regroove helps

This is how we run devices for our clients every day. Our Intune consulting and managed IT services put it in place and keep it current, and our managed security services watch over it. If you are starting from scratch, our guides to zero touch deployment with Intune and the Microsoft 365 security baseline are a good place to begin.

Frequently asked questions

What are the Microsoft Intune best practices in 2026?

Start from Microsoft’s own guidance: the Windows and Defender for Endpoint security baselines, the data protection framework for app protection, Windows Autopatch for updates and phishing resistant sign in for admins. Then adjust only where the business has a clear reason. The checklist at the top of this page lists everything to configure, and the breakdown explains each setting.

Which licence do we need for these Intune policies?

Microsoft 365 Business Premium covers almost everything here: Intune Plan 1, Entra ID P1 for Conditional Access, Defender for Business, Defender for Office 365 Plan 1 and Windows Autopatch. Risk based sign in policies need Entra ID P2. Endpoint Privilege Management, Remote Help, Cloud PKI and Remediations are add ons, some now included in Microsoft 365 E3 or E5, and Credential Guard needs Windows Enterprise.

Should we deploy Microsoft’s security baselines or configure policies ourselves?

Either, but not both for the same settings, because overlapping policies conflict and are hard to troubleshoot. For small and mid sized businesses we prefer individual endpoint security policies like the ones here, which are easier to read and change, and we check them against the baselines.

Why are some attack surface reduction rules in audit mode?

Some rules block things legitimate software also does. The PSExec and WMI rule, for example, catches the same techniques that management and remote monitoring tools use, and both Microsoft baselines keep it in audit. Audit mode shows what a rule would block, so you can add exclusions before switching it to block.

Can admins push SharePoint libraries to users as OneDrive shortcuts?

Not yet. As of October 2026 there is no Microsoft feature, in preview or on the public roadmap, for admins to add OneDrive shortcuts for users. Users can add shortcuts themselves, which Microsoft recommends over syncing, and admins can still sync libraries automatically on Windows with the team site libraries policy, within its limits.

How often should an Intune configuration be reviewed?

At least once a year, and whenever Microsoft ships a new Windows version or security baseline. Settings get renamed and retired, defaults change, and new protections appear several times a year.

Sources

Checked against Microsoft documentation in October 2026. Microsoft updates these pages often, so always confirm a setting in the admin centre before relying on it.

Helio PereiraAuthor: Helio Pereira

Regroove IT Consulting

Microsoft Solutions Partner specializing in Managed IT Services and Modern Work, covering Microsoft 365, Teams, SharePoint, Power Platform, and Azure. Helping organizations everywhere get lasting value from their Microsoft investment since 1993.

About Regroove →

Want a hand with this?

We do this work every week. Have a look at how we help, or just tell us what you are trying to solve.

Comments

Loading comments…

Leave a comment

Comments are reviewed before they appear. Your email is never published, and we only use it to let you know when your comment goes live.

Links are not accepted, which keeps the spam out.

0/2000