Billing FAQs

A: With user assignment-based billing, you pay for the users you assign an access level. When you remove the users, charges stop.

In assignment-based billing, all organizations begin with new users added from projects with Stakeholder access. We don't charge for new users who only need free Stakeholder access. If you want all new users to get Basic, change the default access level for your organization to Basic.

Group rules are a great way to automate access level assignment for your organization and under assignment-based billing, assignment errors are no longer common.

For more information about user assignment-based billing, see our blog post.

A: If you want all new users added to a project to get Basic, change the default access level (Organization Settings > Billing) to Basic.

For more granular control over the access level assigned to new users, consider setting up group rules. Group rules take precedence over default access level. The default access level only applies when a user has zero group rules applied. Group rules assign access to users who aren't directly assigned an access level. To have these group rules apply to your existing users, you need to remove direct assignments.

A: If you add a user with Basic or Basic + Test Plans access level, you pay at the time of assignment. When you create a group rule, applied to users without direct assignments, you don't start paying until they sign in and receive an access level.

A: When a user is permanently deleted in Microsoft Entra ID, within a few hours, they're removed from Azure DevOps and you're no longer be billed for their license. You might need to remove guest users manually from Azure DevOps. For more information, see Delete a user in Microsoft Entra ID

A: If you have inactive users, stop paying for them by removing them or assigning them a free Stakeholder access level. Sort by Last Access to find users who aren't active. Find out how recently they got added by exporting the list of users and checking the Date Added column.

A: Multi-organization billing/licensing is available. For more information, see multi-organization billing.

A: The quantity for all Azure DevOps meters, Basic, Basic + Test Plans, MS-Hosted CI/CD, Self-Hosted CI/CD and Artifacts, pro-rates at 1/31st of a unit per day. So, your charges during a month with fewer than 31 days are slightly less than the published monthly rate.

A: If you set up billing before your trial expires, you don't get charged until the trial ends.

A: Those users assigned Basic + Test Plans lose access until you do set up billing.

A: Microsoft ended support for purchasing third party paid Azure DevOps extensions through your Azure bill on July 1, 2019. We're encouraging our publishers to offer paid access to their services directly.

A: You can pay for Azure DevOps Server through Azure on a monthly basis and you can cancel anytime. You need the following items:

• At least one Visual Studio subscription, which includes the server license. You can also buy the server license through classic purchasing.
• A Client Access License (CAL) for each user accessing the server.
• Paid access to Test Plans for each user accessing Test Plans.

Buy Visual Studio subscriptions for users who need access to Visual Studio Visual Studio Subscriptions include one server license and one user CAL. Visual Studio Enterprise and Visual Studio Test Professional also include access to Test Plans. Test Professional is available as a standard subscription, so you can’t purchase through Azure.

• Buy Visual Studio Enterprise (cloud subscription, monthly)
• Buy Visual Studio Professional (cloud subscription, monthly)
• Buy Visual Studio Test Professional (standard subscription, yearly)

Buy Azure DevOps Basic or Basic + Test Plans for anyone else

1. Create an Azure DevOps organization or select one you already use.
2. Set up billing for the organization.
3. Add users who need access to Azure DevOps server, assigning them Basic or Basic + Test Plans.

Each organization includes five free Basic users, which doesn't include a CAL. Add five users who won’t use the server to ensure you’re paying for everyone who needs a server CAL.

A: If you're already using Azure, chances are you already have an Azure support plan. Also, you don't need to pay for billing support. Report a service outage from our service status page.

If you need technical support with Azure DevOps and don't have an Azure support plan already, complete the following steps:

1. Create an Azure subscription.

• Consider your purchase options and decide whether to set up payment direct with Azure, through a partner, or through a Microsoft representative.
• The simplest option is to pay for Azure directly. It's free to create an Azure subscription - you only pay for what you use.

2. Choose a support plan.

• As part of signing up for an Azure subscription, you can choose a support plan.
• All support plans let you create unlimited support requests for a fixed monthly price.
• All paid plans, including the Developer plan, offer technical support for Azure DevOps.

3. Submit a support ticket.

• Now, you can open a request via the Azure portal or learn how to create a support request.

A: No. You must purchase Azure DevOps through an Azure subscription. Think of it as your Azure billing account.

A: Yes. Use Azure DevOps up to the free tier limits for your organization, listed as follows:

• First five users free (Basic license)
• Azure Pipelines
  • One Microsoft-hosted CI/CD (one concurrent job, up to 30 hours per month)
  • One self-hosted CI/CD concurrent job
• Azure Boards: Work item tracking and boards
• Azure Repos: Unlimited private Git repos
• Azure Artifacts: Two GiB free per organization

A: You can buy Azure DevOps with most Azure subscriptions. We support Azure subscriptions connected to your Enterprise Agreement (EA), Azure subscriptions set up by Cloud Solution Providers (CSPs), through Microsoft Open License resellers, and Pay-As-You-Go.

The only notable exclusion is that you can't use the Azure free trial, Government, or National cloud subscriptions.

A: No, you can't use the monthly Azure credits from Visual Studio subscriptions to pay for Azure DevOps. You can use the subscription by removing your spending limit.

A: You can try to add the subscription with the Azure Sponsorship Offer and see if the system accepts it. If the subscription has a limit, then you can't use it.

A: Not at all. If you only want to buy Azure DevOps via Azure, that's okay.

Multi-organization billing

Multi-organization billing allows you to pay once per human user, for organizations under the same Azure billing subscription. This scenario doesn't apply to service principals and managed identities, which still get charged on a user assignment-based billing. Any service principal or managed identity gets charged once per organization that it gets added to.

A: No. For example, with the default assignment-based billing, each organization gets five free Basic users. When you change to multi-organization billing the Azure subscription gets five free Basic users, to be shared amongst all the organizations linked to it. When most users access only one organization, then five free users are most cost effective. If many users access multiple organizations, then multi-organization billing might be the best option.

A: No. Multi-organization billing applies to the Azure subscription. It needs to only be set once and can be set from any organization that uses that Azure subscription for billing.

A: To turn on multi-organization billing, see how to pay for a user once across multiple organizations.

A: No. Multi-organization billing groups the per user charges at an Azure subscription level, so only organizations that share a common Azure subscription get billed together.

A: Yes.

• All organizations under the same billing Azure subscription are in order. The ordering is consistent month to month, but it isn't configurable.
• The five free Basic users apply to the first organization on the list. Any remaining value carries over to other organizations.
• Users get billed in the first organization they're found in and not again in any other organization.
• If there are any charges for an organization, then there's a separate line item for that organization on the detailed Azure bill.

A: No. User assignments apply to each organization independently. Administrators can't tell whether a user they're adding already has an access level that's assigned in another organization.

A: They're billed for both Basic and Basic + Test Plans, which is a current limitation of multi-organization billing. We recommend assigning users with group rules and setting up the same group rules in each organization to ensure consistent access level assignment.

A: Export a list of users from Organization settings > Users for each organization. Then, remove duplicates based on sign-in address (for example, contoso@contoso.com). You can find the sign-in address under the Username column in the exported file.

A: The most common reason customers received extra free user license grants in the past is because Azure DevOps didn't support multi-organization billing. For that reason, when you enable multi-organization billing, extra free grants get removed. If you have a free grant, contact our Microsoft Azure support team to request that the grant applied to your Azure subscription instead.

Understand your bill

Azure DevOps charges appear with other Azure charges on your Azure bill. This section helps you with understanding how to drill into your Azure DevOps specific charges.

Complete the following step to view by cost analysis.

1. Go to Azure portal > Subscriptions, and then select Cost analysis.

   

A: Follow these steps to see only your charges for Azure DevOps.

1. In the Azure portal, select Subscriptions > Cost analysis.

2. Filter on Service name = Azure DevOps.

   

A: Azure DevOps charges daily, so the best way to see what you're currently paying for Azure DevOps is to view by daily costs.

1. In the Azure portal, select Subscriptions > Cost analysis.

2. View by Daily costs.

   

A: Azure DevOps includes Azure Repos, Azure Boards, Azure Pipelines, Azure Artifacts, and Azure Test Plans. For more information about pricing, see Azure DevOps pricing. To see these services on your bill, follow these steps.

1. In the Azure portal, select Subscriptions > Cost analysis.

2. Group by Meter subcategory.

   

A: If you work in more than one Azure DevOps organization billed to the same Azure subscription, you can separate the charges for each organization.

To make this split easier, we automatically add the tag "_organizationname_" and the name of your Azure DevOps organization associated with the charges. We started emitting this tag in Feb 2020, so you don't see it before that date. See the following two ways you can use this tag to drill into charges for a given organization.

1. In the Azure portal, select Subscriptions > Cost analysis.

   

• Filter based on tag, and see only charges for a given organization or

  

• Group by tag, and see charges stacked by organization

  

Azure portal integration

Your Azure DevOps organization appears as a resource in the Azure portal, but you create and manage it outside of the portal. There are some limitations to this integration and workarounds, as follows.

A: No, you can't move the organization resource that appears in the Azure portal between Azure subscriptions via the Azure portal. But you can move it between subscriptions by changing the subscription your organization uses for billing. When you change the subscription, a new resource group gets created for your organization. You can then safely delete the old resource group.

A: No, the organization resource is created in its own resource group with a predefined naming convention. If you need to know what Azure DevOps organization is in the resource group, create an organization name tag and make it a column in the Resource Groups view.

1. Create a tag called Organization name.
2. Tag each Resource group with the name of the organization that it contains.
3. Select Manager view > Edit columns.
4. Change the selection from Properties to Tags.
5. Select the Organization name column.
6. Move it to Selected columns, and then select Apply.

A: The location of your organization resource could be incorrect for various reasons, such as changing your organization region. To find the location of your organization, check the geography listed in Azure DevOps, which is the source of truth for Azure DevOps locations. If the location listed there doesn't match the location listed inside the Azure portal, do these steps:

1. In Azure DevOps Billing settings, remove your billing subscription.
2. In the Azure portal, delete the Azure DevOps resource group if it's still there.
3. In Azure DevOps Billing settings, set up billing for your organization.

A: If you have renamed your organization after you set up billing, then the name of the organization resource is the original name. To change the name of the organization resource to the new name, first remove billing, and then set up billing again.

A: Deleting the Azure DevOps organization resource in the Azure portal results in an error if it's actively being used for billing. To delete the organization resource, first change billing to a different Azure subscription in the Azure DevOps organization (Organization settings > Billing > Change billing). For more information, see Change billing in Azure DevOps.

If the user removing billing has permission on the Azure subscription, the resource in the Azure portal gets removed automatically. If the user removing billing in Azure DevOps doesn't have access to the Azure subscription, the organization resource persists and a user with access to the Azure subscription can safely remove it later without error.

A: Yes. Select the Azure subscription linked to the desired Azure DevOps organization, in Settings > Resources.

Select the desired organization from list and apply tags by selecting the action Assign tags. The tags you assign appear in your Azure bill for the charges associated with the selected Azure DevOps organization.

A: Charges are metered daily to the Azure subscription you selected when you set up billing. Charges accumulate and are included on the next Azure bill you receive.

A: Reductions and cancellations are effective immediately.

A: When the Azure subscription used for billing on your organization isn't in active status - for example, because you canceled the subscription, or the credit card used for billing expired - your organization reverts to the free tier of service. To resume access to paid services, reactivate your subscription or change your organization's billing subscription.

A: If you're the owner or contributor for the Azure subscription used for billing your organization, you can view your billing details in Azure DevOps Organization settings > Billing tab. If you're the Azure Account Administrator, go to Cost Management + Billing.

A: Yes, you can. You need to be an owner or contributor for an Azure subscription that's created for your EA.

A: The easiest approach to determine if you have the right privileges is to set up billing for your organization. Select an Azure subscription, which is a billing account, from a presented list of Azure subscriptions linked to your sign-in credentials. Since the name of your Azure subscription defaults to the type of billing account, it's often clear whether the Azure subscription is part of your Enterprise Agreement. For example, you can name subscriptions, "Pay-As-You-Go" or "Enterprise Agreement."

Another approach is to try to visit the Azure Enterprise Portal. If you can reach it successfully, then you already have either the enterprise admin or the organization owner role. Only organization owners can set up new Azure billing in an Enterprise Agreement.

Ask your Enterprise Administrator to add you as an organization owner within the Azure Enterprise portal. If you can't find this person, submit a support ticket and request the contact information. You need your organization's name and your Enterprise Agreement enrollment number for the support ticket.

A: Yes, you can use these prepaid funds for all services that Azure DevOps offers. Make sure to choose an Azure subscription that was created for your EA when you set up billing for your organization.

A: You can't create Team Projects or view them in the Azure portal as of September 28, 2018. You can continue to access any Team Projects you create via the Azure portal through your organization URL (https://dev.azure.com/{Your_Organization}). You can always create new organizations and projects from visualstudio.com. The best way for Azure users to get started using Azure DevOps is to create a project.

A: Someone already set up billing for your organization. Each organization can use only one Azure subscription for billing. You can't split across multiple Azure subscriptions.

A: Yes, you can use the same Azure subscription for billing across multiple organizations. You can't link a single organization to multiple Azure subscriptions.

A: Yes, you can, if your reseller participates in the Cloud Solution Provider program. Just ask them.

Buy Azure DevOps now

• Azure DevOps Users/Basic
• Parallel jobs
• Azure Artifacts
• Azure Pipelines

Related articles

• Azure DevOps pricing
• Azure DevOps billing support