You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/managed-devops-pools/features-timeline.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Features timeline and roadmap
3
3
description: Learn about new features in Managed DevOps Pools.
4
-
ms.date: 10/09/2025
4
+
ms.date: 11/19/2025
5
5
ms.topic: overview
6
6
#Customer intent: As a platform engineer, I want to understand the new features in Managed DevOps Pools.
7
7
---
@@ -12,15 +12,15 @@ ms.topic: overview
12
12
13
13
The following section describes new features in development for Managed DevOps Pools.
14
14
15
-
***Service Tag and new IPs**: Managed DevOps Pools control plane is going to add new IP outgoing addresses and is going to publish a service tag to provide a convenient mechanism to allow outbound traffic from Managed DevOps Pools. **Planned for October 2025.**
15
+
***Service Tag and new IPs**: Managed DevOps Pools control plane is going to add new IP outgoing addresses and is going to publish a service tag to provide a convenient mechanism to allow outbound traffic from Managed DevOps Pools. **Planned for November 2025.**
16
16
17
-
***Log analytics**: Managed DevOps Pools is adding support so you can configure your pools to emit logs into Log analytics. The Log Analytics tool in the Azure portal lets you run and edit log queries against data in the Azure Monitor Logs store. Use Log Analytics to analyze and visualize log data using [Kusto Query Language (KQL)](/azure/azure-monitor/logs/get-started-queries) or the point-and-click experience provided in [Log Analytics simple mode](/azure/azure-monitor/logs/log-analytics-simple-mode). **Planned for October 2025.**
17
+
***Log analytics**: Managed DevOps Pools is adding support so you can configure your pools to emit logs into Log analytics. The Log Analytics tool in the Azure portal lets you run and edit log queries against data in the Azure Monitor Logs store. Use Log Analytics to analyze and visualize log data using [Kusto Query Language (KQL)](/azure/azure-monitor/logs/get-started-queries) or the point-and-click experience provided in [Log Analytics simple mode](/azure/azure-monitor/logs/log-analytics-simple-mode). **Planned for November 2025.**
18
18
19
-
***Purge agents**: We're adding the ability for you to manually recycle your agents if desired. **Planned for October 2025.**
19
+
***Azure Pipelines image versions**: When a new image version breaks your pipeline, you can configure an [image version override demand](./demands.md#imageversionoverride) in every pipeline to [revert to the version used by the last successful pipeline run](./troubleshooting.md#check-to-see-if-there-has-been-an-image-update). With the proposed feature, you can select the image version of an Azure Pipelines image in the Managed DevOps Pools user interface, and pin your pool's image to a specific image version. **Planned for November 2025**.
20
20
21
-
***Pool Alias**: We're adding the ability to add an Azure DevOps Pool name in addition to the Azure resource name to address [this ask from our community](https://developercommunity.visualstudio.com/t/Managed-Devops-Pools-Custom-agent-pool/10834336).**Planned for October 2025**.
21
+
***Purge agents**: We're adding the ability for you to manually recycle your agents if desired.**Planned for early 2026.**
22
22
23
-
***Azure Pipelines image versions**: When a new image version breaks your pipeline, you can configure an [image version override demand](./demands.md#imageversionoverride) in every pipeline to [revert to the version used by the last successful pipeline run](./troubleshooting.md#check-to-see-if-there-has-been-an-image-update). With the proposed feature, you can select the image version of an Azure Pipelines image in the Managed DevOps Pools user interface, and pin your pool's image to a specific image version. **Planned for October 2025**.
23
+
***Pool Alias**: We're adding the ability to add an Azure DevOps Pool name in addition to the Azure resource name to address [this ask from our community](https://developercommunity.visualstudio.com/t/Managed-Devops-Pools-Custom-agent-pool/10834336). **Planned for early 2026.**
24
24
25
25
***Spot Virtual Machines instances**: Reduce your Azure cost [by up to 90%](/azure/architecture/guide/spot/spot-eviction#understand-spot-vm-pricing) by switching your non-time-critical pipelines to Spot Virtual Machines. CI/CD workloads make ideal candidates to use Spot Virtual Machines due to the ephemeral nature of CI/CD agents. For more information on Spot Virtual Machines, see [Spot Virtual Machines overview](https://azure.microsoft.com/products/virtual-machines/spot). **Planned for early 2026.**
26
26
@@ -30,7 +30,7 @@ The following section describes new features in development for Managed DevOps P
30
30
31
31
## November 2025
32
32
33
-
***Public Static IP**: We've added support for public static IP addresses in Managed DevOps Pools to enable access to external resources, to prepare for when [Default outbound access for VMs in Azure is retired](https://azure.microsoft.com/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access). This change with Azure will affect Managed DevOps Pools, Azure Virtual Machine Scale Set agent pools, and self-hosted pools that will create a new virtual network and they will not be able to access anything outside the agent without infrastructure like a NAT gateway.
33
+
***Public Static IP**: We've added support for public static IP addresses in Managed DevOps Pools to enable access to external resources, to prepare for when [Default outbound access for VMs in Azure is retired](https://azure.microsoft.com/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access). This change with Azure affects Managed DevOps Pools, Azure Virtual Machine Scale Set agent pools, and self-hosted pools that will create a new virtual network and they will not be able to access anything outside the agent without infrastructure like a NAT gateway.
34
34
35
35
When [Default outbound access for VMs in Azure is retired](https://azure.microsoft.com/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access), all Managed DevOps Pools using a private isolated network will have one static IP address assigned by default. This will incur additional Azure costs for the NAT gateway. For more information, see [Configure Managed DevOps Pools networking:
0 commit comments