Baseline security mode settings
Observed content change
May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
Changed article references · 24 added · 0 removed
- Added link: Restrict the number of devices a user can enroll in Intune
alert-users-new-device-enrolled?view=o365-worldwide - Added link: Always require MFA when admins sign in to the Intune admin center
always-require-mfa-admins-signin-intune?view=o365-worldwide - Added link: Block apps and flows from connecting to external tenants
block-apps-flows-from-connecting-external-tenants?view=o365-worldwide - Added link: Remove applications without exchange RBAC permissions
block-apps-without-exchange-rbac?view=o365-worldwide - Added link: Block chats initiated by Teams free accounts
block-chats-initiated-by-teams-free-accounts?view=o365-worldwide - Added link: Block COM add-ins that aren't on the admin allow list
block-com-addins-not-on-admin-allow-list?view=o365-worldwide - Added link: Block connection of untrusted Microsoft Query files
block-connection-untrusted-microsoft-query-files?view=o365-worldwide - Added link: Block creation and editing of classic SharePoint pages
block-creation-editing-classic-pages-sharepoint?view=o365-worldwide - Added link: Block DDE server lookups in Excel
block-dde-server-lookups-excel?view=o365-worldwide - Added link: Don't allow Microsoft 365 trial tenants to federate with your organization
block-microsoft365-trial-tenants-federate-with-your-organization?view=o365-worldwide - Added link: Require scoped access to files and sites for High-Privileged-Access applications
block-new-guest-users-assigned-ediscovery-roles?view=o365-worldwide - Added link: Block worksheet functions from accessing the web via insecure protocols
block-worksheet-functions-excel?view=o365-worldwide - Added link: Disable client facing preauthenticated URLs for Third-Party (3P) applications
disable-client-facing-preauth-3p?view=o365-worldwide - Added link: Disable Excel 4.0 (XL4/XLM) macros
disable-xl4-xlm-macros?view=o365-worldwide - Added link: Block meeting participants from changing their display names
dont-allow-meeting-participants-to-change-names?view=o365-worldwide - Added link: Require device compliance for Intune portal access
enforce-device-compliance-intune-portal-access?view=o365-worldwide - Added link: Harden macro security in the Microsoft 365 apps
harden-macro-security-microsoft-365-apps?view=o365-worldwide - Added link: Require a device compliance policy
require-device-compliance-policy?view=o365-worldwide - Added link: Require external participants to remain in the lobby until admitted to the meeting
require-external-users-wait-lobby-before-meetings?view=o365-worldwide - Added link: Require multifactor authentication (MFA) for admins signing into Power Platforms
require-mfa-admins-signing-into-power-platforms?view=o365-worldwide
Showing the first 20 references on each side. Counts cover the retained comparison.
… can target. EWS is also used in some first party features in both Outlook and the web add-in platform. Web add-ins for Word, Excel, PowerPoint, and Outlook don't work in some builds. For more information, see Control access to EWS. [added: Always require MFA when administrators sign in to Intune Requiring multifactor authentication (MFA) for Intune administrators adds a critical layer of protection to sensitive device management operations. Admin accounts protected only by passwords are far more vulnerable to compromise through phishing, credential theft, or brute force attacks. Enforcing MFA ensures that all admin sign-ins to the Microsoft Intune admin center require strong identity verification, helping prevent unauthorized access to policy configuration, privilege elevation, or enrollment of rogue devices. This setting reinforces Microsoft’s security baseline by ensuring admins can't override or weaken MFA requirements. For more information, see Always require MFA when admins sign in to the Intune admin center. Require a second administrator to approve sensitive actions Requiring a second administrator to approve sensitive actions adds an essential safeguard against unauthorized or high impact changes in Intune. Without dual approval, a single compromised or misconfigured admin account could perform harmful actions- such as wiping devices, modifying RBAC roles, deploying scripts, or altering app configurations- without detection. Enforcing this setting introduces oversight into high-risk operations, reducing the likelihood of privilege abuse, insider threats, or attacker driven configuration changes. This approval workflow helps ensure that sensitive administrative tasks receive proper review before execution, strengthening the overall security and integrity of your Intune environment. For more information, see Require a second admin to approve sensitive actions. Require device compliance for Intune portal access Requiring device compliance for accessing the Intune admin portal ensures that only trusted, properly managed devices can interact with sensitive] …
Before: … can target. EWS is also used in some first party features in both Outlook and the web add-in platform. Web add-ins for Word, Excel, PowerPoint, and Outlook don't work in some builds. For more information, see Control access to EWS. …
After: … can target. EWS is also used in some first party features in both Outlook and the web add-in platform. Web add-ins for Word, Excel, PowerPoint, and Outlook don't work in some builds. For more information, see Control access to EWS. Always require MFA when administrators sign in to Intune Requiring multifactor authentication (MFA) for Intune administrators adds a critical layer of protection to sensitive device management operations. Admin accounts protected only by passwords are far more vulnerable to compromise through phishing, credential theft, or brute force attacks. Enforcing MFA ensures that all admin sign-ins to the Microsoft Intune admin center require strong identity verification, helping prevent unauthorized access to policy configuration, privilege elevation, or enrollment of rogue devices. This setting reinforces Microsoft’s security baseline by ensuring admins can't override or weaken MFA requirements. For more information, see Always require MFA when admins sign in to the Intune admin center. Require a second administrator to approve sensitive actions Requiring a second administrator to approve sensitive actions adds an essential safeguard against unauthorized or high impact changes in Intune. Without dual approval, a single compromised or misconfigured admin account could perform harmful actions- such as wiping devices, modifying RBAC roles, deploying scripts, or altering app configurations- without detection. Enforcing this setting introduces oversight into high-risk operations, reducing the likelihood of privilege abuse, insider threats, or attacker driven configuration changes. This approval workflow helps ensure that sensitive administrative tasks receive proper review before execution, strengthening the overall security and integrity of your Intune environment. For more information, see Require a second admin to approve sensitive actions. Require device compliance for Intune portal access Requiring device compliance for accessing the Intune admin portal ensures that only trusted, properly managed devices can interact with sensitive …
[added: This section outlines the options available within Office applications for turning off Baseline security mode settings in the Microsoft 365 admin center.]
Before: No saved wording on this side.
After: This section outlines the options available within Office applications for turning off Baseline security mode settings in the Microsoft 365 admin center.
[added: Setting More information Block apps and flows from connecting to external tenants Power Platform apps and Power Automate flows commonly connect to business critical data using Microsoft Entra-based authentication. By default, valid credentials can be used to establish cross tenant connections, even when that behavior isn't intended or reviewed by administrators. For more information, see Block apps and flows from connecting to external tenants. Block applications without Exchange RBAC permissions Identify applications with unscoped Exchange access and replace their Microsoft Entra permissions with scoped RBAC for applications permissions to reduce the risk of unauthorized mailbox access or data exposure. For more information, see Remove applications without exchange RBAC permissions. Block COM add-ins that aren't on the admin allow list COM add-ins are legacy Office extensibility components that run inside the Office client on Windows and execute with the full permissions of the signed in user. Unlike modern Office web add-ins, COM add-ins don't benefit from the same sandboxing and isolation model. For more information, see Block COM add-ins that aren't on the admin allow list. Harden macro security in Office This setting hardens Visual Basic for Applications (VBA) macro security in Microsoft 365 apps by strengthening how macros are evaluated, trusted, and allowed to run. When enabled, it increases protection against malicious macros by expanding runtime scanning, enforcing stricter signing requirements for always loaded macros, and tightening trusted publisher criteria. for more information, see Harden macro security in the Microsoft 365 apps. Block Excel worksheet functions from accessing the web] …
Before: No saved wording on this side.
After: Setting More information Block apps and flows from connecting to external tenants Power Platform apps and Power Automate flows commonly connect to business critical data using Microsoft Entra-based authentication. By default, valid credentials can be used to establish cross tenant connections, even when that behavior isn't intended or reviewed by administrators. For more information, see Block apps and flows from connecting to external tenants. Block applications without Exchange RBAC permissions Identify applications with unscoped Exchange access and replace their Microsoft Entra permissions with scoped RBAC for applications permissions to reduce the risk of unauthorized mailbox access or data exposure. For more information, see Remove applications without exchange RBAC permissions. Block COM add-ins that aren't on the admin allow list COM add-ins are legacy Office extensibility components that run inside the Office client on Windows and execute with the full permissions of the signed in user. Unlike modern Office web add-ins, COM add-ins don't benefit from the same sandboxing and isolation model. For more information, see Block COM add-ins that aren't on the admin allow list. Harden macro security in Office This setting hardens Visual Basic for Applications (VBA) macro security in Microsoft 365 apps by strengthening how macros are evaluated, trusted, and allowed to run. When enabled, it increases protection against malicious macros by expanding runtime scanning, enforcing stricter signing requirements for always loaded macros, and tightening trusted publisher criteria. for more information, see Harden macro security in the Microsoft 365 apps. Block Excel worksheet functions from accessing the web …
[added: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant and the restrict resource account access parameter. Only allow endpoint managed, compliant devices to sign in To increase security, only compliant, organization-managed Teams Rooms devices can sign in to Microsoft 365 applications and resource accounts can't be misused to authenticate from unmanaged devices. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Block unmanaged devices and resource account sign-ins to Microsoft 365 apps To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Require multifactor authentication for device enrollment Requiring multifactor authentication (MFA) for device enrollment ensures that only verified users can add new devices to your organization through Intune. Device enrollment based solely on passwords leaves organizations vulnerable, as attackers who obtain stolen or phished credentials can silently onboard rogue devices that gain access to corporate data and services. Enforcing MFA adds a strong identity check during enrollment, reducing the risk of unauthorized device additions, limiting attacker persistence, and strengthening your overall access security posture. For more information, see Require MFA for device enrollment. Require a device compliance policy Requiring a device compliance policy ensures that every] …
Before: No saved wording on this side.
After: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant and the restrict resource account access parameter. Only allow endpoint managed, compliant devices to sign in To increase security, only compliant, organization-managed Teams Rooms devices can sign in to Microsoft 365 applications and resource accounts can't be misused to authenticate from unmanaged devices. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Block unmanaged devices and resource account sign-ins to Microsoft 365 apps To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Require multifactor authentication for device enrollment Requiring multifactor authentication (MFA) for device enrollment ensures that only verified users can add new devices to your organization through Intune. Device enrollment based solely on passwords leaves organizations vulnerable, as attackers who obtain stolen or phished credentials can silently onboard rogue devices that gain access to corporate data and services. Enforcing MFA adds a strong identity check during enrollment, reducing the risk of unauthorized device additions, limiting attacker persistence, and strengthening your overall access security posture. For more information, see Require MFA for device enrollment. Require a device compliance policy Requiring a device compliance policy ensures that every …
[removed: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant and the restrict resource account access parameter. Only allow endpoint managed, compliant devices to sign in To increase security, only compliant, organization-managed Teams Rooms devices can sign in to Microsoft 365 applications and resource accounts can't be misused to authenticate from unmanaged devices. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Block unmanaged devices and resource account sign-ins to Microsoft 365 apps To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients.]
Before: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant and the restrict resource account access parameter. Only allow endpoint managed, compliant devices to sign in To increase security, only compliant, organization-managed Teams Rooms devices can sign in to Microsoft 365 applications and resource accounts can't be misused to authenticate from unmanaged devices. For more information, see Block Teams resource account sign in to Microsoft 365 clients. Block unmanaged devices and resource account sign-ins to Microsoft 365 apps To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients.
After: No saved wording on this side.
[removed: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant.]
Before: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, remove resource accounts access that Teams Rooms and devices use to access Microsoft 365 assets for meeting and collaboration. For more information, see Set-SPOTenant.
After: No saved wording on this side.
[removed: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients.]
Before: Setting More information Don't allow resource accounts on Teams Rooms devices from accessing Microsoft 365 files To increase security, block resource accounts used for Teams devices from being used to sign in to Microsoft 365 clients. For more information, see Block Teams resource account sign in to Microsoft 365 clients.
After: No saved wording on this side.
Source: Microsoft source · © Microsoft · CC BY 4.0.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- 17 Nov 18:42 UTC
- Source update metadata
- 17 Nov 18:14 UTC
- First observed on this installation
- 12 Oct 19:35 UTC
- Last successful check
- today 00:54 UTC
- Next check due
- today 06:54 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.