[Area 1] Add warning on how to receive support from October

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/area-1.mdx

@@ -7,6 +7,10 @@ sidebar:
 
 ---
 
+import { Render } from "~/components";
+
+<Render file="contact-support" product="email-security" />
+
 [Cloudflare Area 1](https://www.cloudflare.com/products/zero-trust/email-security/) is an email security platform that protects your organization's inbox from phishing, spam, and other malicious messages. This guide covers how to configure Area 1 as a SAML application in Cloudflare Zero Trust.
 
 ## Prerequisites

src/content/docs/email-security/account-setup/escalation-contacts.mdx

@@ -8,11 +8,9 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 Whenever Email Security (formerly Area 1) finds an exceptional <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> threat or Email Service irregularity behavior (compromised email servers at a partner or vendor, wire fraud tactics, and more), we try to reach out to our customers.
 

src/content/docs/email-security/account-setup/manage-account-members.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 If your account is a **Super Admin**, you have the ability to add, edit, and delete users and - if those users lose their <GlossaryTooltip term="two-factor authentication (2FA)">two-factor authentication (2FA)</GlossaryTooltip> device - reset their 2FA.
 

src/content/docs/email-security/account-setup/manage-parent-permissions.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 When you set up Email Security through a [partner](/email-security/partners/), that partner's account is the **parent** account to your **child** account.
 

src/content/docs/email-security/account-setup/permissions.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 When you [create a user](/email-security/account-setup/manage-account-members/#add-user), the available options for permissions depend on whether your account is a **parent** account or a **child** account.
 

src/content/docs/email-security/account-setup/sso/index.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { DirectoryListing, GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 For added security and convenience, Email Security (formerly Area 1) offers support for <GlossaryTooltip term="SAML">Security Assertion Markup Language based (SAML-based)</GlossaryTooltip> single sign-on (SSO) logins. Organizations are able to choose between having users access Email Security (formerly Area 1) with a username and password plus a <GlossaryTooltip term="two-factor authentication (2FA)">two-factor authentication (2FA)</GlossaryTooltip> code, or using an SSO provider, such as OneLogin or Okta.
 

src/content/docs/email-security/api/index.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 Email Security offers Application Programming Interfaces (APIs) to expose our <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> campaign rulesets. These APIs both aid research and provide a set of indicators to block using network security edge devices.
 

src/content/docs/email-security/deployment/api/index.mdx

@@ -10,11 +10,9 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 <Render file="deployment/setup-api-overview" product="email-security" />
 

src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx

@@ -12,12 +12,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 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 <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> attacks. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Microsoft Exchange with Email Security.](~/assets/images/email-security/deployment/api-setup/exchange/bcc-exchange-flow.png)

src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx

@@ -7,10 +7,8 @@ sidebar:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
 
 <Render file="rename-area1-to-ces" product="email-security" />
-:::
 
 To set up Email Security (formerly Area 1) for Gmail:
 

src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/index.mdx

@@ -11,12 +11,8 @@ head:
 
 import { Render, Details } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Gmail, setting up Email Security via BCC is quick and easy. All you need to do is create a content compliance filter to send emails to Email Security through BCC. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Gmail with Email Security.](~/assets/images/email-security/deployment/api-setup/gmail/gmail-bcc-flow.png)

src/content/docs/email-security/deployment/api/setup/index.mdx

@@ -10,12 +10,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 When you first get started with Email Security (formerly Area 1), you will need to set up a way to connect your current mail environment with Email Security.
 
 ## BCC setup

src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx

@@ -9,12 +9,8 @@ description: Learn how to scan and protect Office 365 emails with Email Security
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Microsoft Office 365, setting up Email Security via Microsoft Graph API is quick and easy. The following email flow shows how this works:
 
 ![Email flow when setting up Email Security with the Microsoft Graph API](~/assets/images/email-security/deployment/api-setup/ms-graph/ms-graph.png)

src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx

@@ -12,12 +12,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Microsoft Office 365, setting up Email Security via journaling is quick and easy. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Office 365 with Email Security.](~/assets/images/email-security/deployment/api-setup/journaling/office365-journaling-flow.png)

src/content/docs/email-security/deployment/index.mdx

@@ -7,6 +7,8 @@ sidebar:
 
 import { DirectoryListing, Render } from "~/components";
 
+<Render file="contact-support" product="email-security" />
+
 <Render file="deployment/setup-overview" product="email-security" />
 
 Select a deployment method to get started.

src/content/docs/email-security/deployment/inline/index.mdx

@@ -10,11 +10,9 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 <Render file="deployment/setup-inline-overview" product="email-security" />
 

src/content/docs/email-security/deployment/inline/setup/cisco-area1-mx.mdx

@@ -13,12 +13,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-area1-mx/cisco-area1-mx.png)
 
 In this tutorial, you will learn how to configure Cisco IronPort with Email Security as MX record. This tutorial is broken down into several steps.

src/content/docs/email-security/deployment/inline/setup/cisco-cisco-mx.mdx

@@ -13,12 +13,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-cisco-mx/cisco-mx.png)
 
 In this tutorial, you will learn how to configure Email Security with Cisco as MX record. This tutorial is broken down into several steps.

src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx

@@ -12,12 +12,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/gsuite-area1-mx/gsuite-area1-mx.png)
 
 In this tutorial, you will learn how to configure Google Workspace with Email Security as MX record. This tutorial is broken down into several steps.

src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx

@@ -13,12 +13,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/o365-area1-mx/office365-mx.png)
 
 In this tutorial, you will learn how to configure Microsoft Office 365 with Email Security as its MX record. This tutorial is broken down into several steps. If at any steps during this tutorial you receive a message saying that you need to run the `Enable-OrganizationCustomization` cmdlet, [refer to section 6](#6-execute-enable-organizationcustomization-if-required).

src/content/docs/email-security/email-configuration/email-policies/index.mdx

@@ -6,7 +6,9 @@ sidebar:
 
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components"
+
+<Render file="contact-support" product="email-security" />
 
 When you use an [inline setup](/email-security/deployment/inline/), you can modify incoming, non-blocked messages with a few added layers of protection:
 

src/content/docs/email-security/email-configuration/index.mdx

@@ -7,11 +7,9 @@ sidebar:
 
 import { DirectoryListing, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
+<Render file="contact-support" product="email-security" />
 
 Once you have [set up Email Security](/email-security/deployment/), you have several options to customize and fine-tune email behavior.
 

src/content/docs/email-security/email-configuration/phish-submissions/index.mdx

@@ -6,7 +6,9 @@ sidebar:
 
 ---
 
-import { DirectoryListing, GlossaryTooltip } from "~/components"
+import { DirectoryListing, GlossaryTooltip, Render } from "~/components"
+
+<Render file="contact-support" product="email-security" />
 
 As part of your continuous email security posture, administrators and security analysts need to submit missed <GlossaryTooltip term="phishing">phish</GlossaryTooltip> samples to [Email Security (formerly Area 1) Service Addresses](https://horizon.area1security.com/support/service-addresses/) so Cloudflare can process them and take necessary action.
 

src/content/docs/email-security/index.mdx

@@ -24,12 +24,14 @@ Stop <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> attacks with Em
 
 <Plan id="email.email_security.properties.availability.summary" />
 
-:::caution[Area 1 has been renamed]
+:::note[Area 1 has been renamed]
 
 Area 1 is now **Email Security (formerly Area 1)**. Customers who purchased the new Email Security can access the documentation by going to Cloudflare Zero Trust > [Email Security](/cloudflare-one/email-security/).
 
 :::
 
+<Render file="contact-support" product="email-security" />
+
 <Render file="email-security-description" product="email-security" />
 
 ---

src/content/docs/email-security/migrate-to-email-security.mdx

@@ -5,12 +5,37 @@ sidebar:
   order: 9
 ---
 
+import { Render } from "~/components";
+
 This page aims at showing you how to perform Area 1 actions in [Zero Trust Email Security](/cloudflare-one/email-security/), and new terminology introduced in Email Security.
 
 :::note
 Your Area 1 data and configuration settings are available in Email Security.
 :::
 
+<Render file="contact-support" product="email-security" />
+
+## Contact support
+
+:::note
+Starting from October 1, 2025, access and support for Email Security will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to [email protected].
+:::
+
+In Area 1, you can reach out to support via the following email addresses:
+
+- [email protected]
+- [email protected] (for PhishGuard customers only)
+
+In Email Security, you can:
+
+- Go to the [Cloudflare Help Center](https://www.support.cloudflare.com/s/?language=en_US)
+- [Contact Cloudflare Support](/support/contacting-cloudflare-support/)
+- [Raise a ticket](/support/contacting-cloudflare-support/#getting-help-with-an-issue) and enter the correct answer to the following questions:
+  - What type of question do you have? **Technical - Other Products**
+  - In what area can we help you? **Email Security**
+
+Alternatively, if you are a PhishGuard customer, you can [contact support](https://dash.cloudflare.com/?to=/:account/support) in the Cloudflare dashboard.
+
 ## Invite users
 
 In Area 1, you [invite users](/email-security/account-setup/manage-account-members/#add-user) by logging in to the Area 1 portal and inviting members.
@@ -34,7 +59,7 @@ Once you have added new account members, you will have to assign each member an
 ## Create webhooks
 
 :::note
-Starting from October 2025, Area 1 webhooks will be visible in Zero Trust Email Security, but non-configurable. Use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs) to create new webhooks or configure webhooks.
+Starting from October 1, 2025, Area 1 webhooks will be visible in Zero Trust Email Security, but non-configurable. Use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs) to create new webhooks or configure webhooks.
 :::
 
 In Area 1, you can [create alert webhooks](/email-security/email-configuration/domains-and-routing/alert-webhooks/#create-an-alert-webhook).
@@ -62,7 +87,7 @@ You can also check the status of APIs through the [Cloudflare Status API](https:
 ## Email reports
 
 :::note
-Starting from October 2025, weekly and daily email reports will no longer be available. Go to [Monitoring](/cloudflare-one/email-security/email-monitoring/) in Email Security to monitor your inbox.
+Starting from October 1, 2025, weekly and daily email reports will no longer be available. Go to [Monitoring](/cloudflare-one/email-security/email-monitoring/) in Email Security to monitor your inbox.
 :::
 
 In Area 1, you receive daily or weekly updates of the number of emails dispositioned.
@@ -72,35 +97,13 @@ In Email Security, you can view [email monitoring](/cloudflare-one/email-securit
 ## Email alerts for detections
 
 :::note
-Starting from October 2025, emails alerts for detections will no longer be available. As an alternative, use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs). 
+Starting from October 1, 2025, emails alerts for detections will no longer be available. As an alternative, use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs). 
 :::
 
 In Area 1, you receive an email when an email is assigned a disposition.
 
 In Email Security, you enable [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs) to enable detection logs.
 
-## Contact support
-
-:::note
-Starting from October 2025, we will no longer receive support requests via email to any `@area1security.com` address. We will transition to receiving support requests from the Cloudflare dashboard.
-:::
-
-In Area 1, you can reach out to support via the following email addresses:
-
-- [email protected]
-- [email protected] (for PhishGuard customers only)
-
-In Email Security, you can:
-
-- Go to the [Cloudflare Help Center](https://www.support.cloudflare.com/s/?language=en_US)
-- [Contact Cloudflare Support](/support/contacting-cloudflare-support/)
-- [Raise a ticket](/support/contacting-cloudflare-support/#getting-help-with-an-issue) and enter the correct answer to the following questions:
-  - What type of question do you have? **Technical - Other Products**
-  - In what area can we help you? **Email Security**
-- Email [email protected] (for PhishGuard customers only).
-
-If you are PhishGuard customer, you will be informed when you can start raising PhishGuard tickets in the Cloudflare dashboard. 
-
 ## Search emails
 
 In Area 1, you can perform two types of search: [Fielded Search](/email-security/reporting/search/#fielded-search) and [Freeform Search](/email-security/reporting/search/#freeform-search).