Merge pull request #8092 from MicrosoftDocs/main

Deland-Han · web-flow · commit f5cde3b20709 · 2025-01-23T18:00:12.000+08:00
Auto push to live 2025-01-23 02:00:02
diff --git a/support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md b/support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md
@@ -4,10 +4,10 @@ description: Troubleshoot common issues with monitoring sync health and resolvin
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 01/03/2025
+ms.date: 01/23/2025
 ms.author: kendownie
 ms.custom: sap:File Sync, devx-track-azurepowershell
-ms.reviewer: v-weizhu
+ms.reviewer: v-weizhu, vritikanaik
 ---
 # Troubleshoot Azure File Sync sync health and errors
 
@@ -210,7 +210,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0X80C80342 | -2134375614 | ECS_E_SYNC_CUSTOM_METADATA_VERSION_NOT_SUPPORTED | The sync database has custom metadata with a version higher than the supported version. | Please upgrade the File Sync agent to the latest version. If the error persists after upgrading the agent, create a support request. |
 | 0x80c8604b | -2134351797 | ECS_E_AZURE_FILE_SHARE_FILE_NOT_FOUND | The specified Azure file wasn't found in the file share. This issue might occur if the file has been deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
 | 0x80c80201 | -2134375935 | ECS_E_SYNC_UNPROCESSABLE_ITEM_REPARSEPOINT | The sync failed due to the presence of a reparse point. | Remove the reparse point or replace it with regular file content before attempting the sync again. |
-| 0x80c80362 | -2134375582 | ECS_E_ITEM_PATH_COMPONENT_HAS_TRAILING_DOT | The item failed to sync because one of its path component has trailing dot(s). | Rename the item removing any trailing dot(s) that exist in the path. |
+| 0x80c80362 | -2134375582 | ECS_E_ITEM_PATH_COMPONENT_HAS_TRAILING_DOT | The item failed to sync because one of its path components has trailing dots. | Rename the item by removing any trailing dots that appear in the path. |
 | 0x80c8024e | -2134375858 | ECS_E_SYNC_ITEM_SKIP_CONSTRAINT_CONFLICT_NOT_ALLOWED | This error indicates a constraint conflict that was detected but was unable to be reported. The item will be skipped. | If the error persists, create a support request. |
 
 ### Handling unsupported characters
diff --git a/support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-group-management.md b/support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-group-management.md
@@ -4,9 +4,9 @@ description: Troubleshoot common issues in managing Azure File Sync sync groups,
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 01/13/2025
+ms.date: 01/23/2025
 ms.author: kendownie
-ms.reviewer: v-weizhu
+ms.reviewer: v-weizhu, vritikanaik
 ms.custom: sap:File Sync
 ---
 # Troubleshoot Azure File Sync sync group management
@@ -83,7 +83,7 @@ This error occurs if the server endpoint path is on the system volume and cloud
 
 This error occurs if the server endpoint path specified isn't valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync doesn't support mapped drives as a server endpoint path.
 
-<a id="-2147024894"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024875 or 0x80070015)**
+<a id="-2147024875"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024875 or 0x80070015)**
 
 This error occurs if the server endpoint path specified isn't valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync doesn't support mapped drives as a server endpoint path.
 
@@ -123,7 +123,7 @@ This error occurs if the server is offline or doesn't have network connectivity.
 
 <a id="-2134347720"></a>**Server endpoint deletion fails, with this error: "MgmtFileShareSnapshotCountExceeded" (Error code: -2134347720 or 0x80c87038)**
 
-The error occurs when the ShareSnapshotCount exceeds the limit. Azure Files Sync takes a snapshot of the Azure file share as a backup before creating the server endpoint. This snapshot can be used to restore the share to the state before the server endpoint was created. The snapshot is not removed automatically after the server endpoint is created, so you can delete it manually if you don't need it. You can find the snapshots created by Azure File Sync by looking at the snapshots for the Azure file share and checking for AzureFileSync in the Initiator column.
+The error occurs when the File Share Snapshot Count exceeds the limit. Azure File Sync takes a snapshot of the Azure file share as a backup before creating the server endpoint. This snapshot can be used to restore the share to the state before the server endpoint is created. The snapshot isn't removed automatically after the server endpoint is created. You can delete it manually if it's no longer needed. To identify snapshots created by Azure File Sync, examine the snapshots of the Azure file share and look for "AzureFileSync" in the Initiator column.
 
 ## Server endpoint health
 
diff --git a/support/azure/synapse-analytics/workspace/synapse-studio/wrk-conn-synapse-studio.md b/support/azure/synapse-analytics/workspace/synapse-studio/wrk-conn-synapse-studio.md
@@ -1,7 +1,7 @@
 ---
 title: Resolve Azure Synapse Studio connectivity issues
 description: Provides solutions to common connectivity issues encountered in Azure Synapse Studio.
-ms.date: 02/21/2023
+ms.date: 01/23/2025
 ms.reviewer: scepperl, v-sidong, aminpashna
 ms.custom: sap:Synapse Studio
 ---
@@ -10,7 +10,7 @@ ms.custom: sap:Synapse Studio
 
 _Applies to:_ &nbsp; Azure Synapse Analytics
 
-Connectivity issues in Azure Synapse Studio are typically caused by configuration issues such as incorrect network settings or improper security role assignments.  Use the following guidance to troubleshoot connectivity issues with Synapse Studio.
+Connectivity issues in Azure Synapse Studio are typically caused by configuration issues such as incorrect network settings or improper security role assignments. Use the following guidance to troubleshoot connectivity issues with Synapse Studio.
 
 ## Common issues and solutions
 
@@ -22,8 +22,8 @@ Connectivity issues in Azure Synapse Studio are typically caused by configuratio
 |Error message: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied since Deny public network access is set to Yes.|Using a workspace with data exfiltration protection (DEP) enabled|- [Understanding Azure Synapse Private Endpoints](https://techcommunity.microsoft.com/t5/azure-architecture-blog/understanding-azure-synapse-private-endpoints/ba-p/2281463)<br> - [Connect to a Synapse workspace using private links](/azure/synapse-analytics/security/how-to-connect-to-workspace-with-private-links)<br> - [Data exfiltration protection for Azure Synapse Analytics workspaces](/azure/synapse-analytics/security/workspace-data-exfiltration-protection)<br>- [Managed private endpoints](/azure/synapse-analytics/security/synapse-workspace-managed-private-endpoints)|
 |Error message: COPY statement input file schema discovery failed Cannot bulk load.| Misconfiguration | [Use external tables with Synapse SQL](/azure/synapse-analytics/sql/develop-tables-external-tables?tabs=hadoop)|
 |Table Lock while pulling up the data from SAP ECC.|By design (This issue is due to transaction isolation that reduces inconsistency in the data.)|NA|
-|Error message: Per-machine installation is stopped because there is existing per-user gateway installation. | This error indicates that a Self-Hosted Integration Runtime has already been installed on the target Virtual Machine. Only one SHIR per VM is permitted. | To install another SHIR for Azure Synapse, you need to set up separate Virtual Machines to host each Integration Runtime instance.  At this time, only Azure Data Factory supports the Self-hosted IR sharing feature.  For more information, see [Create a self-hosted integration runtime.](/azure/data-factory/create-self-hosted-integration-runtime?tabs=synapse-analytics) |
-|Error message: Error code 2108, Error calling the endpoint ''. Response status code: ''. More details: Exception message: '' Request didn't reach the server from the client. | This issue could happen because of an underlying issue such as: <br> - Network connectivity<br> - DNS failure <br> - Server certificate validation <br> - Timeout misconfigured with a Managed Virtual Network and with Data Exfiltration Protection enabled | **Note**: The type of VNET (Shared VNET or Managed VNET) applied to the workspace can only be applied at creation time.<br><br> Take a look at the Private Endpoint Overview and related documentation:<br>- [What is a private endpoint?](/azure/private-link/private-endpoint-overview)<br>- [Understanding Azure Synapse Private Endpoints](https://techcommunity.microsoft.com/t5/azure-architecture-blog/understanding-azure-synapse-private-endpoints/ba-p/2281463)<br><br>A Private Link Service may also be a possible solution:<br> - [What is Azure Private Link?](/azure/private-link/private-link-overview)<br> - [What is Azure Private Link service?](/azure/private-link/private-link-service-overview)<br><br> Many configurations require DNS configuration within your network so that requests will be correctly routed to the Private Endpoints inside the VNET:<br>[Azure Private Endpoint DNS configuration](/azure/private-link/private-endpoint-dns)|
+|Error message: Per-machine installation is stopped because there is existing per-user gateway installation. | This error indicates that a Self-Hosted Integration Runtime has already been installed on the target Virtual Machine. Only one SHIR per VM is permitted. | To install another SHIR for Azure Synapse, you need to set up separate Virtual Machines to host each Integration Runtime instance. At this time, only Azure Data Factory supports the Self-hosted IR sharing feature. For more information, see [Create a self-hosted integration runtime.](/azure/data-factory/create-self-hosted-integration-runtime?tabs=synapse-analytics) |
+|Error message: Error code 2108, Error calling the endpoint ''. Response status code: ''. More details: Exception message: '' Request didn't reach the server from the client. | This issue could happen because of an underlying issue such as: <br> - Network connectivity<br> - DNS failure <br> - Server certificate validation <br> - Time-out misconfigured with a Managed Virtual Network and with Data Exfiltration Protection enabled | **Note**: The type of virtual network (Shared virtual network or Managed virtual network) applied to the workspace can only be applied at creation time.<br><br> Take a look at the Private Endpoint Overview and related documentation:<br>- [What is a private endpoint?](/azure/private-link/private-endpoint-overview)<br>- [Understanding Azure Synapse Private Endpoints](https://techcommunity.microsoft.com/t5/azure-architecture-blog/understanding-azure-synapse-private-endpoints/ba-p/2281463)<br><br>A Private Link Service might also be a possible solution:<br> - [What is Azure Private Link?](/azure/private-link/private-link-overview)<br> - [What is Azure Private Link service?](/azure/private-link/private-link-service-overview)<br><br> Many configurations require DNS configuration within your network so that requests will be correctly routed to the Private Endpoints inside the virtual network:<br>[Azure Private Endpoint DNS configuration](/azure/private-link/private-endpoint-dns)|
 |ADLS Gen1 data access via Service Principal isn't working.|The Linked Service in the GIT repo can't be published to Synapse live mode.|NA|
 
 ## Troubleshooting tips
@@ -37,19 +37,19 @@ Connectivity issues in Azure Synapse Studio are typically caused by configuratio
   - Ensure the firewall on your network and local computer allows outgoing communication on TCP ports 80, 443, and 1443 for Synapse Studio.
   - Allow outgoing communication on UDP port 53 for the DNS server for name resolution.
   - To connect using tools such as SSMS and Power BI, you must allow outgoing communication on TCP port 1433.
-  - If you're using the default Redirect connection policy setting, you may need to allow outgoing communication on more ports.
+  - If you're using the default Redirect connection policy setting, you might need to allow outgoing communication on more ports.
 
 - Test access with different browsers, and disable any pop-up blockers and plugins.
 
 - Investigate issues related to security and permissions:
 
   - [Workspaces, data, and pipelines](/azure/synapse-analytics/sql/access-control)
-  - [Managed identities](/azure/synapse-analytics/security/synapse-workspace-managed-identity)
+  - [Managed identities](/azure/synapse-analytics/synapse-service-identity)
   - [Database access](/azure/azure-sql/database/logins-create-manage?toc=%2Fazure%2Fsynapse-analytics%2Ftoc.json&bc=%2Fazure%2Fsynapse-analytics%2Fbreadcrumb%2Ftoc.json)
 
 ## Failed to load one or more resources due to a forbidden issue with error code 403
 
-Error code 403 may be an intermittent issue while opening your Synapse workspace in Synapse Studio.
+Error code 403 might be an intermittent issue while opening your Synapse workspace in Synapse Studio.
 
 Make sure you have the following required permissions to access your workspace:
 
@@ -68,7 +68,7 @@ To solve the issue, use one of the following options:
 
 ## Setting up Synapse on a private network
 
-You may not be able to connect to Azure Synapse if you disable the public network in the firewall.
+You might not be able to connect to Azure Synapse if you disable the public network in the firewall.
 
 Enable Public IP and add specific IPs that need to access Azure Synapse. Azure Firewall won't allow any other Public IP Address besides the one already added.
 
diff --git a/support/power-platform/power-automate/connections/troubleshoot-broken-connections.md b/support/power-platform/power-automate/connections/troubleshoot-broken-connections.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshoot broken connections
+title: Troubleshoot Broken Connections
 description: Learn how to troubleshoot and resolve connection problems and ensure a smoother experience with your applications and services in Microsoft Power Platform.
 ms.custom: sap:Connections
 ms.workload: connectors
diff --git a/support/power-platform/power-automate/desktop-flows/automation-browser-security-update.md b/support/power-platform/power-automate/desktop-flows/automation-browser-security-update.md
@@ -0,0 +1,52 @@
+---
+title: Browser Automation Security Update
+description: Provides security updates for the browser automation component in Microsoft Power Automate for desktop.
+ms.reviewer: nimoutzo, iopanag
+ms.date: 01/23/2025
+ms.custom: sap:Desktop flows\UI or browser automation
+---
+# Security update for the browser automation component in Microsoft Power Automate for desktop
+
+## Summary
+
+A potential security vulnerability is identified in the [browser automation](/power-automate/desktop-flows/actions-reference/webautomation) component in Power Automate for desktop versions 2.51 and earlier.
+
+The **Launch automation browser** option in the [Launch new Internet Explorer](/power-automate/desktop-flows/actions-reference/webautomation#launchinternetexplorerbase) action might navigate to a potentially malicious URL or compromised website, thus allowing an attacker to execute arbitrary code on the affected system. Microsoft has issued a [CVE for this issue](https://msrc.microsoft.com/update-guide/advisory/CVE-2025-21187).
+
+> [!IMPORTANT]
+> The issue affects only flows that use the **Launch automation browser** option in the **Launch new Internet Explorer** action.
+>
+> Flows that use the **Launch automation browser** option for public or untrusted websites are most vulnerable to this issue.
+
+## Mitigation
+
+To mitigate the issue, update your Power Automate for desktop to the following patched versions as soon as possible.
+
+- [2.46.184.25013](https://go.microsoft.com/fwlink/?linkid=2300767)
+- [2.47.126.25010](https://go.microsoft.com/fwlink/?linkid=2300573)
+- [2.48.164.25010](https://go.microsoft.com/fwlink/?linkid=2300574)
+- [2.49.182.25010](https://go.microsoft.com/fwlink/?linkid=2300662)
+- [2.50.139.25010](https://go.microsoft.com/fwlink/?linkid=2300768)
+- [2.51.349.24355](https://go.microsoft.com/fwlink/?linkid=2300789)
+
+> [!NOTE]
+> Starting with release 2.52, all future versions will include the security fix.
+
+## Impact of the patch
+
+In the updated versions, when browser automation attempts to navigate to a potentially malicious URL, it will display a warning dialog with relevant details. The user can choose to continue or stop the navigation.
+
+If this dialog disrupts a flow and the navigation is considered legitimate, you can mitigate the issue by disabling the warning dialog for specific categories of URLs by adding their protocols to the allowlist in the [UI Automation configuration file](desktop-application-crashes-ui-automation.md#how-to-create-the-configuration-file). The key to add in this case is `AutomationBrowser.ProtocolAllowList`, and the value is the protocols that you want to allow, separated by commas. For example:
+
+```xml
+<?xml version="1.0" encoding="utf-8" ?>
+<configuration>
+    <appSettings>
+        <!-- Other configurations -->
+
+        <add key="AutomationBrowser.ProtocolAllowList" value="http,https" />
+    </appSettings>
+</configuration>
+```
+
+With this configuration, if navigating to a URL causes the dialog to appear and the URL uses the `http` or `https` protocol, the dialog will be suppressed.
diff --git a/support/power-platform/power-automate/toc.yml b/support/power-platform/power-automate/toc.yml
@@ -152,6 +152,8 @@
       href: desktop-flows/session-has-logged-off-troubleshooting.md
     - name: 'Security update for "connect with sign-in" connections on AD domain-joined machines'
       href: desktop-flows/connect-with-sign-in-security-update.md
+    - name: Security update for the browser automation component
+      href: desktop-flows/automation-browser-security-update.md  
     - name: Some actions appear to be missing or aren't visible
       href: desktop-flows/actions-not-available.md
     - name: Set drop-down list value in window/on web page action fails
