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.
.
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.
Log into the new Azure Portal.
Go to the Subscriptions View.
Set your account as a Co-Admin. Microsoft Documentation.
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?
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.
Related
I am trying to create an ASP.NET framework app in Azure so i followed the tutorial on the Azure website but while publishing there is always a problem logging in.
I have tried to login several times and it is all successful but i am unable to proceed with creating app services. The page will still be the same page asking to login or create an account.
I am also login to my visual studio 2017 enterprise with the same account so i am wondering why i can't proceed on.
Thank you
According to your description, I suppose you haven't buy the Azure. You could buy Azure from this link. After that, your account could use Azure. Then you could get Subscription for Azure portal. You could also create Resource Group and App Service Plan from Azure portal.
If you want to use Azure for free,you can use trial version.Just like the following screenshot. However, it has use time and function limit.
I'm trying to add a release to VSTS. Our VSTS is backed by Azure AD and I have logged in with the account that is the admin of the Azure subscription to which I want to deploy the release. I can see the Azure subscription in the dropdown but when I click Authorize I get the following error popup.
The reason is that the authentication pop-up window has been blocked, turn pop-up blocker off or change another browser and try again.
Change security and privacy settings for Internet Explorer 11
On the other hand, you also can manual configure the azure service endpoint, refer to this article below (manual configuration section)
Automating Azure Resource Group deployment using a Service Principal in Visual Studio Online: Build/Release Management
We have a Visual Studio Team Services instance that is used by the company I work for.
The company has an Azure instance. As far as I am aware there is no connection to VSTS.
When I was added to VSTS as a Visual Studio Pro level user some months ago we had to use my Microsoft Account as we couldn't use my work identity because my MSDN subscription is linked to my Microsoft Account as we could not link it to my work identity; apparently this was because we use Office365 in the office.
We now have problems adding Basic Users to VSTS. I enter the users Microsoft Account identity and I am told "No Identities Found".
I looked at VSTS Settings where I can see "This account is backed by the Default Directory Azure Active Directory."
I can also see an "Azure Subscription ID". When I follow the Subscription ID link I end up at my Microsoft Account Azure instance.
I had other users log in to VSTS and they too are seeing my Azure Subscription ID in VSTS Settings.
Why is this happening?
How do Azure instances/accounts relate to VSTS instances/accounts
Can I break the link between Azure and VSTS
You can link your VSTS account to the azure from your azure portal:
Azure - VSTS service
Then, what we do is to add the users to the Azure active directories. As far as I know, these users must be registered in Microsoft.
Once it's done, you can add the users to the VSTS.
Hope it helps you.
The Team Services uses an Azure subscription to bill purchases and can control access with Azure AD.
You can unlink your VSTS account from Azure portal. More information, you can refer to this article: Delete or recover Visual Studio Team Services account
I am an idiot.
Turns out the company VSTS was linking to the company Azure.
I became confused when clicking the Manage button in VSTS | Azure Subscription ID.
That took me to the Sign in to Azure page and displayed my login, which takes me my Azure.
It was only when we checked the Azure Subscription ID in VSTS against my Azure Subscription ID that it became apparent I was following a red herring. The ID matched the companies Azure ID. So I can use that to add users and subsequently add them to VSTS.
I have a question regarding Visual Studio Team services / Azure Web App deploy
in order to get my app be published using the Azure Web app deployment in release process, I had to grant access as co-administrator on my azure subscription using the old management manage.windowsazure.com
Is there any way to do the same thing using the new portal.azure.com ?
As we work as a big team, I would like to be very restrictive on users right and I do not want everybody to be co-admin. Is there any other way to grant publishing privileges on specific account (we use an Azure AD connected to VSTS) without giving Azure co admin privileges ?
#Thierry,
new new portal "https://portal.azure.com", you can config access with role base access management.where you can more granular permission (read/contributor/owner) to a user for a specific resources (service/resource group/subscriptions etc ...)
See more details from this articile https://azure.microsoft.com/en-us/documentation/articles/role-based-access-control-configure/
hope this will help!
What is the difference between these two portals and why? And when should I use which of them?
For example:
When I want to configure if/which Java version I want to use in a WebApp, in the "manage"-portal I only can choose between off and v1.7.0_51. In the "portal"-portal I can choose between off, v7 and v8.
Or, if I want to create a new Ubuntu-VM, in the "manage"-portal I can choose between v12.04, v14.04 and v15.04. In the "portal"-portal there is only v14.04.
As commented by Mike, manage.windowsazure.com is the current production Azure Portal while portal.azure.com is the preview portal which will eventually replace the production portal.
From an underlying technology perspective, there's one big difference between the production and preview portal. Production portal makes use of Azure Service Management API while the Preview portal makes use of Azure Resource Manager (ARM). Along with ARM API, you get Role-based access control (RBAC) that enables you to grant granular permissions on your Azure resources to your team members. In the production portal, there's only a concept of Subscription Administrator and Subscription Co-Administrator.
Not all services in Azure has been ported to make use of ARM API as of today and that's why you see only few services in the preview portal. Services that make use of ARM API (all the new services) will only show up the preview portal.
As to when to use what portal, just see the Azure services you need to manage. Based on how they can be managed, you will choose between production and preview portal. Also please note that functionality for a service may differ between portals even though it is present in both portals. That may be another criteria between choosing the portal.
More information Can be find from microsoft site
Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources