Azure DevOps Roadmap update for 2020 Q2
We have recently updated the Features Timeline to showcase areas where we are making key investments for this quarter. I am delighted to share few of those initiatives that we have planned for Q2 with you. Note that each feature links to our public roadmap project where you can find more details about each item and see its status.
A Service Tag represents a group of IP prefixes to help minimize complexity for security rule creation. For scenarios connecting from the Azure DevOps Services outbound to the customer’s on-prem, customers can now easily manage IP whitelisting by using the Azure Service Tag. Some of the scenarios are 1) Azure DevOps Services to connect to endpoints for Service Hooks use cases. 2) For data import, Azure DevOps Services to connect to SQL server in customer’s on-prem. 3) For kicking off a build, Azure DevOps Services to connect to a pool of customer’s agents on-prem. Service Tag for Microsoft Hosted Agents for Pipelines are not supported.
This feature will be delivered in two phases. The first phase is targeted for the end of Q2. It enables Process Administrators to restrict the transition from one state to another on a work item type. The second phase is targeted for Q3. It enables Process Administrators to restrict or allow state transitions by the users group membership.
To help bring better consistency between the Kanban Board and Task board, we are adding a new Parent Work Item filter to the Task board. This will allow teams to filter the list of User Stories (or any work item type in the requirements category) that belong to a specific parent(s).
Organization admins can configure a policy to allow or restrict project and team administrators from being able to invite net-new users to the organization.
New events are now added to the audit log to track the usage of alternate credentials like personal access tokens (PAT), SSH keys as well as token lifecycle management activities like create, renew, delete and revoke PAT tokens and SSH keys.
We have been planning to offer elastic self-hosted agents for quite some time now. These are self-hosted agents that run on a VM scale set in your Azure subscription but their capacity is managed by Azure Pipelines. During the last quarter, we rolled out a private preview of this feature. Our private preview period is now closed. During this quarter, we will enter a public preview. All Azure DevOps organizations should be able to try this feature by May. If you are interested in learning more about how this feature works, see Scale set agents.
Over the past two quarters, we delivered a number of improvements in YAML pipelines aimed at making your pipelines secure. Working with a number of our top customers, we developed techniques that help central teams in your organization develop and enforce best practices while giving enough flexibility to your individual development teams. These techniques revolve around two fundamental concepts – templates and checks. We encourage you to look at our documentation to understand how you can secure your YAML pipelines. During the upcoming quarter, we will continue to enhance these features by adding more built-in checks. We will also make job access tokens more secure by limiting their access to only those repositories that are explicitly declared as resources in a pipeline.
You can now checkout source code from multiple repositories in your YAML pipeline. However, you cannot cause your pipeline to be automatically triggered based on changes to any of those repositories. We will plug this gap this quarter. This will allow you to define a single pipeline for your micro-services that are managed in multiple repositories, or to separate your pipeline YAML file into a different repository altogether.
The new multi-stage pipelines experience has been in preview for several months now. We have been making a number of improvements in that experience based on your feedback. Our focus has been on addressing gaps and blockers. One of the drivers for this experience has been to make it mobile-friendly and, for that reason, we had to get rid of the explorer-style navigation. We understand that this increases the number of clicks to navigate from one pipeline to another. However, for the sake of mobile-friendliness and consistency, we will be moving forward and making this experience generally available at the beginning of Q2. This will also be the experience in the next version of Azure DevOps Server.
We always appreciate your feedback, because it helps us prioritize what we should work on. If you have a new idea, change you’d like to see, or a suggestion on what you’d like to see next, here are some options: