Merge pull request #310907 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-27 06:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-functions/durable/durable-functions-instance-management.md

@@ -1176,14 +1176,14 @@ Push-OutputBinding -Name Response -Value $Response
 
 ---
 
-## Rewind instances (preview)
+## Rewind instances
 
 If you have an orchestration failure for an unexpected reason, you can *rewind* the instance to a previously healthy state by using an API built for that purpose.
 
 > [!NOTE]
 > This API is not intended to be a replacement for proper error handling and retry policies. Rather, it is intended to be used only in cases where orchestration instances fail for unexpected reasons. Orchestrations in states other than `Failed` (e.g., `Running`, `Pending`, `Terminated`, `Completed`) cannot be "rewound". For more information on error handling and retry policies, see the [Error handling](durable-functions-error-handling.md) article.
 
-Use the `RewindAsync` (.NET) or `rewind` (JavaScript) method of the [orchestration client binding](durable-functions-bindings.md#orchestration-client) to put the orchestration back into the *Running* state. This method will also rerun the activity or sub-orchestration execution failures that caused the orchestration failure.
+Use the `RewindAsync` (.NET) or `rewind` (JavaScript) method of the orchestration client binding to put the orchestration back into the `Running` state. This method reruns the activity or sub-orchestration execution failures that caused the orchestration failure. The method only attempts to rerun failed activities, either within the parent or failed sub-orchestrations. It doesn't remedy orchestrations that failed for other reasons.
 
 For example, let's say you have a workflow involving a series of [human approvals](durable-functions-overview.md#human). Suppose there are a series of activity functions that notify someone that their approval is needed, and wait out the real-time response. After all of the approval activities have received responses or timed out, suppose that another activity fails due to an application misconfiguration, such as an invalid database connection string. The result is an orchestration failure deep into the workflow. With the `RewindAsync` (.NET) or `rewind` (JavaScript) API, an application administrator can fix the configuration error, and rewind the failed orchestration back to the state immediately before the failure. None of the human-interaction steps need to be re-approved, and the orchestration can now complete successfully.
 

articles/azure-functions/flex-consumption-plan.md

@@ -109,7 +109,7 @@ To learn how to set concurrency limits for HTTP trigger functions, see [Set HTTP
 Deployments in the Flex Consumption plan follow a single path, and there's no longer the need for app settings to influence deployment behavior. Your project code is built and zipped into an application package, then deployed to a blob storage container. On startup, your app gets the package and runs your function code from this package. By default, the same storage account used to store internal host metadata (AzureWebJobsStorage) is also used as the deployment container. However, you can use an alternative storage account or choose your preferred authentication method by [configuring your app's deployment settings](flex-consumption-how-to.md#configure-deployment-settings).
 
 > [!TIP]
-> A **Flex Function App deployment details** diagnostic tool is available in the Azure portal. Open your Flex Consumption app, select **Diagnose and solve problems**, and search for `Flex Function App deployment details`. This tool displays detailed information about your deployments, including deployment history, package status, and troubleshooting recommendations.
+> A **Flex Consumption Deployment** diagnostic tool is available in the Azure portal. Open your Flex Consumption app, select **Diagnose and solve problems**, and search for `Flex Consumption Deployment`. This tool displays detailed information about your deployments, including deployment history, package status, and troubleshooting recommendations.
 
 ### Zero-downtime deployments
 

articles/azure-functions/functions-deployment-technologies.md

@@ -144,7 +144,7 @@ One deploy is the only deployment technology supported for apps on a [Flex Consu
 >__Where app content is stored:__ When you create a Flex Consumption function app, you specify a [deployment storage container](functions-infrastructure-as-code.md?pivots=flex-consumption-plan#deployment-sources). This blob container is where your tools upload the app content you deployed. To change the location, you can visit the Deployment Settings blade in the Azure portal or use the [Azure CLI](flex-consumption-how-to.md#configure-deployment-settings).
 
 > [!TIP]
-> A **Flex Function App deployment details** diagnostic tool is available in the Azure portal. Open your Flex Consumption app, select **Diagnose and solve problems**, and search for `Flex Function App deployment details`. This tool displays detailed information about your deployments, including deployment history, package status, and troubleshooting recommendations.
+> A **Flex Consumption Deployment** diagnostic tool is available in the Azure portal. Open your Flex Consumption app, select **Diagnose and solve problems**, and search for `Flex Consumption Deployment`. This tool displays detailed information about your deployments, including deployment history, package status, and troubleshooting recommendations.
 
 ### Zip deploy
 

articles/dev-box/dev-box-roadmap.md

@@ -6,7 +6,7 @@ ms.topic: concept-article
 author: RoseHJM
 ms.author: rosemalcolm
 ms.update-cycle: 30-days
-ms.date: 03/05/2025
+ms.date: 01/20/2026
 
 #customer intent: As a customer, I want to understand upcoming features and enhancements in Microsoft Dev Box so that I can plan and optimize development and deployment strategies.
 
@@ -20,64 +20,24 @@ This roadmap presents a set of planned feature releases that underscores Microso
 
 Key Dev Box deliverables can be grouped under the following themes:
 
-- Ready-to-code development environment
-
 - Enterprise management
 
 - Fundamental performance & reliability
 
-## Ready-to-code development environment
-
-Microsoft Dev Box can significantly enhance developer productivity by minimizing configuration time and IT overhead compared to traditional virtual desktop infrastructure (VDI) solutions. We're making it incredibly easy and quick for developers to create ready-to-code environments tailored to their specific projects. Not only are we reducing the time required to set up Dev Box machines, but we're also introducing innovative new customization options for both teams and individuals.
-
-**Config-as-code workflow improvements**
-
-- [Team customizations](https://developercommunity.visualstudio.com/t/Share-customization-files-across-my-team/10729596?sort=newest) and [Dev Center Imaging](https://developercommunity.visualstudio.com/t/Speed-up-Dev-Box-customization-using-a-c/10729598): 
-
-    - As a project lead or a dev center admin, you can now use custom images to create image definitions, instead of just marketplace images.
-
-    - As a project lead or a dev center admin, you can specify a custom network connection to use when building images, so that you can access and fetch resources that are only accessible from your custom virtual networks.
-
-    - You can now use the CLI and VS Code extension to debug tasks that use the PowerShell and Winget primitives, and you can set them to have a custom time out for long running scripts.
-
-    - As a project lead or a dev center admin you can use the Dev Box Visual Studio Code extension, now powered by GitHub Copilot chat, to create customization files.
-
-**Developer onboarding & experience**
-
-- [Region Selection Optimization for Dev Box Creation](https://developercommunity.visualstudio.com/t/Region-selection-optimization-based-on-l/10784537): As a developer, easily create your new Dev Box in an optimal region based on your location. As a dev center admin, optimize the location of existing Dev Box machines based on end user location and available capacity.
-
 ## Enterprise management
 
 Microsoft Dev Box aims to deliver centralized governance based on organizational standards for security, compliance, and cost controls. During this period, we're reducing the time it takes enterprises to get started with Dev Box by making it easier to set up a proof of concept (POC) and then move to production. We're also improving our monitoring, cost control, security, and privacy capabilities.
 
 **Streamlined and flexible onboarding for enterprises**
 
-- [In product prerequisites](https://developercommunity.visualstudio.com/t/User-License-Assignment-as-Pre-requisite/10523902?q=pre-requisits): As a dev center admin, you'll be able to identify the prerequisites, and quickly start setting up the Dev Box service.
-
-- [New Supported Regions](https://devblogs.microsoft.com/develop-from-the-cloud/microsoft-dev-box-regional-availability/): As a dev center admin, you'll be able to enable your development team to create Dev Box machines in new regions including [UAE North](https://developercommunity.visualstudio.com/t/Support-for-Dev-Box-in-UAE-North/10781448) and [Spain Central](https://developercommunity.visualstudio.com/t/Dev-Box-support-in-Spain-Central/10781449).
-
 - [On-behalf creation](https://developercommunity.microsoft.com/t/On-behalf-creation-of-machines/10859734): As a dev center admin, you'll be able to provision a Dev Box machine for other developers in your team.
 
 **Network setup and expansion**
 
-- [Expand IPs within existing subnets](https://developercommunity.visualstudio.com/t/Expand-IPs-within-existing-Subnets-in-a/10781464): As a dev center admin, you'll be able to expand IP ranges in subnets that are running out of IP addresses.
-
-- [RRS Integration into QMS](https://developercommunity.visualstudio.com/t/Automatically-approve-higher-amounts-of/10781465): As a dev center admin for a trusted customer, you'll be able to request and get larger quota automatically approved through QMS.
-
 - [Firewall Service Tags](https://developercommunity.visualstudio.com/t/Dev-Box:-Advanced-notice-and-notificatio/10704156?q=firewall): As an IT administrator working on setting up Dev Box for their organization, quickly configure traffic roles by utilizing Service Tags in your Firewall set up.
 
-**Enhanced monitoring and cost controls capabilities**
-
-- [Active hours of usage and auto-start](https://developercommunity.microsoft.com/t/Automatic-ShutdownPower-up-based-on-wor/10729429): As a dev center admin, reduce the cost of compute by enabling Dev Box machines to be active for certain hours during the day. Give developers the ability to start their machines 15 mins before the active hours begin. 
-
-- [Monitoring logs:](https://developercommunity.visualstudio.com/t/When-Microsoft-Monitoring-Agent-will-be/10471575?entry=suggestion&q=Azure+Monitor) As a dev center admin, access user level engagement metrics and connectivity related metrics.
-
 **Security and privacy**
 
-- [Project Policy](https://developercommunity.visualstudio.com/t/Curation-for-Dev-Center-and-Projects-und/10719953): As a dev center admin, set up guardrails using policies around resources that different projects should and shouldn't access.
-
-- [Customer Managed Keys (CMK):](https://developercommunity.visualstudio.com/t/Encryption-with-customer-managed-keys-fo/10720463) As a dev center admin, have greater control over your data encryption by managing your own encryption keys.
-
 - [Developer offboarding](https://developercommunity.visualstudio.com/t/Provide-a-means-to-do-external-cleanup/10670632?q=delete+unused+): As a dev center admin, configure your Dev Box service to offload users from the service when they leave the organization and switch between teams.
 
 ## Fundamental performance & reliability
@@ -92,21 +52,10 @@ Microsoft Dev Box aims to provide a "like-local" developer experience that is as
 
 - [Latency Improvements](https://developercommunity.visualstudio.com/t/Latency-improvements-when-using-a-mouse/10859786): As a developer you'll experience reduced mouse latency with high-resolution monitors along with other generic latency improvements.
 
-- [Open Dev Box machine in Visual Studio Code](https://developercommunity.microsoft.com/t/Open-a-Dev-Box-machine-in-VS-Code/10859793): As a developer, you'll be able to access your developer environments on your Dev box machine, including WSL, from your local developer machine.
-
-**Service health & reliability**
-
-- [Backup SKUs:](https://developercommunity.visualstudio.com/t/Back-up-SKUs-in-case-of-capacity-outage/10720451) As a developer, you'll be able to smoothly resume working on existing Dev Box machines during service outages by opting to using a fallback SKU.
-
-- [Self-service snapshot and restore](https://developercommunity.visualstudio.com/t/Self-serve-snapshot-and-restore/10719611): As a developer, you can recover your Dev Box by restoring it to a previous snapshot.
-
-- [Azure region optimizations based on user locations:](https://developercommunity.visualstudio.com/t/Move-VM-to-different-poolregion/10277787) As a dev center admin, optimize the location of existing Dev Box machines based on end user location and available capacity.
-
 This roadmap outlines our current priorities, and we remain flexible to adapt based on customer feedback. We invite you to [share your thoughts and suggest more capabilities you would like to see](https://aka.ms/DevBox/Feedback). Your insights help us refine our focus and deliver even greater value.
 
 ## Related content
 
-- [What's new in Microsoft Dev Box](https://aka.ms/devbox/whatsnew)
 - [What is Microsoft Dev Box?](/azure/dev-box/overview-what-is-microsoft-dev-box)
 - [Microsoft Dev Box architecture and key concepts - Microsoft Dev Box | Microsoft Learn](/azure/dev-box/concept-dev-box-architecture)
 - [Microsoft Dev Box architecture - Microsoft Dev Box | Microsoft Learn](/azure/dev-box/concept-dev-box-architecture)

articles/frontdoor/diffie-hellman-ciphers.md

@@ -13,7 +13,7 @@ ms.date: 01/26/2025
 
 **Applies to:** :heavy_check_mark: Front Door Standard/Premium :heavy_check_mark: Front Door (classic) :heavy_check_mark: CDN Standard from Microsoft (classic)
 
-On April 1, 2026, Azure Front Door (Standard, Premium, and Classic) and Azure CDN from Microsoft (Classic) services will stop negotiating the following weak DHE cipher suites for both client to service and service to origin TLS connections:
+On April 1, 2026, Azure Front Door (Standard, Premium, and classic) and Azure CDN from Microsoft (classic) services will stop negotiating the following weak DHE cipher suites for both client to service and service to origin TLS connections:
 * TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 * TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 
@@ -45,11 +45,16 @@ For best compatibility and security on Azure Front Door / Azure CDN endpoints an
 
 ## Frequently asked questions
 - Does this affect both client and origin connections?
+    
     Yes. The retirement applies to both the client to service and service to origin legs. Update both sides to avoid issues.
+
 - What if I still need legacy client compatibility?
+    
     Migrate clients to support TLS 1.2/1.3 with ECDHE. If you operate controlled clients, update their TLS policy. 
+
 - Should I make any changes to my Front Door or CDN profiles?
+    
     As an optional measure, for Front Door Standard/Premium profiles, you can also use the [Configure Azure Front Door TLS policy](/azure/frontdoor/standard-premium/tls-policy) feature to disable the DHE ciphers in advance before 1 April 2026. This option isn't available for other tiers.
 
-    For all Front Door (Standard, Premium, Classic) and Azure CDN from Microsoft (Classic) profiles, Microsoft team will disable the DHE ciphers after 1 April 2026.
+    For all Front Door (Standard, Premium, classic) and Azure CDN from Microsoft (classic) profiles, Microsoft team will disable the DHE ciphers after 1 April 2026.
 

articles/redis/reserved-pricing.md

@@ -72,7 +72,7 @@ To buy a reservation:
 How to use the Azure portal to buy reservations:
 
 1. In the portal, search for and select **Reservations** and then select **Add**, or select this link to the [Purchase reservations](https://portal.azure.com/#blade/Microsoft_Azure_Reservations/CreateBlade/) page.
-1. On the **Purchase reservations** page, select **Azure Cache for Redis**.
+1. On the **Purchase reservations** page, select **Azure Cache for Redis and Managed Redis**.
 1. In the **Select the product you want to purchase** pane, select the **Scope** and **Subscription** you want to use for the reservation.
 1. Select the values you want from the dropdown lists for **Region**, **Term**, and **Billing frequency**.