There are 2 parts to this question:
The Azure DevOps pricing website is very unclear (to say the least).
If I have subscription A - and I create a DevOps organisation under this subscription, how many FREE accounts do I get (in that Organisation)?
So if I have 2 organisations - would I get 5 + 5 free Basic accounts?
Secondly,concerning Azure Stakeholder user - surely this user can be given a PAT to deploy their code to Azure Repos? No?
Or is that only BASIC user privilege?
Every organization has first 5 Basic users free. Pricing for Azure DevOps .
In Private project, Azure Stakeholder has no access to Azure Repos. In Public project, Azure Stakeholder has full access to Azure Repos. You can refer to Public versus private feature access.
Related
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.
I wish move from Microsoft personal DevOps Account to my O365 Account Tenant where I run Azure, too.
Is't possible to mantein the benefits, too?
What you can do is that transfer Transfer Azure DevOps to New Azure Account
Add a AAD member which is a Microsoft account to your Azure DevOps organization.
Add this AAD member to Project collection Administrators group.
Log into the Azure portal and connect the organization to AAD.
Then you could login to your Azure DevOps organization with AAD member
To merge two Azure DevOps account, there is no such kind of feature at the moment.
A related user voice here:
make it possible to move a Team Project between Team Project Collections
https://developercommunity.visualstudio.com/content/idea/365365/make-it-possible-to-move-a-team-project-between-te-1.html
Any other 3rd party extension or tool will not keep history info. Suggest you use two organization separately to keep history. Or manually merge it without history.
I have two Azure Cloud Solution Provider subscriptions and Azure DevOps project created around two/three years ago when it was called Visual Studio Team Services. DevOps resources (organization and project) reside on Azure for billing purposes. I want to move DevOps resources to new subscription, but cannot because of insufficient permissions - I'm missing AccountSubscriptionChange permission - how do I get it? I granted myself all permissions available in DevOps.
Create service desk ticker for Microsoft Azure support.
I understand how to create a new DevOps project from https://portal.azure.com and I see how that creates a new DevOps organisation or reuses an existing one (scoped to that AzureAD).
A new project is also created as well as an associated WebApps project.
These are my challenges:
When one creates a new Project in that DevOps organisation, it doesn't show up for management in https://portal.azure.com. How can one ensure the resources consumed by that project are part of the Azure Subscription to which the parent organisation is tied? Or is that the default?
What is the easiest way of tying existing DevOps organisations and projects to an Azure subscription to allow increasing the default 5 user limit and consuming more pipeline resources?
There doesn't seem to be any documentation anywhere that directly addresses these issues for me.
You may use Azure DevOps Organizations to connect your azure subscription with devops account:
Then you may use users on Azure DevOps from Azure Active Directory and manage billing (get more license):
Also you may use DevOps Project wizard to create a team project from a template:
Additional links:
Quickstart: Set up billing for your organization
Azure DevOps Projects
Tutorial: Connect your organization to Azure Active Directory
Quickstart: Pay for more Basic users
About access levels
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.