Merge pull request MicrosoftDocs#4766 from MicrosoftDocs/main638313697986757268sync_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/developer/component-framework/reference/resources/getstring.md

@@ -27,7 +27,7 @@ Model-driven apps, canvas apps, & portals.
 
 | Parameter Name|Type|Required|Description|
 | ------------- |----|--------|-----------|
-|id|`String`|Yes|Name of the resource in the component manifest.|
+|`id`|String|Yes|Name of the resource in the component manifest.|
 
 ## Return Value
 

powerapps-docs/maker/canvas-apps/ai-overview.md

@@ -58,21 +58,25 @@ The following are requirements to access the waitlist for this preview:
 
 ## Disable Copilot in Power Apps
 
-For this preview, Copilot in Power Apps will be turn on by default. To disable it, you need to have administrator access.
+For this preview, Copilot in Power Apps is enabled by default. To disable it, you need to have administrator access.
 
 Follow these steps to disable **Copilot** in Power Apps for your tenant.
 
 1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
 2. Select **Settings** > **Tenant settings** in the left-side navigation pane.
 3. Select **Copilot (preview)** > set the toggle to **Off** > **Save**.
 
+> [!NOTE]
+> Turning off Copilot for your tenant will only disable Copilot for makers. It won't disable [Copilot control for canvas apps](add-ai-copilot.md) or [Copilot for model-driven apps](../model-driven-apps/add-ai-copilot.md).
+
 Follow these steps to disable **Copilot** for your environment.
 
 1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
 2. In the left-side navigation pane **Environment**.
 3. Select the environment and on the command bar, select **Settings**.
 4. Set the toggle to **Off** for **Copilot**.
 
+
 ## See also
 
 [Transparency notes for Power Apps](../common/transparency-note.md)

powerapps-docs/maker/canvas-apps/connections/azure-devops.md

@@ -22,15 +22,17 @@ Power Apps connector for [Azure DevOps](/connectors/visualstudioteamservices/) a
 > [!TIP]
 > For a complete list of all actions, see [Azure DevOps connector actions](/connectors/visualstudioteamservices/#actions).
 
-In this article, you'll create a canvas app that connects to Azure DevOps to retrieve the list of queries, and work with work items within the project.
+The objective of this article is to guide you in building a canvas app that can connect with Azure DevOps to gather a list of queries and interact with the work items in the project.
 
 ## Prerequisites
 
-- You need a Power Apps license. If you don't have a license, use a [30-day trial](../../signup-for-powerapps.md), or sign up for a [developer plan](../../developer-plan.md) for non-production use.
+The following requirements are necessary:
+
+- A Power Apps license. If you don't have a license, use a [30-day trial](../../signup-for-powerapps.md), or sign up for a [developer plan](../../developer-plan.md) for non-production use.
 - If you're new to Power Apps, familiarize yourself with Power Apps basics by [generating an app](../get-started-test-drive.md) and then customizing that app's [controls](../add-configure-controls.md), [gallery](../add-gallery.md), [forms](../working-with-forms.md), and [cards](../working-with-cards.md).
-- You need a [blank canvas app](../create-blank-app.md) to use to connect to Azure DevOps.
-- You need an [Azure DevOps](/azure/devops/user-guide/what-is-azure-devops) instance that has an organization, a project, and a shared query that has few sample work items to edit using the app that you'll create in this article.
-- The Azure DevOps instance that must be enabled for **Third-party application access via OAuth**. To configure this setting, see [Manage access policies for Azure DevOps](/azure/devops/organizations/accounts/change-application-access-policies#manage-a-policy).
+- A [blank canvas app](../create-blank-app.md) to use to connect to Azure DevOps.
+- To create the app featured in this article, you'll require an  [Azure DevOps](/azure/devops/user-guide/what-is-azure-devops) instance that includes an organization, a project, and a shared query with a few sample work items available for editing.
+- The Azure DevOps instance must be enabled for **Third-party application access via OAuth**. For more information, see [Manage access policies for Azure DevOps](/azure/devops/organizations/accounts/change-application-access-policies#manage-a-policy).
 
 ## Step 1 - Add Azure DevOps data source
 
@@ -163,18 +165,37 @@ So far we have been using the Edit form which simplifies the data access story b
  ```powerapps-dot
     AzureDevOps.GetWorkItemDetails(Gallery2.Selected.Value.'System.Id',Organization, Project, Gallery2.Selected.Value.'System.WorkItemType')
   ```
-Note that "WorkItemType" is a text property passed in (e.g., "Feature") that allows you to pivot from items like Features and Work Items. The set of fields for these items vary from each other - which is why the return type from this call is dynamic. 
+When you pass the text property "WorkItemType", for instance, "Feature", it allows you to switch from items such as Features and Work Items. Since the set of fields for these items differ from one another, the return type from this call is dynamic.
+
+You can access specific values using the common method Text(ThisItem.Value.'System.Id'). Alternatively, you may access them through the more general dynamic response using Text(ThisItem.fields.System_Id). These dynamic value names are not typically documented. To find the correct names for these fields, including non-standard fields, open the monitor tool and examine the data response for the GetWorkItemDetails call. Refer to the image below for further guidance.
 
-To access specific values you can still access the common values the same way (e.g.,`Text(ThisItem.Value.'System.Id')` ). However, you may also access them in the more general dynamic response this way: `Text(ThisItem.fields.System_Id)`. These dynamic values names aren't generally documented.  The easiest way to see the correct names for these fields - including the non-standard fields is to open the monitor tool and look at the data response. In this case, to the `GetWorkItemDetails` call.  (See image below.)
+If you're not utilizing an Edit form, but instead using a container, then you can retrieve these values by using a formula such as the one below, which retrieves information from a custom team field.
 
-If you aren't using an Edit form, but rather simply a container, then you can access these values with a formula like the following: (Which accesses a custom team field.)
 
 ```powerapps-dot
 Text(AzureDevOps.GetWorkItemDetails(Gallery2.Selected.Value.'System.Id',Organization, Project, Gallery2.Selected.Value.'System.WorkItemType').fields.One_custom_CustomField1)
 ```
 
 > [!div class="mx-imgBorder"]
 > ![Text input control that refers to title of the work item.](./media/azure-devops/monitor-workitem-details.png "Text input control referring to title of the work item.")
+>
+> 
+## Updating values in Azure DevOps
+
+To update a value in Azure Dev ops use the UpdateWorkItem in the OnSelect of a button. 
+
+```powerapps-dot
+AzureDevOps.UpdateWorkItem(
+    Gallery2.Selected.Value.'System.Id', 
+    Organization, 
+    {   description: "This is a new description", 
+        dynamicFields: ParseJSON(JSON({'Custom Field 1': "This is new custom text" })) 
+    }
+);
+```
+The formula adds new sample text but you can also use a PowerFx expression. 
+
+Ensure that the formula uses lower case for the *non-custom* or built-in field names. For example, when referring to "Description" field, use `description: "This is a new description"` instead of `Description:"This is a new description"`. Incorrect casing might result in the error "400 Required parameter missing for requested operation: 'UpdateWorkItem'".  For custom / dynamic values, you can use the normal casing of display field. For instance the field name for the custom field is just the display name 'Custom Field 1'. This naming convention of the return values is specific to Azure DevOps and may differ from other services.
 
 
 ## Next steps

powerapps-docs/maker/data-platform/azure-synapse-link-select-FnO-data.md

@@ -1,7 +1,7 @@
 ---
 title: Choose finance and operations data in Azure Synapse Link for Dataverse
 description: Learn how to choose finance and operations data in Microsoft Azure Synapse Link for Dataverse and work with Azure Synapse Link and Power BI.
-ms.date: 07/18/2023
+ms.date: 09/26/2023
 ms.reviewer: johnmichalak
 ms.topic: "how-to"
 applies_to: 
@@ -30,11 +30,18 @@ Azure Synapse Link for Dataverse offers the following features that you can use
 - By default, saving in Parquet Delta Lake format is enabled for finance and operations data, so that query response times are faster.
 
 > [!NOTE]
-> This is a preview feature.
+> 
+> This feature is generally available with finance and operations application versions shown in the following list. If you have not yet applied these application versions, install the latest cumulative update to use this feature.
+> 
+> - 10.0.34 (PU58) cumulative update 7.0.6931.171 or later.
+> - 10.0.35 (PU59) cumulative update 7.0.6972.149 or later.
+> - 10.0.36 (PU60) cumulative update 7.0.7036.78 or later.
+> - 10.0.37 (PU61) cumulative update 7.0.7068.39 or later. 
 >
-> The Export to Data Lake feature in finance and operations apps will eventually be combined with Azure Synapse Link for Dataverse. We also plan to retire the Export to Data Lake service and transition existing customers to Azure Synapse Link for Dataverse.
+> The [Export to Data Lake feature](/dynamics365/fin-ops-core/dev-itpro/data-entities/azure-data-lake-ga-version-overview) in finance and operations apps is being combined with Azure Synapse Link for Dataverse. We will announce deprecation of Export to Data Lake service and transition existing customers to Azure Synapse Link for Dataverse. 
 >
-> If you're planning to adopt the Export to Data Lake feature in finance and operations apps, you should consider adopting Azure Synapse Link with finance and operations data support instead. We will provide a path for existing customers to transition to Azure Synapse Link for Dataverse. If you're currently using the Export to Data Lake feature in finance and operations apps, you can continue to use both services in parallel until the transition.
+> If you're planning to adopt the Export to Data Lake feature in finance and operations apps, you should consider adopting Azure Synapse Link with finance and operations data support instead.
+> We will provide guidance and tools for existing customers to transition to Azure Synapse Link for Dataverse. If you're currently using the Export to Data Lake feature in finance and operations apps, you can continue to use both services in parallel until the transition. To stay in touch with the product team and community, you can join the [Preview Viva engage group](https://www.yammer.com/dynamicsaxfeedbackprograms/). 
 
 ## Prerequisites
 
@@ -83,17 +90,14 @@ To enable this feature during the preview, you must use the following URL to ope
 
 ### Known limitations
 
-The preview has several limitations that will be addressed in future releases. To learn more about the upcoming roadmap and stay in touch with product team, join the [preview Yammer group](https://aka.ms/SynapseLinkforDynamics).
+The preview has several limitations that will be addressed in future releases. To learn more about the upcoming roadmap and stay in touch with product team, join the [preview Viva Engage group](https://www.yammer.com/dynamicsaxfeedbackprograms/).
 
 - You must create a new Azure Synapse Link profile. You can't add finance and operations apps tables to existing Azure Synapse Link profiles.
-- The following Microsoft-provided finance and operations apps tables aren't currently enabled in Azure Synapse Link. However, they will be enabled in a future release.
-    - Tables that don't have a unique index on the `Rec ID` column. An example is the `REQPLAN` table.
-    All other finance and operations apps tables that Microsoft provides are already enabled in Azure Synapse Link.
-
+- Up to 4,250 Microsoft provided finance and operations apps tables are already enabled in Azure Synapse Link with application version 10.0.38. If you have a previous version of finance and operations apps, not all required tables may be enabled by default. You can enable more tables yourself by extending table properties and enabling the change tracking feature. For more information about how to enable change tracking, see [Enable row version change tracking for tables](/dynamics365/fin-ops-core/dev-itpro/data-entities/rowversion-change-track#enable-row-version-change-tracking-for-tables).  
 - To enable custom tables, you must enable change tracking in them. For more information about how to enable change tracking, see [Enable row version change tracking for tables](/dynamics365/fin-ops-core/dev-itpro/data-entities/rowversion-change-track#enable-row-version-change-tracking-for-tables).
 - When you work with finance and operations data, you must select Delta Lake format as the default format. To enable Delta Lake format, follow the steps in [Export Microsoft Dataverse data in Delta Lake format](azure-synapse-link-delta-lake.md).
 - The initial data export of finance and operations apps tables in Delta Lake format might take up to an hour. However, performance of the initial export will be improved in future updates.
-- You can choose a maximum of 1,000 tables in a single Azure Synapse Link profile.
+- You can choose a maximum of 1,000 tables in an Azure Synapse Link profile. To enable more tables, create another Synapse Link profile.
 
 ## Enable finance and operations data entities in Azure Synapse Link