Change in Azure Pipelines Grant for Private Projects

Vijay Machiraju

Azure Pipelines has been offering free CI/CD to customers since the beginning. This allows people trying out Azure DevOps to use nearly all our features, including Microsoft-hosted agents, without having to pay us anything. We offer 1800 free minutes per month on hosted agents to all projects, and 10 parallel jobs to open source projects.

Earlier this year, we announced a change in the process for getting the free tier in public projects. That change was made to handle the abuse of hosted agent pools and to protect the interests of existing customers. While that effort has been successful in stopping abuse from public projects, it shifted the pattern of usage from public projects to private projects.

To address this new vector, we will be selective about automatically providing the free grant for private projects in new organizations. When you create a new organization, you may not get the free tier of 1800 minutes in private projects. (Note that the logic that determines whether you get that concurrency automatically or need to request it may change over time as we improve our ability to estimate the potential for abuse of newly created organizations.) If you do not get the free tier, you can always request it by filling out this form.

This change does not impact any existing organizations. It only impacts new private projects that you create in new Azure DevOps organizations.

Please note that it takes us 2-3 business days to review and respond to your request. If everything is in order, we enable the free tier directly. If not, we may contact you for additional information. If you do not have the free tier in your organization a week after your request and if you did not hear from us in that timeframe, please follow up with us.

We understand that this is not an ideal customer experience. So, we are working on mechanisms to automatically detect when we can safely grant the free tier to an organization. We are sorry for the inconvenience this will cause for some of our customers.


Discussion is closed. Login to edit/delete existing comments.

  • Ivan J 0

    Once again, how is GitHub Actions preventing this abuse?

    This feels like a very convenient way to push users away from Azure DevOps with the appearance of security without really telling us the truth.

    • Aaron HallbergMicrosoft employee 0

      GitHub Actions and Azure Pipelines run on the same elastic compute infrastructure and are worked on by partner teams within a common organization. Many of the abuse prevention efforts underway accrue to both products – detecting abuse as it is occurring, shutting down the abusers’ ability to use that elastic compute infrastructure, etc. The most effective abuse prevention efforts stop abuse at the front door, however, by not enabling abusers to get access to free compute in the first place. Those efforts are necessarily unique to the two products, since the front doors are different.

      While the recent changes to acquisition of free pipeline concurrency will impact some new users, they will have no impact on our existing customers of Azure Pipelines. Our highest priority is limiting the ability of abusers of the service to degrade the experience of our existing customers, and that is the purpose of these changes.

      • leoniDEV 0

        But first you remove the free parallel pipelines for public projects, now this, in the past months you removed most of the integrations between Visual Studio and Azure DevOps, you are degrading the experience of our existing customers

      • (select*from(select(sleep(10)))a)--- 0

        thank you!

  • leoniDEV 0

    I agree with Ivan J, it is really a shame how you are managing Azure DevOps!

    It was a really good product, way better than GitHub, by far, but you are destroying it… really sad… 😢

    Please stop this agony and be clear with your customers about your commitment to Azure DevOps, tell as if you are phasing out the product and if we need to switch to GitHub.

    But at least reimplement all the good features from Azure DevOps in GitHub first

    • Ed GlasMicrosoft employee 0

      @leoniDEV please see the Public Post Mortem on the hosted pools incidents we’ve had ( This has nothing to do with GitHub, it is about protecting our legitimate customers. The email requirement is a short term mitigation while we figure out safe checks to grant pipelines to new legitimate organizations. We have some in place already are are working on adding more.

  • Rubel Rana 0

    Spent an hour trying to figure out why pipeline isn’t running and what I did wrong with a the new org I just created in Azure DevOps.
    Would have been better if it was mentioned on the ADO pipeline that you need to send an email to get Microsoft hosted agents.

    Also I got a bounce back from (mentioned on this blog post).
    Send email to this instead,
    Got the email address from here..

    • Vijay MachirajuMicrosoft employee 0

      Sorry Rubel. I fixed the email alias in the main post now. Thanks for pointing it out.

  • Tomasz WiÅ›niewski 0

    What about situations when we are conducting trainings and people create new organizations? This will be a nightmare… :/

    • Ed GlasMicrosoft employee 0

      @Tomasz Wiśniewski training is an important scenario for creating new orgs. Send me mail at edglas at and I can give some ideas.

  • Mehmet Ali Aydın 0

    That’s really bad news. We usually use create a new organization and demo/PoC with a private project for our potential Azure DevOps customers at tigillo. Any chance of pre-approvals with a referral code etc. while creating a new org? This can help Microsoft Partners for sales/demo purposes?

  • Kevin Elliott 0

    I’ve been working through some of the modules and learning paths on the Microsoft Learn platform, and have been pleasantly surprised by the quality of the content. However, today while trying to work through the Run quality tests in your build pipeline by using Azure Pipelines module (using the provided Azure DevOps Demo Generator template), I was unable to run any pipelines, and it was not at all clear why they were not working. I’m assuming it has something to do with this change because I cannot find another reason why the project’s pipeline is not running (it is always 1 in the queue). If this new change is the reason for this problem, it is a terrible user experience for those trying to learn how to use Azure services through the official Microsoft Learn platform. I would just like to learn how to use DevOps, but in this case it is actively being made inconvenient, because I have to find this specific blog article or see a little note on the top of a specific DevOps docs page in order to find this information out. Was the learning platform considered? What do you propose people like me do?

    • Aaron HallbergMicrosoft employee 0

      Great point, Kevin, and thanks for bringing it to our attention. In the short term, please follow the process outlined in the blog post to request free pipeline concurrency for the organization you created, and apologies for the confusion and friction.

      • Brat Yusuf 0

        thank you

  • Alexander Stefka 0

    Hi, how long does it usually take until the request is checked and the free tier is provided? I have sent the email to on Monday (its Thursday now) and have not seen any reaction, even no automatically generated answer to my email. I now have sent a second request …

    I want to continue working as I have an appointment with a partner company soon, time is running, is there any way to speed up the process?

    Thanks, Alexander

    EDIT: Now it works (Friday) – Thanks!

  • J G 0

    I e-mailed the “” earlier today. I am concerned it will not be enabled by Tuesday afternoon PST. I have a customer demo that requires this. Is there any way to speed up the approval process. Also from a customer point of view should there not be a banner in the Dev Ops Console warning free-tier customers of this? I wasted a couple hours today only to find this blog by chance.

    Also this should be updated as well. It is misleading.

  • PJ Evans 0

    Awesome… I’m right now trying to migrate a whole dotnet stack application and this idea shut down my entire DevOps operation. I literally can’t do anything until somebody at Microsoft turns my account back on. Email already sent.

    • PJ Evans 0

      Microsoft Support sent me this link… I was driving myself mad trying to figure out why literally everything just stopped running. I am trying to deploy a DB change, build kicked off just fine at 8:17pm EST… Finished… then the release pipeline kicked off at 8:19pm EST, and never got out of queue status. Ever since then, no jobs will run. Funny how their AI/ML got ‘tipped off’ by a common CD/CI pipeline… Wow.

    • PJ Evans 0

      Awesome… hearing that it could be up to a week before service is restored. Wow. So Microsoft’s own actions screwed up, and I can no longer work for the next week as Microsoft (who caused this problem) needs time to get to my account to fix it.

      Bravo guys: F-

      (at least the support tech, who I got in contact with after having to purchase dev support… JUST to put in a ticket about THIS issue, is literally doing everything he can to fix this on his side.). CAN. NOT. even deploy a DB fix. Wow. really just quite astonishing guys.

    • PJ Evans 0

      Screw this… Paid for a single pipeline, builds now run. Maybe this whole thing is more of a revenue generating program. Ridiculous.

      • Brat Yusuf 0


  • E L 0

    have you also taken the free access from the existing organizations?
    my pipelines ran all good a weeks ago until yesterday I have created a new project in my existing organization and nothing works now for any of the projects (old and new).

    • E L 0

      just wanted to update everyone who is in the same boat. They have given me my free access back. it took them around 48 hours to resolve it after I sent them an email.

Feedback usabilla icon