An infographic insight into various architecture components of a typical Connected Field Service deployments on Azure and Dynamics 365.

1. Architecture Components
twitter.com/khanali - https://medium.com/crm-donuts
IOT DEVICE AZURE
SERVICE BUS
Any IOT device which can send
sensory data and optionally receive
commands. Simulator Web App is
part of Connected Field Service
solution. MXChip IoT DevKit is also
fully supported.
ASB is a generic, cloud-based
messaging system that is used to
connect practically anything. In CFS,
Service Bus connects D365 and IOT
Hub by managing messages flowing
in both directions.
$ 1.00
0
5
10
15
20
25
Device 1 Device 2 Device 3
LOGIC APPS
STREAM
ANALYTICS
Azure Storage is a general purpose
storage account providing access to
saving data in tables, blobs, files,
queues and VMs. In CFS, Storage is
used to keep device rules for
triggering actions.
Logic Apps enables building,
scheduling and automating
processes among various integrated
systems. Two logic apps (CRM->IOT
and IOT-CRM) are part of CFS for
commands and alerts respectively.
DYNAMICS
365
POWER BI
SERVICE
STORAGE
IOT Hub enables connecting,
monitoring and managing millions of
IOT devices. IOT Hub manages devices
registration, usage metrics and
commands. All IOT devices data is first
interfaced with Hub.
Stream Analytics is an event-
processing engine that is capable of
examining huge data volumes,
identifying patterns & then running
triggers/actions. This always works
with IOT Hub in IOT deployments.
Power BI Service is an analytics
service that enables users to
visualize and analyze data from
connected services. In CFS, Power Bi
Service is connected with both D365
and Azure.
Field Serivce and IOT are two solutions
within Dynamics 365 that are used in
CFS. IOT Solution lets users to register
devices, send commands, see alerts
etc. Field Service is used to create
Work Orders against IOT alerts.
IOT HUB
DYNAMICS 365 CONNECTED FIELD SERVICE
Device Azure IOT D365 PowerBI
All logos are copyrighted to Microsoft