Description
Shield connectors reside in the Microsoft 365 tenant of the Shield organization. All connectors are deployed during Step 3 of Shield onboarding except Bracket Connector. This connector is only created once Preferences are saved to Configure Bracket after an organization has been successfully onboarded.
Corresponding transport rules are detailed here.
For Shield organizations whose Microsoft 365 tenants do not yet contain these Shield Connectors, please submit a request for assistance.
Shield - Receive from Courier
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
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
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
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).
Related to
Updated