Microsoft 365 tenant · Devices, Intune tenant settings & Microsoft 365 Apps

Block file opens over HTTP, FTP and FrontPage RPC in Microsoft 365 apps

When it fails: Microsoft 365 apps can open files over insecure protocols. Users can open documents over cleartext HTTP or FTP, or fall back to the FrontPage RPC protocol, exposing content and credentials to interception and legacy protocol attacks.

CB-M365-DEVICE-013mediumactivemanualprofile baseline

Description

Two Baseline Security Mode settings are turned on in the Microsoft 365 admin center:

  • Block files from opening with insecure protocols: Microsoft 365 apps refuse to open files from HTTP or FTP locations (Cloud Policy policy Block Insecure Protocols);
  • Block files from opening with FPRPC protocol: apps never fall back to FrontPage Server Extensions RPC and use HTTPS instead (Cloud Policy policy Restrict Apps from FPRPC Fallback).

In both cases users can no longer override the behavior in the Trust Center.

Rationale

HTTP and FTP carry document content, and sometimes credentials, in clear text: anyone on the network path can read or modify them, or inject a malicious document. FrontPage RPC is a decades-old authoring protocol with a history of exploitable flaws. Microsoft 365 apps already block FPRPC by default; enforcing both settings removes the user override and the remaining cleartext paths.

Impact

Documents published on plain HTTP or FTP servers no longer open from Office; move them to HTTPS, SharePoint or OneDrive. Old intranet servers that only support FrontPage extensions stop working for file opens. Run the Baseline Security Mode impact reports first.

Audit

  1. Sign in to the Microsoft 365 admin center (https://admin.cloud.microsoft) as at least a Global Reader.
  2. Browse to Settings > Org settings > Security & privacy > Baseline security mode.
  3. Check that Block files from opening with insecure protocols and Block files from opening with FPRPC protocol are both turned on.
  4. In the Office Cloud Policy service (https://config.office.com), Customization > Policy Management, check that no policy configuration with a higher priority than the tenant one sets Block Insecure Protocols or Restrict Apps from FPRPC Fallback to Disabled.
  5. Fail if either setting is off or overridden for a group of users.

Remediation

  1. In Settings > Org settings > Security & privacy > Baseline security mode, open each setting and download its impact report; move the listed documents to HTTPS locations.
  2. Turn on Block files from opening with insecure protocols and Block files from opening with FPRPC protocol. Role: Office Apps Administrator.
  3. Alternative: in the Office Cloud Policy service, set Block Insecure Protocols and Restrict Apps from FPRPC Fallback to Enabled in a policy configuration targeting all users. No PowerShell cmdlet exists.

Rollback

Turn the settings off in Baseline security mode, or set the Cloud Policy policies back to not configured.

References

Mappings

FrameworkIDRelation
NIST SP 800-53 Rev. 55.1.1SC-8related
NIST SP 800-53 Rev. 55.1.1CM-7related

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

Threats mitigated

People and lifecycle

Authors
Introduced inv0.1.0
Created, updated2026-10-24, 2026-10-24
Translationsfr