Drag and Drop Question A company deploys Dynamics 365 Customer Service. The company plans to use IoT to collect information about manufacturing equipment. Work orders must be automatically generated w

Question

Exhibit

Answer Area

Explanation

Connected Customer Service - Explanation

This question tests knowledge of the Connected Customer Service (CCS) architecture in Dynamics 365, which integrates IoT signals with field service workflows.

The Architecture (in order)

1. Azure IoT Central

Role: Device management and monitoring platform

IoT Central is a fully managed SaaS IoT application built on top of IoT Hub. It provides:

• Device registration, templates, and dashboards with minimal coding
• A built-in rules engine to detect anomalies (e.g., equipment malfunction thresholds)
• Native integration with Dynamics 365 Connected Customer Service

Why it goes first: It's the customer-facing IoT management layer - the platform where devices are enrolled and monitored. It's the recommended starting point for CCS deployments that don't require deep custom development.

2. Azure IoT Hub

Role: Cloud messaging gateway / telemetry ingestion

IoT Hub is the underlying PaaS service that receives raw device-to-cloud messages. IoT Central is actually built on top of IoT Hub. When you need:

• Custom data pipelines
• Advanced routing of telemetry
• More control over processing logic

Why it goes second: It represents the lower-level, more customizable alternative. In CCS, you choose either IoT Central or a direct IoT Hub integration depending on complexity needs. IoT Hub handles the raw message ingestion before any business logic runs.

3. Power Automate

Role: Automated workflow trigger for work order creation

Once an IoT alert is raised (by IoT Central or Hub), Power Automate acts as the automation bridge - it listens for the alert event and automatically creates a work order in Dynamics 365 Customer Service.

Why it goes third: It sits at the end of the pipeline, translating IoT signals into business actions. This is what fulfills the requirement: "work orders must be automatically generated when malfunctions are detected."

Common Mistakes

Summary Flow

Manufacturing Equipment
        ↓ telemetry
  Azure IoT Hub (raw ingestion)
        ↓ built on top
Azure IoT Central (device mgmt + anomaly rules)
        ↓ alert triggered
   Power Automate (workflow)
        ↓ creates
  Dynamics 365 Work Order

No community discussion yet for this question.