Merge remote-tracking branch 'upstream/main' into learn-build-service-prodbot/docutune-autopr-20260108-225327-7524624-ignore-build

Author: v-tappelgate

support/azure/virtual-machines/linux/removing-extensions-netapp-cvo.md

@@ -43,19 +43,34 @@ Cloud Volumes ONTAP doesn't support Azure VM extensions because extensions affec
 > Starting in BlueXP 3.9.54, NetApp enforces this pre-existing limitation as a notification in BlueXP. 
 
 ## Resolution
-To resolve this issue, run the following script against any affected NetApp CVO VMs in PowerShell:
+To resolve this issue, run the following script against any affected NetApp CVO VMs.
+
+### [PowerShell](#tab/powershell)
 
 ```powershell
-    $subscriptionId = (Get-AzContext).Subscription.Id 
-    $resourceGroup = "RGname" 
-    $vmName = "VMName" 
-    $apiVersion = "2025-04-01" 
-    $uri = "https://management.azure.com/subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.Compute/virtualMachines/${vmName}?api-version=${apiVersion}"
-    $response = Invoke-AzRestMethod -Method GET -Uri $uri 
-    $vmModel = $response.Content | ConvertFrom-Json 
-    $vmModel.resources = @() 
-    $body = $vmModel | ConvertTo-Json -Depth 10 -Compress 
-    Invoke-AzRestMethod -Method PUT -Uri $uri -Payload $body
+$subscriptionId = (Get-AzContext).Subscription.Id 
+$resourceGroup = "RGname" 
+$vmName = "VMName" 
+$apiVersion = "2025-04-01" 
+$uri = "https://management.azure.com/subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.Compute/virtualMachines/${vmName}?api-version=${apiVersion}"
+$response = Invoke-AzRestMethod -Method GET -Uri $uri 
+$vmModel = $response.Content | ConvertFrom-Json 
+$vmModel.resources = @() 
+$body = $vmModel | ConvertTo-Json -Depth 10 -Compress 
+Invoke-AzRestMethod -Method PUT -Uri $uri -Payload $body
+```
+
+### [CLI](#tab/cli)
+
+```cmd
+subscriptionId=$(az account show --query id -o tsv)
+resourceGroup="RGName"
+vmName="VMName"
+apiVersion="2025-04-01"
+uri="https://management.azure.com/subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.Compute/virtualMachines/${vmName}?api-version=${apiVersion}"
+response=$(az rest --method get --uri "$uri")
+vmModel=$(echo "$response" | jq '.resources = []')
+az rest --method put --uri "$uri" --body "$vmModel"
 ```
 
 > [!NOTE]

support/dynamics/gp/version-numbers-build-numbers-of-dexterity.md

@@ -31,7 +31,7 @@ This error also occurs when you try to view a source code dictionary that is bas
 
 To resolve this problem, we recommend that you obtain a new dictionary that is based on the current build of the Dynamics.dic file. For third-party dictionaries, you can update the code that is in the current build of the Dynamics.dic file by using the Dexterity Source Code Control Service.
 
-For more information about how to upgrade a Dexterity-based application by using the Dexterity Source Code Control Service, see [How to upgrade a Dexterity-based application in Microsoft Dynamics GP by using the Dexterity Source Code Control Service](https://support.microsoft.com/topic/how-to-upgrade-a-dexterity-based-application-in-microsoft-dynamics-gp-by-using-the-dexterity-source-code-control-service-9a592921-430d-e33b-9ab5-b7072dd9d026).
+For more information about how to upgrade a Dexterity-based application by using the Dexterity Source Code Control Service, see [How to upgrade a Dexterity-based application in Microsoft Dynamics GP by using the Dexterity Source Code Control Service](./upgrade-a-dexterity-based-application.md).
 
 For dictionaries that you want to access but that you do not plan to change, follow these steps to enable the dictionaries to run in Test Mode:
 
@@ -50,4 +50,4 @@ Alternatively, you can take the following actions:
 
 ## References
 
-For more information about index files and Great Plains Dexterity source code control functionality, see [How to use an index file and the Microsoft Dynamics GP Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code](https://support.microsoft.com/topic/how-to-use-an-index-file-and-the-microsoft-dynamics-gp-dexterity-source-code-control-functionality-to-make-sure-that-the-resources-that-you-create-maintain-the-same-resource-id-in-different-builds-and-versions-of-your-code-02402cc4-d884-afcf-d910-1d47722c18cc).
+For more information about index files and Great Plains Dexterity source code control functionality, see [How to use an index file with Dexterity to ensure resource IDs do not change in new builds and versions](./how-to-use-index-file-with-dexterity-to-maintain-resource-ids-in-new-builds-and-versions.md).

support/entra/entra-id/ad-dmn-services/send-microsoft-authenticator-logs.md

@@ -16,7 +16,7 @@ Follow these steps to send logs to customer support and get the incident ID.
 1. Open Microsoft Authenticator.
 1. Tap **Send feedback** in the app's top menu.
 1. Select **Having trouble?**.
-1. Fill out the form, and then select **Send** to send the feedback and/or logs (**Send** is on the top left on iOS, and on the top right on Android).
+1. Fill out the form, and then select **Send** to send the feedback and logs.
 1. Note the incident ID. You or your administrator will need this ID if you contact Microsoft Support.
 
 

support/power-platform/dataverse/environment-app-access/troubleshooting-user-needs-read-write-access-organization.md

@@ -12,6 +12,8 @@ search.audienceType:
 ---
 # Troubleshoot user access issues for different environments
 
+## Summary
+
 This article helps administrators diagnose and resolve common user access issues in Power Platform environments. You'll learn how to use the built-in diagnostics tool to identify problems with permissions, licenses, security roles, and group memberships that prevent users from accessing environments and resources.
 
 To access an environment, a user must meet the following criteria:

support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md

@@ -12,6 +12,8 @@ ms.custom: sap:Working with Solutions\Dependencies prevent a solution import
 ---
 # Missing dependencies error during solution import
 
+## Summary
+
 When you [import a solution](/powerapps/maker/data-platform/import-update-export-solutions) into a target environment in Microsoft Power Apps, you might encounter errors about missing dependencies. This article helps you identify the cause of missing dependency errors and provides workarounds to resolve them. It also includes best practices to help you prevent these errors in future solution imports.
 
 _Applies to:_   Power Platform, Solutions

support/power-platform/power-apps/create-and-use-apps/common-issues-and-resolutions.md

@@ -16,6 +16,8 @@ contributors:
 ---
 # Common issues and resolutions for Power Apps
 
+## Summary
+
 This article provides solutions to common problems that you might encounter when you create or use Power Apps. The article organizes problems by functional area, such as connectors, Power Automate integrations, Power Fx, and Power Apps Studio. Each section includes troubleshooting steps and links to related documentation.
 
 Before you troubleshoot specific problems, review [Power Apps troubleshooting strategies](./isolate-common-issues.md) for guidance on how to identify the source of a problem. That article outlines key principles for debugging both functional and performance problems.

support/power-platform/power-automate/desktop-flows/application-certificate-error.md

@@ -1,7 +1,7 @@
 ---
 title: Could not read the application certificate when creating connection with CyberArk credential
 description: Solves an error that occurs when you create a desktop flow connection using a CyberArk credential in Microsoft Power Automate.
-ms.custom: sap:Desktop flows\Cannot create desktop flow connection
+ms.custom: sap:Desktop flows\Connection Setup - CyberArk
 ms.date: 11/17/2024
 ms.author: quseleba 
 author: QuentinSele
@@ -18,25 +18,25 @@ When you [create a desktop flow connection using a CyberArk credential](/power-a
 
 ## Cause
 
-The error message occurs because the credential used in the connection can't be authenticated on the target machine you selected.
+The error message occurs because the credential used in the connection can't authenticate on the target machine you selected.
 
 ## Resolution
 
-If you use [Power Automate for desktop installer version](/power-platform/released-versions/power-automate-desktop#all-power-automate-desktop-versions) earlier than 2.50, you can upgrade to version 2.50 or later. After the upgrade, when you create a desktop flow connection using a CyberArk credential, you might see an error message with specific details on what went wrong. The details will give you enough information to solve the problem.
+If you use [Power Automate for desktop installer version](/power-platform/released-versions/power-automate-desktop#all-power-automate-desktop-versions) earlier than 2.50, upgrade to version 2.50 or later. After the upgrade, when you create a desktop flow connection using a CyberArk credential, you might see an error message with specific details on what went wrong. The details will give you enough information to solve the problem.
 
 Check the following sections for some specific error messages and their resolutions:
 
 ## "The configuration for the cyberArk store is incorrect. Validate all connection information."
 
 This error occurs because the CyberArk store is misconfigured, and a valid request can't be made for CyberArk.
 
-To solve this issue, make sure that the configuration settings in Power Automate match those in CyberArk, including the server address and the application ID. For example, the hostname of the CyberArk server should follow the `https://hostname.com` or `https://hostname.com:443` format. For more information, see [Create a CyberArk credential](/power-automate/desktop-flows/create-cyberark-credential#create-a-cyberark-credential-1).
+To solve this problem, make sure that the configuration settings in Power Automate match those in CyberArk, including the server address and the application ID. For example, the hostname of the CyberArk server should follow the `https://hostname.com` or `https://hostname.com:443` format. For more information, see [Create a CyberArk credential](/power-automate/desktop-flows/create-cyberark-credential#create-a-cyberark-credential-1).
 
 ## "Could not contact the CyberArk vault. Verify connectivity to the server and validate all connection information."
 
-This error occurs due to issues with network connectivity between your machine and the CyberArk server.
+This error occurs because of problems with network connectivity between your machine and the CyberArk server.
 
-To solve this issue:
+To fix this problem:
 
 - Confirm that your machine can communicate with the CyberArk server.
 - Ensure that the server certificate is trusted by installing it in the [Trusted Root Certification Authorities Certificate Store](/windows-hardware/drivers/install/trusted-root-certification-authorities-certificate-store).
@@ -46,40 +46,63 @@ To solve this issue:
 
 This error occurs because the object name doesn't match a CyberArk secret that the configured application can retrieve.
 
-To solve this issue,
+To fix this problem,
 
 1. Use the [Get accounts API](https://docs.cyberark.com/pam-self-hosted/latest/en/content/sdk/getaccounts.htm?tocpath=Developer%7CREST%20APIs%7CAccounts%7C_____1) to get a list of all the accounts in the Vault.
 1. If no account name matches the object name, update the object name with an existing account, or confirm with your CyberArk team that the application has access to the CyberArk safe that contains the object.
 
 ## "The CyberArk server was unable to verify the certificate, please confirm that the CyberArk server is correctly configured for SSL authentication."
 
-This issue occurs because the CyberArk Central Credential Provider (CCP) might not be correctly set up or configured.
+This problem occurs because the CyberArk Central Credential Provider (CCP) might not be correctly set up or configured.
 
-To solve this issue, see [CCP Error APPAP330E Failed to verify application authentication data: Could not obtain client certificate details](https://community.cyberark.com/s/article/CCP-Error-APPAP330E-Failed-to-verify-application-authentication-data-Could-not-obtain-client-certificate-details).
+To fix this problem, see [CCP Error APPAP330E Failed to verify application authentication data: Could not obtain client certificate details](https://community.cyberark.com/s/article/CCP-Error-APPAP330E-Failed-to-verify-application-authentication-data-Could-not-obtain-client-certificate-details).
 
 ## "Could not read the application certificate. Try to delete and recreate the application."
 
 This error message means that the CyberArk certificate can't be processed correctly. The application certificate might be missing, corrupted, or incorrectly installed.
 
-This message often appears incorrectly for most errors with Power Automate for desktop versions before 2.50. If you're using a version earlier than 2.50, try an upgrade.
+For most errors, this message appears incorrectly in versions of Power Automate for desktop before 2.50. If you're using a version earlier than 2.50, try an upgrade.
 
 Otherwise, [delete](https://docs.cyberark.com/identity/latest/en/content/applications/appsadminportal/appremove.htm) and [re-create](https://docs.cyberark.com/credential-providers/13.0/en/content/common/adding-applications.htm) the application in CyberArk as suggested in the error message. Ensure that you correctly enter the **Application ID**, **Safe**, **Folder**, and **Object** details when [setting up the connection](/power-automate/desktop-flows/create-cyberark-credential#create-a-cyberark-credential-1).
 
+## Troubleshoot certificate trust errors
+
+If a connection check times out while retrieving credentials from CyberArk, the issue might be related to HTTPS certificate trust. To determine whether an untrusted certificate is causing the problem, you can temporarily configure the [Power Automate service (UIFlowService)](/power-automate/desktop-flows/pad-architecture) to accept untrusted certificates for testing purposes.
+
+> [!WARNING]
+> For security, the service accepts only trusted certificates by default. Use the following steps only for testing. After you finish testing, delete the registry entry and restart the service to restore the default behavior.
+
+To test for certificate trust issues, follow these steps:
+
+1. Open [Registry Editor](~/windows-server/performance/windows-registry-advanced-users.md#use-registry-editor).
+1. Go to the following registry key:
+
+   `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\Registration`
+
+1. Create a new **DWORD** value named `AllowUntrustedCyberArkHttpsCertificate`.
+1. Set the value to `1` to allow untrusted CyberArk HTTPS certificates.
+1. Restart the Power Automate service (UIFlowService) to apply the change.
+1. Retry creating the desktop flow connection with the CyberArk credential.
+1. After testing, delete the `AllowUntrustedCyberArkHttpsCertificate` registry entry.
+1. Restart the Power Automate service again to restore the default behavior.
+
+If the connection succeeds after you allow untrusted certificates, the root cause is a certificate trust problem. To permanently resolve this problem, install the CyberArk server certificate in the [Trusted Root Certification Authorities Certificate Store](/windows-hardware/drivers/install/trusted-root-certification-authorities-certificate-store) on the target machine.
+
 ## Other troubleshooting steps
 
-If you still don't have enough information to mitigate the issue, here are some steps you can take to troubleshoot the issue:
+If you still don't have enough information to resolve the issue, try the following steps:
 
-1. Try using a dedicated action to get a secret from CyberArk in Power Automate for desktop with a local run to validate your configuration.
-1. Try using a browser to get the secret from the target machine with one of the following methods:
+1. Use a dedicated action to get a secret from CyberArk in Power Automate for desktop with a local run to validate your configuration.
+1. Use a browser to get the secret from the target machine by using one of the following methods:
 
     - Install the client certificate required for the application on the machine in the user store.
     - Use the following URI in your browser, and select the appropriate certificate to authenticate:
 
       `https://<hostname>/AIMWebService/api/Accounts?AppId=<appid>&Query=Safe=<safe>;Object=<object>`
 
-1. If you receive a warning message indicating that the server certificate isn't trusted with one of the methods in step 2, make sure you install the server certificate in the [Trusted Root Certification Authorities Certificate Store](/windows-hardware/drivers/install/trusted-root-certification-authorities-certificate-store).
+1. If you receive a warning message indicating that the server certificate isn't trusted by using one of the methods in step 2, make sure you install the server certificate in the [Trusted Root Certification Authorities Certificate Store](/windows-hardware/drivers/install/trusted-root-certification-authorities-certificate-store).
 
-1. Try [changing the Power Automate for desktop service user](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account) to a user who has successfully retrieved the secret with one of the methods in step 2.
+1. Try [changing the Power Automate for desktop service user](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account) to a user who successfully retrieved the secret by using one of the methods in step 2.
 
 ## More information
 

support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md

@@ -11,6 +11,8 @@ search.audienceType:
 ---
 # Troubleshoot Power Automate trigger issues and errors
 
+## Summary
+
 When Power Automate flows don't run as expected, the trigger might be the problem. [Triggers](/power-automate/triggers-introduction) are the entry point for your flows. They can fail for several reasons, such as connection problems, expired authentication tokens, licensing problems, and misconfigured conditions.
 
 This article describes the most common trigger problems and their solutions. You'll learn how to diagnose connection problems, check licensing requirements, review trigger conditions, and handle environment-specific problems.