If you've configured Dynamics CRM 2015 Online with Azure Service Bus you will know that the "message" it puts on the queue is the plugin execution context. This is the same context that you use within a plugin. You will know that to do anything with the context you have to use the Microsoft.Xrm.Sdk and extract the Pre or Post Image and the so called Target image. "Target" is s stupid name I always think. It contains the delta - the attributes that were changed during the operation. The Post Image of say an Update event will contain all the attributes that have values in it and excludes any attributes with null values.
The reason for using the Azure Service Bus is usually to get data from CRM to your on-premise systems and more often than not you may be using an ESB to read messages from the Azure Service Bus. BizTalk for example has an adaptor that you just need to configure to read messages from Azure Service Bus. However any BizTalk developer is going to be very disappointed if you provide them with just a Plugin Execution Context because they will have to use the CRM SDK to convert it into an XML message. Even then the entity objects when serialized will result in a collection of KeyValuePairs. The biggest problem with that is trying to map it to a strongly typed schema particularly because the structure varies so much when attributes that are null are set to a value and vice versa. I've tried using the BizTalk mapper and failed.
UPDATE: CRM Online restricts plugins to Sandbox mode and you cannot serialize objects to XML because this is prohibited. I have recently stumbled on a way of getting round this. This may provide a much simpler solution then described in the rest of this article.
One solution is to have custom code that will read the context, convert it to a strongly typed schema and then put it back in another queue. This needs to be done serially to ensure that Ordered Delivery is maintained but at least it gets to a schema that is worthy of the name.
Now you have to be careful when using CRM Online because if your plugins consume a lot of CPU they will be terminated with extreme prejudice. It is best to keep the code within your plugin as minimal as possible and then have the bulk of your code execute on an Azure VM where you don't need to worry about CPU usage because you can size the VM to suit.
The best way to architect this is
a) Have a Plugin that sends the Plugin Execution Context to a Azure Service Bus Queue
b) Create an Azure Worker Process that reads messages from the Queue, creates an XML message and puts it into another Azure Service Bus Queue (be sure to maintain the order)
c) If using BizTalk create a Receive Port that will read XML messages from the second Queue
The Azure Worker Process is a lot like a Windows Service (in Azure its called a Cloud Service) and will automatically restart if it is stopped. When you deploy the Azure Worker Process it will create its own VM. You can supply configuration settings which in our case would include the EndPoint of the Queue we are reading from and the EndPoint of the Queue we are writing to.
While you messages should be placed on the first queue using a plugin running synchronously, the Azure Worker Process is running asynchronously. If you want to post messages back to CRM because of a failure then you need to setup another asynchronous process to send the messages back to CRM.