Deploying Azure Industrial IoT Platform



The simplest way to get started is to deploy the Azure Industrial IoT Platform and Simulation demonstrator using the deployment script. Unless you decide otherwise, it also deploys 2 simulated Edge Gateways and assets.

The all in one hosting option is intended as a quick start solution. For production deployments that require staging, rollback, scaling and resilience you should deploy the platform into Kubernetes as explained here.

To connect your physical Assets install one ore more Azure IoT Edge Gateways.

What you get when you deploy the platform

The deployment script allows to select which set of components to deploy using deployment types. The dependencies and deployments types are explained below.

  • Minimum dependencies:

    • 1 IoT Hub to communicate with the edge and ingress raw OPC UA telemetry data
    • 1 Key Vault, Premium SKU (to manage secrets and certificates)
    • 1 Service Bus, Standard SKU (as integration event bus)
    • 1 Event Hubs with 4 partitions and 2 day retention, Standard SKU (contains processed and contextualized OPC UA telemetry data)
    • 1 Cosmos DB with Session consistency level (to persist state that is not persisted in IoT Hub)
    • 1 Blob Storage V2, Standard LRS SKU (for event hub checkpointing)
  • Standard dependencies: Minimum +

  • Microservices:

  • UI (Web app):

    • App Service Plan (shared with microservices), 1 App Service for hosting the Industrial IoT Engineering Tool cloud application
  • Simulation:

    • Virtual machine, Virtual network, IoT Edge used for a factory simulation to show the capabilities of the platform and to generate sample telemetry. By default, 4 Virtual Machines, 2 B2 SKU (1 Linux IoT Edge gateway and 1 Windows IoT Edge gateway) and 2 B1 SKU (factory simulation).
  • Azure Kubernetes Service should be used to host the cloud microservices

The types of deployments are the following:

  • minimum: Minimum dependencies
  • local: Minimum and Standard dependencies
  • services: local and Microservices
  • simulation: Minimum dependencies and Simulation components
  • app: services and UI components
  • all (default): all the above components

Other hosting and deployment methods

Alternative options to deploy the platform services include: