Problems deploying Extended Services error is change server

Question

Problems deploying Extended Services error is change server

Brian Williams 0

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'

I have tried a lower and higher server like Standard_D2_v3, we have been packaging via Visual Studio. I can package and deploy to our QA Subscription without issue that's in the same central US region. I have listed all the available servers, asked chat what one is compatible with Azure Compute Extended Services and it said none. I also don't see Standard_D4_v3 or Standard_D2_v3 in the list.

Brian Williams 0 Reputation points

2025-08-19T19:30:27.9366667+00:00

I have checked my resource limits or quotas, well under on both. We are currently running Standard_D4_v3 and I'm trying to stage the same and lower / higher versions for a flip. Just tried Standard_D2as_v6 it comes back with Failed to update the deployment for cloud service 'nextup.web'. Reason: Requested operation cannot be performed because VM size Standard_D2as_v6 does not support PaaS deployments.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-19T20:36:57.87+00:00
Hi Brian Williams

The error message you're seeing is accurate: Standard_D2as_v6 does not support PaaS deployments, specifically Azure Cloud Services (classic or extended).

These are fully compatible with Azure Cloud Services (Extended Support):

Standard_D2_v3

Standard_D4_v3

Standard_D8_v3

Standard_D16_v3

If you don’t see these sizes listed, it could be due to:

Regional availability (even within Central US, some zones may differ)

Subscription restrictions or feature flags

Run this command to list available sizes in your region:

az vm list-sizes --location "Central US"

Hope this helps!

Please Let me know if you have any queries.
Brian Williams 0 Reputation points

2025-08-19T21:34:28.2+00:00

I've tried 4 VM Sizes from the list of available sizes. Always in the same result... this has happened before recently in our QA subscription, we did nothing to fix it just started working again a day or so later. We are going on 3 days now where it just won't take any size.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T00:23:42.3866667+00:00

Hi Brian Williams

Even within Central US, try deploying to a different availability zone or region temporarily.

Instead of flipping the VM size in the same cloud service, try creating a new cloud service with the same configuration and deploy there.

Hope this helps!

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

2025-08-20T16:00:23.02+00:00

Hi Brian Williams

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.
Brian Williams 0 Reputation points

2025-08-20T18:14:32.3533333+00:00

It turned out to be related to the swap selection.

When we deleted the previous stage after encountering an error, it broke the circular reference between the stage and the production compute. Later, when I uploaded a new stage and selected our production environment as the swap target, production still had a pointer to the stage we had already deleted.

At least, that’s how I understood it. The reported error was misleading, it indicated that the compute wasn’t available, when in reality the issue was the broken swap reference.

Publishing works correctly if no swap is selected.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T18:37:54.1433333+00:00

Hi Brian Williams

Thanks for your update.

1 answer

Your answer

Brian Williams 0 Reputation points

2025-08-19T19:30:27.9366667+00:00

I have checked my resource limits or quotas, well under on both. We are currently running Standard_D4_v3 and I'm trying to stage the same and lower / higher versions for a flip. Just tried Standard_D2as_v6 it comes back with Failed to update the deployment for cloud service 'nextup.web'. Reason: Requested operation cannot be performed because VM size Standard_D2as_v6 does not support PaaS deployments.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-19T20:36:57.87+00:00

Hi Brian Williams

The error message you're seeing is accurate: Standard_D2as_v6 does not support PaaS deployments, specifically Azure Cloud Services (classic or extended).

These are fully compatible with Azure Cloud Services (Extended Support):

Standard_D2_v3

Standard_D4_v3

Standard_D8_v3

Standard_D16_v3

If you don’t see these sizes listed, it could be due to:

Regional availability (even within Central US, some zones may differ)

Subscription restrictions or feature flags

Run this command to list available sizes in your region:

az vm list-sizes --location "Central US"

Hope this helps!

Please Let me know if you have any queries.
Brian Williams 0 Reputation points

2025-08-19T21:34:28.2+00:00

I've tried 4 VM Sizes from the list of available sizes. Always in the same result... this has happened before recently in our QA subscription, we did nothing to fix it just started working again a day or so later. We are going on 3 days now where it just won't take any size.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T00:23:42.3866667+00:00

Hi Brian Williams

Even within Central US, try deploying to a different availability zone or region temporarily.

Instead of flipping the VM size in the same cloud service, try creating a new cloud service with the same configuration and deploy there.

Hope this helps!

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

2025-08-20T16:00:23.02+00:00

Hi Brian Williams

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.
Brian Williams 0 Reputation points

2025-08-20T18:14:32.3533333+00:00

It turned out to be related to the swap selection.

When we deleted the previous stage after encountering an error, it broke the circular reference between the stage and the production compute. Later, when I uploaded a new stage and selected our production environment as the swap target, production still had a pointer to the stage we had already deleted.

At least, that’s how I understood it. The reported error was misleading, it indicated that the compute wasn’t available, when in reality the issue was the broken swap reference.

Publishing works correctly if no swap is selected.
Durga Reshma Malthi 11,400 Reputation points Microsoft External Staff Moderator

2025-08-20T18:37:54.1433333+00:00

Hi Brian Williams

Thanks for your update.

Answer 1

Hi Brian Williams

Ensure that your Azure subscription has not hit any resource limits or quotas. You can check your subscription quotas in the Azure portal under Subscriptions -> Usage + quotas.
Verify that the VM sizes you are trying to deploy (e.g., Standard_D2_v3, Standard_D4_v3) are available in the region you are deploying to. Sometimes, specific VM sizes may not be available in certain regions.
Sometimes, transient issues can cause provisioning failures. Try redeploying the resource after some time.
If the specific VM sizes you are trying to use are not available, consider using alternative sizes that meet your requirements. If you are using Azure Compute Extended Services, ensure that the VM sizes you are trying to deploy are compatible with these services.
Consider using newer or ACES-compatible VM sizes like the Dalsv6-series or Daldsv6-series, which use AMD EPYC processors and are optimized for modern workloads

Refer to these documents:

Additional References:

https://github.com/Azure/RDS-Templates/issues/373

Hope this helps!

Please Let me know if you have any queries.

Share via

Problems deploying Extended Services error is change server

1 answer

Your answer