Walkthrough: Register an Azure-aware plug-in using the Plug-in Registration Tool
This walkthrough demonstrates how to register a service endpoint step using the Plug-in Registration Tool. Once configured, Dynamics 365 for Customer Engagement Customer Engagement can post the execution context of the current operation to a Azure solution endpoint. For this walkthrough, the step is registered to post the execution context of the CreateRequest message for an
Account entity to the Azure Service Bus.
The following prerequisites must be completed before you start this walkthrough:
Access to the Plug-in Registration Tool. To get the Plug-in Registration Tool, see Download tools from NuGet.
Your Dynamics 365 for Customer Engagement system user account must have the System Customizer or System Administrator role. For more information, see How Role-Based Security Can Be Used to Control Access to Entities In Dynamics 365 for Customer Engagement.
Have access to a Azure platform service namespace that is configured for SAS authorization, to which Dynamics 365 for Customer Engagement will post a message.
If you plan to use any other Azure messaging entity other than a queue, for example a relay, there must be a listener application actively listening to the specified solution endpoint for Dynamics 365 for Customer Engagement to successfully post to the Azure Service Bus. For more information, see Write a Listener for an Azure Solution.
A configured service endpoint with SAS authorization is available in the target organization. More information: Walkthrough: Configure Microsoft Azure (SAS) for integration with Dynamics 365 for Customer Engagement.
This walkthrough contains the following steps:
Connect to the Dynamics 365 for Customer Engagement server
Follow the steps below to connect to the Dynamics 365 for Customer Engagement server using the Plug-in Registration tool.
Run the Plug-in Registration tool.
Click Create New Connection.
In the Login dialog box, select the deployment type radio button corresponding to the Dynamics 365 for Customer Engagement server you intend to register a service endpoint with. The On-premises radio button includes an IFD deployment and the Office 365 button is for the Microsoft Online Services provider of Dynamics 365 for Customer Engagement.
Login form for an online deployment
Login form for an on-premises deployment
If you check Display list of available organizations, you are presented with a list of organizations that you belong to after you click Login. This enables you to choose the organization that you want to register the service endpoint with. Otherwise, your default organization is used.
Enter the indicated information about the server and login account, and then click Login.
Register a service endpoint step for an event
Follow the steps below to register a step for an event on the service endpoint.
Select an existing service endpoint in the tab of the tab of the target organization.
Navigate to the Register menu and click Register New Step.
Fill out the Register New Step dialog box for an account create event as shown in the following figure.
Click Register New Step.
Dynamics 365 for Customer Engagement will now post the current message containing the execution context to the service bus whenever an account is created. The post is performed asynchronously and is not executed immediately.
Test the endpoint registration
After you register the endpoint you can test it. A listener must be running or a queue available on the target endpoint for the service bus post from the plug-in to happen.
Open the Dynamics 365 for Customer Engagement web application for the same organization that you registered the service endpoint under.
Click the Create button , and then click Account.
Enter an account name, for example
Adventure Works Cycle, into the Account Name field, and then click Save.
Wait about 10 minutes for the Azure Service Bus post to occur.
Click Settings > System Jobs.
Open the system job that has the same name that you specified for your service endpoint. Check the status to see if the post was successful, is waiting, or failed.
You can now unregister the endpoint, if so desired, by selecting it in the tool’s tree view and click Unregister.