Setting UAMI and Primary Identity Managed Instance timeout

Question

Setting UAMI and Primary Identity Managed Instance timeout

Julie 40

Hello,

I want to set identites after provisioning Azure SQL Managed Instance with Azure Powershell.

First I set my automation-umi and a unique umi per instance to UAMI, then I set primary to the automation-umi. The automation-umi has Directory Reader Role.

$AllIdentities = @($AutomationUserManagedIdentityId, $InstanceUserAssignedIdentityId)      

Set-AzSqlInstance -Name $InstanceName `        
-ResourceGroupName $ResourceGroup `         
-IdentityType UserAssigned `         
-UserAssignedIdentityId $AllIdentities `         
-AssignIdentity `         
-Force      

Set-AzSqlInstance -Name $InstanceName `         
-ResourceGroupName $ResourceGroup `         
-PrimaryUserAssignedIdentityId $AutomationUserManagedIdentity.ClientId `         
-AssignIdentity `         
-Force

My problem is that it times out when setting primary identity.

WARNING: Failed to terminate process: 1 error occurred:

* failed to send Ctrl-Break event to process being terminated: The handle is invalid.

Do you have any advice? The timeout happens after 1 hour

I have also tried to to it in one command, but it still times out. But when I do this I see the instance is set to currently updating. How long can you expect this would take? :)


Set-AzSqlInstance -Name $InstanceName `        
-ResourceGroupName $ResourceGroup `         
-IdentityType UserAssigned `         
-UserAssignedIdentityId $AllIdentities `    
-PrimaryUserAssignedIdentityId $AutomationUserManagedIdentity.ClientId `       
-AssignIdentity `         
-Force

Mahesh Kurva 9,725 Reputation points Microsoft External Staff Moderator

2025-10-30T13:32:16.4066667+00:00
Hi Julie •,

Greetings!!

It seems like you're having a timeout issue while setting the primary identity for your Azure SQL Managed Instance using PowerShell. This can be frustrating, and I’m here to help!

Here are few things you can try:

Timeout Duration & Command Structure: You mentioned that the timeout happens after one hour. While the command execution time can vary, setting identities should not typically take that long. As a workaround, you could try running the command with the -AsJob parameter if you haven’t already. This allows the command to run as a background job, freeing up PowerShell for other tasks.

For example:

Set-AzSqlInstance -Name $InstanceName ` -ResourceGroupName $ResourceGroup ` -IdentityType UserAssigned ` -UserAssignedIdentityId $AllIdentities ` -PrimaryUserAssignedIdentityId $AutomationUserManagedIdentity.ClientId ` -AssignIdentity ` -Force -AsJob

Review Managed Identity Permissions: Ensure your automation-umi has the necessary permissions, specifically the Directory Reader Role. If the role is not correctly assigned, the identity assignment can fail.

Connectivity Issues: Check if there are any potential connectivity issues between your client and Azure SQL Managed Instance. You might want to run the Azure SQL Connectivity Checker tool to diagnose any connectivity problems that could cause the timeout.

Temperature/Instance Status: If the instance shows as "currently updating," it may be necessary to wait for the update to complete. Long-running operations can lead to extended wait times for subsequent commands. Usually, Azure resources should not take too long to process changes – if it gets stuck, there might be other issues involved.

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 9,725 Reputation points Microsoft External Staff Moderator

2025-10-31T16:23:48.08+00:00

Hi Julie •,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Mahesh Kurva 9,725 Reputation points Microsoft External Staff Moderator

2025-10-30T13:32:16.4066667+00:00

Hi Julie •,

Greetings!!

It seems like you're having a timeout issue while setting the primary identity for your Azure SQL Managed Instance using PowerShell. This can be frustrating, and I’m here to help!

Here are few things you can try:

Timeout Duration & Command Structure: You mentioned that the timeout happens after one hour. While the command execution time can vary, setting identities should not typically take that long. As a workaround, you could try running the command with the -AsJob parameter if you haven’t already. This allows the command to run as a background job, freeing up PowerShell for other tasks.

For example:

Set-AzSqlInstance -Name $InstanceName ` -ResourceGroupName $ResourceGroup ` -IdentityType UserAssigned ` -UserAssignedIdentityId $AllIdentities ` -PrimaryUserAssignedIdentityId $AutomationUserManagedIdentity.ClientId ` -AssignIdentity ` -Force -AsJob

Review Managed Identity Permissions: Ensure your automation-umi has the necessary permissions, specifically the Directory Reader Role. If the role is not correctly assigned, the identity assignment can fail.

Connectivity Issues: Check if there are any potential connectivity issues between your client and Azure SQL Managed Instance. You might want to run the Azure SQL Connectivity Checker tool to diagnose any connectivity problems that could cause the timeout.

Temperature/Instance Status: If the instance shows as "currently updating," it may be necessary to wait for the update to complete. Long-running operations can lead to extended wait times for subsequent commands. Usually, Azure resources should not take too long to process changes – if it gets stuck, there might be other issues involved.

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 9,725 Reputation points Microsoft External Staff Moderator

2025-10-31T16:23:48.08+00:00

Hi Julie •,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Setting UAMI and Primary Identity Managed Instance timeout

Your answer