My customer added my microsoft profile to his subscription as owner.
I logged to Visual Studio with this profile and try to publish cloud service. But I get an error:
why so and how to fix it?
Cloud services are not available in this subscription.
This error is caused because for Azure Service Management (ASM) resources you should be co-admin in order to deploy services.
If you look on the new portal, you can see that you have permission for publishing on this subscription but one thing to keep in mind is that this “Owner” role is only valid for Azure Resource Manager resources. Even though you can manage Cloud Services on the new portal, it is an ASM resource and that’s why this role is not applicable for it. Roles configured on the new portal are RBAC and they are only valid for ARM resources.
So, you should ask for the subscription an Admin to add your user as co-admin on the old portal.
More information about co-admin and owner, please refer to this blog.
Update:
Sorry for my mistake.
For now, we should use new portal to add co-administrator, like this:
More information about add Co-administrator via new portal, please refer to this link.
User should be added as co-administrator, not only as owner. More information about it here:
https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/
Ability to add user as co-administrator is already added to new portal (and deprecated on old portal):
Related
I am trying to set up octopus to deploy resources to azure.
Under azure active directory I've added a new app registration, and have generated a key and hooked up octopus with the correct Application ID, Tenant ID and key
The organisation has multiple azure subscriptions corresponding to the environments, so I've noticed if I use the Subscription ID of my "Visual Studio Professional MSDN" subscription it works and creates the resources, however if I try to use any of the other organisation Subscription IDs I get the following error:
Login-AzureRmAccount : The provided account c0b2.......76a6 does not
have access to subscription ID "f06.......2aa3". Please try logging in
with different credentials or a different subscription ID.
I have looked through all the settings of the Application Registration and granted it every "Windows Azure Active Directory" permission available, but still no luck.
How do I go about granting permissions to this Application Registration so that it can access the relevant subscriptions?
You need to give the app a role on the subscription/resource group/resource you want it to be able to access.
So for example, you can go to the Access Control (IAM) tab of the subscription, and give the app the Contributor role, which allows the app to read and modify anything in the subscription.
You can also give a more limited role if desired.
Roles can also be applied at a lower scope, like a resource group.
More info in the docs: https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal
We have purchased one Pay-As-You-Go subscription that was not visible in azure old portal (management portal)
but its visible in new portal!
I have given the contributer role
Please let me know how I can add in old management portal
Thank,
Nihal
In order to access old management portal, you need to be added as a co-administrator there. A Contributor role is specific to Azure's Role-based access control (RBAC) and only new portal is aware of them. Old portal doesn't know anything about RBAC and only users added as administrators (administrators, co-administrator, service administrator etc.) can access old portal.
Please ask your account administrator to add you as a co-administrator. Please see this link for more details: https://azure.microsoft.com/en-in/documentation/articles/billing-add-change-azure-subscription-administrator/.
I don't really understand why on this case. My company has an azure subscription for development/testing environment.
At the beginning I am co-admin on this subscription with my Microsoft account. Now I need to manage applications under Azure AD of that subscription. So my Microsoft Account is leveraged to Global Admin of this Azure AD.
But even my MS account is leveraged to Global Admin, I cannot see or have access to Azure AD.
After searching around and based on this article:
https://blogs.msdn.microsoft.com/dstfs/2015/12/23/issues-with-azure-active-directory-guest-users-in-aad-backed-visual-studio-team-services-accounts/
I am GUEST (user type) on Azure AD, so even I am global admin, I still cannot have access to this Azure AD.
From the link, this happens because:
One way you can become an AAD GUEST is when you are made a co-admin on an Azure subscription before being added to the AAD associated with it
It can be fixed by using powershell like #CtrlDo's answer. But you have to create an global admin with work/school account since this approach does not work with Microsoft account:
PowerShell - Connecting to Azure Active Directory using Microsoft Account
We have another approach which can be done in the UI that we think it's simpler:
Remove my account out of co-admins of subscription.
Remove my account out of Azure AD.
Add my account back to Azure AD as Global Admin.
Add my account back to be co-admin on subscription.
That does work perfectly
When you were added to the AAD, your user type might have been set to "guest"
See https://azure.microsoft.com/en-us/documentation/articles/active-directory-create-users/ for more information.
See https://blogs.msdn.microsoft.com/dstfs/2015/12/23/issues-with-azure-active-directory-guest-users-in-aad-backed-visual-studio-team-services-accounts/ for an older post on how to view the issue in powershell and fix it.
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.
In Azure trial subscription my MSN email is associated with an other account with owner rights. But when I try to access Azure publishSettings it generates an error No Subscription fouund .
Please help me to resolve the issue. Do I need Co-administrator or Service Administrator rights along with owner rights ?
Service Administrator and Co-Administrator originated with the old portal at http://manage.windowsazure.com. The new portal, found at http://portal.azure.com, has introduced role based access control (RBAC), which provides the notion of Owner. You can find a lot of details about RBAC at https://azure.microsoft.com/en-us/documentation/articles/role-based-access-control-configure/.
When RBAC was rolled out, Administrators where automatically added as Owners. It's possible to be an RBAC Owner in a subscription without being an Administrator, as Owner applies to ResourceGroups or Resources within a subscription.
The webpage you're trying to use has been available for a long time and from the looks of it has not have been updated to support RBAC. The download of the publish profile from that webpage is based on selecting a subscription, which an Owner of a ResourceGroup or Resource would not necessarily have full access to everything in the subscription.
That means if you have your account added as a Co-Administrator or Service Administrator, that webpage should work.
It could be the difference between Microsoft Account and Azure Active Directory Account. Check which you are using.
I suggest you to clear all cookies, cache and temporary internet files on browser or use InPrivate/Incognito mode. Login again and it will work.
Click the "Sign Out" button and then login with the account that is associated with your trial. Owner rights should be sufficient.
You may have found an answer but in searching for an answer I found this link which says the owners you added through the Azure portal cannot manage services in the Azure classic portal.
So I MUST add co-administrator IN the classic portal so they can administer classic portal
Worked immediately after added my New Portal global admin as a co-administrator in the classic portal
nigel.jones#kloud.com.au