check before: 2025-07-15
Product:
Entra, Microsoft 365 Apps, OneDrive, SharePoint
Platform:
Online, Web, World tenant
Status:
Change type:
Feature update, User impact, Admin impact
Links:
Details:
Summary:
Microsoft 365 will update default settings to enhance security by blocking legacy authentication protocols and requiring admin consent for third-party app access. Changes start mid-July 2025 and complete by August 2025. Organizations should assess configurations, notify stakeholders, update documentation, and configure the Admin Consent workflow.
Details:
As part of the Microsoft Secure Future Initiative (SFI) and in alignment with the "Secure by Default" principle, we are updating default settings in Microsoft 365 to help you meet the minimum security benchmark and harden your tenant's security posture. These changes target legacy authentication protocols and app access permissions that may expose organizations to unnecessary risk.
This is the first step in a broader effort to evaluate and evolve Microsoft 365 defaults through the lens of security best practices.
[When this will happen:]
These changes will begin rolling out in mid-July 2025 and are expected to complete by August 2025.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-06-18
updated:
2025-06-19
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
Microsoft 365 is enhancing security by blocking legacy authentication protocols and requiring administrative approval for third-party app access, with these changes automatically applying to all users from mid-July to August 2025, at no additional cost.
Direct effects for Operations**
Blocking Legacy Authentication Protocols
Blocking legacy authentication protocols like RPS may prevent users from accessing SharePoint and OneDrive, leading to disruptions in workflow and productivity.
- roles: IT Admin, End User
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies, https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-legacybrowserauthprotocolsenabled
Blocking FPRPC Protocol
Blocking the FPRPC protocol will prevent users from opening Office files using outdated methods, potentially causing issues for users relying on legacy systems.
- roles: IT Admin, End User
- references: https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-legacybrowserauthprotocolsenabled
Admin Consent Requirement for Third-Party Apps
Requiring admin consent for third-party apps may slow down access to necessary tools for users, impacting their ability to work efficiently.
- roles: IT Admin, End User
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow, https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies
Increased Administrative Workload
The need for admin consent for third-party apps will increase the workload for IT admins, as they will need to manage and approve requests from users.
- roles: IT Admin, App Owner
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow
" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow
Documentation Updates
Organizations will need to update internal documentation to reflect the new defaults and processes, which may lead to temporary confusion among users.
- roles: IT Admin, End User
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
Enhancing Security Posture through Legacy Protocol Blocking
By blocking legacy authentication protocols like RPS and FPRPC, organizations can significantly reduce their exposure to vulnerabilities associated with outdated methods. This aligns with security best practices and protects sensitive data from potential breaches.
- next-steps: Conduct a security audit to identify any dependencies on legacy protocols. Implement the blocking measures as per the provided Microsoft guidelines and monitor the impact on user experience.
- roles: IT Security Team, System Administrators, Compliance Officers
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies, https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-legacybrowserauthprotocolsenabled
Streamlining Admin Consent Workflow for Third-Party Apps
Requiring admin consent for third-party app access minimizes the risk of unauthorized data exposure. This change enables IT departments to have better control over which applications can access sensitive organizational data, thus enhancing overall security.
- next-steps: Set up the Admin Consent workflow as outlined in Microsoft documentation. Train IT staff on the new process and communicate changes to all users to ensure compliance.
- roles: IT Administrators, Security Officers, Application Owners
- references: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow, https://go.microsoft.com/fwlink/p/?linkid=2324703
Improving Documentation and Stakeholder Communication
Updating internal documentation to reflect new default settings and processes will ensure that all stakeholders are informed and prepared for the changes. This reduces confusion and enhances compliance with new security measures.
- next-steps: Review and update all relevant internal documentation regarding Microsoft 365 settings. Schedule a meeting with stakeholders to discuss changes and implications, ensuring everyone understands their roles in the transition.
- roles: IT Documentation Specialists, Project Managers, Change Management Teams
- references: https://go.microsoft.com/fwlink/p/?linkid=2324508, https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-06-19 | MC prepare | We recommend the following actions:
Assess current configurations: As applicable, identify current configurations for RPS or FPRPC protocols and review third-party apps that access SharePoint and OneDrive content. Notify stakeholders: Inform IT admins, app owners, and security teams about the upcoming changes. Update documentation: Ensure internal guidance reflects the new defaults and admin consent process. Configure Admin Consent workflow: If third party apps access is applicable for your organization, learn how to set up the workflow: Configuring admin consent workflow. Additional considerations Does the change alter how existing customer data is processed, stored, or accessed? Yes - it blocks access to content via legacy authentication protocols. https://aka.ms/AppConsentLearn https://aka.ms/entra-app-access https://go.microsoft.com/fwlink/p/?linkid=2324508 https://go.microsoft.com/fwlink/p/?linkid=2324509 https://go.microsoft.com/fwlink/p/?linkid=2324703 https://learn.microsoft.com/en-us/defender-endpoint/web-content-filtering https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps | We recommend the following actions:
Assess current configurations: As applicable, identify current configurations for RPS or FPRPC protocols. Notify stakeholders: Inform IT admins, app owners, and security teams about the upcoming changes. Update documentation: Ensure internal guidance reflects the new defaults and admin consent process. Configure Admin Consent workflow: If third party apps access is applicable for your organization, learn how to set up the workflow: Configuring admin consent workflow. Additional considerations Does the change alter how existing customer data is processed, stored, or accessed? Yes - it blocks access to content via legacy authentication protocols. https://aka.ms/entra-app-access https://go.microsoft.com/fwlink/p/?linkid=2324508 https://go.microsoft.com/fwlink/p/?linkid=2324509 https://go.microsoft.com/fwlink/p/?linkid=2324703 https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-legacybrowserauthprotocolsenabled https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps |
| 2025-06-19 | MC How Affect | The following settings will be updated:
SettingsImpact Block legacy browser authentication to SharePoint and OneDrive using RPS (Relying Party Suite)Legacy authentication protocols like RPS (Relying Party Suite) are vulnerable to brute-force and phishing attacks due to non-modern authentication. Blocking this prevents applications that are using outdated methods from accessing SharePoint and OneDrive via browser. To use PowerShell to block legacy browser authentication, see Set-SPOTenant. Block FPRPC (FrontPage Remote Procedure Call) protocol for Office file opensFrontPage Remote Procedure Call (FPRPC) is a legacy protocol used for remote web page authoring. While no longer widely used, Legacy protocols such as FPRPC can be more susceptible to compromise and blocking FPRPC helps reduce exposure to vulnerabilities. With this change, FPRPC will be blocked for opening files, preventing the use of this non-modern protocol in Microsoft 365 clients. To learn how to block the FPRPC protocol, see turn on web content filtering. Require admin consent for third-party apps accessing files and sitesUsers allowing third-party apps to access file and site content can lead to overexposure of an organization's content. Requiring admins to consent to this access can help reduce overexposure. With this change, Microsoft managed App Consent Policies will be enabled, and users will be unable to consent to third party applications accessing their files and sites by default. Instead, they can request administrators to consent on their behalf. To configure admin consent, follow instructions here: configuring the Admin Consent workflow. Customers who have already blocked user consent or applied custom user consent settings will not be affected by this change. Admins can also configure granular app access policies, such as limiting user access to the application for specific users or groups. Learn more here. These changes are on by default and apply to all Microsoft 365 tenants. No additional licensing is required. | The following settings will be updated:
SettingsImpact Block legacy browser authentication to SharePoint and OneDrive using RPS (Relying Party Suite)Legacy authentication protocols like RPS (Relying Party Suite) are vulnerable to brute-force and phishing attacks due to non-modern authentication. Blocking this prevents applications that are using outdated methods from accessing SharePoint and OneDrive via browser. To use PowerShell to block legacy browser authentication, see Set-SPOTenant. Block FPRPC (FrontPage Remote Procedure Call) protocol for Office file opensFrontPage Remote Procedure Call (FPRPC) is a legacy protocol used for remote web page authoring. While no longer widely used, Legacy protocols such as FPRPC can be more susceptible to compromise and blocking FPRPC helps reduce exposure to vulnerabilities. With this change, FPRPC will be blocked for opening files, preventing the use of this non-modern protocol in Microsoft 365 clients. To learn how to block the FPRPC protocol, see turn on web content filtering. Require admin consent for third-party apps accessing files and sitesUsers allowing third-party apps to access file and site content can lead to overexposure of an organization's content. Requiring admins to consent to this access can help reduce overexposure. With this change, Microsoft managed App Consent Policies will be enabled, and users will be unable to consent to third party applications accessing their files and sites by default. Instead, they can request administrators to consent on their behalf. To configure admin consent, follow instructions here: Configuring the Admin Consent workflow. Customers who have already blocked user consent, turned on our previously recommended consent settings, or applied custom user consent settings will not be affected by this change. Admins can also configure granular app access policies, such as limiting user access to the application for specific users or groups. Learn more here. These changes are on by default and apply to all Microsoft 365 tenants. No additional licensing is required. |
| 2025-06-19 | MC Last Updated | 06/18/2025 08:14:42 | 2025-06-18T21:08:09Z |
| 2025-06-18 | MC Last Updated | 06/18/2025 01:24:21 | 2025-06-18T08:14:42Z |
Last updated 3 weeks ago
