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

Author: dlepow

articles/communication-services/quickstarts/network-security-perimeter.md

@@ -65,7 +65,7 @@ Provide the same network security perimeter name used in **Step 3**.
 
 `az network perimeter profile create --name <network-perimeter-profile-name> --resource-group <resource-group-name> --perimeter-name <network-security-perimeter-name>`
 
-### Step 5: Create an inbound access rule with a public IP address [YC2.1] [YC2.2] prefix for the profile created with the following command
+### Step 5: Create an inbound access rule with a public IP address prefix for the profile created with the following command
 
 `az network perimeter profile access-rule create --name <access-rule-name> --profile-name <network-perimeter-profile-name> --perimeter-name <network-security-perimeter-name> --resource-group <resource-group-name> --address-prefixes "[192.0.2.0/24]"`
 
@@ -90,7 +90,7 @@ Provide the same network security perimeter name used in **Step 3**.
    `az network perimeter association create --name <network-perimeter-association-name>  --perimeter-name <network-security-perimeter-name> --resource-group <network-perimeter-resource-group>  --access-mode Enforced --private-link-resource "{id:<ACSArmId>}" --profile "{id:<networkSecurityPerimeterProfileId>}"`
 
 
-### Step 7: Verify the allowlisted IP addresses can send email with NSP enabled [YC3.1] [YC3.2] [NM3.3]
+### Step 7: Verify the allowlisted IP addresses can send email with NSP enabled 
 
 Make sure that the Azure Communication Services resource is connected to a verified email domain. For more information, see [Connect a verified email domain](./email/connect-email-communication-resource.md).
 

articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md

@@ -495,6 +495,9 @@ StartRecordingOptions recordingOptions = new StartRecordingOptions("<callConnect
 Response<RecordingStateResult> response = await callAutomationClient.GetCallRecording()
 .StartAsync(recordingOptions);
 ```
+> [!NOTE]
+> Recording started with connection Id is started async (204 response code) and recording state change is updated via call back event (Microsoft.Communication.RecordingStateChanged) received on RecordingStateCallbackUri.
+Additionally any failures to start recording is reported via a new callback event (Microsoft.Communication.StartRecordingFailed) received on RecordingStateCallbackUri.
 
 
 ## Alpha SDKs

articles/defender-for-iot/organizations/release-notes.md

@@ -38,6 +38,7 @@ Cloud features may be dependent on a specific sensor version. Such features are
 | Version / Patch |  Release date | Scope     | Supported until |
 | ------- |  ------------ | ----------- | ------------------- |
 | **25.1** | | | |
+| 25.1.2 | 05/2025 | Minor |04/2026 |
 | 25.1.1  |03/2025 | Minor |02/2026 |
 | 25.1.0  |03/2025 | Major |02/2026 |
 | **24.1** | | | |
@@ -82,6 +83,14 @@ To understand whether a feature is supported in your sensor version, check the r
 
 ## Versions 25.1.x
 
+### Version 25.1.2
+
+**Release date**: 05/2025
+
+**Supported until**: 04/2026
+
+This version includes bug fixes for stability improvements.
+
 ### Version 25.1.1
 
 **Release date**: 04/2025

articles/digital-twins/how-to-use-azure-digital-twins-explorer.md

@@ -211,9 +211,9 @@ If you choose a property that isn't present on every twin, any twins in the grap
 
 You can rearrange the twins into different configurations by clicking and dragging them around the Twin Graph screen.
 
-You can also apply one of several layout algorithms to the graph from the options in the **Choose Layout** menu. 
+You can also apply one of several layout algorithms to the graph from the options in the **Choose layout** menu. 
 
-:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/twin-graph-panel-layout.png" alt-text="Screenshot of Azure Digital Twins Explorer Twin Graph panel. The Choose Layout button is highlighted, showing a menu with the layout options Cola, Dagre, fCoSE, and Klay." lightbox="media/how-to-use-azure-digital-twins-explorer/twin-graph-panel-layout.png":::
+:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/twin-graph-panel-layout.png" alt-text="Screenshot of Azure Digital Twins Explorer Twin Graph panel. The Choose Layout button is highlighted, showing a menu with layout options." lightbox="media/how-to-use-azure-digital-twins-explorer/twin-graph-panel-layout.png":::
 
 ### Control twin graph expansion
 
@@ -356,9 +356,9 @@ You can also view a model's full definition by selecting it in the **Model Graph
 
 You can rearrange the models into different configurations by clicking and dragging them around the Model Graph screen.
 
-You can also apply one of several layout algorithms to the model graph from the options in the **Choose Layout** menu. 
+You can also apply one of several layout algorithms to the model graph from the options in the **Choose layout** menu. 
 
-:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/model-graph-panel-layout.png" alt-text="Screenshot of Azure Digital Twins Explorer Model Graph panel. The Choose Layout button is highlighted, showing a menu with the layout options Cola, Dagre, fCoSE, Klay, and d3Force." lightbox="media/how-to-use-azure-digital-twins-explorer/model-graph-panel-layout.png":::
+:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/model-graph-panel-layout.png" alt-text="Screenshot of Azure Digital Twins Explorer Model Graph panel. The Choose Layout button is highlighted, showing a menu with layout options." lightbox="media/how-to-use-azure-digital-twins-explorer/model-graph-panel-layout.png":::
 
 ### Filter and highlight model graph elements
 

articles/digital-twins/media/how-to-use-azure-digital-twins-explorer/model-graph-panel-layout.png

@@ -21,7 +21,7 @@ When creating an ExpressRoute virtual network gateway, you must select a [gatewa
 - Ensure you have an existing [ExpressRoute virtual network gateway](expressroute-howto-add-gateway-portal-resource-manager.md) in your Azure subscription.
 
 > [!TIP]
-> You can now deploy two ExpressRoute gateways within the same virtual network. To do this, create a second ExpressRoute gateway with its admin state set to **disabled**. Once the second gateway is deployed, initiate the *Prepare* step in the migration tool. This step will establish the connection without redeploying the gateway, as it is already in place. Finally, run the *Migrate* step, which will change the new gateway's admin state to **_enabled_**, completing the migration process. This method minimizes the migration or maintenance window, significantly reducing downtime when transitioning from a non-zonal to a zone-redundant gateway.
+> You can now deploy two ExpressRoute gateways within the same virtual network. To do this, create a second ExpressRoute gateway with its admin state set to **disabled**. Once the second gateway is deployed, initiate the *Prepare* step in the migration tool. This step establishes the connection without redeploying the gateway, as it's already in place. Finally, run the *Migrate* step, which will change the new gateway's admin state to **_enabled_**, completing the migration process. This method minimizes the migration or maintenance window, significantly reducing downtime when transitioning from a non-zonal to a zone-redundant gateway.
 
 ## Steps to migrate to a new gateway in Azure portal
 
@@ -50,11 +50,11 @@ Follow these steps to migrate to a new gateway using the Azure portal:
 
 1. Select **Prepare** to create the new gateway. This operation can take up to 45 minutes.
 
-1. After the new gateway is created, proceed to the **Migrate** stage. Select the new gateway (for example, **myERGateway_migrated**) to transfer settings from the old gateway to the new one. All network traffic and data path connections transfer without interruptions. Select **Migrate Traffic** to start the process. This step can take up to 5 minutes.
+1. After the new gateway is created, proceed to the **Migrate** stage. Select the new gateway (for example, **myERGateway_migrated**) to transfer settings from the old gateway to the new one. All network traffic and data path connections transfer. Select **Migrate Traffic** to start the process. This step can take up to 5 minutes.
 
     :::image type="content" source="media/gateway-migration/migrate-traffic-step.png" alt-text="Screenshot of migrating traffic for migrating a virtual network gateway." lightbox="media/gateway-migration/migrate-traffic-step.png":::
 
-1. Once traffic migration is complete, proceed to the **Commit** stage. Finalize the migration by deleting the old gateway. Select **Commit Migration** to complete this step without downtime.
+1. Once traffic migration is complete, proceed to the **Commit** stage. Finalize the migration by deleting the old gateway. Select **Commit Migration** to complete this step.
 
     :::image type="content" source="media/gateway-migration/commit-step.png" alt-text="Screenshot of the commit step for migrating a virtual network gateway." lightbox="media/gateway-migration/commit-step.png":::
 

articles/digital-twins/media/how-to-use-azure-digital-twins-explorer/twin-graph-panel-layout.png

@@ -161,8 +161,10 @@
       href: tier-migration.md
     - name: Classic to Standard/Premium mapping
       href: tier-mapping.md
-    - name: Migrate from Front Door (classic)
+    - name: Migrate from Front Door (classic) - Portal
       href: migrate-tier.md
+    - name: Migrate from Front Door (classic) - PowerShell
+      href: migrate-tier-powershell.md
   - name: Microsoft CDN (classic) retirement FAQ
     href: ../cdn/classic-cdn-retirement-faq.md
   - name: Edgio retirement FAQ