Walkthrough: Configure Azure (SAS) for integration with Customer Engagement apps
This walkthrough guides you through configuring the Azure Service Bus issuer, scope, and rules to allow a listener application to read the Dynamics 365 for Customer Engagement Customer Engagement messages posted to the Azure Service Bus.
This walkthrough applies to any Dynamics 365 for Customer Engagement deployment when using SAS authorization for Customer Engagement-Azure messaging. For more information aboutAzure Service Bus authorization see Service Bus authentication and authorization.
You must use the Plug-in Registration Tool. To download the plug-in registration tool, see Download tools from NuGet.
An Azure account with a license to create Service Bus entities.
A SAS configured service bus namespace.
A SAS configured service bus messaging entity: queue, topic, relay, or event hub.
The messaging entity must have the
Sendpolicy permission at a minimum. For a two-way relay, the policy must also have the
The authorization connection string of your messaging entity.
Refer to the Create a Service Bus namespace using the Azure portal for instructions on how to create a Service Bus namespace and messaging entity.
Create a service endpoint
A ServiceEndpoint Entity contains configuration data that is required for external messaging with a Azure Service Bus solution endpoint. By using the Plug-in Registration Tool, you can easily create a service endpoint entity in a Customer Engagement organization and configure the service bus endpoint issuer, scope, and rules.
Register a Service Endpoint
Run the Plug-in Registration Tool and log into your target Customer Engagement organization.
Select Register > Register New Service Endpoint.
Check Let's Start with the connection string from the Azure Service Bus Portal and paste the connection string of your service bus messaging entity.
Fill out the Service Endpoint Registration form by entering the Designation Type, Message Format, and optionally the User Information Sent and Description fields
For more information about the message format, see Write a listener application for a Azure solution.
After a few seconds or so, you will see the new service endpoint in the Registered Plug-ins & Custom Workflow Activities list.