Merge remote-tracking branch 'origin/main' into pnghub-patch-1

Author: Mattp123

powerapps-docs/maker/canvas-apps/connections-list.md

@@ -166,7 +166,7 @@ When your app is republished and shared, then end-users won't have access to the
 3. For tabular connectors, we only limit CRUD actions such as Get, Post, Put, or Delete. If you have permissions to **Put** then you have access to **Post**.
 4. Action based connectors limit based on the specific API being used in the application. 
 5. Warnings are still enabled in sharing. The warning around implicitly shared connections still warns while in private preview. However, your connection with this feature is secure – despite the warning.
-
+6. Publishing to an entire tenant, as opposed to specific groups or individuals isn't supported.  
 
 ### Windows Authentication
 

powerapps-docs/maker/data-platform/azure-synapse-incremental-updates.md

@@ -51,10 +51,8 @@ Azure Synapse Link for Dataverse. This guide assumes that you have already met t
    :::image type="content" source="media/azure-synapse-add-tables-settings.png" alt-text="Add tables settings":::
 
 > [!NOTE]
-> Please be advised that **time interval configuration** is considered final once the setup process is completed and will be grayed out to indicate that it can't be changed. 
+> The minimum time interval is 15 minutes. That means the incremental update folder will be created every 15 minutes and contain the changes that occurred within the time interval. This setting is also configurable after the link creation via **Manage tables**
 >
-> The minimum time interval is 15 minutes. That means the incremental update folder will be created every 15 minutes and contain the changes that occurred within the time interval.
-> 
 > Ensure **Connect to your Azure Synapse workspace Azure Synapse workspace** is not checked in the first page of setup.
 
 ## View incremental folder at Microsoft Azure Storage

powerapps-docs/maker/data-platform/azure-synapse-link-advanced-configuration.md

@@ -46,7 +46,7 @@ The table below describes how rows are handled in the lake against CUD events fo
 |---------|---------|---------|
 |Create     |  The row is inserted in the partition file and is based on the `createdOn` value on the row.       | The row is added to the end of the partition file and is based on the `createdOn` value of the record.    |
 |Update     | If the row exists in the partition file, then it's replaced or updated with updated data. If it doesn't exist, it's inserted in the file.    |  The row, along with the updated version, is added to the end of the partition file.   |
-|Delete     |  If the row exists in the partition file, it's removed from the file.    | The row is added to the end of the partition file with `isDeleted column = True`.    |
+|Delete     |  If the row exists in the partition file, it's removed from the file.    | The row is added to the end of the partition file with `IsDelete column = True`.    |
 
 > [!NOTE]
 > For Dataverse tables where **Append only** is enabled, deleting a row in the source will not delete or remove the row in the lake. Instead, the deleted row is appended as a new row in the lake and the `isDeleted` column is set to **True**.