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

Author: gitName

articles/azure-functions/durable/durable-functions-external-events.md

@@ -63,7 +63,7 @@ import azure.functions as func
 import azure.durable_functions as df
 
 def orchestrator_function(context: df.DurableOrchestrationContext):
-    approved = context.wait_for_external_event('Approval')
+    approved = yield context.wait_for_external_event('Approval')
     if approved:
         # approval granted - do the approved action
     else:
@@ -169,7 +169,7 @@ def orchestrator_function(context: df.DurableOrchestrationContext):
     event2 = context.wait_for_external_event('Event2')
     event3 = context.wait_for_external_event('Event3')
 
-    winner = context.task_any([event1, event2, event3])
+    winner = yield context.task_any([event1, event2, event3])
     if winner == event1:
         # ...
     elif winner == event2:
@@ -426,4 +426,4 @@ In this case, the instance ID is hardcoded as *MyInstanceId*.
 > [Learn how to implement error handling](durable-functions-error-handling.md)
 
 > [!div class="nextstepaction"]
-> [Run a sample that waits for human interaction](durable-functions-phone-verification.md)
+> [Run a sample that waits for human interaction](durable-functions-phone-verification.md)

articles/azure-maps/media/tutorial-ev-routing/create-project.png

@@ -5,7 +5,7 @@ ms.service: azure-netapp-files
 ms.topic: how-to
 author: b-ahibbard
 ms.author: anfdocs
-ms.date: 08/20/2024
+ms.date: 10/18/2024
 ---
 # Access SMB volumes from Microsoft Entra joined Windows virtual machines
 
@@ -91,7 +91,7 @@ The configuration process takes you through five process:
     * `$servicePrincipalName`: The SPN details from mounting the Azure NetApp Files volume. Use the CIFS/FQDN format. For example: `CIFS/NETBIOS-1234.CONTOSO.COM`
     * `$targetApplicationID`: Application (client) ID of the Microsoft Entra application.
     * `$domainCred`: use `Get-Credential` (should be an AD DS domain administrator)
-    * `$cloudCred`: use `Get-Credential` (should be a Microsoft Entra Global Administrator)
+    * `$cloudCred`: use `Get-Credential` (likely a [Hybrid Identity Administrator](/entra/identity/role-based-access-control/permissions-reference#hybrid-identity-administrator))
 
     ```powershell
     $servicePrincipalName = CIFS/NETBIOS-1234.CONTOSO.COM

articles/azure-maps/media/tutorial-ev-routing/install-packages.png

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 03/19/2024
+ms.date: 10/18/2024
 ms.author: anfdocs
 ---
 # Benefits of using Azure NetApp Files for Electronic Design Automation (EDA)
@@ -31,7 +31,7 @@ The Azure NetApp Files large volumes feature is ideal for the storage needs of t
 
 * **At 826,000 operations per second:** the performance edge of a single large volume - the application layer peaked at 7ms of latency in our tests, which shows that more operations are possible in a single large volume at a slight cost of latency. 
 
-Tests conducted internally using an EDA benchmark in 2020 found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge.   
+Tests conducted using an EDA benchmark found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge. See the table and chart below for regular and large volume side-by-side overview.
 
 
 | Scenario | I/O Rate at 2ms latency | I/O Rate at performance edge (~7 ms) | MiB/s at 2ms latency | MiB/s performance edge (~7 ms) | 
@@ -43,7 +43,7 @@ The following chart illustrates the test results.
 
 :::image type="content" source="./media/solutions-benefits-azure-netapp-files-electronic-design-automation/latency-throughput-graph.png" alt-text="Chart comparing latency and throughput between large and regular volumes." lightbox="./media/solutions-benefits-azure-netapp-files-electronic-design-automation/latency-throughput-graph.png":::
 
-The 2020 internal testing also explored single endpoint limits, the limits were reached with six volumes. Large Volume outperforms the scenario with six regular volumes by 260%.
+The regular volume testing also explored single endpoint limits, the limits were reached with six volumes. Large Volume outperforms the scenario with six regular volumes by 260%. The following table illustrates these results.
 
 | Scenario	| I/O Rate at 2ms latency | I/O Rate at performance edge (~7ms) | MiB/s at 2ms latency | MiB/s performance edge (~7ms) |
 | - | - | - | - | - |