Shield Connectors

Description

Shield connectors reside in the Microsoft 365 tenant of the Shield organization. Automatically deployed connectors include Bracket connectors whether an organization is using Bracket (yet) or not. This allows for Bracket to be enabled per user without any additional manual configuration required.

 

Corresponding transport rules are detailed here.

 

Shield - Receive from Courier

Shield - Receive from Courier -- Connector.png

Status

On

 

Mail flow scenario

From: Partner organization

To: Office 365

 

Authenticating sent email

How do you want Office 365 to identify your partner organization?

Identify the partner organization by verifying that messages are coming from these IP

address ranges:

3.129.146.181

3.128.208.182

13.58.249.20

3.135.43.190

3.21.178.168

3.13.18.50

18.189.152.83

3.133.222.181

 

Security Restrictions

What security restrictions do you want to apply?

Reject messages if they aren't encrypted using Transport Layer Security (TLS), or the subject name on the certificate that the partner uses to authenticate with Office 365 doesn't match this domain name: *.shield.security


Shield - Send to Outpost

Shield - Send to Outpost -- Connector.png

Status

On

 

Mail flow scenario

From: Office 365

To: Partner organization

 

Use of connector

Use only when I have a transport rule set up that redirects messages to this connector.

 

Routing

Route email messages through these smart hosts:

domain-tld.out.shield.security

 

Security restrictions

Always use Transport Layer Security (TLS) and connect only if the recipient's email server has a digital certificate.

 


Shield - Send to Frontline

Shield - Send to Frontline -- Connector.png

Status

On

 

Mail flow scenario

From: Office 365

To: Partner organization

 

Use of connector

Only when I have a transport rule set up that redirects messages to this connector

 

Routing

Route email messages through these smarthosts:

domain-tld.in.shield.security

 

Security restrictions

Always use Transport Layer Security (TLS) and connect only if the recipient's email server certificate has a digital certificate.

 


Bracket Connector

Bracket Connector - Connector.png

Status

On

 

Mail flow scenario

From: Office 365

To: Partner organization

 

Use of connector

Use only when I have a transport rule set up that redirects messages to this connector.

 

Routing

Route email through these smarthosts: Encrypt.bracket.email

 

Security restrictions

Always use Transport Layer Security (TLS) and connect only if the recipient's email server certificate is issued by a trusted certificate authority (CA).


Getting Help

If you need assistance, please contact the Partner Success team.

 

Related to

Updated

Was this article helpful?

0 out of 0 found this helpful