Enterprise DLP
Create Microsoft Exchange Connectors
Table of Contents
Expand All
|
Collapse All
Enterprise DLP Docs
-
- About Enterprise DLP
- What’s Supported with Enterprise DLP?
- Data Patterns, Document Types, and Data Profiles
- Enable Role Based Access
- Edit the Cloud Content Settings
- Edit the Enterprise DLP Data Filtering Settings
- Edit the Enterprise DLP Snippet Settings
- Configure Syslog Forwarding for Enterprise DLP Incidents
- Request a New Feature
-
-
- Enable Existing Data Patterns and Filtering Profiles
- Modify a DLP Rule on Strata Cloud Manager
- Create a SaaS Security Policy Recommendation to Leverage Enterprise DLP
- Reduce False Positive Detections
- Data Dictionaries
- Recommendations for Security Policy Rules
- Enterprise DLP Migrator
-
-
-
- Driver License - Australia
- Driver License - Austria
- Driver License - Belgium
- Driver License - Brazil
- Driver License - Bulgaria
- Driver License - Canada
- Driver License - China
- Driver License - Croatia
- Driver License - Cyprus
- Driver License - Czech Republic
- Driver License - Denmark
- Driver License - Estonia
- Driver License - Finland
- Driver License - France
- Driver License - Germany
- Driver License - Greece
- Driver License - Hungary
- Driver License - Iceland
- Driver License - Ireland
- Driver License - Italy
- Driver License - Japan
- Driver License - Latvia
- Driver License - Liechtenstein
- Driver License - Lithuania
- Driver License - Luxembourg
- Driver License - Malta
- Driver License - Netherlands
- Driver License - New Zealand
- Driver License - Norway
- Driver License - Poland
- Driver License - Portugal
- Driver License - Romania
- Driver License - Slovakia
- Driver License - Slovenia
- Driver License - South Africa
- Driver License - South Korea
- Driver License - Spain
- Driver License - Sweden
- Driver License - Switzerland
- Driver License - Taiwan
- Driver License - Turkey
- Driver License - UK
- Driver License - US
- Driver License - US - AK
- Driver License - US - AL
- Driver License - US - AR
- Driver License - US - AZ
- Driver License - US - CA
- Driver License - US - CO
- Driver License - US - CT
- Driver License - US - DC
- Driver License - US - DE
- Driver License - US - FL
- Driver License - US - GA
- Driver License - US - HI
- Driver License - US - IA
- Driver License - US - ID
- Driver License - US - IL
- Driver License - US - IN
- Driver License - US - KS
- Driver License - US - KY
- Driver License - US - LA
- Driver License - US - MA
- Driver License - US - ME
- Driver License - US - MI
- Driver License - US - MN
- Driver License - US - MO
- Driver License - US - MS
- Driver License - US - MT
- Driver License - US - NC
- Driver License - US - ND
- Driver License - US - NE
- Driver License - US - NH
- Driver License - US - NM
- Driver License - US - NV
- Driver License - US - NY
- Driver License - US - OH
- Driver License - US - OK
- Driver License - US - OR
- Driver License - US - PA
- Driver License - US - RI
- Driver License - US - SC
- Driver License - US - SD
- Driver License - US - TN
- Driver License - US - TX
- Driver License - US - UT
- Driver License - US - VA
- Driver License - US - VT
- Driver License - US - WA
- Driver License - US - WI
- Driver License - US - WV
- Driver License - US - WY
- National ID - Albania
- National Id - Argentina ID
- National ID - Australia
- National Id - Austria - Central Register of Residents
- National Id - Austria Social Security Card - e-card
- National ID - Bahrain
- National Id - Belgium - Citizen Service Number - BSN
- National Id - Belgium - National Registration Number
- National ID - Bosnia and Herzegovina
- National ID - Brazil
- National Id - Brazil - CNPJ
- National Id - Brazil - CPF
- National Id - Bulgaria - Uniform Civil Number
- National Id - Canada - Social Insurance Number - SIN
- National ID - Chile
- National Id - China ID
- National Id - Colombia National ID
- National ID - Costa Rica
- National Id - Croatia - Personal Identification Number
- National ID - Cuba
- National Id - Cyprus - Identity Card
- National Id - Czech - Birth Number
- National Id - Czech - National eID Card
- National Id - Denmark - CPR Number
- National ID - Dominican Republic
- National ID - Ecuador
- National ID - Egypt
- National Id - Estonia - Personal Identification Code
- National Id - Finland - Personal Identity Code - HETU
- National Id - France - INSEE
- National Id - France - Social Security Number - NIR
- National Id - Germany
- National Id - Greece
- National Id - Hong Kong ID
- National Id - Hungary - Personal Identification Number
- National Id - Iceland
- National ID - India
- National ID - Indonesia
- National ID - Iran
- National Id - Ireland - Personal Public Service Number - PPSN
- National ID - Israel
- National Id - Italy - Fiscal Code Card - Codice Fiscale
- National Id - Japan Corporate Number
- National Id - Japan My Number
- National ID - Kazakhstan
- National ID - Kuwait
- National Id - Latvia - Personal Public Service Number - PPSN
- National Id - Liechtenstein
- National Id - Lithuania
- National Id - Luxembourg
- National Id - Malaysia National ID
- National Id - Malta
- National ID - Mexico
- National ID - Moldova
- National ID - Montenegro
- National Id - Netherlands - Citizen Service Number - BSN
- National ID - North Macedonia
- National Id - Norway - Identification Number - Fødselsnummer
- National ID - Pakistan
- National ID - Paraguay
- National ID - Peru
- National ID - Philippines
- National Id - Poland
- National Id - Portugal
- National Id - Romania - Identity Card - CNP
- National ID - Russia
- National ID - Serbia
- National Id - Singapore NRIC
- National Id - Slovakia
- National Id - Slovenia
- National ID - South Africa
- National ID - South Korea
- National Id - Spain - National Identity Document - Documento Nacional de Identidad
- National ID - Sri Lanka
- National Id - Sweden - Personal Identity Number
- National ID - Switzerland
- National Id - Taiwan ID
- National Id - Thailand ID
- National Id - Turkey Identification Number
- National Id - UAE Emirates ID
- National Id - UK National Insurance Number - NINO
- National ID - Uruguay
- National Id - US Social Security Number - SSN
- National ID - Venezuela
- Passport - Australia
- Passport - Austria
- Passport - Belgium
- Passport - Brazil
- Passport - Bulgaria
- Passport - Canada
- Passport - Croatia
- Passport - Cyprus
- Passport - Czech Republic
- Passport - Denmark
- Passport - Estonia
- Passport - Finland
- Passport - France
- Passport - Germany
- Passport - Greece
- Passport - Hungary
- Passport - Iceland
- Passport - Ireland
- Passport - Italy
- Passport - Latvia
- Passport - Liechtenstein
- Passport - Lithuania
- Passport - Luxembourg
- Passport - Malta
- Passport - Netherlands
- Passport - New Zealand
- Passport - Norway
- Passport Number - China
- Passport Number - Singapore
- Passport Number - South Africa
- Passport number - South Korea
- Passport number - Taiwan
- Passport - Poland
- Passport - Portugal
- Passport - Romania
- Passport - Slovakia
- Passport - Slovenia
- Passport - Spain
- Passport - Sweden
- Passport - Switzerland
- Passport - Turkey
- Passport - UK
- Passport - US
- Tax Id - Australia
- Tax Id - Austria
- Tax Id - Belgium
- Tax Id - Brazil
- Tax Id - Bulgaria
- Tax ID - Canada
- Tax ID - China
- Tax ID - Costa Rica
- Tax Id - Cyprus
- Tax Id - Czech Republic
- Tax Id - Denmark
- Tax ID - Dominican Republic
- Tax Id - Estonia
- Tax Id - Finland
- Tax Id - France
- Tax Id - Germany
- Tax Id - Greece
- Tax Id - Hungary
- Tax Id - Iceland
- Tax Id - India - PAN
- Tax Id - Ireland
- Tax Id - Italy
- Tax ID - Japan
- Tax Id - Latvia
- Tax Id - Liechtenstein
- Tax Id - Lithuania
- Tax Id - Luxembourg
- Tax Id - Malta
- Tax Id - Netherlands
- Tax Id - New Zealand
- Tax Id - Norway
- Tax Id - Poland
- Tax Id - Portugal
- Tax Id - Romania
- Tax Id - Slovakia
- Tax Id - Slovenia
- Tax ID - South Africa
- Tax ID - South Korea
- Tax Id - Spain
- Tax Id - Sweden
- Tax Id - Switzerland
- Tax ID - Taiwan
- Tax Id - Turkey
- Tax Id - UK - UTR
- Tax Id - US - TIN
-
-
-
-
- March 2025
- February 2025
- January 2025
- December 2024
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- April 2024
- March 2024
- January 2024
- December 2023
- November 2023
- October 2023
- August 2023
- July 2023
- June 2023
- May 2023
- March 2023
- February 2023
- January 2023
- November 2022
- October 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- July 2021
- New Features in Enterprise DLP Plugin 5.0
- New Features in Enterprise DLP Plugin 4.0
- New Features in Enterprise DLP Plugin 3.0
- New Features in Enterprise DLP Plugin 1.0
-
- Known Issues in the Enterprise DLP Cloud Service
- Known Issues in Endpoint DLP
-
- Known Issues in Enterprise DLP Plugin 5.0.6
- Known Issues in Enterprise DLP Plugin 5.0.5
- Known Issues in Enterprise DLP Plugin 5.0.4
- Known Issues in Enterprise DLP Plugin 5.0.3
- Known Issues in Enterprise DLP Plugin 5.0.2
- Known Issues in Enterprise DLP Plugin 5.0.1
- Known Issues in Enterprise DLP Plugin 5.0.0
-
- Known Issues in Enterprise DLP Plugin 3.0.10
- Known Issues in Enterprise DLP Plugin 3.0.9
- Known Issues in Enterprise DLP Plugin 3.0.8
- Known Issues in Enterprise DLP Plugin 3.0.7
- Known Issues in Enterprise DLP Plugin 3.0.6
- Known Issues in Enterprise DLP Plugin 3.0.5
- Known Issues in Enterprise DLP Plugin 3.0.4
- Known Issues in Enterprise DLP Plugin 3.0.3
- Known Issues in Enterprise DLP Plugin 3.0.2
- Known Issues in Enterprise DLP Plugin 3.0.1
- Known Issues in Enterprise DLP Plugin 3.0.0
-
- Known Issues in Enterprise DLP Plugin 1.0.8
- Known Issues in Enterprise DLP Plugin 1.0.7
- Known Issues in Enterprise DLP Plugin 1.0.6
- Known Issues in Enterprise DLP Plugin 1.0.5
- Known Issues in Enterprise DLP Plugin 1.0.4
- Known Issues in Enterprise DLP Plugin 1.0.3
- Known Issues in Enterprise DLP Plugin 1.0.2
- Known Issues in Enterprise DLP Plugin 1.0.1
- Enterprise DLP Limitations
- Changes to Default Behavior
-
Create Microsoft Exchange Connectors
Create an outbound and inbound Microsoft Exchange Online Connector to forward and
return outbound emails sent from Microsoft Exchange to and from Enterprise Data Loss Prevention (E-DLP) for
inline inspection of emails.
On May 7, 2025, Palo Alto Networks is introducing new Evidence Storage and Syslog Forwarding service IP
addresses to improve performance and expand availability for these services
globally.
You must allow these new service IP addresses on your network
to avoid disruptions for these services. Review the Enterprise DLP
Release Notes for more
information.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
To prevents sensitive data exfiltration contained in outbound emails using Enterprise Data Loss Prevention (E-DLP), you must create outbound and inbound Microsoft Exchange
Online connector to control the flow of emails forwarded from Microsoft Exchange
Online to Enterprise DLP. The outbound connector controls the flow of outbound
emails from Microsoft Exchange to Enterprise DLP for inspection and verdict
rendering. The inbound connector to return emails forwarded to Enterprise DLP
back to Microsoft Exchange and instruct Microsoft Exchange to take action based on
the transport rule.
Create a Microsoft Exchange Outbound Connector
Create an outbound Microsoft Exchange Online Connector to connect Microsoft Exchange
with Enterprise Data Loss Prevention (E-DLP) for inline inspection of emails.
- Select Mail flowConnectors and Add a connector to launch the Microsoft Exchange Connector wizard.
- Specify the connector source and destination.
- For Connection from, select Office 365.
- For Connection to, select Partner organization.A partner can be any third-party cloud service that provides services such as services, such as data protection. In this case, the third-party partner organization is Palo Alto Networks.
- Click Next.
- Name the Microsoft Exchange connector.
- Enter a descriptive Name for the connector.
- (Optional) Enter a Description for the connector.
- (Best Practices) For What do you want to do after connector is saved?, check (enable) Turn it on.Enable this to automatically turn on the connector after you have finished creating and saved the new Microsoft Exchange connector.
- Click Next.
- To specify when the connector should be used, select Only when I have a transport rule set up that redirects messages to this connector and click Next.Using the connector only when a transport rule exists enables fine-grained control of what action to take when an email contains sensitive data. By selecting this option, Microsoft Exchange enforces action on emails based on the action specified in the Enterprise DLP data profile.
- To configure the route settings for emails, check (enable) Route email through these smart hosts to add the following smart host Fully Qualified Domain Name (FQDN) and click Next.The FQDN specifies the region where emails are forwarded to Enterprise DLP for inspection and verdict rendering. This also generates and displays Email DLP incidents in the specified region. All processes and data related to Email DLP occur and are stored in this region.
- APACmail.asia-southeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Australiamail.australia-southeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Europemail.europe-west3.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Indiamail.asia-south1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Japanmail.asia-northeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- United Kingdommail.europe-west2.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- United Statesmail.us-west1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
Expand allCollapse all - Specify the security restrictions for the connector.
- Check (enable) Always use Transport Layer Security (TLS) to secure the connection.Enterprise DLP requires this setting to successfully forward emails for inspection. Enterprise DLP rejects the connect connection if you disable this setting.
- Select Issued by a trusted certificate authority (CA).
- Check (enable) Add the subject name or subject alternative (SAM) matches to this domain: and add the following domain name.Enterprise DLP requires you add the subject name for positive identification of the Enterprise DLP cloud service. The CA issuer FQDN you add must match the email routing FQDN you added in the previous step.
- APACmail.asia-southeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Australiamail.australia-southeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Europemail.europe-west3.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Indiamail.asia-south1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- Japanmail.asia-northeast1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- United Kingdommail.europe-west2.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
- United Statesmail.us-west1.email.dlp.paloaltonetworks.comCode copied to clipboardUnable to copy due to lack of browser support.
Expand allCollapse all - Click Next.
- Add a validation email.A valid email address associated with the email domain used by your organization. This is required to validate connectivity between the Microsoft Exchange Admin Center and the Palo Alto Networks smart host, and that emails can be successfully delivered.
- Add a valid email address for validation.
- Validate.The Microsoft Exchange validation tests take a few minutes to complete.
- Under the Task, verify that the Check connectivity validation test status to the Enterprise DLP FQDN displays Succeed.It's expected that the following errors occur when adding the validation email.
- Validation failed error is displayed.
- The Send test email validation test status displays Failed.
- Click Done.
- When prompted to confirm whether to proceed without successful validation, click Yes, proceed.
- Review the connector details and Create Connector.Click Done when prompted that the outbound connector was successfully created.
- Back in the Connectors page, verify the outbound connector is displayed and that the Status is On.
- Create the Microsoft Exchange inbound connector if not already created.Enterprise DLP requires the inbound connector to return emails forwarded to Enterprise DLP for inspection back to Microsoft Exchange.Skip this step if you have already created the inbound connector.
- Create Microsoft Exchange Transport Rules.After you successfully created the Microsoft Exchange connectors, you must create Microsoft Exchange transports rule to forward emails to and from Enterprise DLP, and to specify what actions Microsoft Exchange takes based on the Enterprise DLP verdicts.
Create a Microsoft Exchange Inbound Connector
Create an inbound Microsoft Exchange Online Connector to return emails forwarded to
Enterprise Data Loss Prevention (E-DLP) for inline inspection back to Microsoft Exchange.
- Select Mail flowConnectors and Add a connector to launch the Microsoft Exchange Connector wizard.
- Specify the connector source and destination.
- For Connection from, select Your organization's email server.
- Click Next.
- Name the Microsoft Exchange connector.
- Enter a descriptive Name for the connector.
- (Optional) Enter a Description for the connector.
- (Best Practices) For What do you want to do after connector is saved?, check (enable) Turn it on.Enable this to automatically turn on the connector after you have finished creating and saved the new Microsoft Exchange connector.
- Click Next.
- Specify the authentication IP addresses that Microsoft Exchange uses to verify Enterprise DLP.Enterprise DLP requires the authentication IP addresses to forward emails back to Microsoft Exchange.
- Select By verifying that the IP address of the sending server matches one of the following IP address, which belong to your partner organization.
- Add the following to IP addresses.Add the IP addresses for the region where you host your email domain. You can add multiple regional IP addresses if you have email domains hosted in multiple regions.
- APAC35.186.151.226 and 34.87.43.120
- Australia35.197.179.113 and 35.244.122.65
- Europe34.141.90.172 and 34.107.47.119
- India34.93.185.212 and 35.200.159.173
- Japan34.84.8.170 and 35.221.111.27
- United Kingdom34.105.128.121 and 34.89.40.221
- United States34.168.197.200 and 34.83.143.116
Expand allCollapse all
- Review the connector details and Create Connector.Click Done when prompted that you successfully created the inbound connector.
- Back in the Connectors page, verify the inbound connector is displayed and that the Status displays On.
- Create the Microsoft Exchange outbound connector if not already created.Enterprise DLP requires the outbound connector to control the flow of emails forwarded from Microsoft Exchange Online to Enterprise DLP for inline inspection.Skip this step if you have already created the outbound connector.
- Create Microsoft Exchange Transport Rules.After you successfully created the Microsoft Exchange connectors, you must create Microsoft Exchange transports rule to forward emails to Enterprise DLP, and to specify what actions Microsoft Exchange takes based on the Enterprise DLP verdicts.
Create a Microsoft Exchange Proofpoint Server Connector
Create a Microsoft Exchange connector for your Proofpoint server to forward emails
for encryption after Enterprise Data Loss Prevention (E-DLP) inspection and verdict rendering.
- Prepare your Proofpoint server to encrypt emails inspected by Enterprise DLP.
- Enable DKIM signing for your Proofpoint server.When enabling DKIM signing, you must also select Enabled for the domain.Additionally, keep a record of your DKIM public key. This is required when updating your domain host records.
- Contact your email domain provider to update your SPF record.
- Add your Proofpoint IP address to your SPF record.Enterprise DLP requires this to forward emails to Proofpoint for encryption. Skip this step if you have already updated your SPF record with your Proofpoint IP address.
- Add the DKIM public key to your domain host records.
- Select Mail flowConnectors and Add a connector to launch the Microsoft Exchange connector wizard.
- Specify the connector source and destination.
- For Connection from, select Office 365.
- For Connection to, select Partner organization.A partner can be any third-party cloud service that provides services such as services, such as data protection. In this case, the third-party partner organization is Palo Alto Networks.
- Click Next.
- Name the Microsoft Exchange connector.
- Enter a descriptive Name for the connector.
- (Optional) Enter a Description for the connector.
- (Best Practices) For What do you want to do after connector is saved?, check (enable) Turn it on.Enable this to automatically turn on the connector after you have finished creating and saved the new Microsoft Exchange connector.
- Click Next.
- To specify when the connector should be used, select Only when I have a transport rule set up that redirects messages to this connector and click Next.
- To configure the route settings for your Proofpoint server, check (enable) Route email through these smart hosts to add the Proofpoint server smart host Fully Qualified Domain Name (FQDN) and click Next.
- Specify the security restrictions for the connector.
- Check (enable) Always use Transport Layer Security (TLS) to secure the connection.Enterprise DLP requires this setting to successfully forward emails for inspection. Enterprise DLP rejects the connect connection if you disable this setting.
- Select Issued by a trusted certificate authority (CA).
- Click Next.
- Add a validation email.Enterprise DLP requires a valid email address associated with the email domain to validate connectivity between the Microsoft Exchange Admin Center and the Email DLP smart host, and to verify Enterprise DLP can successfully deliver any required notification emails.
- Add a valid email address for validation.
- Validate.The Microsoft Exchange validation tests take a few minutes to complete.
- Under the Task, verify that the Check connectivity validation test status to the Enterprise DLP FQDN displays Succeed.
- Click Done.
- When prompted to confirm whether to proceed without successful validation, click Yes, proceed.
- Review the connector details and Create Connector.Click Done when prompted that you successfully created the outbound connector.
- Back in the Connectors page, verify that you successfully created the outbound connector and that the Status displays On.
- Create the Microsoft Exchange outbound and inbound connectors if not already created.Enterprise DLP requires the outbound connector to control the flow of emails forwarded from Microsoft Exchange Online to Enterprise DLP for inline inspection and requires the inbound connector to return emails forwarded to Enterprise DLP for inspection back to Microsoft Exchange.Skip this step if you have already created the outbound and inbound connectors.
- Create Microsoft Exchange Transport Rules.After you successfully created the Microsoft Exchange connectors, you must create Microsoft Exchange transports rule to forward emails to and from Enterprise DLP, and to specify what actions Microsoft Exchange takes based on the Enterprise DLP verdicts.