Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into iot-overview-consistency

Author: asergaz

.openpublishing.redirection.json

@@ -5749,6 +5749,26 @@
       "redirect_url": "/azure/vpn-gateway/point-to-site-vpn-client-cert-windows",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/sql-server-stretch-database/sql-server-stretch-database-encryption-tde.md",
+      "redirect_url": "/azure/azure-sql/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/sql-server-stretch-database/sql-server-stretch-database-tde-tsql.md",
+      "redirect_url": "/azure/azure-sql/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/sql-server-stretch-database/sql-server-stretch-database-index-all-articles.md",
+      "redirect_url": "/azure/azure-sql/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/sql-server-stretch-database/index.yml",
+      "redirect_url": "/azure/azure-sql/",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/vs-azure-tools-access-private-azure-clouds-with-visual-studio.md",
       "redirect_url": "/visualstudio/azure/vs-azure-tools-access-private-azure-clouds-with-visual-studio",

articles/application-gateway/for-containers/application-gateway-for-containers-components.md

@@ -86,7 +86,9 @@ A set of routing rules evaluates how the request for that hostname should be ini
 
 ### HTTP/2 Requests
 
-Application Gateway for Containers fully supports HTTP/2 protocol for communication from the client to the frontend. Communication from Application Gateway for Containers to the backend target uses the HTTP/1.1 protocol. The HTTP/2 setting is always enabled and can't be changed. If clients prefer to use HTTP/1.1 for their communication to the frontend of Application Gateway for Containers, they may continue to negotiate accordingly.
+Application Gateway for Containers supports both HTTP/2 and HTTP/1.1 protocols for communication between the client and the frontend. The HTTP/2 setting is always enabled and can't be changed. If clients prefer to use HTTP/1.1 for their communication to the frontend of Application Gateway for Containers, they may continue to negotiate accordingly.
+
+Communication between Application Gateway for Containers and the backend target is always via HTTP/1.1, except for gRPC, which uses HTTP/2.
 
 ### Modifications to the request
 

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

@@ -18,7 +18,7 @@ Binding to a function is a way of declaratively connecting your functions to oth
 
 You can mix and match different bindings to suit your function's specific scenario. Bindings are optional and a function might have one or multiple input and/or output bindings.
 
-Triggers and bindings let you avoid hardcoding access to other services. Your function receives data (for example, the content of a queue message) in function parameters. You send data (for example, to create a queue message) by using the return value of the function. 
+Triggers and bindings let you avoid hardcoding access to other services. Your function receives data (for example, the content of a queue message) in function parameters. You send data (for example, to create a queue message) by using the return value of the function.
 
 Consider the following examples of how you could implement different functions.
 
@@ -41,6 +41,8 @@ A function has a single trigger and one or more bindings. The type of binding is
 
 Triggers and bindings are defined differently depending on the development language. Make sure to select your language at the [top](#top) of the article.
 
+Trigger and binding names are limited to alphanumeric characters and `_`, the underscore.
+
 This example shows an HTTP triggered function with an output binding that writes a message to an Azure Storage queue.
 
 ::: zone pivot="programming-language-csharp"
@@ -52,7 +54,7 @@ The HTTP trigger (`HttpTrigger`) is defined on the `Run` method for a function n
 
 :::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-storage-queue-isolated/HttpExample.cs" range="11-14":::
 
-This example shows the `MultiResponse` object definition which both returns an `HttpResponse` to the HTTP request and also writes a message to a storage queue using a `QueueOutput` binding: 
+This example shows the `MultiResponse` object definition which both returns an `HttpResponse` to the HTTP request and also writes a message to a storage queue using a `QueueOutput` binding:
 
 :::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-storage-queue-isolated/HttpExample.cs" range="33-38":::
 
@@ -90,13 +92,13 @@ In Node.js for Functions version 3, you configure triggers and bindings in a fun
 
 ---
 
-::: zone-end  
+::: zone-end
 This example is an HTTP triggered function that creates a queue item for each HTTP request received.
 
-::: zone pivot="programming-language-javascript"  
+::: zone pivot="programming-language-javascript"
 ### [v4](#tab/node-v4)
 
-The `http` method on the exported `app` object defines an HTTP trigger, and the `storageQueue` method on `output` defines an output binding on this trigger.  
+The `http` method on the exported `app` object defines an HTTP trigger, and the `storageQueue` method on `output` defines an output binding on this trigger.
 
 :::code language="javascript" source="~/azure-functions-nodejs-v4/js/src/functions/storageQueueOutput1.js" :::
 
@@ -131,8 +133,8 @@ This example `function.json` file defines the HTTP trigger function that returns
 
 ---
 
-::: zone-end  
-::: zone pivot="programming-language-typescript"  
+::: zone-end
+::: zone pivot="programming-language-typescript"
 ### [v4](#tab/node-v4)
 
 The `http` method on the exported `app` object defines an HTTP trigger, and the `storageQueue` method on `output` defines an output binding on this trigger.
@@ -168,20 +170,20 @@ This example `function.json` file defines the HTTP trigger function that returns
 }
 ```
 
-::: zone-end  
-::: zone pivot="programming-language-powershell"  
+::: zone-end
+::: zone pivot="programming-language-powershell"
 This example `function.json` file defines the function:
 
 :::code language="json" source="~/functions-docs-powershell/functions-add-output-binding-storage-queue-cli/HttpExample/function.json" range="3-26":::
 
 For more information, see the [PowerShell developer guide](functions-reference-powershell.md#bindings).
-::: zone-end  
-::: zone pivot="programming-language-python"  
+::: zone-end
+::: zone pivot="programming-language-python"
 The way that the function is defined depends on the version of Python for Functions:
 
 ### [v2](#tab/python-v2)
 
-In Python for Functions version 2, you define the function directly in code using decorators. 
+In Python for Functions version 2, you define the function directly in code using decorators.
 
 :::code language="python" source="~/functions-docs-python-v2/function_app.py" range="4-9" :::
 
@@ -194,25 +196,25 @@ In Python for Functions version 1, this example `function.json` file defines an
 
 ---
 
-::: zone-end  
+::: zone-end
 
 ## Add bindings to a function
 
-You can connect your function to other services by using input or output bindings. Add a binding by adding its specific definitions to your function. To learn how, see [Add bindings to an existing function in Azure Functions](add-bindings-existing-function.md).  
+You can connect your function to other services by using input or output bindings. Add a binding by adding its specific definitions to your function. To learn how, see [Add bindings to an existing function in Azure Functions](add-bindings-existing-function.md).
 
-Azure Functions supports multiple bindings, which must be configured correctly. For example, a function can read data from a queue (input binding) and write data to a database (output binding) simultaneously. 
+Azure Functions supports multiple bindings, which must be configured correctly. For example, a function can read data from a queue (input binding) and write data to a database (output binding) simultaneously.
 
 ## Supported bindings
 
 [!INCLUDE [Full bindings table](../../includes/functions-bindings.md)]
 
-For information about which bindings are in preview or are approved for production use, see [Supported languages](supported-languages.md). 
+For information about which bindings are in preview or are approved for production use, see [Supported languages](supported-languages.md).
 
 Specific binding extension versions are only supported while the underlying service SDK is supported. Changes to support in the underlying service SDK version affect the support for the consuming extension.
 
 ## Bindings code examples
 
-Use the following table to find more examples of specific binding types that show you how to work with bindings in your functions. First, choose the language tab that corresponds to your project. 
+Use the following table to find more examples of specific binding types that show you how to work with bindings in your functions. First, choose the language tab that corresponds to your project.
 
 [!INCLUDE [functions-bindings-code-example-chooser](../../includes/functions-bindings-code-example-chooser.md)]
 

articles/azure-maps/open-source-projects.md

@@ -71,7 +71,6 @@ Find more open-source Azure Maps projects.
 
 [@azure-maps/animations]: https://www.npmjs.com/package/@azure-maps/animations
 [@azure-maps/gridded-data-source]: https://www.npmjs.com/package/@azure-maps/gridded-data-source
-[Azure Maps & Microsoft Entra ID Samples]: https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples
 [Azure Maps Animation module]: https://github.com/Azure-Samples/azure-maps-animations
 [Azure Maps Bring Data Into View Control module]: https://github.com/Azure-Samples/azure-maps-bring-data-into-view-control
 [Azure Maps Code Samples]: https://github.com/Azure-Samples/AzureMapsCodeSamples
@@ -87,7 +86,6 @@ Find more open-source Azure Maps projects.
 [Azure Maps Sync Map module]: https://github.com/Azure-Samples/azure-maps-sync-maps
 [Code samples]: /samples/browse/?products=azure-maps
 [Getting Started]: https://azure.github.io/react-azure-maps-playground/?path=/docs/getting-started--docs
-[Implement IoT spatial analytics using Azure Maps]: https://github.com/Azure-Samples/iothub-to-azure-maps-geofencing
 [React Azure Maps Playground]: https://azure.github.io/react-azure-maps-playground/?path=/docs/getting-started--docs
 [react-azure-maps]: https://github.com/Azure/react-azure-maps
 [react-azure-maps-npm]: https://www.npmjs.com/package/react-azure-maps

articles/business-continuity-center/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.topic: landing-page
   author: jyothisuri
   ms.author: jsuri
-  ms.date: 03/03/2025
+  ms.date: 03/25/2025
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
@@ -64,3 +64,11 @@ landingContent:
         links:
           - text: Manage BCDR estate (preview)
             url: tutorial-manage-data-using-copilot.md
+
+  # Card (optional)
+  - title: Architecture
+    linkLists:
+      - linkListType: architecture
+        links:
+          - text: Well-Architecture design recommendation for monitoring/ alerting
+            url: /azure/well-architected/reliability/monitoring-alerting-strategy#azure-facilitation

articles/business-continuity-center/tutorial-monitor-alerts-metrics.md

@@ -2,7 +2,7 @@
 title: Tutorial - Monitor alerts and metrics in Azure Business Continuity Center
 description: In this tutorial, learn how to monitor alerts and configure notifications for your business continuity estate using Azure Business Continuity center.
 ms.topic: tutorial
-ms.date: 12/30/2024
+ms.date: 03/30/2025
 ms.service: azure-business-continuity-center
 ms.custom:
   - ignite-2023
@@ -76,6 +76,6 @@ To view metrics, follow these steps:
 
 ## Next steps
 
-- [Configure datasources](./tutorial-configure-protection-datasource.md)
-
+- [Configure datasources](./tutorial-configure-protection-datasource.md).
+- [Well-Architected Framework design recommendation for reliable monitoring and alerting strategy](/azure/well-architected/reliability/monitoring-alerting-strategy#azure-facilitation).
 

articles/business-continuity-center/tutorial-view-protected-items-and-perform-actions.md

@@ -6,7 +6,7 @@ ms.service: azure-business-continuity-center
 ms.custom:
   - ignite-2023
   - ignite-2024
-ms.date: 11/19/2024
+ms.date: 03/30/2025
 author: jyothisuri
 ms.author: jsuri
 ---
@@ -155,4 +155,5 @@ With the protected items view, you can choose to perform actions from:
 
 ## Next steps
 
-For more information about Azure Business Continuity center and how it works, check out [Configure protection from ABC Center](./tutorial-configure-protection-datasource.md).
+- For more information about Azure Business Continuity center and how it works, check out [Configure protection from ABC Center](./tutorial-configure-protection-datasource.md).
+- [Cloud-Adoption Framework for business continuity and disaster recovery of SAP migration](/azure/cloud-adoption-framework/scenarios/sap/eslz-business-continuity-and-disaster-recovery#backup-and-restore).

articles/container-apps/services.md

@@ -4,20 +4,108 @@ description: Learn how to use runtime services in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
-ms.custom:
-  - ignite-2023
 ms.topic: conceptual
-ms.date: 11/02/2023
+ms.date: 03/31/2025
 ms.author: cshoe
 ---
 
 # Connect to services in Azure Container Apps (preview)
 
-As you develop applications in Azure Container Apps, you often need to connect to different services. Rather than creating services ahead of time and manually connecting them to your container app, you can quickly create instances of development-grade services that are designed for nonproduction environments known as add-ons.
+> [!IMPORTANT]
+> The public preview add-ons feature will be retired on September 30, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for a production-level service. For development and testing purposes, review the supported open-source software (OSS) quickstart images.
 
-Add-ons allow you to use OSS services without the burden of manual downloads, creation, and configuration.
+As you develop applications in Azure Container Apps, you often need to connect to different services. Rather than creating services ahead of time and manually connecting them to your container app, you can quickly create instances of development-grade services that are designed for nonproduction environments known as add-ons. 
 
-Once you're ready for your app to use a production level service, you can connect your application to an Azure managed service.
+Add-ons allow you to use OSS services without the burden of manual downloads, creation, and configuration. Since add-ons will be retired on September 30, 2025, we recommend you use our new OSS quickstarts if you want to continue using these OSS services for nonproduction environments.
+
+If you're ready for your app to use a production level service, you can connect your application to an Azure managed service.
+
+## Migration Guide
+
+As add-ons are being retired, you need to plan how to transition your applications away from this preview feature. Use the following steps help you for either a production level service if you're using open source technologies in a development or testing capacity.
+
+Make sure you prepare for data continuity between your add-on and your new Container App.
+
+### Option 1: Transition to Azure managed services
+
+If you're ready for a production level service, follow these steps to transition your add-on to an Azure managed service.
+
+1. Identify add-ons in use. Run the following command to locate all existing add-ons in your environment.
+
+    Before you run the following command, make sure to replace the placeholders surrounded by `<>` with you values.
+
+    ```azurecli
+    az containerapp add-on list \
+      --environment <ENVIRONMENT_NAME> \
+      --resource-group <RESOURCE_GROUP>
+    ```
+  
+1. Plan data continuity.
+
+    Create a backup or snapshot of your data in the current add-on if applicable.  
+
+1. Deploy the new managed service.
+
+    For example, create an [Azure Cache for Redis](/azure/azure-cache-for-redis/scripts/create-manage-cache?pivots=azure-managed-redis) or [Azure Database for PostgreSQL](/azure/postgresql/) instance using the Azure portal or CLI.
+
+1. Create a new container app.
+
+    Create a new app using the [Azure portal](quickstart-portal.md) or [CLI](get-started.md?tabs=bash).
+
+1. Configure connection settings.
+
+    In your new container app configuration, set the environment variables and network settings to point to your new managed service’s connection string, credentials, and endpoints.
+  
+1. Remove the add-on.
+
+    Once the add-on is no longer needed, delete it with the following command.
+
+    Before you run the following command, make sure to replace the placeholders surrounded by `<>` with you values.
+
+    ```azurecli
+    az containerapp add-on <SERVICE_TYPE> delete \
+      --name <ADDON_NAME> \
+      --resource-group <RESOURCE-GROUP>
+    ```
+
+### Option 2: Use open source quickstart images
+
+If you only need these services for development or testing environments and don't require production-level guarantees, follow these steps to switch to use the open-source quickstart images. 
+
+1. Identify add-ons in use. Run the following command to locate all existing add-ons in your environment.
+
+    Before you run the following command, make sure to replace the placeholders surrounded by `<>` with you values.
+
+    ```azurecli
+    az containerapp add-on list \
+      --environment <ENVIRONMENT_NAME> \
+      --resource-group <RESOURCE_GROUP>
+    ```
+
+1. Review the supported quickstart images: Redis, PostgreSQL, MariaDB, Qdrant, and Kafka. 
+
+1. Plan data continuity.
+
+    Create a backup or snapshot of your data in the current add-on if applicable.
+
+1. Create a new [Container App](quickstart-portal.md) using a quickstart image.
+
+1. Remove the add-on.
+
+    Once the add-on is no longer needed, delete it with the following command.
+
+    Before you run the following command, make sure to replace the placeholders surrounded by `<>` with you values.
+
+    ```azurecli
+    az containerapp add-on <SERVICE_TYPE> delete \
+      --name <ADDON_NAME> \
+      --resource-group <RESOURCE-GROUP>
+    ```
+
+## Add-ons
+
+> [!IMPORTANT]
+> The public preview add-ons feature will be retired on September 30, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for a production-level service. For development and testing purposes, review the supported open-source quickstarts. 
 
 Services available as an add-on include:
 
@@ -81,7 +169,7 @@ You're responsible for data continuity between development and production enviro
 
 To connect a service to an application, you first need to create the service.
 
-Use the `az containerapp add-on <SERVICE_TYPE> create` command with the service type and name to create a new service.
+To create a new service, use the `az containerapp add-on <SERVICE_TYPE> create` command with the service type and name.
 
 ``` CLI
 az containerapp add-on redis create \
@@ -124,9 +212,9 @@ For more information on the service commands and arguments, see the
 - Add-ons are in public preview.
 - Any container app created before May 23, 2023 isn't eligible to use add-ons.
 - Add-ons come with minimal guarantees. For instance, they're automatically restarted if they crash, however there's no formal quality of service or high-availability guarantees associated with them. For production workloads, use Azure-managed services.
-- If you use your own VNET, you must use a workload profiles environment. The Add-ons feature is not supported in consumption only environments that use custom VNETs.
+- If you use your own virtual network (virtual network), you must use a workload profiles environment. The Add-ons feature isn't supported in consumption only environments that use custom virtual networks.
 
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Connect services to a container app](connect-services.md)
+> [Connect services to a container app](connect-services.md)