This curriculum reflects the scope typically addressed across a full consulting engagement or multi-phase internal transformation initiative.

Design device-to-cloud ingestion patterns balancing throughput, latency, and cost using IoT Hub tiers and partitioning strategies.
Evaluate trade-offs between IoT Hub, Event Hubs, and Azure IoT Central based on device scale, management needs, and telemetry volume.
Implement message routing to multiple endpoints (Blob Storage, Service Bus, Logic Apps) with filtering and dead-letter handling.
Configure device twin synchronization for state consistency while managing update frequency and bandwidth consumption.
Assess impact of device connection protocols (MQTT, AMQP, HTTPS) on power usage, firewall traversal, and message overhead.
Plan for regional failover and disaster recovery using paired IoT Hubs and cross-region device provisioning.
Optimize pricing model selection (S1, S2, S3) based on daily message quotas and connection concurrency.
Integrate IoT Hub with Time Series Insights for long-term telemetry analysis and anomaly detection workflows.

Provision and deprovision device identities at scale using IoT Hub identity registry and automated scripts.
Compare group enrollment vs individual enrollment strategies in Device Provisioning Service (DPS) for manufacturing scalability.
Manage X.509 certificate rotation and symmetric key regeneration with minimal device downtime.
Implement zero-touch provisioning workflows integrating DPS with hardware secure elements.
Enforce device retirement policies with audit trails and revocation mechanisms.
Monitor device lifecycle events (creation, deletion, connection) via diagnostic logs and Azure Monitor alerts.
Design identity naming conventions that support hierarchical organization and access control delegation.
Handle orphaned device identities resulting from failed provisioning attempts or network outages.

Configure shared access policies with principle of least privilege for backend services and device clients.
Implement per-device SAS tokens with short expiry times to limit exposure from credential leakage.
Integrate IoT Hub with Azure Active Directory for role-based access control (RBAC) on management operations.
Enforce TLS 1.2+ and disable deprecated protocols using network security policies and device SDK configuration.
Design secure bidirectional communication patterns using C2D commands and file uploads with integrity checks.
Isolate high-risk devices using dedicated IoT Hub instances or network segmentation via private endpoints.
Implement certificate-based mutual authentication and validate chain of trust across device fleets.
Audit access logs to detect brute-force attacks or anomalous connection patterns from compromised devices.

Structure telemetry payloads using JSON schema standards to ensure downstream compatibility with analytics pipelines.
Apply message enrichment at IoT Hub level to inject contextual metadata (location, environment) for routing.
Balance message size and frequency to stay within IoT Hub quotas while preserving diagnostic fidelity.
Implement batching and compression strategies on device side to reduce egress costs and network load.
Handle message ordering and deduplication requirements for time-sensitive control systems.
Design fallback storage mechanisms on edge devices during cloud connectivity outages.
Use custom endpoints and Azure Functions to preprocess telemetry before storage or analysis.
Monitor end-to-end message latency and identify bottlenecks in ingestion pipeline.

Deploy desired property updates via device twin to enforce configuration drift remediation across device groups.
Orchestrate firmware updates using direct methods with timeout and retry logic for unreliable networks.
Implement configuration rollback procedures triggered by failed health checks or metric anomalies.
Use configuration metrics to measure compliance rate and time-to-convergence across device fleets.
Design conditional deployments based on device tags, location, or software version.
Manage configuration conflicts when multiple services write to the same twin properties.
Integrate with CI/CD pipelines to version-control device configurations and enable auditability.
Simulate configuration rollouts in staging environments before production deployment.

Enable IoT Hub diagnostic logs and route to Log Analytics for queryable operational history.
Define alert thresholds for connection failures, throttling events, and message drop rates.
Use distributed tracing across device, IoT Hub, and backend services to isolate failure domains.
Interpret built-in metrics (e.g., D2C Telemetry, C2D Commands) to detect performance degradation.
Recover from IoT Hub throttling by implementing client-side backoff and queuing strategies.
Diagnose device disconnection causes using connection state telemetry and network path analysis.
Validate failover procedures by simulating regional outages and measuring recovery time objectives (RTO).
Correlate device-reported errors with backend processing failures to identify systemic issues.

Connect IoT Hub to enterprise ERP and asset management systems using Logic Apps or API Management.
Expose device data to business users via Power BI with appropriate row-level security and refresh policies.
Implement change data capture patterns to synchronize device twins with external CMDBs.
Integrate with Azure Digital Twins to model physical relationships and propagate state changes.
Enable cross-cloud interoperability using standardized message formats and API gateways.
Handle data sovereignty requirements by routing region-specific device data to local processing nodes.
Support third-party vendor devices through abstraction layers and adapter services.
Manage API versioning and deprecation cycles for long-lived IoT integrations.

Forecast monthly costs based on device count, message volume, and endpoint routing rules.
Implement tagging and resource grouping to allocate IoT costs to business units or projects.
Right-size IoT Hub tier and unit count using utilization metrics and growth projections.
Enforce governance policies using Azure Policy to prevent unauthorized IoT Hub creation.
Archive cold data from IoT Hub routes to lower-cost storage tiers with lifecycle management.
Monitor SDK version distribution to retire outdated clients with security vulnerabilities.
Conduct periodic access reviews to remove stale shared access policies and device identities.
Establish quota alerts and throttling safeguards to prevent runaway billing from misconfigured devices.

Azure Iot Hub