Skip to content

Commit 49a277a

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into yelevin/aux-logs-ga
2 parents 81acb38 + 181f8d4 commit 49a277a

33 files changed

+268
-204
lines changed

articles/business-continuity-center/index.yml

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ metadata:
1313
ms.topic: landing-page
1414
author: jyothisuri
1515
ms.author: jsuri
16-
ms.date: 03/03/2025
16+
ms.date: 03/25/2025
1717
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1818

1919
landingContent:
@@ -64,3 +64,11 @@ landingContent:
6464
links:
6565
- text: Manage BCDR estate (preview)
6666
url: tutorial-manage-data-using-copilot.md
67+
68+
# Card (optional)
69+
- title: Architecture
70+
linkLists:
71+
- linkListType: architecture
72+
links:
73+
- text: Well-Architecture design recommendation for monitoring/ alerting
74+
url: /azure/well-architected/reliability/monitoring-alerting-strategy#azure-facilitation

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Tutorial - Monitor alerts and metrics in Azure Business Continuity Center
33
description: In this tutorial, learn how to monitor alerts and configure notifications for your business continuity estate using Azure Business Continuity center.
44
ms.topic: tutorial
5-
ms.date: 12/30/2024
5+
ms.date: 03/30/2025
66
ms.service: azure-business-continuity-center
77
ms.custom:
88
- ignite-2023
@@ -76,6 +76,6 @@ To view metrics, follow these steps:
7676

7777
## Next steps
7878

79-
- [Configure datasources](./tutorial-configure-protection-datasource.md)
80-
79+
- [Configure datasources](./tutorial-configure-protection-datasource.md).
80+
- [Well-Architected Framework design recommendation for reliable monitoring and alerting strategy](/azure/well-architected/reliability/monitoring-alerting-strategy#azure-facilitation).
8181

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-business-continuity-center
66
ms.custom:
77
- ignite-2023
88
- ignite-2024
9-
ms.date: 11/19/2024
9+
ms.date: 03/30/2025
1010
author: jyothisuri
1111
ms.author: jsuri
1212
---
@@ -155,4 +155,5 @@ With the protected items view, you can choose to perform actions from:
155155

156156
## Next steps
157157

158-
For more information about Azure Business Continuity center and how it works, check out [Configure protection from ABC Center](./tutorial-configure-protection-datasource.md).
158+
- For more information about Azure Business Continuity center and how it works, check out [Configure protection from ABC Center](./tutorial-configure-protection-datasource.md).
159+
- [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/connectors/connectors-azure-monitor-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Both of the following actions can run a log query against a Log Analytics worksp
5050
| Max connector timeout | 110 seconds ||
5151
| Max query timeout | 100 seconds ||
5252

53-
To avoid reaching these limits, try aggregating data to reduce the results size, or adjusting the workflow recurrence to run more frequently across a smaller time range. However, due to caching, frequent queries with intervals less than 120 seconds aren't recommended.
53+
To avoid reaching these limits, try aggregating data to reduce the results size, or adjusting the workflow recurrence to run more frequently across a smaller time range.
5454

5555
- Visualizations on the Logs page and the connector use different charting libraries. So, the connector currently doesn't include some functionality.
5656

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.topic: how-to
66
author: abhishjain002
77
ms.author: abhishjain
88
ms.reviewer: sairamyeturi
9-
ms.date: 03/03/2025
9+
ms.date: 03/31/2025
1010
---
1111

1212
# Basic Load balancer deprecation: Guidelines for Azure HDInsight
@@ -132,7 +132,12 @@ NAT gateway provides outbound network connectivity for the cluster. NSG controls
132132

133133
134134
* **Method 2:** Create a new subnet and then create the cluster with the new subnet.
135-
135+
136+
> [!IMPORTANT]
137+
> * 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:
138+
> * 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).
139+
> * 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).
140+
136141
> [!NOTE]
137142
> If you are using an ESP cluster with MFA disabled, ensure to check the MFA status once cluster is recreated using a NAT gateway.
138143

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ title: Use Managed Identity for SQL Database authentication in Azure HDInsight
33
description: Learn how to use managed identity for SQL Database authentication in Azure HDInsight.
44
ms.service: azure-hdinsight
55
ms.topic: how-to
6-
author: hareshg
7-
ms.author: hgowrisankar
6+
author: abhishjain002
7+
ms.author: abhishjain
88
ms.reviewer: nijelsf
9-
ms.date: 01/09/2025
9+
ms.date: 03/31/2025
1010
---
1111

1212
# 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:
3333
> * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
3434
> * 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.
3535
36-
3736
## Steps to Use Managed Identity during cluster creation in Azure portal
3837

3938
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
5655
> For example:
5756
> * MSI Name: contosoMSI
5857
> * Object ID: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`
59-
> * user_name could be `contosoMSI-2ba6c`
58+
> * user_name could be `contosoMSI_aaaaaaaa`
6059
6160

6261
```

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: template-overview
1515

1616
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.
1717

18-
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.
18+
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.
1919

2020
# [Edge-based solution](#tab/edge)
2121

@@ -55,6 +55,14 @@ The following articles show some examples of how to use Microsoft Fabric to anal
5555
- [Tutorial: Get insights from your processed data](../iot-operations/end-to-end-tutorials/tutorial-get-insights.md)
5656
- [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)
5757

58+
### Azure Machine Learning
59+
60+
[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).
61+
62+
- [Deploy Azure Machine Learning extension on Arc-enabled Kubernetes cluster](/azure/machine-learning/how-to-deploy-kubernetes-extension)
63+
- [Enable machine learning inference on an Azure IoT Edge device](/azure/architecture/guide/iot/machine-learning-inference-iot-edge)
64+
65+
5866
### Azure Data Explorer
5967

6068
[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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ Azure IoT Operations is an edge runtime environment that hosts the services to c
207207

208208
Data flows provide data transformation and data contextualization capabilities before routing messages to various locations including cloud endpoints.
209209

210-
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).
210+
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).
211211

212212
### [Cloud-based solution](#tab/cloud)
213213

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ To learn more, see [Azure IoT device and service SDKs](iot-sdks.md).
155155

156156
> 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.
157157
158-
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).
158+
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).
159159

160160
To learn more, see [What is IoT Plug and Play?](overview-iot-plug-and-play.md).
161161

articles/role-based-access-control/best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: rolyon
55
manager: femila
66
ms.service: role-based-access-control
77
ms.topic: conceptual
8-
ms.date: 01/30/2024
8+
ms.date: 03/30/2025
99
ms.author: rolyon
1010
#Customer intent: As a dev, devops, or it admin, I want to learn how to best use Azure RBAC.
1111
---
@@ -22,7 +22,7 @@ When planning your access control strategy, it's a best practice to grant users
2222

2323
The following diagram shows a suggested pattern for using Azure RBAC.
2424

25-
![Azure RBAC and least privilege](./media/best-practices/rbac-least-privilege.png)
25+
:::image type="content" source="./media/best-practices/rbac-least-privilege.png" alt-text="Diagram of suggested pattern for using Azure RBAC and least privilege." lightbox="./media/best-practices/rbac-least-privilege.png":::
2626

2727
For information about how to assign roles, see [Assign Azure roles using the Azure portal](role-assignments-portal.yml).
2828

0 commit comments

Comments
 (0)