You’re offline. This is a read only version of the page.
1,010
I've done this: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/walkthrough-configure-azure-sas-integration and registered a create custom entity step against it. (the invisible out-of-the-box plugin)
Now, assuming I can write an Azure listener, it seems there needs to be more than just the program. All that information that I entered to register the Azure Service Bus endpoint needs to be known to the listener so that it knows where to listen. The CRM documentation falls short of walking one through to the end of deploying the listener.
Anyone's guidance would be greatly appreciated.
*This post is locked for comments
my Azure plumber decided there was some reason to go with a queue on the endpoint rather than the virtual path. Anyway, the queue seems to want to deliver a "Message" object instead of a RemoteExecutionContext. It allows us to caste the message to an REContext but, when we do so the subsequent Microsoft.Xrm.Tooling.Connector.CrmServiceClient breaks -- it fails to make a connection.
However, if we caste it to string, the Connector works but we don't have a Context object.
Can anyone flesh out the middleware in this arrangement?
I found this https://ansrikanth.com/2017/04/17/two-way-communication-between-crm-and-azure-service-bus/
ansrikanth fills in a bunch of details that only someone much smarter than I could get from the Microsoft documentation. I haven't had time to get to the next page but, he promises to answer the questions about activating the listener there...
Anyone?
In the listener project one downloads from github, the code has a main() method where a command-line, console app allows the investigator to type in the security pieces for the Service Bus Endpoint. No where does it describe how to configure a real listener to work WITHOUT this human intervention.
Anyone?
In fact one of those articles is the same one I posted. I’m looking for the article on how to publish, deploy and activate a listener on the other side of the Azure Bus Endpoint.
Hi mardukes,
This walkthrough explains how to register an Azure-aware Plugin using the Plugin Registration Tool.
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. This article explains how to write a listener application for a Azure solution.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (