Merge branch 'main' into main

articles/TOC.yml

@@ -802,8 +802,12 @@
       href: process-mining-copilot-in-process-analytics.md   
     - name: Connect to SAP ERP from process mining (preview)
       href: process-mining-sap-erp.md    
-    - name: Use your own Azure Data Lake Storage Gen2
-      href: process-mining-byo-azure-data-lake.md
+    - name: Storage Gen2
+      items:
+      - name: Bring your own Azure Data Lake Storage Gen2
+        href: process-mining-byo-azure-data-lake.md
+      - name: Use your own network isolated Azure Data Lake Storage Gen2
+        href: process-mining-byo-azure-data-lake-private.md
     - name: Transform and map data
       href: process-mining-transform.md
     - name: Visualize and gain insights from processes

articles/desktop-flows/hosted-machines.md

@@ -56,6 +56,8 @@ To evaluate hosted machines, you need one of the following trial licensing optio
 - Use the **90-days self-assisted premium trial.**
 
     Trial users are granted the capacity of one hosted machine per tenant. To start a trial, select **Try free** under **Power Automate Premium** in the [Power Automate pricing page](https://powerautomate.microsoft.com/pricing/) or the desktop flow page of the [Power Automate portal](https://make.powerautomate.com/).
+  > [!NOTE]
+  > Hosted machine capacity based on the 90-days self-assisted premium trial has been temporarily disabled until further notice.
 
 ## Prerequisites
 

articles/desktop-flows/schema.md

@@ -4,7 +4,7 @@ description: Learn about the Power Automate v2 schema.
 author: nvigne
 ms.subservice: desktop-flow
 ms.topic: conceptual
-ms.date: 04/09/2024
+ms.date: 04/15/2024
 ms.author: nvigne
 ms.reviewer: matp
 contributors:
@@ -37,7 +37,7 @@ Convert desktop flows stored in the v1 schema to the v2 schema by end of 2024, a
 
 ## Schema v2 enabled by default
 
-Starting January 2024, v2 schema is automatically enabled for all environments. Although not recommended, the option to opt-out of the autoenablement is available in the Power Platform admin center. By turning the opt-out on, we'll delay the enablement of v2 schema on this particular environment.
+Starting January 2024, v2 schema is automatically enabled for all environments. Although not recommended, the option to opt-out of the autoenablement is available in the Power Platform admin center. Turning on the opt-out delays the enablement of v2 schema on this particular environment.
 
 :::image type="content" source="media/schema/schema-v2-off.png" alt-text="The option in the Power Platform Admin Center to opt-out of schema v2 enabled by default.":::
 
@@ -69,10 +69,17 @@ If a desktop flow belongs to a solution in a v2-enabled environment, follow [the
 
 Power Automate for desktop version 2.29 or later allows organizations that moved ahead with the v2 schema to roll back until the v1 schema becomes deprecated.
 
-You can roll back a desktop flow converted to the v2 schema by resaving the desktop flow to an environment where the PPAC administrator has the feature disabled.
+You can roll back a desktop flow converted to the v2 schema by resaving the desktop flow to an environment where the Power Platform administrator has the feature disabled.
 
 For most scenarios, there's no need to downgrade your version of Power Automate for desktop. However, desktop flows that use v2-related features that aren't supported by the v1 schema can't roll back.
 
+A rollback from v2 to v1 can result in some screenshots associated with UI elements not being saved. Although those screenshots aren't necessary for the desktop flow to run, you can save them:
+
+1. Go to the **UI Elements** right panel in Power Automate desktop.
+1. Select each UI element in the list.
+
+This ensures that the screenshots are saved when you rollback to v1.
+
 ## Limitations of v2 schema desktop flows
 
 Desktop flows stored in the v2 schema only function in environments with the v2 schema feature enabled.