Download Defender IoT Sensor

Justin Tomkowicz 0 Reputation points
2026-11-09T13:03:54.37+00:00

Unable to download ISO from Microsoft site for over a month. Is there a direct link to the ISO for downloading?

The following is what we see when trying to download:

User's image

Windows for business | Windows for IoT
0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Chance Maurice Niyonzima 825 Reputation points Independent Advisor
    2026-11-09T13:49:06.4933333+00:00

    Hello Justin,

    Thank you for posting your question on the Microsoft Windows Forum!

    Thank you for including the screenshot. It provides an important clue.

    The most important finding

    The error shown in the portal indicates that the download process is failing while attempting to reach:

    storprodweunotif.blob.core.windows.net

    Rather than a permissions or licensing error, this appears to be a connectivity issue between the browser and the Azure Blob Storage endpoint that hosts the Defender for IoT sensor software.

    Because you've been experiencing the same behavior for more than a month, I'd focus on understanding why the storage endpoint cannot be reached rather than looking for an alternative ISO source.

    Regarding a direct ISO link

    At this time, Microsoft does not document a supported static public URL for downloading the Defender for IoT OT sensor ISO directly.

    The supported process is to download the sensor image through:

    Microsoft Defender for IoT
→ Getting started
→ Sensor

    and the downloaded software is delivered through the Azure-hosted portal workflow.

    Highest-value next step

    Given the timeout shown in your screenshot, I'd be interested to know whether you've had an opportunity to test the download from:

    A different network connection
A browser session without proxy inspection
A workstation outside the corporate network

    The reason I ask is that the portal itself loads successfully, while the Blob Storage endpoint appears not to respond.

    That often points toward:

    Proxy filtering
SSL/TLS inspection
Firewall restrictions
DNS resolution issues
Network routing problems

    rather than a problem with Defender for IoT itself.

    Additional observation

    If possible, try comparing the results from:

    Corporate network

    and:

    Mobile hotspot / external Internet connection

    If the sensor download succeeds from an alternate network, that would strongly suggest that the download request is being blocked or interrupted somewhere along the original network path.

    If the issue persists

    If the Blob Storage endpoint continues to time out even from an unrestricted network, I'd recommend opening a support case with the Defender for IoT team and including:

    UTC time of the failed download attempt
Browser HAR trace
Screenshot of the timeout
Defender for IoT subscription details
Required sensor software version

    This will allow the service team to investigate the backend download process and verify whether there are issues affecting the storage endpoint.

    Microsoft References

    One clarification

    Justin, does the timeout occur for all Defender for IoT sensor versions, or only when attempting to download a specific sensor image version?

    That detail may help determine whether the issue is tied to the storage endpoint itself or to a particular file being served.

    I hope this answer has brought you useful information. If so, please click on Accept Answer and consider upvoting it. Doing so helps other community members identify useful solutions to similar issues.

    Was this answer helpful?

  2. AI answer

    2026-11-09T13:04:59.0133333+00:00

    Microsoft does not document a supported static ISO URL for the Defender for IoT OT sensor; resolve access to the Azure Blob Storage endpoint and download the signed ISO through Defender for IoT → Getting started → Sensor.

    Resolve the timeout

    The message storprodweunotif.blob.core.windows.net took too long to respond shows that the browser cannot retrieve content from the Blob Storage host used by the portal. Since this has persisted for a month, have the network/security team check the workstation’s outbound path:

    1. Permit outbound HTTPS/TCP 443 to Azure Blob Storage, including the displayed storprodweunotif.blob.core.windows.net host.
    2. Check whether a proxy, web-content filter, or TLS inspection service is blocking or timing out the request.
    3. Test the same Azure portal page from a different network path that does not use the organization’s proxy or TLS inspection.
      • If it works there, the restriction is on the original network path.
      • If it fails from independent networks, proceed to Microsoft support.

    Defender for IoT uses Azure services including Blob Storage and requires HTTPS/TCP 443 connectivity. The portal can also provide the applicable endpoint list from Sites and sensors → More options → Download endpoint details.^1^

    Download the ISO after connectivity is restored

    For a new sensor installation:

    1. Sign in to the Azure portal with a Security Reader, Security Admin, Contributor, or Owner role.
    2. Open Defender for IoT → Getting started → Sensor.
    3. Under Purchase an appliance and install software, select the required or recommended software version.
    4. Select Download and save the ISO somewhere accessible to the target appliance or VM.^2^

    Microsoft states that files downloaded through this portal workflow are signed by its root of trust.^3^ A copied or unofficial mirror should therefore not be used as a substitute.

    For an existing sensor update, do not use the installation ISO page. Open:

    Defender for IoT → Sites and sensors → Sensor update (Preview) → Local update

    Select the installed version, choose the recommended available version, and select Download. Update downloads are .tar packages rather than installation ISOs.^4^

    Escalation

    If the Blob endpoint still times out from an unrestricted network, open Defender for IoT → Diagnose and solve problems or create a Microsoft support case. Include:

    • The hostname shown in the timeout
    • UTC date and time of a failed request
    • Required sensor software version
    • Azure subscription and tenant details entered only in the private support case
    • Browser network trace/HAR file
    • Whether the failure occurs from another browser and another network

    Microsoft’s sensor troubleshooting guidance directs unresolved issues to Microsoft Support.^5^ Support can investigate the portal-hosted download or provide an appropriate current download mechanism; a permanent public ISO URL is not included in the documented deployment process.

    References

    1. Networking requirements
    2. Install OT sensor monitoring software
    3. Maintain OT network sensors from the sensor console
    4. Defender for IoT - Update OT monitoring software
    5. Troubleshoot the sensor
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.