> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/reports/antiphishing-filters.md).

# Anti-Phishing Filters

This report lists the anti-phishing policies configured in the selected tenant, each paired with the rule that decides who it applies to. It shows at a glance whether a policy is in force, which domains it covers, which senders and domains are excluded, and how its impersonation and spoof protections are set.

## Table Details

The properties returned are for the combination of the following Exchange PowerShell commands. For more information on the command please see the Microsoft documentation:

* [Get-AntiPhishPolicy](https://learn.microsoft.com/en-us/powershell/module/exchange/get-antiphishpolicy?view=exchange-ps)
* [Get-AntiPhishRule](https://learn.microsoft.com/en-us/powershell/module/exchange/get-antiphishrule?view=exchange-ps)

Every row is a policy. **Rule Name**, **Priority**, **Recipient Domain Is**, and **State** come from the rule paired with that policy, and everything else comes from the policy itself.

{% hint style="warning" %}
The built-in default policy shows no **Rule Name**, **Priority**, **Recipient Domain Is**, or **State**, and cannot be enabled or disabled from this page. Manage it from the Microsoft 365 Defender portal or with a CIPP standard instead.
{% endhint %}

Spoof intelligence, unauthenticated sender indicators, and the first contact safety tip are part of Exchange Online Protection. The impersonation protection settings, which are the mailbox intelligence protection action, the targeted user and targeted domain protection actions, and their quarantine tags, only take effect where the tenant is licensed for Microsoft Defender for Office 365.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Enable Rule</td><td>Brings the policy into force so it starts applying to the recipients its rule covers. Greyed out where <strong>State</strong> is already <code>Enabled</code>.</td><td>true</td></tr><tr><td>Disable Rule</td><td>Stops the policy applying while keeping all of its settings, so it can be brought back later. Greyed out where <strong>State</strong> is already <code>Disabled</code>.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/email/reports/antiphishing-filters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.