Merge remote-tracking branch 'upstream/main' into AB#7180-Error-code-0x8024402C

Author: v-tappelgate

support/entra/entra-id/app-integration/error-code-AADSTS50020-user-account-identity-provider-does-not-exist.md

@@ -33,9 +33,9 @@ In the prior experience, a directory (for example: UserNamehotmail735.onmicrosof
 
 If you aim to have a directory, you must create an Azure account and a new tenant: 
 
-1.    Browse to [https://azure.microsoft.com/en-us/free/](https://azure.microsoft.com/free/), and then select **Start free** .
-2.    Follow the instructions to create an Azure account.
-3.    A tenant will be generated alongside the Azure account, and you will be automatically designated as the Global Administrator. This grants you full access to all options within this tenant.
+1. Browse to [the Azure account website](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn), and then select **Try Azure for free**.
+2. Follow the instructions to create an Azure account.
+3. A tenant will be generated alongside the Azure account, and you will be automatically designated as the Global Administrator. This grants you full access to all options within this tenant.
 
 ## Cause 2: Used unsupported account type (multitenant and personal accounts)
 
@@ -104,7 +104,7 @@ Make sure that you follow the steps in [Quickstart: Add guest users to your dire
 
 If your application is an enterprise application that requires user assignment, error `AADSTS50020` occurs if the user isn't on the list of allowed users who are assigned access to the application. To check whether your enterprise application requires user assignment:
 
-1. In the [Azure portal](https://portal.azure.com), search for and select **Enterprise applications**.
+1. In [the Azure portal](https://portal.azure.com), search for and select **Enterprise applications**.
 
 1. Select your enterprise application.
 
@@ -157,7 +157,7 @@ Then, check the creation date of the guest user in the resource tenant against t
 
 #### Microsoft Entra PowerShell
 
-Run the [Get-EntraUser](/powershell/module/microsoft.entra/get-entrauser) PowerShell cmdlet to review the user creation date, as follows:
+Run the [Get-EntraUser](/powershell/module/microsoft.entra.users/get-entrauser) PowerShell cmdlet to review the user creation date, as follows:
 
 ```powershell
 Get-EntraUser -UserId {id | userPrincipalName} | Select-Object id, userPrincipalName, createdDateTime

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -2,7 +2,7 @@
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
 ms.date: 09/11/2025
-ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon, iopanag
+ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon, iopanag, v-shaywood
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -70,3 +70,4 @@ _Original KB number:_   4555406
 |MachineNotFound|404|Attended</br>Unattended|This error can occur when the machine is unregistered during a run or if the Dataverse organization has been migrated to a different region. Verify that:</br>- Your machine is still registered by [viewing its status](/power-automate/desktop-flows/manage-machines#view-list-of-machines) in the machine runtime application or the Power Automate portal.</br>- Your [desktop flow connection](/power-automate/desktop-flows/desktop-flow-connections) isn't broken in the Power Automate portal.</br>- [Scripting actions](/power-automate/desktop-flows/actions-reference/scripting) in your flow don't register your machine while the flow is running.|
 |NoSessionFoundForPasswordless|400|Attended|An opened session on the machine is required to run the desktop flow in attended mode. You can also use unattended mode instead of using a [Power Automate Process license](/power-platform/admin/power-automate-licensing/deep-dive-on-specific-license#power-automate-process-license).|
 |MSEntraRemoteDesktopAppConsentRequired|400|Unattended|The Remote Desktop connection consent dialog was shown when attempting to establish the unattended session. For more information about how to hide the consent dialog, see [Admin consent for unattended runs using CBA or sign-in credentials with NLA](/power-automate/desktop-flows/run-unattended-desktop-flows#admin-consent-for-unattended-runs-using-cba-or-sign-in-credentials-with-nla-preview).|
+|UIFlowParentFlowFailed|N/A|Attended</br>Unattended|- Check if a parent cloud flow failed. If so, resolve any issues in the parent flow.</br>- Check if your machine's (or machine group’s) run queue is too large, or if the connection usage is being throttled. If so, assign your desktop flow to a new connection to avoid throttling issues.|