Identifying the connection string to connect to IOThub RRS feed

  • Question

  • Hello,

    I've been working my way through the "Data visualization with Web Apps" tutorial, and I seem to have run into a snag. I am uncertain as to which connection string to use. I tried to follow the directions and get the connection string that is created for my device with the iothub-explorer tool, but that caused the site to give me a 500 error. Could someone explain which connection string I need, and how I should go about generating it?

    Friday, February 2, 2018 8:03 PM

All replies

  • Dear Stephen,

    Do you mean IoT Hub connection string? 

    If you mean this, you can open your Azure Portal(portal.azure.com) , Login with your username and password.

    Then click All-resources->your IotHub->Shared access policies->iothubowner->

    Connection string—primary key. You will find the connection string for your IoTHub.

    Keep Fighting

    Monday, February 5, 2018 1:32 AM
  • Hello Stephen,

    You need IoT Hub Connection String and you can find it from device explorer like this:

    Or as @Jiong Shi pointed out you can get it from Azure Portal.

    I followed "Data visualization with Web Apps" tutorial and saw the see real-time temperature and humidity data like this:

    Best regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, February 5, 2018 5:37 AM
  • When you log in to your Azure portal, you can find "Shared Access Policies".

    From there, you can find the "iothubowner" policy, if you didn't change any configuration when you create the IOT hub in Azure. By clicking the iothubowner, you can find the connection string as per the key you used.

    Monday, February 5, 2018 6:21 AM
  • Thank you very much! The test samples are working now!
    Monday, February 5, 2018 1:45 PM