This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 59%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
I'm currently using cloud services (classic). I'm aware it's retiring by 1st of September and am trying to migrate the resource. Since the cloud service was created before 2018 I was trying to follow the steps suggested here. I managed to create a staging deployment and swap it with production. Then deleted staging (as both slots cannot be used when doing the migration) and tried to do the in-place migration which seemed promising as at least the first step succeeded. However, there was an error that the vmSize "Small" was deprecated. I updated the config file to have vmsize="Standard_A1" as suggested here. I exported the new package with the needed files but when trying to upload it to staging again I get an error that something went wrong but not much more than that. The operation log doesn't show any details.
The activity log doesn't show any errors either and looks like it created the deployment slot but when uploading details it fails.
This is all I'm seeing in the classic log:
I saw a suggestion somewhere this could be an allocation error? But I don't see any indication anywhere what the error ACTUALLY is. I created a new cloud service and when trying to upload deployment with the wrong certificate thumbprint I got an error. But when I updated it then again got the same vague "Deployment could not be created. There was an error processing your request. Try again in a few moments" error even though no deployments have been made to this cloud service so this shouldn't be an allocation error?
Within the older cloud service I tried uploading the deployment with the old settings and that still gave me an error.
Please help me troubleshoot this as I'm at a loss at the moment of what's happening.
Hello Ewa
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
'Standard_A1' is not a valid VM SKU name. you would need to use 'Standard_A1_v2'
Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/av2-series
Can you please try with this SKU and see if that helps.
Hope this helps.
I updated the config but it still failed unfortunately. As I mentioned before it's failing even with the settings I had originally even though I managed to get those on staging once before.
Hello Ewa
Thanks for responding back and adding more details.
This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case.
When trying to create the Cloud Service Extended Support from scratch I realised that Standard_A1_v2 is not a size that can be used for my region (Europe) and had to go with a different size so that was potentially one of the issues before reaching out to support.
The main issue was that the migration wasn't aborted properly previously. There were no specific errors or logs to show it but when trying the do the ARM migration again, going through the validation and preparation step and then clicking abort it seems to have resolved the issue. The cloud service was in a state of lock and didn't allow updated or creating new deployments.
The new service I created also had an incorrect type of certificate attached to it. Again, there were no specific logs or errors that showed me this information but technical support was able to see these errors on their end.
Hello Ewa
Thanks for responding back and sharing the details for the benefit of community.