Merge pull request #283821 from MicrosoftDocs/main

PMEds28 · web-flow · commit 87d188b17293 · 2024-08-07T12:18:04.000+01:00
Publish to Live Wednesday 4AM PST 8/7
diff --git a/articles/azure-monitor/alerts/itsmc-dashboard-errors.md b/articles/azure-monitor/alerts/itsmc-dashboard-errors.md
@@ -3,7 +3,7 @@ title: Connector status errors in the ITSMC dashboard
 description: Learn about common errors that exist in the IT Service Management Connector dashboard. 
 ms.author: abbyweisberg
 ms.topic: conceptual
-ms.date: 06/19/2023
+ms.date: 08/06/2024
 ms.reviewer: nolavime
 ---
 
diff --git a/articles/certification/edge-secured-core-devices.md b/articles/certification/edge-secured-core-devices.md
@@ -4,7 +4,7 @@ description: List of devices that have passed the Edge Secured-core certificatio
 author: sufenfong
 ms.author: sufon
 ms.topic: conceptual 
-ms.date: 07/22/2024 
+ms.date: 08/06/2024 
 ms.custom: Edge Secured-core certified devices
 ms.service: azure-certified-device
 ---
@@ -16,7 +16,8 @@ This page contains a list of devices that have successfully passed the Edge Secu
 ---|---|---|---
 |AAEON|[SRG-TG01](https://newdata.aaeon.com.tw/DOWNLOAD/2014%20datasheet/Systems/SRG-TG01.pdf)|Windows 10 IoT Enterprise|2022-06-14|
 |Advantech|[ITA-580](https://www.advantech.com/en-eu/products/5130beef-2b81-41f7-a89b-2c43c1f2b6e9/ita-580/mod_bf7b0383-e6b2-49d7-9181-b6fc752e188b)|Windows 10 IoT Enterprise|2024-07-08|
-|Asus|[PE200U](https://www.asus.com/networking-iot-servers/aiot-industrial-solutions/embedded-computers-edge-ai-systems/pe200u/)|Windows 10 IoT Enterprise|2022-04-20|
+|Asus|[NUC13L5K-B (i5)](https://www.asus.com/us/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-13-pro/)|Windows 10 IoT Enterprise|2024-08-01|
+|Asus|[NUC13L5K-B (i7)](https://www.asus.com/us/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-13-pro/)|Windows 10 IoT Enterprise|2024-08-01|
 |Asus|[PN64-E1 vPro](https://www.asus.com/ca-en/displays-desktops/mini-pcs/pn-series/asus-expertcenter-pn64-e1/)|Windows 10 IoT Enterprise|2023-08-08|
 |Asus|[NUC13L3Hv7](https://www.asus.com/us/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-13-pro/)|Windows 10 IoT Enterprise|2023-04-28|
 |Asus|[NUC13L3Hv5](https://www.asus.com/us/displays-desktops/nucs/nuc-mini-pcs/asus-nuc-13-pro/)|Windows 10 IoT Enterprise|2023-04-12|
@@ -26,4 +27,5 @@ This page contains a list of devices that have successfully passed the Edge Secu
 |Asus|[NUC12WSKV7](https://www.asus.com/us/displays-desktops/nucs/nuc-kits/asus-nuc-12-pro/)|Windows 10 IoT Enterprise|2022-10-31|
 |Asus|BELM12HBv716W+CMB1AB|Windows 10 IoT Enterprise|2022-10-25|
 |Asus|[NUC11TNHv5000](https://www.asus.com/us/displays-desktops/nucs/nuc-kits/nuc-11-pro-kit/)|Windows 10 IoT Enterprise|2022-06-14|
+|Asus|[PE200U](https://www.asus.com/networking-iot-servers/aiot-industrial-solutions/embedded-computers-edge-ai-systems/pe200u/)|Windows 10 IoT Enterprise|2022-04-20|
 |Lenovo|[ThinkEdge SE30](https://www.lenovo.com/us/en/p/desktops/thinkedge/thinkedge-se30/len102c0004)|Windows 10 IoT Enterprise|2022-04-06|
diff --git a/articles/energy-data-services/how-to-set-up-private-links.md b/articles/energy-data-services/how-to-set-up-private-links.md
@@ -155,6 +155,30 @@ Use the following steps to create a private endpoint for an existing Azure Data
 >
 > [![Screenshot that shows options for rejecting or approving a request to create a private endpoint.](media/how-to-manage-private-links/private-links-10-awaiting-approval.png)](media/how-to-manage-private-links/private-links-10-awaiting-approval.png#lightbox)
 
+## Manage multiple endpoints in the same virtual network
+### Access via IP vs DNS
+In the same virtual network, you can create multiple endpoints. Each end point will have a different IP. It is not possible to resolve one host name with two difference IPs. 
+- If you access the resource via IP: 
+   - The resource will be accessible only via the latest private IP address. 
+   - All the previous private IPs in the same vnet will become dangling. 
+   - Even when you delete the latest IP, all the previous IPs still remain dangling. 
+- If you access via DNS name:  You won't see any difference.
+
+
+### Know which endpoint the resource is connected to
+1. Go to any of the private endpoints, to the DNS configuration, and to Private DNS Zone associated with ADME resource.
+
+[![Screenshot that shows DNS Config.](media/how-to-manage-private-links/private-links-17-dns-config.png)](media/how-to-manage-private-links/private-links-17-dns-config.png#lightbox)
+
+
+2. In the private DNS zone, check the IP associated with the entry for your Azure Data Manager for Energy instance.
+
+[![Screenshot that shows DNS Zone.](media/how-to-manage-private-links/private-links-18-dns-zone.png)](media/how-to-manage-private-links/private-links-18-dns-zone.png#lightbox)
+
+
+3. This is the IP to which your resource is connected.
+
+
 ## Next steps
 <!-- Add a context sentence for the following links -->
 To learn more about using Customer Lockbox as an interface to review and approve or reject access requests.
diff --git a/articles/energy-data-services/media/how-to-manage-private-links/private-links-17-dns-config.png b/articles/energy-data-services/media/how-to-manage-private-links/private-links-17-dns-config.png
diff --git a/articles/energy-data-services/media/how-to-manage-private-links/private-links-18-dns-zone.png b/articles/energy-data-services/media/how-to-manage-private-links/private-links-18-dns-zone.png
diff --git a/articles/energy-data-services/toc.yml b/articles/energy-data-services/toc.yml
@@ -68,6 +68,8 @@
           href: how-to-manage-legal-tags.md
         - name: Manage data partitions
           href: how-to-add-more-data-partitions.md
+        - name: Deploy Geospatial Consumption Zone (GCZ)
+          href: how-to-deploy-gcz.md
         - name: Deploy OSDU Admin UI
           href: how-to-deploy-osdu-admin-ui.md
         - name: How to enable External Data Sources (EDS)
diff --git a/articles/hdinsight/TOC.yml b/articles/hdinsight/TOC.yml
@@ -264,7 +264,9 @@ items:
         - name: New Azure Monitor experience Migration
           href: ./hdinsight-hadoop-oms-log-analytics-tutorial.md
         - name: Selective Logging
-          href: ./selective-logging-analysis-azure-logs.md    
+          href: ./selective-logging-analysis-azure-logs.md
+        - name: Enable new Azure Monitor integration
+          href: ./log-analytics-migration.md  
       - name: Use Azure Monitor Agent  
         items:    
         - name: Azure Monitor Agent Migration
@@ -279,8 +281,6 @@ items:
         href: ./hdinsight-cluster-availability.md
       - name: Cluster availability - Azure Monitor logs
         href: ./cluster-availability-monitor-logs.md
-      - name: Enable new Azure Monitor integration
-        href: ./log-analytics-migration.md
       - name: Monitoring data reference
         href: monitor-hdinsight-reference.md
     - name: Troubleshoot
diff --git a/articles/hdinsight/log-analytics-migration.md b/articles/hdinsight/log-analytics-migration.md
@@ -48,7 +48,7 @@ This document outlines the changes to the Azure Monitor integration and provides
 
 ## Customer scenarios
 
-The following sections describe how customers can use the new Azure Monitor integration in different scenarios. The [Activate a new Azure Monitor integration](#activate-a-new-azure-monitor-integration) section outlines how to activate and use the new Azure Monitor integration. The [Migrating from Azure Monitor Classic to the new Azure Monitor Integration](#migrate-to-the-new-azure-monitor-integration) section includes additional information for users that depend on the old Azure Monitor integration.
+The following sections describe how customers can use the new Azure Monitor integration in different scenarios. The [Activate a new Azure Monitor integration](./azure-monitor-agent.md#activate-a-new-azure-monitor-agent-integration) section outlines how to activate and use the new Azure Monitor integration. The [Migrating from Azure Monitor Classic to the new Azure Monitor Integration](#migrate-to-the-new-azure-monitor-integration) section includes additional information for users that depend on the old Azure Monitor integration.
 
 > [!NOTE]
 > Only clusters created in late-September 2020 and after are eligible for the new Azure Monitoring integration.
@@ -166,11 +166,12 @@ Creating new clusters with classic Azure Monitor integration is not available af
 
 ## Release and support timeline
 
-- Classic Azure Monitoring integration will be unavailable after October 15, 2021. You can't enable classic Azure Monitoring integration after that date.
-- Existing classic Azure monitoring integrations will continue to work. There will be limited support for the classic Azure Monitoring integration. 
-  - Issues will be investigated once customers submit the support ticket.
-  - If solution requires image change, customers should move to the new integration.
-  - We won't patch the classic Azure Monitoring integration clusters except for critical security issues.
+* Classic Azure Monitoring integration isn't unavailable after October 15, 2021. You can't enable classic Azure Monitoring integration after that date.
+* Classic Azure Monitoring integration ingestion will not be working after August 31, 2024.
+* HDInsight clusters with Azure Monitor integration (preview) will not be supported beyond February 1, 2025.
+* Existing Azure Monitor integration(preview) will continue to work, until January 31, 2025. There will be limited support for the Azure Monitor integration(preview).
+  * If solution requires image change, customers should move to the new integration.
+  * Microsoft will not patch the Azure Monitor integration (preview) clusters except for critical security issues.
 
 ## Appendix: Table mapping
 
diff --git a/articles/synapse-analytics/spark/synapse-file-mount-api.md b/articles/synapse-analytics/spark/synapse-file-mount-api.md
@@ -274,10 +274,6 @@ mssparkutils.fs.unmount("/test")
 
 + Mounting a Data Lake Storage Gen1 storage account is not supported for now. 
 
-## Known issues:
-
-+ In Spark 3.4, the mount points might be unavailable when there are multiple active sessions running in parallel in the same cluster. You can mount with `workspace` scope to avoid this issue.
-
 ## Next steps
 
 - [Get started with Azure Synapse Analytics](../get-started.md)
