But can someone figure out how to get out of this catch 22? All I want is to have a cloud service on a domain. I understand that classic cloud service is deprecated, and I'm fine with being on cloud services extended support. So this is something that has changed in the last 2 weeks. I should also mention that 2 weeks ago, I made a classic cloud service for testing purposes and I was able to deploy to it. And I can't start on extended support, because then I can't have a address.
So I seem to be stuck in a catch 22 I can't migrate to extended support without making a deployment, and I can't make a deployment without being on extended support. It wouldn't let me do that without a deployment, and it wouldn't let me make a deployment because I received the error message above. I tried migrating the empty cloud service I had created to extended support, so that I could have an extended support cloud service but be able to keep the domain. This won't do because our applications are hardcoded to use the address. So I tried to make a cloud service (extended support), but when I make an extended support cloud service, it only lets me use a address, not a address. I tried creating a new cloud service (classic) and was able to do so, but I was unable to deploy to the cloud service, because I received an error saying, "Please use cloud services (extended support) instead of cloud services (classic)." Someone accidentally deleted the cloud service, but we still had the data, so I went to recreate it. We had a cloud service (classic) running on a domain.
0 kommentar(er)
