Creating an Azure IoT Hub

You have recently been hired by Parktronics, a monitoring company that works with local, state, and national park services. They have decided to use Azure IoT to develop a solution that will monitor entry and exit gates to ensure they are closed and locked at closing time.

Your current task is to create two IoT hubs with various settings in order to develop a proof-of-concept solution.

Create two IoT hubs that meet the provided criteria. Create the first IoT hub using the Azure Portal.

IoT Hub 1

This hub will be used for device-to-cloud telemetry only. It will not be required for device management or cloud-to-device commands.

• Name: IoTHub1-B1-XXXXX, where XXXXX is the five-character suffix for the lab resources. This can be found by looking at the pre-deployed storage account in the lab and noting the last five characters of the name.

To create the second IoT hub, you will be using the Azure CLI. We can access the CLI via:

1. Click the Cloud Shell icon (>_) in the upper-right of the screen.
2. Click Bash.
3. Click Show advanced settings, and set the following values:
   • Subscription: Use the lab provided subscription
   • Resource group: Use the lab provided Resource Group
   • Cloud Shell region: Use the same location as the lab provided Resource Group.
   • Storage account: Use existing
   • File share: Use existing, and enter cloudshell

IoT Hub 2

This hub will be required to facilitate two-way communication between devices and the back-end solution. It will also require Azure Security Center functionality.

• Name: IoTHub2-S1-XXXXX where XXXXX is the five-character suffix for the lab resources. This can be found by looking at the pre-deployed storage account in the lab and noting the last five characters of the name.

When creating 2nd IOT, choose Public Endpoint (All Networks). Instead of Azure Security Center, you'll see Defender for iot (enable)

If you get stuck, feel free to check out the solution video or the detailed instructions under each objective. Good luck!

Note: A log analytics workspace is no longer automatically created.

Lab Suffix

Pre-deployed lab resources will all end with a unique five-character suffix. Make note of this suffix, as you may need it when naming resources during the lab.

WARNING: Be Prepared for UI Changes

Given the fluid nature of Microsoft cloud tools, you may experience user interface (UI) changes that were made following the development of this hands-on lab that do not match up with lab instructions. When any such changes are brought to our attention, we will attempt to update the content accordingly. However, if changes occur, students will have to adapt to the changes and work through them in the hands-on labs as needed.