Imagine a world where Case automatically gets created even before a customer noticing something as broken. That is the potential of a marriage of IoT with CRM. This aims at showing a quick demo of integration and functional capabilities of Microsoft Azure, IOT and Dynamics 365

1. CRM & IOT
#ConnectedFieldService, #Azure, #CRM, #Dynamics365, #IOT, #IOTHub

2. Azure dashboard showing connection with Dynamics 365

3. Azure dashboard showing list of all resources added for this demo (includes IoT Hub and related resources)

4. Azure deployment status. It’ll take a while for entire deployment to happen.

5. Click on Open Simulator to open a thermostat simulator

6. Go back to Azure dashboard and see alerts being received in Activity Log from simulator

7. Next open Dynamics 365 instance.This adds another app (called IoT) in menu however from functional perspective, it should be part of Service of Field Service.

8. Create a Command record to send command to device (simulator in this case)

9. Add device (called Customer Asset) and relate to Command

10. Remember when Command record is saved, at the same time it tries to send command to device

11. Status of Command changes once command is sent

12. Command is a related record of Device too

13. You could change sensors data (Humidity andTemperature) in this case for devices to send failure notifications

14. Just a note: If device is not added or not activated, Dynamics 365 will throw a validation error

15. Device validation and registration happens within IoT Device record through a plug-in

16. Once device is activated, a valid Device ID (previously added in Dynamics 365) is shown in simulator too

17. Alerts records is created within Dynamics 365 once threshold is reached

18. Alert record showing temperature above threshold

19. You could chose to create a Case against this alert

20. Back toAzure world, it shows data being saved in Azure storage, persisting all rules data for alerts being sent by device

21. Data is stored, in this case, in a Blob. In actual implementation, other options (tables, files) could also be used

22. Threshold values lies in a json file which resides within a blob

23. Download and open the file

24. It is a simple json, you can change threshold values here

25. Service Hub compont shown requests and messages graph

26. Service Bus showing stream of data. Point to be noted here is that only that data is being sent to Dyn365 which exceeds threshold, thus saving storage costs.

27. IoT Hub keeps a registration of connected IoT devices

28. You could pass on analytics data to Power BI for further insights into devices data

29. More to read/explore:
https://msdn.microsoft.com/en-us/library/mt790243.aspx
https://msdn.microsoft.com/en-us/library/mt744253.aspx
https://msdn.microsoft.com/en-us/library/mt744242.aspx