Microsoft 365 brings the shutters down on legacy protocols However, the protocol for remote web authoring has lived on until now Describing legacy protocols like RPC as "more susceptible to compromise," Microsoft will block them to prevent their use in Microsoft 365 clients Microsoft testing PC-to-Cloud-PC failover for those times your machine dies or disappears
Microsoft 365 Boosts Security: Legacy File Access Protocols RPS . . . Beginning in mid-July, Microsoft will disable legacy file authentication protocols across Microsoft 365, Office applications, SharePoint, and OneDrive Once deprecated, applications and services that rely on the Relying Party Suite (RPS) or FrontPage Remote Procedure Calls will no longer be able to use browser-based authentication to access Office files
Microsoft Phases Out Legacy Authentication in Microsoft 365 by July . . . From mid-July 2025 extending into August, Microsoft 365’s updated defaults will block not only legacy browser authentication to SharePoint and OneDrive via RPS but also shut the door on protocols like FrontPage Remote Procedure Call (RPC)—a vestige from the web authoring tool discontinued roughly two decades ago that nonetheless lingered long enough to be considered a soft underbelly in
Microsoft 365 Security: Legacy Authentication Blocked By Default – What . . . Microsoft announces a major security update: starting mid-July 2025, all Microsoft 365 tenants will block legacy authentication protocols by default for SharePoint, OneDrive, and Office files Learn how this Microsoft 365 security change impacts your organization and why legacy authentication is being phased out
Microsoft 365 to Block Legacy Authentication by Default Key Takeaways: Microsoft will block legacy authentication protocols in Microsoft 365 by default The changes aim to enhance security under the Secure Future Initiative and “Secure by Default