[Area 1] Add warning on how to receive support from October (#24740)

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

* Add warning to integration guide

* add contact support phishguard customers

* Apply suggestions from code review

Co-authored-by: Pedro Sousa <[email protected]>

* Removing redundant caution warning

* Removing redundant caution note

* Delete email

---------

Co-authored-by: Pedro Sousa <[email protected]>

Author: 2 people

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: