This document discusses integrating SharePoint and Dynamics CRM using the Azure Service Bus. It begins with an overview of out-of-the-box integration options and their limitations. Then it compares a point-to-point integration architecture to a service bus architecture, noting that the service bus approach is more loosely coupled, scalable, and upgrade-friendly. The bulk of the document provides an overview of the Azure Service Bus and demonstrations of creating a service bus namespace and connecting CRM to publish and subscribe to messages. It concludes by emphasizing that the Azure Service Bus provides an easy, flexible, and reliable integration option compared to native or point-to-point integration.

1. Advanced SharePoint
Integration with the Azure
Service Bus and Dynamics CRM
Aonghus Fraser / @gusfraser

2. Aonghus (Gus) Fraser
 Director, SharePoint Lead Consultant @ C5
 Gold Partner with ~160 consultants in the
Channel Islands (www.c5alliance.com)
 Approx 18 SharePoint Consultants
 Run www.cispug.org, SPSJE
 4th time presenting at SPEVO
 af@c5.je / @gusfraser

4. Jersey

5. Guernsey

7. Agenda
 Introductions
 Out Of The Box Options (SP / CRM)
 Point to Point vs Service Bus Architecture
 Azure Service Bus Overview
 Azure Service Bus Demonstrations
 Q&A

8. Out Of The Box
SharePoint / CRM
Integration

9. OOTB SharePoint CRM Integration
 Limited flexibility
 Folder per CRM Entity
 Security limitations

12. Point to Point
vs
Service Bus Architecture

13. Point to Point Integration
 E.g. CRM Plugin -> SharePoint Client Object
Model
 Tightly coupled
 Fails “ungracefully”
 Unsuitable for multiple systems (2+)
 Migration / upgrade pain
 Scalability

14. Point to Point Example
SharePoint
CRM SQL
LoB
LoB 2

16. Service Bus Example
SharePoint
CRM SQL
LoB
LoB 2

17. Service Bus Architecture
 Loosely coupled
 Scalable
 Less complexity / connections
 Easier to upgrade/migrate systems

18. Azure Service Bus
Overview

19. Azure Service Bus
 Lightweight Cloud Messaging Service
 Connect anything (on-prem or cloud)
 Cheap (£6.109/mo)
 First 12.5 million Ops/Month Included..
 Flexible
 .NET, Java, Node.js, PHP, Python, Ruby..

20. Azure Service Bus – Basic vs Standard

21. Azure Service Bus Queues
 One-to-one
Source: http://azure.microsoft.com/en-gb/documentation/articles/service-bus-dotnet-how-to-use-queues/

22. Azure Service Bus Topics
 One-to-many
 Publish/subscribe to relevant topics
Source: http://azure.microsoft.com/en-gb/documentation/articles/service-bus-dotnet-how-to-use-topics-subscriptions/

23. Azure Flexibility – SDKs
http://azure.microsoft.com/en-us/downloads/

24. AZURE SERVICE BUS NAMESPACE
AND TOPIC SETUP
Creating an Azure Service Bus Namespace and Topic

25. Creating a Namespace
 Azure Portal limited
 Use PowerShell for ACS integration:
 PS C:> New-AzureSBNamespace -
NAME SPEvo15-ns -Location
"West Europe" -
CreateACSNamespace $true

26. Creating a Topic

28. CONNECTING DYNAMICS CRM TO
THE SERVICE BUS

29. CRM 2015 Basics
 Plugin = Event Receiver (kind of..)
 Native (OOTB) Azure Service Bus Plugin
 Azure ACS to handle claims
 SDK Plugin Registration Tool to
configure/activate
 Beware of .NET Versions (4.5.2 not yet
supported fully in Azure)

35. Summary
 Native integration if Entity > Folder is
sufficient (security/flexibility limitations)
 Azure Service Bus is easy, flexible, scalable,
reliable
 Topics provide one-to-many sender to
receivers
 CRM 2015 SDKs and Azure SDKs provide
great examples

36. Useful Links
 Azure CRM Connectivity
https://msdn.microsoft.com/en-
us/library/gg309276.aspx
 Messaging With Topics
https://code.msdn.microsoft.com/windowsa
zure/Getting-Started-Brokered-614d42e5

37. Thank you for attending!
Aonghus Fraser
@gusfraser
af@c5.je