Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft 365 Foundations v7.0.0 · 1.3.5

Microsoft Forms should scan internal forms for phishing

  • E3 Level 1
  • Microsoft 365 admin center
  • Automated check

This check looks at the Microsoft Forms tenant setting that scans forms created inside your organization for phishing content. The safe setting is for internal phishing protection to be turned on.

Why it matters

Microsoft Forms is easy to use and easy to share, which makes it a convenient way to collect passwords, payment details or sign-in information under a false pretext. A form sent from a compromised colleague account looks trustworthy to its recipients, because it comes from a real internal address and opens on a Microsoft domain.

Microsoft provides a tenant-wide option that scans forms created inside your organization for phishing and blocks those that look like attempts to harvest credentials or sensitive data. Microsoft's administrator documentation states that the Internal phishing protection option under Phishing protection is checked by default, and that an administrator can clear it. A tenant where someone turned it off has lost a safeguard that costs nothing to keep. See the Microsoft Forms administrator settings page on Microsoft Learn.

Because the setting is a single switch, it is also a good example of drift: someone changes it once for a one-off survey and nobody switches it back.

How to check it yourself

Portal path: sign in to the Microsoft 365 admin center as an administrator who can manage Forms settings, open Settings, then Org settings, then the Microsoft Forms pane. Under Phishing protection, confirm that Internal phishing protection is ticked.

Read-only command (Microsoft Graph PowerShell, run on a test tenant first; the call only reads, but it uses a beta endpoint whose shape Microsoft may change). Connect with a read-only Forms admin scope, then request the settings:

Connect-MgGraph -Scopes "OrgSettings-Forms.Read.All"
$s = Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/beta/admin/forms/settings"
$s.isInOrgFormsPhishingScanEnabled

A result of True means the safe setting is in place. False means the check fails.

How to fix it

Portal steps: in the Microsoft 365 admin center go to Settings, Org settings, Microsoft Forms. Under Phishing protection, tick Internal phishing protection and select Save. The change applies to the whole tenant.

Script option, using the same Graph endpoint with a scope that allows writing Forms settings (run it yourself, as an administrator, and test it first; ConfigCobra itself only reads your tenant and never applies the fix):

Connect-MgGraph -Scopes "OrgSettings-Forms.ReadWrite.All"
Invoke-MgGraphRequest -Method PATCH -Uri "https://graph.microsoft.com/beta/admin/forms/settings" -Body @{ isInOrgFormsPhishingScanEnabled = $true }

Afterwards, repeat the read-only check above to confirm the value is now True.

What changes when you fix it

Form creators and respondents inside your organization are the people affected. Forms that Microsoft's scan classifies as phishing can be blocked or removed, so a person who built a genuine form that happens to ask for sensitive details may find it flagged. Tell survey owners, HR and finance teams beforehand that forms asking for passwords or payment details may be blocked, and point them to your usual process for legitimate data collection.

Nothing changes for people who only fill in forms, and no licences or settings elsewhere are touched. If a legitimate form is flagged, the owner can raise it with your administrators, who can review it instead of turning the whole protection off. Roll back by clearing the same tick box, though leaving it on is the safer choice.

Included in

BenchmarkCIS IDProfile
CIS Microsoft 365 Foundations v7.0.01.3.5E3 Level 1

Check this on your Microsoft 365

ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial