Azure DevOps (formerly Visual Studio Team Services)

Announcement: Towards the end of this month, we will move ideas to the Azure DevOps Developer Community where users already report and track their issues. The move is aimed at providing a single platform for all your feedback and improve your engagement with our product team. After the move, this UserVoice site will become read-only and new suggestions can be added on Developer Community.

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

    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 will use an alternate solution.

    105 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      14 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    • Add Support For PYPI Packages Using PIP

      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
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

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

        Add Upstream Sources for Maven feeds to proxy maven central or other maven repositories

        86 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

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

          Currently, package icons are not shown when browsing a Package Management feed in Visual Studio's NuGet Package Manager Extension.

          62 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            22 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
          • Add PowerShellGet support for PackageManagement

            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.

            58 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              5 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

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

              [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
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                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.

              • anonymous access to download packages

                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
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

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

                  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
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    4 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

                  • Have a built in docker container registry in VSTS

                    It would be great to have a built in docker container registry in VSTS much like GitLab has solved it.

                    28 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

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

                      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
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

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

                        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 roadmap yet for support of this feature?

                        Thank you!

                        24 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

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

                          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
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            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

                          • Add support for helm repositories

                            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
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                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

                              • Add support for conan packages

                                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
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

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

                                    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
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

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

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

                                      11 votes
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        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

                                      • 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
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          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

                                        • Know which VSTS build published which artifacts to VSTS Feed

                                          It would be great if we could some how correlate the VSTS builds that published artifacts (maven, npm, nuget) to VSTS feeds with those artifacts that exist in the feed. I'm mainly thinking of an API that would reveal such data, if correlation is known.

                                          10 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3
                                          • Don't see your idea?

                                          Azure DevOps (formerly Visual Studio Team Services)

                                          Feedback and Knowledge Base