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.
Related
I have created an Azure DevOps organization for my company and I am trying to link this to our Azure subscription. I have followed the chat bot's instructions:
Sign in to your organization (https://dev.azure.com/{yourorganization}).
Select Organization settings.
Select Billing.
Select Set up billing.
Select your Azure subscription, and then select Save.
Billing is now setup
However, no subscription information is coming up.
Note:
(1) I am using the same Microsoft account that I do for the Azure portal
(2) When I log into the portal with these credentials, I can find the DevOps organisation under 'my organisations'
(3) I have 'owner' status on the subscription
(4) When I set up a pipeline via Visual Studio, both DevOps organisation and Azure subscription were picked up.
Could anyone tell me what is going wrong and how to fix it?
I was having the same issue and stumbled upon a solution. Posting it here in case someone else finds this post as I did via Google.
Go to https://app.vsaex.visualstudio.com/
Check to see which account your organization is on - see link below
The organization I had set up was associated with my Microsoft account. I created a new organization in the Default Directory and it found the subscription in Billing.
I'm a student so it was no problem for me to start over with a new organization. I don't know how one would transfer an existing org to the correct account if needed.
I have an Azure Organization and Devops Project assigned to my user with all the permissions setup to same as the Organiazation Owner (same email AD domain).
When I launch Azure Devops App within MS Teams, I click to Set up and it says "Sorry, you have no associated Azure DevOps organizations". The Organization Owner has no problem and can see the Option. I have rebooted, re-logged-in etc etc, checked every conceivable permission in MS Teams, OFfice 365 Admin, dev.azure.com Organization level... it still does not show the Organization in Teams.
Yet I can see the Devops Board which the Azure Devops Organization owner setup on Teams as a Tab.
Is there something I'm missing? Any help would be much appreciated.
Thank you
Thank you again for the feedback. The problem was that I had created another Azure account with my email address. I deleted the Organization but the Azure Devops add-in for MS Teams still picked the deleted Organisation as my primary Azure account despite me being assigned as an Admin to another Azure Devops Organisation and Project. It took about a week for my legacy credentials to expire and eventually I could connect to the new Azure Devops organisation.
I also received some excellent links to manage and support MS Teams integration with Devops so am posting it here in case anyone else finds it useful...
The MS teams extension for Azure DevOps has been deprecated and we suggest you to use the MS Teams apps for Azure DevOps.
https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/boards/integrations/boards-teams?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/repos/integrations/repos-teams?view=azure-devops
You could refer the below document which mentions the multi tenant feature of the MS teams app for Azure DevOps. This could help you to connect to all the organizations from different client AADs.
https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops#multi-tenant-support
Users need to be granted with at least stakeholders access at the DevOps organization level ( not just the project ). Tell the owner to add them in there.
Check this out for further references: https://learn.microsoft.com/en-us/azure/devops/organizations/security/access-levels?view=azure-devops#stakeholder-access
You can check the prerequisites in this link and check whether your account and organization meet the prerequisites:
You should have Office365 account in order to integrate Azure DevOps
Services with Microsoft Teams.
Only Azure DevOps organizations in the same organization (AAD tenant)
can be used to integrate with your Microsoft Teams account.
In addition, here is a case you can refer to.
In our organization, we have an Enterprise Azure Subscription and a few members of our team can use it with their own AD credentials.
For instance, I have the 'owner' role for my account, but don't have the login/pwd of the subscription.
However, in Visual Studio 2015, for a Azure Service, publish Azure application, I need to specify a account an choose the subscription.
And there is no subscription listed for my account.
So what should I do to be able to publish from Visual Studio?
Or what further rights should I ask aside my 'owner' role in Azure?
EDIT: I opened the same topic on MSDN (https://social.msdn.microsoft.com/Forums/en-US/e242ae0a-8da3-49fd-9fff-0460c4e294b8/how-to-use-azure-publish-from-visual-studio-with-entreprise-team-subscription?forum=azureapimgmt)
EDIT: this topic has some interessting info but not directly related since I do NOT have the subscription myself:
Visual Studio not finding my Azure subscriptions
I'm guessing you're working with multiple accounts...
You may not be signed into visual studio with the correct account. The account name dropdown in the upper right hand corner of visual studio and select Account Settings. From here ensure the account associated with your Azure resources is present under All Accounts. MS has some more guidance here:
https://msdn.microsoft.com/en-us/library/dn872465.aspx
We have two Azure subscriptions and an Office 365 subscription for our company.
In "Subscription #1", we have a VNET and a bunch of VMs. We have our "organizational AD" in this VNET. We also set our Office 365 subscription to use our organizational AD that is in this Subscription #1.
We then have a second Azure subscription (Subscription #2) in which we have WebApp's, databases and Visual Studio Team Services (VSTS - formerly Visual Studio Online) repositories. We set up our VSTS to use the directory service -- WAAD -- associated with this second subscription.
My question is: can we set it so that this second Azure subscription uses our organizational AD to manage user access? Our primary goal here is to have "single sign-on" in this second Azure subscription. For example, we want our developers to be able to use their organization AD accounts to access the VSTS repositories.
P.S. We do prefer keeping these two Azure subscriptions separate but still have single sign-on.
In short, yes you can. The easiest way to do this is by putting in a support ticket with Azure and asking them to perform this task for you. You should be able to put a ticket in with billing support to avoid costs.
The other way to do this involves having the Service Administrator of the 2nd Azure subscription be a Global Admin on the Azure Active Directory in question. You can then follow the steps found in this link.
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.