Create a dedicated consumer group in the IoT hub for the Time Series Insights environment to consume from. Each Time Series Insights event source must have its own dedicated consumer group that isn't shared with any other consumer. If multiple readers consume events from the same consumer group, all readers are likely to exhibit failures.
Reference:
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source- iothub
Topic 3, Fabrikam
General Overview
Fabrikam, Inc. is an international food company that has a main office in London and 250 sites worldwide.
FabRIkam uses a prototype hydroponics loT management system that tracks temperatures and PH levels and adjusts conditions automatically.
Location
The prototype environment is deployed to the main office.
IoT Hub
The management system uses a free tier Azure loT hub.
Devices
The prototype contains the devices shown in the following table.

Each device will use the following:
* A common set of Azure loT Edge modules
* A unique module for each type of sensor or controller
Each device has a device twin. Each device twin contains a tag that identifies the device type. For example, the device twin of Child4 contains a tag of ph. Each device sends 1.440 4-KB messages to the loT hub per day.
Pilot deployment
A pilot of the hydroponics loT management system will be deployed initially to 50 of the company's worldwide sites.
Device Requirements
Fabrikam identifies the following device requirements:
* Cloud-to-device commands will be sent to each primary control device.
* All module communication from the child devices must be routed to the loT hub.
* The parameters of each device type must be configured in the loT Edge container configuration file.
* Device modules must be deployed to all the devices automatically, and then updated automatically. The solution must support targeted deployments by using device twin tags.
Networking Requirements
Fabrikam identifies the following networking requirements:
* Child devices will NOT have internet access.
* The primary control device in each site will have internet access.
* Child devices will communicate with their local primary control device by using the AMQP protocol.
Monitoring Requirements
Fabrikam identifies the following monitoring requirements:
* The number of device-to-cloud telemetry messages sent to the loT hub by the primary control devices must be tracked.
* An email notification must be sent if a message is NOT received from Child4 every 10 minutes.
Technical Requirements
Fabrikam identifies the following technical requirements:
* The solution must support cloud-to-device commands.
* Administrative effort must be minimized whenever possible.
* Hardware and software costs must be minimized whenever possible.
* Access to the loT hub must be restricted to devices that connect from the company's sites.

Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-use-create-options

1 - From Microsoft Visual Studio Code,...
2 - Build and push the module to Azure Container Registry
3 - Create a deployment for the IoT Edge device.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/tutorial-develop-for-linux?view=iotedge-2020-11

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-azure-service-health-integration