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. 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 →
  2. 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.

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. PHP Packagist

    I don't feel like there are many good solutions for PHP Packagist and providing it in TFS could provide that experience.

    8 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 →

    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

  9. Support for Carthage

    One of our customers is asking for Carthage support for one of our private SDKs for iOS. Carthage works with any git repo. I know there is a GitHub Enterprise https://github.com/Microsoft/. Does anyone know who to contact for access and permission? It would be nice to have a separate GitHub account for Carthage/CocoaPods.

    4 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 →

    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

  10. RPM Package Managment

    Support RPM packages and dependancies management. Many corporate enterprise environments wont allow access to public RPM repos and as such need to host their own internally.

    Should include the ability to sync/re-host from a public or Red Hat subscription to expose approved packages internally. The VSTS package management would connect directly to the public source, interpret the dependency tree of desired package to sync, then prompt for approval to sync package and dependencies list to internal package repository.

    Should be able to add it as an internal RPM repo to RHEL machines and install packages using yum.

    3 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 →

    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

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base