We are facing IOT based device provisioning issues since from 1st Jan 2026 in US region

Question

We are facing IOT based device provisioning issues since from 1st Jan 2026 in US region

Pradeep Gurav 0

Support Request Details

Customer: XYZ Contact Name: ABC Role: Senior Firmware Test Engineer

Issue Summary

We are experiencing persistent IoT device provisioning failures in the US region, starting from January 1st, 2026, impacting both new device onboarding and re‑provisioning of existing devices.

Architecture Overview

IoT Products: DEF
Provisioning Method: Gateway‑based provisioning
Authentication: X.509 Certificates (installed on Gateway)
Mobile Platforms: iOS and Android
Cloud Services:
- Azure IoT Hub
  - Azure IoT Hub Device Provisioning Service (DPS)

The Gateway device is provisioned via the mobile application and registered in Azure IoT Hub through DPS.

Issue Description

Since 01‑Jan‑2026, provisioning failures have been consistently observed in the US region, affecting:

✅ All newly installed devices
✅ Some existing devices that were previously disconnected and are now attempting to reconnect / reprovision after reset or power cycle

Observed Error Messages

The most commonly reported failures are:

ConnectDeviceApiPolling - IoTHubFail
Provisioning polling timer fail

These errors occur during the device provisioning / DPS polling phase, preventing the device from completing IoT Hub registration.

Impact

Affected customers: 24 (and increasing daily)
User impact: Devices unable to complete setup or reconnect, blocking product usage
Geographic scope: US region only

Request for Azure Support

We request Azure Support’s assistance to:

Investigate possible service-side changes in:

Azure IoT Hub

Azure IoT Hub Device Provisioning Service (DPS)

Confirm whether any regional updates, policy changes, certificate handling changes, or service degradations were introduced around 01‑Jan‑2026 that could affect:

  - X.509 certificate‑based provisioning
  
  
     - DPS polling behavior
  
     
        - IoT Hub connectivity during device registration
  
        
        Provide guidance on:
  
        
           - Relevant **diagnostic logs** or **metrics** we should review
  
           
              - Any **known issues** or **recommended mitigations**
  ```---

Additional Information

Issue reproducible across multiple product types
Observed consistently on both iOS and Android mobile builds
Certificates used have not changed from our side during this period

Thank you for your support. Please let us know if additional logs, timestamps, IoT Hub names, DPS instance IDs, or correlation IDs are required for further investigation.

Best regards, FGH Senior Firmware Test Engineer TYU

Support Request Details

Customer: NOP
Contact Name: RST
Role: Senior Firmware Test Engineer

Issue Summary

We are experiencing persistent IoT device provisioning failures in the US region, starting from January 1st, 2026, impacting both new device onboarding and re‑provisioning of existing devices.

Architecture Overview

IoT Products: FGH
Provisioning Method: Gateway‑based provisioning
Authentication: X.509 Certificates (installed on Gateway)
Mobile Platforms: iOS and Android
Cloud Services:
- Azure IoT Hub
  - Azure IoT Hub Device Provisioning Service (DPS)

The Gateway device is provisioned via the mobile application and registered in Azure IoT Hub through DPS.

Issue Description

Since 01‑Jan‑2026, provisioning failures have been consistently observed in the US region, affecting:

✅ All newly installed devices
✅ Some existing devices that were previously disconnected and are now attempting to reconnect / reprovision after reset or power cycle

Observed Error Messages

The most commonly reported failures are:

ConnectDeviceApiPolling - IoTHubFail
Provisioning polling timer fail

These errors occur during the device provisioning / DPS polling phase, preventing the device from completing IoT Hub registration.

Impact

Affected customers: 24 (and increasing daily)
User impact: Devices unable to complete setup or reconnect, blocking product usage
Geographic scope: US region only

Request for Azure Support

We request Azure Support’s assistance to:

Investigate possible service-side changes in:

Azure IoT Hub

Azure IoT Hub Device Provisioning Service (DPS)

Confirm whether any regional updates, policy changes, certificate handling changes, or service degradations were introduced around 01‑Jan‑2026 that could affect:

  - X.509 certificate‑based provisioning
  
  
     - DPS polling behavior
  
     
        - IoT Hub connectivity during device registration
  
        
        Provide guidance on:
  
        
           - Relevant **diagnostic logs** or **metrics** we should review
  
           
              - Any **known issues** or **recommended mitigations**
  ```---

Additional Information

Issue reproducible across multiple product types
Observed consistently on both iOS and Android mobile builds
Certificates used have not changed from our side during this period

Thank you for your support. Please let us know if additional logs, timestamps, IoT Hub names, DPS instance IDs, or correlation IDs are required for further investigation.

Best regards,
RTU
Senior Firmware Test Engineer
OPQ

Sander van de Velde | MVP 37,066 Reputation points MVP

2026-01-31T23:38:41.4133333+00:00

Question moderated. Personal data obfuscated. This is a public moderated Azure community forum. Please do not share personal information.

Notice that regarding your request for official Azure support, you need to check this site.
SRILAKSHMI C 19,005 Reputation points Microsoft External Staff Moderator

2026-02-03T05:55:34.6133333+00:00

Hi Pradeep Gurav,

I noticed your feedback, and I’m sorry to hear that your experience wasn’t fully satisfactory. Your input is very important, and I’ll make sure it’s taken into account so we can improve.

If there’s anything more I can do to clarify or assist further, please don’t hesitate to let me know I’ll be happy to help.

Thank you!
SRILAKSHMI C 19,005 Reputation points Microsoft External Staff Moderator

2026-02-04T07:22:35.0066667+00:00

Hi Pradeep Gurav,

I noticed your feedback, and I’m sorry to hear that your experience wasn’t fully satisfactory. Your input is very important, and I’ll make sure it’s taken into account so we can improve.

If there’s anything more I can do to clarify or assist further, please don’t hesitate to let me know I’ll be happy to help.

Thank you!

1 answer

Your answer

Sander van de Velde | MVP 37,066 Reputation points MVP

2026-01-31T23:38:41.4133333+00:00

Question moderated. Personal data obfuscated. This is a public moderated Azure community forum. Please do not share personal information.

Notice that regarding your request for official Azure support, you need to check this site.
SRILAKSHMI C 19,005 Reputation points Microsoft External Staff Moderator

2026-02-03T05:55:34.6133333+00:00

Hi Pradeep Gurav,

I noticed your feedback, and I’m sorry to hear that your experience wasn’t fully satisfactory. Your input is very important, and I’ll make sure it’s taken into account so we can improve.

If there’s anything more I can do to clarify or assist further, please don’t hesitate to let me know I’ll be happy to help.

Thank you!
SRILAKSHMI C 19,005 Reputation points Microsoft External Staff Moderator

2026-02-04T07:22:35.0066667+00:00

Hi Pradeep Gurav,

I noticed your feedback, and I’m sorry to hear that your experience wasn’t fully satisfactory. Your input is very important, and I’ll make sure it’s taken into account so we can improve.

If there’s anything more I can do to clarify or assist further, please don’t hesitate to let me know I’ll be happy to help.

Thank you!

Answer 1

Hello @Pradeep Gurav,

Welcome to this Azure community forum.

You experience communication issues with Azure IoT Hub devices.

the last official changes are:

TLS cert move towards Digicert G2 root
Move to TLS version 1.2

The Digitcert G2 Root migration should be finished a couple of years ago already.

The deprecation of TLS 1.0 and 1.1 is more recent.

As seen in the post, you could try to check the diagnostics regarding connectivity:

AzureDiagnostics 
| project Category, tls = tostring( todynamic(properties_s).tlsVersion) , deviceId = tostring( todynamic(properties_s).deviceId) 
| where tls != ''
| distinct deviceId, tls

Notice that is only covers the devices that actually connect to IoT Hubs.

It seems you need to connect with Azure support for a detailed diagnosis.

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.

Share via

We are facing IOT based device provisioning issues since from 1st Jan 2026 in US region

Support Request Details

Issue Summary

Architecture Overview

Issue Description

Observed Error Messages

Impact

Request for Azure Support

Additional Information

Support Request Details

Issue Summary

Architecture Overview

Issue Description

Observed Error Messages

Impact

Request for Azure Support

Additional Information

1 answer

Your answer