How to unblock Linux agent pool for container registry stuck in the "Update" state

Question

How to unblock Linux agent pool for container registry stuck in the "Update" state

Georges-André Janett 20

I've got two agent pool provided by Microsoft in two Azure Container Registry that are stuck in the "Updating" state.

How can I force delete them or anything that would make them work again ?

Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-13T15:31:55.0833333+00:00
Hi Georges-André Janett

Could you please try the below steps to resolve the issue:

Navigate to Azure Container Registry -> Agent Pools section -> Select the agent pool stuck in the Updating state and restart it manually.

Run the below command to check the registry status in Azure CLI:
az acr show --name <registry-name>

Try updating the agent pool:
az acr agentpool update --name <agentpool-name> --resource-group <resource-group>
If this fails, try re-assigning the pool:
az acr agentpool assign --name <agentpool-name> --registry <registry-name>

Restarting the ACR might resolve the stuck update:
az acr agent-pool restart --name <YourAgentPoolName> --registry-name <YourRegistryName> --resource-group <YourResourceGroup>
(or)
az acr update --name <registry-name> --resource-group <resource-group>

If updating doesn’t work, you may need to delete and recreate the agent pools: Delete the agent pool forcefully:
az acr agentpool delete --name <agentpool-name> --resource-group <resource-group> --force
and recreate a new agent pool:
az acr agentpool create --name <new-agentpool-name> --resource-group <resource-group>

Hope this helps!

Please Let me know if you have any queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-14T10:58:57.1966667+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know. Thank You.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-15T08:37:23.3433333+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know. Thank You.
Georges-André Janett 20 Reputation points

2025-05-19T14:58:42.0333333+00:00
Hi @Durga Reshma Malthi , thank you for you reply and for your patience regarding mine.

Unfortunately I cannot reboot said agent all options are greyed out.

Status looks good : "provisioningState": "Succeeded"

I had to modify the command to make it work
az acr agentpool update --name agentName --registry registryName --resource-group rg-name
returns : (RegistryStatusConflict) Cannot perform the operation as the resource 'agetnName' is in 'Updating' state.

Code: RegistryStatusConflict

Message: Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Target: request
4. 'agent-pool' is misspelled or not recognized by the system. Did you mean 'agentpool' ? I update it. But still : az acr agentpool restart --name AgentName --registry-name registryName --resource-group rg-name

'restart' is misspelled or not recognized by the system.

the following arguments are required: --registry/-r
I update it
unrecognized arguments: --force
I remove it and try again
Are you sure you want to delete the agentpool 'agentName' in registry 'registryName'? (y/n): y

(RegistryStatusConflict) Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Code: RegistryStatusConflict

Message: Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Target: request

And here lies my probleme. The agent pool is stuck in updating state and I cannot delete it forcefully.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-19T16:39:34.54+00:00
Hi Georges-André Janett

Since the agent pool is still stuck in Updating, there might be a pending operation preventing changes. Run the following command to check for any ongoing tasks:

az acr agentpool show --name agentName --resource-group rg-name --registry registryName

Look for any status messages indicating an incomplete operation.

Ensure that there is no resource locks applied to the agent pool or the registry that might prevent modifications or deletions.
If the update process is stuck, you can try stopping it manually:

az acr agentpool update --name agentName --resource-group rg-name --registry registryName --set provisioningState=Failed

This might allow you to delete the agent pool afterward.

If CLI commands aren't working, you can try deletion via Azure Resource Manager:

Go to Azure Portal → Navigate to Azure Container Registry and then find the stuck agent pool -> Click JSON View. Manually edit the state to Failed and try deleting it.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-20T08:07:00.9333333+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.

Georges-André Janett 20

@Durga Reshma Malthi thank you for the follow up, here is the latest feedback

az acr agentpool show --name agentName --resource-group rg-name --registry registryName

Returned this (spoiler alert, nothing fancy)

{
  "count": 1,
  "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/anonymized-rg/providers/Microsoft.ContainerRegistry/registries/anonymized-registry/agentPools/anonymized-agentpool",
  "location": "switzerlandnorth",
  "name": "devops",
  "os": "Linux",
  "provisioningState": "Updating",
  "resourceGroup": "anonymized-rg",
  "systemData": {
    "createdAt": "2024-06-24T13:38:41.559515+00:00",
    "createdBy": "anonymous@example.com",
    "createdByType": "User",
    "lastModifiedAt": "2025-04-20T00:13:56.775831+00:00",
    "lastModifiedBy": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "lastModifiedByType": "Application"
  },
  "tags": null,
  "tier": "S1",
  "type": "Microsoft.ContainerRegistry/registries/agentPools",
  "virtualNetworkSubnetResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/anonymized-rg/providers/Microsoft.Network/virtualNetworks/anonymized-vnet/subnets/anonymized-subnet"
}

az acr agentpool update --name agentName --resource-group rg-name --registry registryName --set provisioningState=Failed

returns
unrecognized arguments: --set provisioningState=Failed

Go to Azure Portal → Navigate to **Azure Container Registry and then find the stuck agent pool -> Click JSON View**. Manually edit the state to Failed and try deleting it.

Looked promising but unfortunately, where I find the stuck agent I don't have the Json View. And In the overview of the Container Registry (where I can see the Json view) I don't see the "Updating" status (and the json is in read only mode)
But it offers a fresh axe of action. I'm going to try the ARM way.

Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-21T10:57:27.65+00:00
Hi Georges-André Janett

Could you please try the below commands:

az acr show --name <ACR_NAME> --query provisioningState

If the state is "Failed" or "Pending", proceed with the reset.

Try restarting the registry to refresh its state:

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

If this doesn't work, try restarting the entire resource group:

az group deployment operation list --resource-group <RESOURCE_GROUP>

If restarting doesn’t work, try forcing an update using Azure Resource Manager: This forces the provisioning state to Succeeded, but it may require admin permissions.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

az container restart --name <CONTAINER_NAME> --resource-group <RESOURCE_GROUP>

Hope this helps!

Please Let me know if you have any queries.
Georges-André Janett 20 Reputation points

2025-05-21T12:56:37.16+00:00

az acr show --name <ACR_NAME> --query provisioningState

"Succeeded"

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

Shows a lot but nothing related to the Agent Pool

az group deployment operation list --resource-group <RESOURCE_GROUP>

This concerns the deployment and nothing is stuck in the updating state. Only Succeeded or Failed. Anyway it requires the name of the deployment (the following arguments are required: --name/-n) and it is not something I have since it's not a deployment issue but an update on the Agent Pool.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

--resource-type is required

=> -az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded -resource-type Microsoft.ContainerRegistry/registries
=> result gives nothing on the agent pool state.

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

It is not related to Azure Container Instance but to ACR Agent Pool

https://learn.microsoft.com/en-us/cli/azure/acr/agentpool?view=azure-cli-latest

Thank you Durga Reshma Malthi, your help is really appreciated.
Georges-André Janett 20 Reputation points

2025-05-21T13:15:39.8133333+00:00

az acr show --name <ACR_NAME> --query provisioningState

"Succeeded"

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

Shows a lot but nothing related to the Agent Pool

az group deployment operation list --resource-group <RESOURCE_GROUP>

This concerns the deployment and nothing is stuck in the updating state. Only Succeeded or Failed. Anyway it requires the name of the deployment (the following arguments are required: --name/-n) and it is not something I have since it's not a deployment issue but an update on the Agent Pool.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

--resource-type is required

=> -az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded -resource-type Microsoft.ContainerRegistry/registries => result gives nothing on the agent pool state.

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

It is not related to Azure Container Instance but to ACR Agent Pool

https://learn.microsoft.com/en-us/cli/azure/acr/agentpool?view=azure-cli-latest

Thank you Durga Reshma Malthi, your help is really appreciated.
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-23T11:04:20.2533333+00:00

Hi Georges-André Janett,

Thank you for the detailed information and your thorough troubleshooting efforts. You've correctly identified that the provisioning state Updating is read-only and cannot be overridden via CLI or ARM APIs. This is a backend-side stale state issue, often caused by an interrupted or untracked provisioning event (network, VNET misconfiguration, or control plane glitch).

Since deletion, update, and override attempts are all blocked with RegistryStatusConflict, and your agent pool JSON confirms no recent modification since April 2025, this is a backend issue that requires manual state correction from backend

You've already provided all required identifiers. Will need some more details from you, please check your private message.

We’ll keep you posted once the backend reset is complete.
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-26T03:30:47.69+00:00

One quick question Georges-André Janett, have you tried?

az acr agentpool update -n devops -r crimdpreprod -g rg-devops-preprod --count 0 on both of the agent pools?
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-27T09:04:16.5566667+00:00

Georges-André Janett did you pass the --count flag? I have updated the pool status on my end, I'm going to wait to see if the remediation service kicks in, but you can try to update --count to 0 again
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-29T05:40:44.8866667+00:00

Georges-André Janett we have taken some action from backend. Could you check once and confirm now if the issue is resolved?

Accepted answer

0 additional answers

Your answer

Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-13T15:31:55.0833333+00:00

Hi Georges-André Janett

Could you please try the below steps to resolve the issue:

Navigate to Azure Container Registry -> Agent Pools section -> Select the agent pool stuck in the Updating state and restart it manually.

Run the below command to check the registry status in Azure CLI:
az acr show --name <registry-name>

Try updating the agent pool:
az acr agentpool update --name <agentpool-name> --resource-group <resource-group>
If this fails, try re-assigning the pool:
az acr agentpool assign --name <agentpool-name> --registry <registry-name>

Restarting the ACR might resolve the stuck update:
az acr agent-pool restart --name <YourAgentPoolName> --registry-name <YourRegistryName> --resource-group <YourResourceGroup>
(or)
az acr update --name <registry-name> --resource-group <resource-group>

If updating doesn’t work, you may need to delete and recreate the agent pools: Delete the agent pool forcefully:
az acr agentpool delete --name <agentpool-name> --resource-group <resource-group> --force
and recreate a new agent pool:
az acr agentpool create --name <new-agentpool-name> --resource-group <resource-group>

Hope this helps!

Please Let me know if you have any queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-14T10:58:57.1966667+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know. Thank You.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-15T08:37:23.3433333+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know. Thank You.
Georges-André Janett 20 Reputation points

2025-05-19T14:58:42.0333333+00:00

Hi @Durga Reshma Malthi , thank you for you reply and for your patience regarding mine.

Unfortunately I cannot reboot said agent all options are greyed out.

Status looks good : "provisioningState": "Succeeded"

I had to modify the command to make it work
az acr agentpool update --name agentName --registry registryName --resource-group rg-name
returns : (RegistryStatusConflict) Cannot perform the operation as the resource 'agetnName' is in 'Updating' state.

Code: RegistryStatusConflict

Message: Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Target: request
4. 'agent-pool' is misspelled or not recognized by the system. Did you mean 'agentpool' ? I update it. But still : az acr agentpool restart --name AgentName --registry-name registryName --resource-group rg-name

'restart' is misspelled or not recognized by the system.

the following arguments are required: --registry/-r
I update it
unrecognized arguments: --force
I remove it and try again
Are you sure you want to delete the agentpool 'agentName' in registry 'registryName'? (y/n): y

(RegistryStatusConflict) Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Code: RegistryStatusConflict

Message: Cannot perform the operation as the resource 'agentName' is in 'Updating' state.

Target: request

And here lies my probleme. The agent pool is stuck in updating state and I cannot delete it forcefully.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-19T16:39:34.54+00:00

Hi Georges-André Janett

Since the agent pool is still stuck in Updating, there might be a pending operation preventing changes. Run the following command to check for any ongoing tasks:

az acr agentpool show --name agentName --resource-group rg-name --registry registryName

Look for any status messages indicating an incomplete operation.

Ensure that there is no resource locks applied to the agent pool or the registry that might prevent modifications or deletions.
If the update process is stuck, you can try stopping it manually:

az acr agentpool update --name agentName --resource-group rg-name --registry registryName --set provisioningState=Failed

This might allow you to delete the agent pool afterward.

If CLI commands aren't working, you can try deletion via Azure Resource Manager:

Go to Azure Portal → Navigate to Azure Container Registry and then find the stuck agent pool -> Click JSON View. Manually edit the state to Failed and try deleting it.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-20T08:07:00.9333333+00:00

Hi Georges-André Janett

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.
Georges-André Janett 20 Reputation points

2025-05-21T09:25:54.21+00:00

@Durga Reshma Malthi thank you for the follow up, here is the latest feedback

az acr agentpool show --name agentName --resource-group rg-name --registry registryName

Returned this (spoiler alert, nothing fancy)

{ "count": 1, "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/anonymized-rg/providers/Microsoft.ContainerRegistry/registries/anonymized-registry/agentPools/anonymized-agentpool", "location": "switzerlandnorth", "name": "devops", "os": "Linux", "provisioningState": "Updating", "resourceGroup": "anonymized-rg", "systemData": { "createdAt": "2024-06-24T13:38:41.559515+00:00", "createdBy": "anonymous@example.com", "createdByType": "User", "lastModifiedAt": "2025-04-20T00:13:56.775831+00:00", "lastModifiedBy": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "lastModifiedByType": "Application" }, "tags": null, "tier": "S1", "type": "Microsoft.ContainerRegistry/registries/agentPools", "virtualNetworkSubnetResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/anonymized-rg/providers/Microsoft.Network/virtualNetworks/anonymized-vnet/subnets/anonymized-subnet" }

az acr agentpool update --name agentName --resource-group rg-name --registry registryName --set provisioningState=Failed

returns
unrecognized arguments: --set provisioningState=Failed

Go to Azure Portal → Navigate to **Azure Container Registry and then find the stuck agent pool -> Click JSON View**. Manually edit the state to Failed and try deleting it.

Looked promising but unfortunately, where I find the stuck agent I don't have the Json View. And In the overview of the Container Registry (where I can see the Json view) I don't see the "Updating" status (and the json is in read only mode)
But it offers a fresh axe of action. I'm going to try the ARM way.
Durga Reshma Malthi 4,430 Reputation points Microsoft External Staff Moderator

2025-05-21T10:57:27.65+00:00

Hi Georges-André Janett

Could you please try the below commands:

az acr show --name <ACR_NAME> --query provisioningState

If the state is "Failed" or "Pending", proceed with the reset.

Try restarting the registry to refresh its state:

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

If this doesn't work, try restarting the entire resource group:

az group deployment operation list --resource-group <RESOURCE_GROUP>

If restarting doesn’t work, try forcing an update using Azure Resource Manager: This forces the provisioning state to Succeeded, but it may require admin permissions.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

az container restart --name <CONTAINER_NAME> --resource-group <RESOURCE_GROUP>

Hope this helps!

Please Let me know if you have any queries.
Georges-André Janett 20 Reputation points

2025-05-21T12:56:37.16+00:00

az acr show --name <ACR_NAME> --query provisioningState

"Succeeded"

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

Shows a lot but nothing related to the Agent Pool

az group deployment operation list --resource-group <RESOURCE_GROUP>

This concerns the deployment and nothing is stuck in the updating state. Only Succeeded or Failed. Anyway it requires the name of the deployment (the following arguments are required: --name/-n) and it is not something I have since it's not a deployment issue but an update on the Agent Pool.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

--resource-type is required

=> -az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded -resource-type Microsoft.ContainerRegistry/registries
=> result gives nothing on the agent pool state.

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

It is not related to Azure Container Instance but to ACR Agent Pool

https://learn.microsoft.com/en-us/cli/azure/acr/agentpool?view=azure-cli-latest

Thank you Durga Reshma Malthi, your help is really appreciated.
Georges-André Janett 20 Reputation points

2025-05-21T13:15:39.8133333+00:00

az acr show --name <ACR_NAME> --query provisioningState

"Succeeded"

az acr update --name <ACR_NAME> --resource-group <RESOURCE_GROUP>

Shows a lot but nothing related to the Agent Pool

az group deployment operation list --resource-group <RESOURCE_GROUP>

This concerns the deployment and nothing is stuck in the updating state. Only Succeeded or Failed. Anyway it requires the name of the deployment (the following arguments are required: --name/-n) and it is not something I have since it's not a deployment issue but an update on the Agent Pool.

az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded

--resource-type is required

=> -az resource update --name <ACR_NAME> --resource-group <RESOURCE_GROUP> --set properties.provisioningState=Succeeded -resource-type Microsoft.ContainerRegistry/registries => result gives nothing on the agent pool state.

If the provisioning issue is related to ACIS, restart the container instance to refresh the connection between ACIS and ACR

It is not related to Azure Container Instance but to ACR Agent Pool

https://learn.microsoft.com/en-us/cli/azure/acr/agentpool?view=azure-cli-latest

Thank you Durga Reshma Malthi, your help is really appreciated.
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-23T11:04:20.2533333+00:00

Hi Georges-André Janett,

Thank you for the detailed information and your thorough troubleshooting efforts. You've correctly identified that the provisioning state Updating is read-only and cannot be overridden via CLI or ARM APIs. This is a backend-side stale state issue, often caused by an interrupted or untracked provisioning event (network, VNET misconfiguration, or control plane glitch).

Since deletion, update, and override attempts are all blocked with RegistryStatusConflict, and your agent pool JSON confirms no recent modification since April 2025, this is a backend issue that requires manual state correction from backend

You've already provided all required identifiers. Will need some more details from you, please check your private message.

We’ll keep you posted once the backend reset is complete.
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-26T03:30:47.69+00:00

One quick question Georges-André Janett, have you tried?

az acr agentpool update -n devops -r crimdpreprod -g rg-devops-preprod --count 0 on both of the agent pools?
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-27T09:04:16.5566667+00:00

Georges-André Janett did you pass the --count flag? I have updated the pool status on my end, I'm going to wait to see if the remediation service kicks in, but you can try to update --count to 0 again
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-29T05:40:44.8866667+00:00

Georges-André Janett we have taken some action from backend. Could you check once and confirm now if the issue is resolved?

Answer 1

Hello Georges-André Janett,

Thank you for reporting this.

The issue you were experiencing where the Azure Container Registry (ACR) agent pool gets stuck in the "Updating" state typically occurs when an update operation (such as resizing or scaling the pool) fails to complete and the resource becomes locked in a transitional state. This prevents further operations like updating, deleting, or scaling the agent pool, and results in errors like:


(RegistryStatusConflict) Cannot perform the operation as the resource 'devops' is in 'Updating' state.

What was done to fix this?

In your case, we resolved the issue through a backend remediation. I've manually reset the provisioning state of the agent pool using internal tools. Once that was done, the az acr agentpool update command succeeded.

The command that was used to scale the pool to zero was-


az acr agentpool update -n devops -r crimdpreprod -g rg-devops-preprod --count 0

After the backend state was corrected, the command executed successfully, confirming that the agent pool had exited the "Updating" state and was back in a healthy "Succeeded" state.

The stuck state was due to an incomplete or failed internal update that did not finish properly. This left the agent pool in a locked provisioning state. These situations require manual intervention as Azure’s automatic remediation may not always recover them promptly.

It would be great if you could kindly mark the answer as accepted so that anyone having similar query on MS QnA forum can refer to this and be benefited from it. Thanks

enter image description here

Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-05-29T19:10:42.9433333+00:00

Hi Georges-André Janett, please do not forget to accept and upvote the answer.
Arko 4,150 Reputation points Microsoft External Staff Moderator

2025-06-02T04:50:27.0033333+00:00

Hello Georges-André Janett, following up on this.

Share via

How to unblock Linux agent pool for container registry stuck in the "Update" state

0 additional answers

Your answer