Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into dns-new

Author: greg-lindsay

articles/azure-maps/map-show-traffic.md

@@ -59,7 +59,7 @@ There are two different traffic controls that can be added to the map. The first
 The following code shows how to add the traffic controls to the map.
 
 ```JavaScript
-//Att the traffic control toogle button to the top right corner of the map.
+//Att the traffic control toggle button to the top right corner of the map.
 map.controls.add(new atlas.control.TrafficControl(), { position: 'top-right' });
 
 //Att the traffic legend control to the bottom left corner of the map.

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

@@ -3,7 +3,7 @@ title: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
 description: Learn how to create Azure NetApp Files-based NFS datastores for Azure VMware Solution hosts.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/13/2024
+ms.date: 01/29/2025
 ms.custom: "references_regions, engagement-fy23"
 ---
 
@@ -98,6 +98,26 @@ There are some important best practices to follow for optimal performance of NFS
 
 For performance benchmarks that Azure NetApp Files datastores deliver for VMs on Azure VMware Solution, see [Azure NetApp Files datastore performance benchmarks for Azure VMware Solution](../azure-netapp-files/performance-benchmarks-azure-vmware-solution.md).  
 
+
+### Considerations for Azure NetApp Files storage with cool access
+
+When choosing to use [Azure NetApp Files storage with cool access](../azure-netapp-files/cool-access-introduction.md) on datastores for AVS, consider the performance characteristics of your workloads. Cool access is best suited for applications and workloads that primarily involve sequential I/O operations or tolerate varying read latency. Workloads with high random I/O and latency sensitivity should avoid using cool access due to an increase in latency when reading data from the cool tier.
+
+Also consider adjusting cool access settings for the workload to fit the expected access patterns. For more information, see [Performance considerations for Azure NetApp Files storage with cool access](../azure-netapp-files/performance-considerations-cool-access.md).
+
+**Use cases where cool access is a good fit:**
+
+- Virtual machine templates and ISO files
+- VMDKs with home directories (if not using Azure NetApp Files directly for this purpose)
+- VMDKs with content repositories
+- VMDKs with application data
+- VMDKs with archive and application-level backup data
+ 
+**Use cases to not use cool access:**
+
+- VMDKs containing production database files with high random I/O and latency sensitivity
+- VMDKs with operating system boot disks
+
 ## Attach an Azure NetApp Files volume to your private cloud
 
 ### [Portal](#tab/azure-portal)

articles/iot-operations/troubleshoot/known-issues.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.topic: troubleshooting-known-issue
 ms.custom:
   - ignite-2023
-ms.date: 01/07/2025
+ms.date: 01/28/2025
 ---
 
 # Known issues: Azure IoT Operations
@@ -112,3 +112,5 @@ kubectl delete pod aio-opc-opc.tcp-1-f95d76c54-w9v9c -n azure-iot-operations
 - When connecting multiple IoT Operations instances to the same Event Grid MQTT namespace, connection failures may occur due to client ID conflicts. Client IDs are currently derived from dataflow resource names, and when using Infrastructure as Code (IaC) patterns for deployment, the generated client IDs may be identical. As a temporary workaround, add randomness to the dataflow names in your deployment templates.
 
 - When network connection is disrupted, Dataflows may encounter errors sending messages due to a mismatched producer ID. If you experience this issue, restart your Dataflows pods.
+
+- When using control characters in Kafka headers, you might encounter disconnections. Control characters in Kafka headers such as `0x01`, `0x02`, `0x03`, `0x04` are UTF-8 compliant but the IoT Operations MQTT broker rejects them. This issue happens during the data flow process when Kafka headers are converted to MQTT properties using a UTF-8 parser. Packets with control characters might be treated as invalid and rejected by the broker and lead to data flow failures.