Outbound Message Protection
The following figure shows the security features in BizTalk Server that you use to help protect outbound messages from being read by unauthorized parties.
Security features BizTalk Server uses to protect outbound messages.
When BizTalk Server sends a message, it takes the following steps to help ensure that it sends the message securely, and that the receiving party can determine the message sender:
If the send pipeline contains an encoding component (such as S/MIME) that is configured to sign all outbound messages, the signing certificate for the BizTalk group is retrieved from the personal certificate store for the host instance service account under which the pipeline is running, and the message is signed using the private key associated with the certificate.
If the send pipeline contains an encoding component (such as S/MIME) that is configured to encrypt all outbound messages, the encryption certificate thumbprint is used to retrieve the public key certificate from the Other People certificate store, and the message is encrypted using that certificate.
Important
Although you use one signing certificate for all the send pipelines in your BizTalk environment, you must ensure this signing certificate is available in the certificate store of the service account of each host instance of the hosts where the send pipelines are running.
For more information about how to send signed messages, see How to Configure BizTalk Server for Sending Signed Messages.
See Also
Inbound Message Authentication
Authentication of Messages Between Processes
Authenticating the Sender of a Message
Authorizing the Receiver of a Message
Certificates that BizTalk Server Uses for Signed Messages
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for