---
title: Setup phishing risk assessment for Microsoft Exchange with Email Security
  (formerly Area 1) · Cloudflare Email Security (formerly Area 1) docs
description: "For customers using Microsoft Exchange, setting up Email Security
  via BCC is quick and easy. You need to configure an inbound rule to send
  emails to Email Security via BCC for processing and detection of potential
  phishing attacks. The following email flow shows how this works:"
lastUpdated: 2025-08-29T19:00:56.000Z
chatbotDeprioritize: false
source_url:
  html: https://developers.cloudflare.com/email-security/deployment/api/setup/exchange-bcc-setup/
  md: https://developers.cloudflare.com/email-security/deployment/api/setup/exchange-bcc-setup/index.md
---

Area 1 has been renamed

Area 1 is now **Email Security (formerly Area 1)**.

For customers using Microsoft Exchange, setting up Email Security via BCC is quick and easy. You need to configure an inbound rule to send emails to Email Security via BCC for processing and detection of potential phishing attacks. The following email flow shows how this works:

![Email flow when setting up a phishing assessment risk for Microsoft Exchange with Email Security.](https://developers.cloudflare.com/_astro/bcc-exchange-flow.0rQkIXIG_1AzEWs.webp)

## Configure Inbound Rule

1. Access Exchange's **Management Console**, and go to **Organization Configuration** > **Hub Transport**.

   ![Access Hub transport](https://developers.cloudflare.com/_astro/step1.Cr53r8C4_Z5ydXG.webp)

2. On the **Actions** pane, select **New Transport Rule**.

3. Give the transport rule a name and a description and select **Next**.

   ![Give transport rule a name and description](https://developers.cloudflare.com/_astro/step3.Bo-0qS8t_Z2sg8Aj.webp)

4. In the **Condition** configuration panel, select the option **from users that are inside or outside the organization** option. In the dropdown that opens, select **Outside the organization**.

   ![Select scope of transport rule](https://developers.cloudflare.com/_astro/step4.CxndsEWe_Z2oMkGp.webp)

5. Still in the same **Condition** configuration panel, add a second condition to the transport rule. Select **sent to users that are inside or outside the organization, or partners**. Keep the default value of **Inside the organization**.

   ![Select where to send emails](https://developers.cloudflare.com/_astro/step5.CFjU-V5M_ZAp0uJ.webp)

6. Select **Next**.

7. In the **Action** configuration panel, select **Blind carbon copy (Bcc) the message to addresses**. Edit the **addresses** variable to add the addresses you want to copy as BCC.

   ![Select BCC and edit email addresses](https://developers.cloudflare.com/_astro/step7.DJeDn5tj_1h2CAV.webp)

8. In **Specify Recipient**, select the **down arrow** next to the **Add** button > **External E-Mail Address**.

   ![Select external e-mail address](https://developers.cloudflare.com/_astro/step8.D1wRFlWS_Z13foj2.webp)

9. Enter the BCC address provided by Area 1. This address is specific to your account.

   ![Enter the BCC address provided by Area 1](https://developers.cloudflare.com/_astro/step9.DnJuKcbu_16p1ca.webp)

10. Select **OK** > **OK** to return to the main configuration page of the transport rule.

11. At the main configuration page of the transport rule, select **Next** to continue to the Exception configuration panel.

12. You do not need to configure an exception rule. Select **Next**.

    ![You do not need to configure an exception rule](https://developers.cloudflare.com/_astro/step12.CubH_6Qs_2atp1F.webp)

13. In **Create Rule**, select the **New** button.

    ![Select the new button](https://developers.cloudflare.com/_astro/step13.Bk-qDQZk_I2FaW.webp)

14. Select **Finish** to close the transport rule configuration panel. This will return you to the Exchange Management Console.

    ![Select finish](https://developers.cloudflare.com/_astro/step14.FJuX6pFq_1KjQwl.webp)

Note

If you have multiple rules, you may need to change the order of the BCC rule and move it to the right location in your rule sequence. This is needed so you can send BCC messages to Email Security (formerly Area 1). Usually, the Email Security BCC rule will be at the top of the ruleset. The configured conditions of the Email Security BCC rule will only trigger for inbound messages.

## Email processing and reports

In BCC mode, all emails are put through automated phishing detections by Email Security. Emails that trigger phishing detections are logged for reporting via product portal, email and Slack. Emails that do not trigger any detections are deleted.
