Pay-per-GiB pricing and more Azure Artifacts updates

Alex Mullans

Alex

Azure Artifacts is the one place for all of the packages, binaries, tools, and scripts your software team needs. It’s part of Azure DevOps, a suite of tools that helps teams plan, build, and ship software. For Microsoft Build 2019, we’re excited to announce some long-requested changes to the service.

Until now, a separate, additional license was required for anyone using Azure Artifacts, beyond the Azure DevOps Basic license. We heard your feedback that this was inflexible, hard to manage, and often not cost-effective, and we’ve removed it. Now, Azure Artifacts charges only for the storage you use, so that every user in your organization can access and share packages.

Every organization gets 2 GiB of free storage. Additional storage usage is charged according to tiered rates starting at $2 per GiB and decreasing to $0.25 per GiB. Full details can be found on our pricing page.

Included in all on-premises versions

Updated 6/12/2019: Azure Artifacts is now included with every Basic license for Team Foundation Server (TFS) 2017, TFS 2018, as well as Azure DevOps Server 2019.

Python and Universal Packages are GA

We’ve had support for Python packages, as well as our own Universal Packages, in public preview for some time. As of now, both are generally available and ready for all of your production workloads.

What’s next: public feeds

If you’re developing an open source project using a public Azure Repo or a repo on GitHub, you might want to share nightly or pre-release versions of your packages with your project team. Azure Artifacts public feeds will enable you to do just that, backed by the same scale and reliability guarantees as the private feeds you use for internal development. Interested in joining the preview? Get in touch (@alexmullans on Twitter).

Capabilities of Azure Artifacts

With Azure Artifacts, your teams can manage all of their artifacts in one place, with easy-to-configure permissions that help you share packages across the entire organization, or just with people you choose. Azure Artifacts hosts common package types:

  • Maven (for Java development)
  • npm (for Node.js and JavaScript development)
  • NuGet (for .NET, C#, etc. development)
  • Python

Screenshot of Azure Artifacts

If none of those are what you need, Azure Artifacts provides Universal Packages, an easy-to-use and lightweight package format that can take any file or set of files and version them as a single entity. Universal Packages are fast, using deduplication to minimize the amount of content you upload to the service.

Azure Artifacts is also a symbol server. Publishing your symbols to Azure Artifacts enables engineers in the next room or on the next continent to easily debug the packages you share.

Artifacts are most commonly used as part of DevOps processes and pipelines, so we’ve naturally integrated Azure Artifacts with Azure Pipelines. It’s easy to consume and publish packages to Azure Artifacts in your builds and releases.

We’re excited for you to try Azure Artifacts. If you’ve got questions, comments, or feature suggestions, get in touch on Twitter (@alexmullans) or leave a comment.

21 comments

Comments are closed. Login to edit/delete your existing comments

  • Avatar
    Nick Williams

    Hi Alex, bit late to the party. You mentioned below that `There is no more user license for Azure Artifacts – every user in the organization can access any package feeds they have permissions to.`
    Do users accessing the artifact feeds still need to be at least a basic user? I’ve tried adding a stakeholder via the artifact feed ‘Add User’ option but get the below error message when tring to access a nuget feed. Seems like there is still some user licensing requirements?

    <m:error xmlns:m=”http://schemas.microsoft.com/ado/2007/08/dataservices/metadata”>
      <m:code/>
        <m:message xml:lang=”en-US”>The user does not have a license for the extension ms.feed.</m:message>
      </m:error>

  • Avatar
    Bright Ran

    Now, Azure Artifacts charges only for the storage you use, so that every user in your organization can access and share packages.”
    But the Stakeholders in our Organization still can’t access Azure Artifacts, if the user still need a Basic access?