Merge pull request MicrosoftDocs#4946 from MicrosoftDocs/main638356897848624731sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

powerapps-docs/maker/TOC.yml

@@ -2297,7 +2297,7 @@
         href: ./data-platform/azure-synapse-link-choices-serverless.md
       - name: Export data in Delta Lake format
         href: ./data-platform/azure-synapse-link-delta-lake.md
-      - name: View Dataverse data in Microsoft Fabric (preview)
+      - name: View Dataverse data in Microsoft Fabric
         href: ./data-platform/azure-synapse-link-view-in-fabric.md
     - name: Analyze in Azure Data Lake Storage Gen2
       items:

powerapps-docs/maker/common/faqs-excel-to-table-app.md

@@ -47,6 +47,10 @@ We have set up reports and dashboards to track the usage, net promoter score (NP
 
 - Users can configure the ownership of the table. Ownership depends on whether the data of the table is owned by specific users, teams, or the entire organization.
 
+## How can I use this feature in a Power Platform environment that is created outside of the United States or Switzerland?
+
+To do this, turn on data movement across regions. More information: [Enable copilots and generative AI features outside United States and Switzerland](https://go.microsoft.com/fwlink/?linkid=2244595)
+
 ## See also
 
 [Upload an Excel file](../data-platform/create-edit-entities-portal.md#upload-an-excel-file-preview)

powerapps-docs/maker/data-platform/Azure-Synapse-Link-view-in-Fabric.md

@@ -9,9 +9,7 @@ ms.topic: how-to
 ms.date: 11/14/2023
 ms.custom: template-how-to
 ---
-# Link your Dataverse environment to Microsoft Fabric and unlock deep insights 
-
-[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
+# Link your Dataverse environment to Microsoft Fabric and unlock deep insights
 
 Microsoft Dataverse direct link with Microsoft Fabric enables organizations to extend their Power Apps, Dynamics 365 enterprise applications, and business processes into Fabric. The **Link to Microsoft Fabric** feature built into Power Apps makes all your Dynamics 365 and Power Apps data available in Microsoft OneLake, the built-in data lake for Microsoft Fabric.
 

powerapps-docs/maker/model-driven-apps/commanding-use-powerfx.md

@@ -205,6 +205,7 @@ The following Power Fx functions are currently not supported with commanding in
 - Back()
 - Clear()
 - Collect()
+- Copy()
 - Disable()
 - Enable()
 - Exit()

powerapps-docs/maker/model-driven-apps/form-component-control.md

@@ -2,7 +2,7 @@
 title: "Edit table records directly from another table’s main form | MicrosoftDocs"
 description: Learn how to design a main form that can be used to edit a related table record.
 ms.custom: ""
-ms.date: 02/28/2023
+ms.date: 11/14/2023
 ms.reviewer: ""
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -31,7 +31,7 @@ For example, here's the form component on an **existing tab** on the main accoun
 
 ## Add the form component to a table main form
 
-1. On the left navigation pane select **Components**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
+1. On the left navigation pane, select **Components**. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
 1. Expand either **Input** or **Display**, and then select **Form**.
 On the form component control configuration page, select the properties for the control:  
    - Select the **Lookup column** for the form.
@@ -119,7 +119,9 @@ Note the following limitations when you add the form component control to a tabl
 
 - Forms with a business process flow aren’t currently supported in either the main table form or the related table form. If you have a form with a business process flow, you may encounter unexpected behavior.  We recommend that you don't use a form component with a form that uses a business process flow.
 
-- The form component control doesn't support embedded form component controls, such as adding a form component control to a form that is used by a form component control. 
+- The form component control doesn't support embedded form component controls, such as adding a form component control to a form that is used by a form component control.
+
+- The form component control doesn't support [embedded canvas apps](embed-canvas-app-in-form.md). You might encounter unexpected behavior with these canvas apps.
 
 - The form component control will only display the first tab of the form it uses if multiple tabs are included in that form.  
 
@@ -129,7 +131,7 @@ Note the following limitations when you add the form component control to a tabl
 
 - Form component controls have certain limitations when rendered in multi-session apps. If the client API is used to modify the form component control, or if data is entered on the form, the changes might not be persisted when switching multi-session tabs.
 
-- You may notice that the timeline wall may not update when a column that is used to set the timeline wall has changed in the form component. When the page is refreshed the timeline wall will update as expected.
+- You might notice that the timeline wall might not update when a column that is used to set the timeline wall has changed in the form component. When the page is refreshed the timeline wall will update as expected.
 
 - On mobile, the timeline control doesn't currently appear in the form component control.