Getting Started: Azure Injector Quick Start Shows end to end configuration of Azure Injector and getting tag data flowing into Azure IoT Hub. Using IoT Hub Message Based Routing Shows configuration for an Azure Injector module to publish live tag data to an Azure IoT Hub where the messages are then automatically routed and stored in an Azure Storage Container. Pushing Data to Azure Time Series Insights Shows configuration for an Azure Injector module to publish live tag data to an Azure IoT Hub configured as a data source form Time Series Insights. Messages are then automatically stored in Time series Insights. Publishing Data to Azure IoT Edge Shows how how to make a module connection from the Azure Injector modules to Azure IoT Edge.  Publishing Data to Azure IoT Central Shows how to connect and publish live tag data to am Azure IoT Hub. Python Scripting Details the API calls available for the Azure Injector Module Azure Injector Tags Describes the tags Azure Injector automatically creates for the Azure Injector control Azure Custom Tag Properties Describes the Azure Injector custom tag properties Increasing throughput for the Azure Injector Describes how to set the Push Policy to utilize multiple endpoints to increase throughput Cloud Injector Tag Agents and Tag Trees Describes how Cloud Injector Agent configurations interact with Ignition tag trees to push messages and tag change events to the cloud service Managing UDTs through Injector Tag Agents Describes how the UDT parameters for the Tag Agents affect the message payload JSON format published by MQTT Modules  Details the JSON format published by MQTT Modules Determining the settings for an Injector History Store Describes how to determine the configuration settings for an Injector History Store Connecting to Azure IoT Hub with Certificate Based Authentication Describes how to create the device certificates required and how to configure Azure Injector to support certificate based authentication How the MQTT Injector Push Trigger affects data published Describes how the Push Trigger configuration affects data published