CODEWITHSUNDEEP
azuresubscriptionazure-cloud-servicesazure-deployment
Krishna_K_Batham
Krishna_K_Batham

Reputation: 310

Azure cloud service deployment issue with pay as you go subscription - cloud services are not available in this subscription

I am having an issue while deploying an Azure web role to a cloud service. It shows me the error

Cloud services are not available in this subscription.

I am using a pay as you go subscription on Azure. I don't know if there is any limitation with this subscription for cloud service deployment or not.

Error Details.

Upvotes: 8

Views: 4128

Answers (3)

ChasetopherB
ChasetopherB

Reputation: 464

Updated version of JerryGoyal's solution.

Cloud Service Management will have to be done using the new Azure Portal, because Cloud Service Management in the old portal will be disabled as of 11/15/2017.

Upvotes: 10

GorvGoyl
GorvGoyl

Reputation: 49570

Cloud services are not available in this subscription

The error is caused because the Cloud Services still use the old deployment model that is based on Azure Service Management (ASM).
To deploy an ASM based component to Azure you need to be ‘co-admin’ for the subscription.

Right now you are ‘Owner’ on the new portal but this role only has impact on the new ARM based resources.

So, just ask your subscription admin to login to the old portal (https://manage.windowsazure.com) and make you co-administrator:

  • Login to the old portal
  • Click on Settings –> Administrators
  • Click on the Add button at the bottom
  • Enter the co-admin email address and click on the OK button.

After this reload your Visual Studio and the problem will be solved.

Upvotes: 4

bmoore-msft
bmoore-msft

Reputation: 8737

I think the issue you're running into is that the Cloud Service Publish Wizard in VS only supports subscriptions in which you are an admin or co-admin granted via via the old portal (manage.windowsazure.com). If you've been given access via RBAC or the new portal, then VS will not see the resources under those subscriptions.

To work around it, you can build the package using msbuild.exe and then upload it via the portal.

That help?

Upvotes: 5

Related Questions