Microsoft.DeviceUpdate RP stuck in 'Registering' state — all instance creates fail with InternalServerError

Question

Microsoft.DeviceUpdate RP stuck in 'Registering' state — all instance creates fail with InternalServerError

Kensei Kawamura 80 Microsoft Employee

We are unable to create any new Microsoft.DeviceUpdate/accounts/instances resources in our subscription. Every attempt — via Bicep, ARM, Azure CLI, and the Azure Portal — fails with the same opaque error:

{

"code": "InternalServerError",

"message": "Job failed due to an internal error."

}

Activity log shows no further detail beyond ResourceOperationFailure → InternalServerError.

The Microsoft.DeviceUpdate resource provider in this subscription has been stuck in Registering state for 24+ hours.

registrationState : Registering

registrationPolicy : RegistrationRequired

namespace : Microsoft.DeviceUpdate

providerAuthorizationConsentState: (empty)

Forcing re-registration (az provider register -n Microsoft.DeviceUpdate --wait) does not complete and the RP never returns to Registered.

Environment:

Subscription: [REDACTED]
Tenant: Microsoft TME [REDACTED]
Region: West US 2 (account location)
API version tried: Both 2022-10-01 and 2023-07-01

What we've verified:

Existing ADU resources in the same subscription (created Oct 2025) work normally — only new instance creates fail.
The IoT Hub being linked is healthy (provisioningState: Succeeded, state: Active) and has the deviceupdateservice shared access policy.
The ADU first-party service principal in this tenant (objectId [REDACTED], appId [REDACTED], displayName Azure Device Update) has been granted IoT Hub Data Contributor on the linked hub.
The parent Microsoft.DeviceUpdate/accounts resource provisions successfully and shows provisioningState: Succeeded — only the child accounts/instances resource fails.
Resource locks, policies, and quotas are not blocking the operation.
All ADU subscription feature flags are NotRegistered, but they were also NotRegistered when our existing working instances were created, so this should not be the cause.

Repro:

In subscription above, create any Microsoft.DeviceUpdate/accounts/instances resource (any name, any RG, link to any healthy IoT Hub).
Resource transitions to provisioningState: Failed within 30s with InternalServerError.

What we need:

Confirmation whether Microsoft.DeviceUpdate RP being stuck in Registering is a known issue or service-side problem.
Guidance on how to force the RP back to a healthy Registered state, or whether this requires PG intervention.Forcing re-registration (az provider register -n Microsoft.DeviceUpdate --wait) does not complete and the RP never returns to Registered. Environment:
```
    - **Subscription:** [REDACTED]
  
  
    - **Tenant:** Microsoft TME [REDACTED]
  
    
       - **Region:** West US 2 (account location)
  
       
          - **API version tried:** Both `2022-10-01` and `2023-07-01`
```
What we've verified:
- Existing ADU resources in the same subscription (created Oct 2025) work normally — only new instance creates fail.
  - The IoT Hub being linked is healthy (provisioningState: Succeeded, state: Active) and has the deviceupdateservice shared access policy.
    - The ADU first-party service principal in this tenant (objectId [REDACTED] , appId[REDACTED], displayName Azure Device Update) has been granted IoT Hub Data Contributor on the linked hub.
```
                      - The parent `Microsoft.DeviceUpdate/accounts` resource provisions successfully and shows `provisioningState: Succeeded` — only the child `accounts/instances` resource fails.
        
          
             - Resource locks, policies, and quotas are not blocking the operation.
        
             
                - All ADU subscription feature flags are `NotRegistered`, but they were also `NotRegistered` when our existing working instances were created, so this should not be the cause.
        
                
          **Repro:**
```
      1. In subscription above, create any Microsoft.DeviceUpdate/accounts/instances resource (any name, any RG, link to any healthy IoT Hub).
      2. Resource transitions to provisioningState: Failed within 30s with InternalServerError.
  What we need:
- Confirmation whether Microsoft.DeviceUpdate RP being stuck in Registering is a known issue or service-side problem.
- Guidance on how to force the RP back to a healthy Registered state, or whether this requires PG intervention.

Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-04T17:24:08.4433333+00:00

Hello @Kensei Kawamura ,

Checking in to see if you had any chance to review the above response

Thank you!
Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-05T18:05:20.07+00:00

Hello @Kensei Kawamura ,

Checking in to see if the above response was helpful

Thank you
Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-06T17:29:29.0433333+00:00

Hello @Kensei Kawamura ,

Since I’ve converted Anshika's comment into an answer, could you please take a moment to mark it as Accepted with an upvote? This helps others in the community with the same question find the solution more easily.

Thank you!
Manas R Mohanty 17,270 Reputation points Moderator

2026-05-19T18:11:17.0666667+00:00

Hello @Kensei Kawamura ,

Good day

Hope situation is improved now.

Have reached you via team for the steps and CLI commands to replicate the issue.

Thank you.

1 answer

Your answer

Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-04T17:24:08.4433333+00:00

Hello @Kensei Kawamura ,

Checking in to see if you had any chance to review the above response

Thank you!
Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-05T18:05:20.07+00:00

Hello @Kensei Kawamura ,

Checking in to see if the above response was helpful

Thank you
Karnam Venkata Rajeswari 4,925 Reputation points Microsoft External Staff Moderator

2026-05-06T17:29:29.0433333+00:00

Hello @Kensei Kawamura ,

Since I’ve converted Anshika's comment into an answer, could you please take a moment to mark it as Accepted with an upvote? This helps others in the community with the same question find the solution more easily.

Thank you!
Manas R Mohanty 17,270 Reputation points Moderator

2026-05-19T18:11:17.0666667+00:00

Hello @Kensei Kawamura ,

Good day

Hope situation is improved now.

Have reached you via team for the steps and CLI commands to replicate the issue.

Thank you.

Answer 1

Hi Kensei Kawamura •,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

The current behavior—where the Microsoft.DeviceUpdate resource provider remains in a Registering state and instance creation consistently fails with InternalServerError—indicates that the provider has not fully completed initialization within the subscription.

In Azure, a resource provider must be fully registered before any dependent resources can be created. If the provider registration does not complete successfully, provisioning operations may fail without detailed error messages.

Please check if the following steps help -

Verifying provider registration state -This command helps confirm whether the provider remains in Registering or transitions to Registered.
```
   az provider show --namespace Microsoft.DeviceUpdate --query registrationState
```
Reviewing Azure Service Health for active advisories
Use the Service Health dashboard to check for any ongoing service issues, planned maintenance, or advisories that may impact resource provisioning.
1. Azure Service Health provides real-time updates and guidance on service-related incidents affecting subscriptions and regions.
Retrying deployment only after provider becomes Registered Instance creation should be retried once the resource provider successfully transitions to the Registered state, as this is a prerequisite for resource creation.

The following references might be helpful , please check them out

Thank you