Merge pull request #297301 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 3/31

Author: ttorble

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)

articles/data-factory/connector-oracle.md

@@ -86,7 +86,7 @@ The following sections provide details about properties that are used to define
 
 ## Linked service properties
 
-The Oracle connector now supports version 2.0 (Preview). Refer to this [section](#upgrade-the-oracle-connector) to upgrade your Oracle connector version from version 1.0. For the property details, see the corresponding sections.
+The Oracle connector version 2.0 (Preview) supports TLS 1.3. Refer to this [section](#upgrade-the-oracle-connector) to upgrade your Oracle connector version from version 1.0. For the property details, see the corresponding sections.
 
 - [Version 2.0 (Preview)](#version-20-preview)
 - [Version 1.0](#version-10)
@@ -672,3 +672,5 @@ The Oracle connector version 2.0 (Preview) offers new functionalities and is com
 |The following mappings are used from Oracle data types to interim service data types used by the service internally. <br><br>NUMBER(p,s) -> Int16, Int32, Int64, Double, Single, Decimal <br>FLOAT(p)-> Double or Decimal based on its precision <br>NUMBER -> Decimal <br>TIMESTAMP WITH TIME ZONE -> DateTimeOffset <br>INTERVAL YEAR TO MONTH -> Int64 <br>INTERVAL DAY TO SECOND ->  TimeSpan  |The following mappings are used from Oracle data types to interim service data types used by the service internally. <br><br>NUMBER(p,s) ->  Decimal or String based on its precision <br>FLOAT(p)-> Double  <br>NUMBER -> Double <br>TIMESTAMP WITH TIME ZONE -> DateTime <br>INTERVAL YEAR TO MONTH -> String <br>INTERVAL DAY TO SECOND ->  String  | 
 | Support convertDecimalToInteger in copy source when `supportV1DataTypes` is set to `true`. | Support convertDecimalToInteger in copy source.  | 
 | Using `?` as a placeholder for script activity query parameters is not support. You can use the named parameter (such as `:paramA`) or the positional parameter (such as `:1`) as a replacement.    | Support using `?` as a placeholder for script activity query parameters.  | 
+| Support TLS 1.3.| TLS 1.3 is not supported. | 
+

articles/hdinsight/load-balancer-migration-guidelines.md

@@ -6,7 +6,7 @@ ms.topic: how-to
 author: abhishjain002
 ms.author: abhishjain
 ms.reviewer: sairamyeturi
-ms.date: 03/03/2025
+ms.date: 03/31/2025
 ---
 
 # Basic Load balancer deprecation: Guidelines for Azure HDInsight
@@ -132,7 +132,12 @@ NAT gateway provides outbound network connectivity for the cluster. NSG controls
 
          
        * **Method 2:** Create a new subnet and then create the cluster with the new subnet.
- 
+
+> [!IMPORTANT]
+> * If you experience job slowness or network issues after cluster recreation with a standard load balancer, check the "Total SNAT Connection Count" and "Dropped Packets" on your NAT Gateway. High values may indicate SNAT port exhaustion. To address this, consider implementing one of the following methods:
+>   * Bind additional IP addresses or IP prefixes to your NAT Gateway. For more information, see [Troubleshoot Azure NAT Gateway connectivity](/azure/nat-gateway/troubleshoot-nat-connectivity) and [Metrics and alerts for Azure NAT Gateway](/azure/nat-gateway/nat-metrics#total-snat-connection-count).
+>   * Enable private link to storage accounts which could reduce SNAT port dependency. For more information, see [Use private endpoints for Azure Storage](/azure/storage/common/storage-private-endpoints).
+
 > [!NOTE]
 > If you are using an ESP cluster with MFA disabled, ensure to check the MFA status once cluster is recreated using a NAT gateway.
 

articles/hdinsight/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md

@@ -3,10 +3,10 @@ title: Use Managed Identity for SQL Database authentication in Azure HDInsight
 description: Learn how to use managed identity for SQL Database authentication in Azure HDInsight. 
 ms.service: azure-hdinsight 
 ms.topic: how-to 
-author: hareshg
-ms.author: hgowrisankar
+author: abhishjain002
+ms.author: abhishjain
 ms.reviewer: nijelsf
-ms.date: 01/09/2025 
+ms.date: 03/31/2025 
 ---
 
 # Use Managed Identity for SQL Database authentication in Azure HDInsight 
@@ -33,7 +33,6 @@ The Managed Identity (MI) option is available for the following Databases:
 > * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
 > * When you recreate an MSI with the same name, you must recreate the contained user and reassign roles, as the new MSI will have different object and client IDs even if the name remains unchanged.
 
-
 ## Steps to Use Managed Identity during cluster creation in Azure portal
 
 1. During cluster creation, navigate to the Storage section and select the SQL database for Ambari/Hive/Oozie. Choose Managed Identity as the Authentication method.
@@ -56,7 +55,7 @@ Object ID of managed identity can be obtained from portal on the managed identit
    > For example: 
    > * MSI Name: contosoMSI 
    > * Object ID: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`
-   > * user_name could be `contosoMSI-2ba6c`
+   > * user_name could be `contosoMSI_aaaaaaaa`
 
 
     ``` 

articles/iot/iot-overview-analyze-visualize.md

@@ -15,7 +15,7 @@ ms.custom: template-overview
 
 This overview introduces the key concepts around the options to analyze and visualize your IoT data. Each section includes links to content that provides further detail and guidance.
 
-In Azure IoT, analysis and visualization services are used to identify and display business insights derived from your IoT data. For example, you can use a machine learning model to analyze device telemetry and predict when maintenance should be carried out on an industrial asset. You can also use a visualization tool to display a map of the location of your devices.
+In Azure IoT, analysis and visualization services are used to identify and display business insights derived from your IoT data. For example, you can use a machine learning model to analyze device sensor data and predict when maintenance should be carried out on an industrial asset. You can also use a visualization tool to display a map of the location of your devices.
 
 # [Edge-based solution](#tab/edge)
 
@@ -55,6 +55,14 @@ The following articles show some examples of how to use Microsoft Fabric to anal
 - [Tutorial: Get insights from your processed data](../iot-operations/end-to-end-tutorials/tutorial-get-insights.md)
 - [Tutorial: Send data from an OPC UA server to Azure Data Lake Storage Gen 2](../iot-operations/connect-to-cloud/tutorial-opc-ua-to-data-lake.md)
 
+### Azure Machine Learning
+
+[Azure Machine Learning](/azure/machine-learning/overview-what-is-azure-machine-learning) is a cloud-based service for building, training, and deploying machine learning models. It provides a variety of tools and services to help you create and manage machine learning workflows. You can use Azure Machine Learning to analyze IoT data and build predictive models. On Azure Arc-enabled Kubernetes clusters, such as Azure IoT Operations, you can train and deploy machine learning models at the edge with the [Kubernetes compute target in Azure Machine Learning](/azure/machine-learning/how-to-attach-kubernetes-anywhere).
+
+- [Deploy Azure Machine Learning extension on Arc-enabled Kubernetes cluster](/azure/machine-learning/how-to-deploy-kubernetes-extension)
+- [Enable machine learning inference on an Azure IoT Edge device](/azure/architecture/guide/iot/machine-learning-inference-iot-edge)
+
+
 ### Azure Data Explorer
 
 [Azure Data Explorer](/azure/data-explorer/data-explorer-overview/) is a fully managed, high-performance, big-data analytics platform that makes it easy to analyze high volumes of data in near real time. The following articles and tutorials show some examples of how to use Azure Data Explorer to analyze and visualize IoT data:

articles/iot/iot-overview-device-connectivity.md

@@ -207,7 +207,7 @@ Azure IoT Operations is an edge runtime environment that hosts the services to c
 
 Data flows provide data transformation and data contextualization capabilities before routing messages to various locations including cloud endpoints.
 
-Azure IoT Operations runs on Azure Arc-enabled edge Kubernetes clusters, enabling a fully automated machine learning operations in hybrid mode, including training and AI model deployment steps that transition seamlessly between cloud and edge. To learn more, see [Introduction to Kubernetes compute target in Azure Machine Learning](/azure/machine-learning/how-to-attach-kubernetes-anywhere).
+Azure IoT Operations runs on Azure Arc-enabled Kubernetes clusters, enabling a fully automated machine learning operations in hybrid mode, including training and AI model deployment steps that transition seamlessly between cloud and edge. To learn more, see [Introduction to Kubernetes compute target in Azure Machine Learning](/azure/machine-learning/how-to-attach-kubernetes-anywhere).
 
 ### [Cloud-based solution](#tab/cloud)
 

articles/iot/iot-services-and-technologies.md

@@ -155,7 +155,7 @@ To learn more, see [Azure IoT device and service SDKs](iot-sdks.md).
 
 > Azure IoT Plug and Play is a programming model that enables you to build a **cloud-based IoT solution** that use IoT Hub or IoT Central.
 
-IoT Plug and Play enables solution builders to integrate IoT devices with their solutions without any manual configuration. At the core of IoT Plug and Play, is a device _model_ that a device uses to advertise its capabilities to an IoT Plug and Play-enabled service such as IoT Hub, IoT Central or Azure Digital Twins. You define IoT Plug and Play models and interfaces using the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/README.md).
+IoT Plug and Play enables solution builders to integrate IoT devices with their solutions without any manual configuration. At the core of IoT Plug and Play, is a device _model_ that a device uses to advertise its capabilities to an IoT Plug and Play-enabled service such as IoT Central or Azure Digital Twins. You define IoT Plug and Play models and interfaces using the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/README.md).
 
 To learn more, see [What is IoT Plug and Play?](overview-iot-plug-and-play.md).