Merge pull request #306495 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-03 22:00 UTC

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

articles/azure-fluid-relay/concepts/customer-managed-keys.md

@@ -212,6 +212,14 @@ For more information about the command, see [az fluid-relay server update](/cli/
 
 ---
 
+## Delete an Azure Fluid Relay Resource with CMK enabled
+
+Deleting a Customer-Managed Key (CMK) enabled Azure Fluid Relay resource follows the same process as deleting a standard Fluid Relay resource. However, you must ensure that the Fluid Relay resource is deleted **before** its CMK dependencies, such as the encryption key, Key Vault and any user-assigned managed identities.
+
+If you provision the Fluid Relay resource and its CMK dependencies (Key Vault and user-assigned identity) in the same resource group, you must explicitly delete the Fluid Relay resource first. Otherwise, attempting to delete the entire resource group at once will fail because the Fluid Relay resource cannot be removed after its dependencies are deleted.
+
+---
+
 ## Troubleshooting
 
 ### Error: Unexpected error happened when configuring CMK

articles/azure-functions/functions-bindings-azure-mysql-trigger.md

@@ -9,16 +9,13 @@ ms.custom:
   - devx-track-js
   - devx-track-python
   - ignite-2023
-ms.date: 6/26/2024
+ms.date: 10/03/2025
 ms.author: bspendolini
 ms.reviewer: glenga
 zone_pivot_groups: programming-languages-set-functions-lang-workers
 ---
 
-# Azure Database for MySQL trigger binding for Azure Functions (preview)
-
-> [!NOTE]
-> Although input and output bindings are supported on all plans, Azure Database for MySQL trigger binding is available only on [Dedicated and Premium plans](functions-scale.md) during the preview.
+# Azure Database for MySQL trigger binding for Azure Functions
 
 Azure Database for MySQL trigger bindings monitor the user table for changes (inserts and updates) and invoke the function with updated row data.
 

articles/azure-functions/functions-bindings-azure-mysql.md

@@ -3,7 +3,7 @@ title: Azure Database for MySQL Bindings for Functions
 description: Understand how to use Azure Database for MySQL bindings in Azure Functions.
 author: JetterMcTedder
 ms.topic: reference
-ms.date: 10/26/2024
+ms.date: 10/03/2025
 ms.author: bspendolini
 ms.reviewer: glenga
 zone_pivot_groups: programming-languages-set-functions-lang-workers
@@ -18,13 +18,13 @@ ms.custom:
 
 # Overview of Azure Database for MySQL bindings for Azure Functions
 
-This set of articles explains how to work with [Azure Database for MySQL](/azure/mysql/index) bindings in Azure Functions. Azure Functions supports input bindings and output bindings in general availability. For the preview, Azure Functions supports trigger bindings for Azure Database for MySQL.
+This set of articles explains how to work with [Azure Database for MySQL](/azure/mysql/index) bindings in Azure Functions. Azure Functions supports input bindings, output bindings and trigger bindings in general availability for Azure Database for MySQL
 
 | Action | Type |
 |---------|---------|
 | Read data from a database | [Input binding](./functions-bindings-azure-mysql-input.md) |
 | Save data to a database |[Output binding](./functions-bindings-azure-mysql-output.md) |
-| Trigger a function when a change is detected in a MySQL table (preview) | [Trigger binding](./functions-bindings-azure-mysql-trigger.md) |
+| Trigger a function when a change is detected in a MySQL table | [Trigger binding](./functions-bindings-azure-mysql-trigger.md) |
 
 ::: zone pivot="programming-language-csharp"
 
@@ -36,20 +36,20 @@ The extension NuGet package that you install depends on the C# mode you're using
 
 Functions run in an isolated C# worker process. To learn more, see [Guide for running C# Azure functions in an isolated worker process](dotnet-isolated-process-guide.md).
 
-Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.MySql/1.0.3-preview/).
+Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.MySql/1.0.129/).
 
 ```bash
-dotnet add package Microsoft.Azure.Functions.Worker.Extensions.MySql --version 1.0.3-preview
+dotnet add package Microsoft.Azure.Functions.Worker.Extensions.MySql --version 1.0.129
 ```
 
 # [In-process model](#tab/in-process)
 
 Functions run in the same process as the Azure Functions host. To learn more, see [Develop C# class library functions using Azure Functions](functions-dotnet-class-library.md).
 
-Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.MySql/1.0.3-preview).
+Add the extension to your project by installing [this NuGet package](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.MySql/1.0.129).
 
 ```bash
-dotnet add package Microsoft.Azure.WebJobs.Extensions.MySql --version 1.0.3-preview
+dotnet add package Microsoft.Azure.WebJobs.Extensions.MySql --version 1.0.129
 ```
 
 ---
@@ -62,15 +62,15 @@ dotnet add package Microsoft.Azure.WebJobs.Extensions.MySql --version 1.0.3-prev
 
 The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./extension-bundles.md). This bundle is specified in your host.json project file.
 
-### Preview bundle v4.x
+### Bundle v4.x
 
-You can use the preview extension bundle by adding or replacing the following code in your host.json file:
+You can use the extension bundle by adding or replacing the following code in your host.json file:
 
 ```json
 {
   "version": "2.0",
   "extensionBundle": {
-    "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
+    "id": "Microsoft.Azure.Functions.ExtensionBundle",
     "version": "[4.*, 5.0.0)"
   }
 }
@@ -86,15 +86,15 @@ You can use the preview extension bundle by adding or replacing the following co
 
 The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./extension-bundles.md). This bundle is specified in your host.json project file.
 
-### Preview bundle v4.x
+### Bundle v4.x
 
-You can use the preview extension bundle by adding or replacing the following code in your host.json file:
+You can use the extension bundle by adding or replacing the following code in your host.json file:
 
 ```json
 {
   "version": "2.0",
   "extensionBundle": {
-    "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
+    "id": "Microsoft.Azure.Functions.ExtensionBundle",
     "version": "[4.*, 5.0.0)"
   }
 }
@@ -110,15 +110,15 @@ You can use the preview extension bundle by adding or replacing the following co
 
 The extension for Azure Database for MySQL bindings is part of the v4 [extension bundle](./extension-bundles.md). This bundle is specified in your host.json project file.
 
-### Preview bundle v4.x
+### Bundle v4.x
 
-You can use the preview extension bundle by adding or replacing the following code in your host.json file:
+You can use the extension bundle by adding or replacing the following code in your host.json file:
 
 ```json
 {
   "version": "2.0",
   "extensionBundle": {
-    "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
+    "id": "Microsoft.Azure.Functions.ExtensionBundle",
     "version": "[4.*, 5.0.0)"
   }
 }
@@ -128,13 +128,13 @@ You can use the preview extension bundle by adding or replacing the following co
 
 ## Update packages
 
-You can use the preview extension bundle with an update to the pom.xml file in your Java Azure Functions project, as shown in the following snippet:
+You can use the extension bundle with an update to the pom.xml file in your Java Azure Functions project, as shown in the following snippet:
 
 ```xml
 <dependency>
 <groupId>com.microsoft.azure.functions</groupId>
 <artifactId>azure-functions-java-library-mysql</artifactId>
-<version>1.0.1-preview</version>
+<version>1.0.2</version>
 </dependency>
 ```
 

articles/azure-functions/functions-reference-node.md

@@ -1862,7 +1862,7 @@ Before upgrading your Node.js version, make sure your function app is running on
 Run the Azure CLI [`az functionapp config appsettings set`](/cli/azure/functionapp/config#az-functionapp-config-appsettings-set) command to update the Node.js version for your function app running on Windows:
 
 ```azurecli-interactive
-az functionapp config appsettings set  --settings WEBSITE_NODE_DEFAULT_VERSION=~20 \
+az functionapp config appsettings set  --settings WEBSITE_NODE_DEFAULT_VERSION=~22 \
  --name <FUNCTION_APP_NAME> --resource-group <RESOURCE_GROUP_NAME>
 ```
 
@@ -1883,7 +1883,7 @@ az functionapp config set --linux-fx-version "node|22" --name "<FUNCTION_APP_NAM
  --resource-group "<RESOURCE_GROUP_NAME>"
 ```
 
-This sets the base image of the Linux function app to Node.js version 20.
+This sets the base image of the Linux function app to Node.js version 22.
 
 # [Azure portal](#tab/azure-portal/linux)
 

articles/dev-box/dev-box-windows-365-announcement.md

@@ -14,17 +14,75 @@ ms.service: dev-box
 
 # Microsoft Dev Box capabilities are coming to Windows 365
 
-Windows 365 delivers personalized, persistent Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. The Microsoft Dev Box service in Azure extends this vision by providing ready-to-code, cloud-powered development environments that enable developers to quickly spin up secure, ready-to-code, project-specific workspaces optimized for productivity. We are excited to announce that we're bringing these developer-specific capabilities to Windows 365, further empowering organizations to deliver the best information worker and developer experiences from a single unified solution.
+Microsoft Dev Box is evolving and transitioning into a unified business model under Windows 365. This transition reflects feedback from customers who asked for: 
 
-Dev Box is built on Windows 365, and by consolidating these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution, and seamless integration with enterprise identity and security. IT admins and platform engineers can leverage more centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place.
+- A predictable business model that scales with enterprise adoption. 
+- Support for smaller SKUs (2 vCPU, 4 vCPU). 
+- Access to a broader range of options, including GPU-backed SKUs. 
+- Greater flexibility to support hybrid and ephemeral development scenarios. 
 
+Windows 365 delivers personalized, persistent Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. The Microsoft Dev Box service in Azure extends this vision by providing ready-to-code, cloud-powered development environments that enable developers to quickly spin up secure, ready-to-code, project-specific workspaces optimized for productivity. 
 
-Effective *November 1, 2025*, the following changes will take place:
+We're excited to announce that we're bringing these developer-specific capabilities to Windows 365, further empowering organizations to deliver the best information worker and developer experiences from a single unified solution. 
 
-- The Dev Box service will *stop accepting new customers*. Customers interested in the Dev Box capabilities should reach out to their Microsoft account team to begin learning about Windows 365.
-- *Existing Dev Box customers can continue to use and expand their Dev Box deployments* while new capabilities are being introduced in Windows 365. As new capabilities are available in Windows 365, we will provide resources to customers to support a smooth migration. No immediate action is required.
+Dev Box is built on Windows 365, and by consolidating these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution, and seamless integration with enterprise identity and security. IT admins and platform engineers can use more centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place. 
 
-For more details, contact your Microsoft account team with additional questions.
+Effective November 1, 2025, the following changes will take place: 
+
+- The Microsoft Dev Box service stops accepting net new customers. 
+    - *Net new customers* are defined as those with no prior Dev Box deployment in any form. 
+    - As features are integrated into Windows 365 and made available publicly, Customers interested in continuing to leverage these capabilities should reach out to their Microsoft account team. 
+- There's no immediate change to existing customers 
+    - Customers who have run a POC, experimented, or begun configuring Dev Box are considered as existing customers and they can continue using and scaling their current Dev Box deployments. 
+    - If you plan to start using or scaling Dev Boxes into additional tenants, submit a request through [Azure Support](https://go.microsoft.com/fwlink/p/?linkid=2202692&clcid=0x409) to your new tenants allowlisted.  
+
+All core workflows and value props remain intact - including managing development teams through the Dev Center/Project platform in Azure, configuring guardrails, providing self-serve capabilities for developers, and offering ready-to-code machines with imaging and customizations, as well as custom network support. 
+
+As new developer capabilities are released in Windows 365, Microsoft will provide resources and tools to ensure a smooth transition.  
+
+## Key Actions for Customers 
+
+- **No Immediate Action Required:** Continue using and scaling your Dev Box deployments as usual. Migration resources will be provided as new features roll out in Windows 365. 
+- **Stay Informed:** Monitor communications from Microsoft and your account team for updates. 
+- **Interested in Previewing New Features?** Express your interest to your Microsoft account team. 
+
+## Frequently Asked Questions (FAQs) 
+
+### Why is Microsoft making this change? 
+
+Dev Box is built on Windows 365, and by transitioning these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution with additional SKUs to choose from, and seamless integration with enterprise identity and security. By consolidating value propositions, we aim to offer a predictable license-based business model. Each license will allow the creation of three persistent dev boxes and one active connection, supporting ephemeral scenarios, and a broader range of SKUs, including 2-core, 4-core, 8-core, and 16-core GPU options. This shift addresses critical feedback from our customers. 
+
+### Which edition of Windows 365 will incorporate Microsoft Dev Box functionalities? 
+
+Dev Box capabilities will be enabled with Windows 365 Frontline. This edition is best suited for developers who need flexible work setups, advanced workstations, and support for multi-environment and hybrid development scenarios, which benefit geographically distributed development teams. Each license will allow creation of three persistent workstations and provides nonconcurrent access for as many as three users. 
+
+### How do we define net new customers? 
+
+Net new customers are those with no prior deployment of Dev Box in any form. Existing customers, or those who have run a POC, experimented, or begun configuring Dev Box, aren't affected and can continue to use and scale their deployments.  
+
+### Will there be any changes to my core Dev Box experience? 
+
+No. All core workflows will remain unchanged, including management of development teams through the Dev Center/Project platform in Azure, configuration of guardrails, access to self-service for developers, provisioning ready-to-code machines with in-built imaging and customizations, and support for custom networks. The existing automation investments will continue to be relevant and are expected to require only minor modifications when you transition. 
+
+### Do I need to take any action before the transition? 
+
+No action is required at this time. You're encouraged to explore Windows 365 and engage with your Microsoft account team to evaluate licensing options. If you're also interested in participating in the upcoming preview of the new developer features in Windows 365, please contact your Microsoft account team. 
+
+### What is the transition timeline for existing customers? 
+
+As new capabilities become available in Windows 365, Microsoft will provide migration guidance and timelines. No immediate action is required. 
+
+### Will there be additional costs for using developer capabilities in Windows 365? 
+
+No. Customers who plan to use developer capabilities in Windows 365 once they become available will receive them as part of their Windows 365 license at no additional cost. 
+
+### How will my data and configurations be handled during migration? 
+
+As new capabilities become available, Microsoft will release migration guidance, including tools and timelines. Stay engaged with your account team for updates.
+
+### How can I try out new developer features in Windows 365 before they're released? 
+
+Previews will be available as features are integrated into Windows 365. Contact your Microsoft account team to express interest in joining the preview. 
 
 ## Related content
 - [Windows 365 integration with Microsoft Dev Box](https://aka.ms/WindowsSeptAnnouncements)