Azure DevOps (formerly Visual Studio Team Services)

Announcement: Last fall, we migrated this forum to Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Azure DevOps Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Azure DevOps teams

We’d like your suggestions and ideas to help us continuously improve future releases of Azure DevOps and Team Foundation Server (TFS), so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The VSTS Team

How can we improve Azure DevOps?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow users with a Visual Studio Professional license to use Package Management

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365759/allow-users-with-a-visual-studio-professional-lice.html
    Users with Visual Studio Professional licenses are able to use source control. However, they are not allowed to access any packages stored in VSTS Package Management. In order to do development, they need to be able to access the packages stored in Package Management. This requires all developers to have a VS Enterprise license or an additional license for Package Management needs to be purchased for all of our developers. This licensing model doesn't make sense. Please fix the license model or we…

    105 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add Support For PYPI Packages Using PIP

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365634/add-support-for-pypi-packages-using-pip.html
    Skype & I believe other Microsoft teams heavily rely on Python for Build orchestration, testing, data analysis, and other functions. We would like to use PYPI packages natively through PIP, rather than having to ingest them in to Git repos to consume them.

    It would be great if VSTS could support PYPI packages through PIP clients https://pypi.python.org/pypi.

    97 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Upstream Sources for Maven feeds

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365864/add-upstream-sources-for-maven-feeds.html
    Add Upstream Sources for Maven feeds to proxy maven central or other maven repositories

    87 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Show icons for packages in the Visual Studio NuGet Package Manager

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365589/show-icons-for-packages-in-the-visual-studio-nuget.html
    Currently, package icons are not shown when browsing a Package Management feed in Visual Studio's NuGet Package Manager Extension.

    62 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add PowerShellGet support for PackageManagement

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365613/add-powershellget-support-for-packagemanagement.html
    Supporting PowerShellGet would allow us to write the following in PowerShell.

    Install-Module -Name "My.VSTS.Module"

    By allowing VSTS to support PowerShellGet, our company can then build our own "internal PowerShellGallery" to share PowerShell scripts across the company.

    59 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    We’re working with the PowerShellGet team now to improve the PowerShellGet client’s support for authenticated feeds. Once that work is completed, we’re also looking into supporting PowerShell modules as a native package type in Package Management (with the correct icon, metadata, download instructions, etc.)

    -Alex Mullans
    Program Manager, Package Management

  6. Component Governance (mirroring feeds, white/blacklisting packages, etc.)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365599/component-governance-mirroring-feeds-whiteblacklis.html
    [Alex Mullans - Microsoft] I've broadened this suggestion to cover the overall investment area that we call "Component Governance", which includes a set of features to help you manage security, legal, and other risks in the external and OSS components you use.

    For package and version curating like:
    ProGet Connectors:
    http://inedo.com/support/documentation/proget/core-concepts/connectors

    Feed Sync in MyGet:
    http://myget.org/features#advancedfeatures

    Klondike Mirror
    https://github.com/themotleyfool/Klondike/blob/master/src/Klondike.WebHost/Settings.config

    47 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    This suggestion remains under review. Like we often do in VSTS engineering, we are in process of building integrated tooling for Microsoft’s engineering teams to enhance the sophistication of our own processes for governing OSS usage and managing risk. We are continuing to assess how this meets the needs of external customers as well as aligns with our commercial priorities and will provide updates should we decide to turn what we use internally into a public offering for our customers. The VSTS marketplace does include offerings from partners that integrate well with VSTS to provide Component Governance services.

  7. anonymous access to download packages

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365748/anonymous-access-to-download-packages.html
    the Nuget server in VSTS would make a nice Internal PowerShell Gallery or local Choclatey repository.
    However the requirement for having a login and license makes that unworkable.
    It would be nice to allow anonymous access to download packages. either by default or as a played option.

    33 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Support for Chocolatey Packages

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365617/add-support-for-chocolatey-packages.html
    To use as a true internal Package Manager I want to be able to support all kinds of "Microsoft" based packages. In this case Chocolatey

    33 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    For the next 6 months, we won’t be taking new package formats, as we’re finishing Maven and planning major improvements to our existing NuGet and npm support and new features to improve the package lifecycle, like Package CI and Package CD for better Team Build and RM integration.

    However, we’re very interested in your input to define the next wave of package formats that are supported by Package Management so that we can inform our next major planning wave. So, we’ve left all “Ecosystem”-tagged requests open for voting.

    Alex Mullans
    Program Manager, Package Management for Visual Studio Team Services

  9. Have a built in docker container registry in VSTS

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365911/have-a-built-in-docker-container-registry-in-vsts.html
    It would be great to have a built in docker container registry in VSTS much like GitLab has solved it.

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add task to promote packages for release management

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365674/add-task-to-promote-packages-for-release-managemen.html
    The release views of package management is great. However, it is still a manual process to promote packages to any defined release views. There should be a task that can be part of a release definition that could promote a package after deploying it.

    26 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. npm audit

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365958/npm-audit.html
    npm added support for `npm audit` in npm@6 and npm@5.10.0 to highlight security issues with packages and their dependencies. The npm registry itself just added support for this very recently:

    https://blog.npmjs.org/post/173719309445/npm-audit-identify-and-fix-insecure

    When issuing an `npm audit` call to the npm registry from within a directory with a package.json, an analysis is returned to the console.

    When issuing the same request to a VSTS registry, a 400 is presently returned:

    https://<project>.pkgs.visualstudio.com/_packaging/<registry>/npm/registry/-/npm/v1/security/audits.

    Given that this is a security-related matter, is there anything on the…

    24 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Visual Studio Extensions (vsix) support in the VSO Package Manager

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365631/visual-studio-extensions-vsix-support-in-the-vso-p.html
    It would be nice if there was support for private/company vsix packages in the package management solution for vso. For example: We have a bunch of snippets that we share internally, but would be meaningless to the world if we published it publicly.

    22 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
    Alex Mullans
    Program Manager, VSTS

  13. Add support for helm repositories

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366067/add-support-for-helm-repositories.html
    As a developer
    I want to publish my helm packages to VSTS package management
    So that I can provide access to other developers in my organisation

    19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add support for conda packages

    It would be useful if the package management solution supported conda packages: http://conda.pydata.org/docs/ as this is widely used within python development

    18 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.

    Alex Mullans
    Program Manager, VSTS

  15. Add support for conan packages

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365873/add-support-for-conan-packages.html
    Conan (https://www.conan.io/) is a popular open source cross-platform package manager for C/C++ libraries.

    Once VSTS package manager supports PyPy and Conan, in addition to Nuget, npm, and Maven, then all our build artifacts can be managed centrally from VSTS, obviating the need for JFrog Artifactory.

    17 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow me to contact the consumers of my Package feeds

    Once I create a package feed in my organization, people outside of my immediate team will start to use the packages we create. It would be great to have that information, so that if I need to update the packages in a breaking way, delete older packages that are out of service, or change the location of the feed itself I can communicate that to my dependants.

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. Tfs symbol server

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365919/tfs-symbol-server.html
    Please bring the VSTS symbol server functionality into on premise tfs.

    The following idea says completed:
    https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/2564053-treat-tfs-as-an-enterprise-symbol-server

    However you can still only connect to vsts symbol sources in vs2017

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Be able to use VSTS Package Manager with Visual Studio Code (VS Code)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365849/be-able-to-use-vsts-package-manager-with-visual-st.html
    Currently, there is no way easy way to connect VS Code to a private nuget package repo on VSTS. It seems the only way would be to store a PAT in the nuget.config file under the repo configuration. There should be an easier / more portable solution to this problem as our teams become more diverse (.net core) and expecting everyone to be on VS Pro / Enterprise on Windows is no longer a reality.

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Gem Package Management

    Add the ability to manage Gem files and other supporting file formats that the ELK stack uses.

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
    Alex Mullans
    Program Manager, VSTS

  20. Support for Cocoapods

    Recently we had to explore ideas how to share our binaries from VSTS. As it's not a problem for source files to use :git notation with VSTS repository, it becomes an issue when you have to share compiled binaries. This can be approached by droping binaries to artifactory, linking to the URL with :http notation inside Podfile and specifing PAT in .netrc file (:http uses curl to fetch package). Still, this solution is not ideal and would be great to have Cocoapods packaging in place.

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
    Alex Mullans
    Program Manager, VSTS

← Previous 1 3

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base