You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/how-to-display-encryption-settings-with-azure-resource-explorer.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
title: How to display encryption settings on Azure Linux Virtual Machines
2
+
title: How to Display Encryption Settings on Azure Linux Virtual Machines
3
3
description: Learn how to visualize encryption settings stamped on a disk or VM after Azure Disk Encryption (ADE) is deployed.
4
4
author: elicorme
5
5
ms.author: elcorral
6
6
ms.date: 01/20/2025
7
7
ms.reviewer: divargas
8
8
ms.service: azure-virtual-machines
9
9
ms.custom: linux-related-content
10
-
ms.topic: troubleshooting
10
+
ms.topic: how-to
11
11
ms.collection: linux
12
12
---
13
13
@@ -24,7 +24,7 @@ When Azure Disk Encryption (ADE) is enabled on an Azure Linux Virtual Machine (V
24
24
25
25
## How to identify the ADE extension version
26
26
27
-
You can identify the ADE version in the Azure portal. To do this, open the properties of the VM, and then select `Extensions` to open the `Extensions` blade. On the `Extensions` blade, view the version number of **AzureDiskEncryptionForLinux**.
27
+
You can identify the ADE version in the Azure portal. To do this, open the properties of the VM, and then select **Extensions** to open the **Extensions** blade. On the **Extensions** blade, view the version number of **AzureDiskEncryptionForLinux**.
28
28
29
29
- If the version number is `0.*`, the disk uses **dual-pass encryption**.
30
30
- If the version number is `1.*` or a later version, the disk uses **single-pass encryption**.
@@ -37,17 +37,17 @@ If ADE single-pass is used, the extension process stamps the encryption settings
37
37
## <aid="portal"> </a> Verify ADE encryption settings through Azure portal
38
38
39
39
1. Log in to your subscription in [the Azure portal](https://portal.azure.com)
40
-
2. Search for "Resource Explorer" on the search bar.
40
+
2. Search for "resource explorer" on the search bar.
:::image type="content" source="./media/how-to-display-encryption-settings-in-azure-vms/searchresourceexplorerportal.png" alt-text="Screenshot that shows searching for resource explorer on the Azure portal search bar.":::
43
43
44
-
3. Select the "Resource Explorer" icon.
44
+
3. Select the **Resource Explorer** icon.
45
45
4. Select the subscription that you want to review.
46
46
5. Locate the disk that you want to review by using either by the resource group path or the provider path.
47
47
48
-
:::image type="content" source="./media/how-to-display-encryption-settings-in-azure-vms/providersrgs.png" alt-text="Provider and resource groups view":::
48
+
:::image type="content" source="./media/how-to-display-encryption-settings-in-azure-vms/providersrgs.png" alt-text="Screenshot that shows the provider and resource groups view in which you can select the desired disk for review.":::
:::image type="content" source="./media/how-to-display-encryption-settings-in-azure-vms/compute.jpeg" alt-text="Screenshot that shows the desired disk selected.":::
51
51
52
52
6. After the disk is selected, the corresponding JSON metadata is shown in the right panel. The encryption settings block is enclosed inside the `encryptionSettingsCollection` key. It resembles the following code:
53
53
@@ -89,7 +89,7 @@ If you're already using the dual-pass version of ADE, the encryption settings ar
89
89
90
90
## Verify ADE encryption settings through Azure Web Resource Explorer
91
91
92
-
You can access the web version of Resource Explorer through [this link](https://resources.azure.com). Follow steps 1 through 6 in []"Verify ADE encryption settings through Azure portal"](#portal) to locate the component that ou want to analyze.
92
+
Open the [web version of Resource Explorer](https://resources.azure.com), and then follow steps 1 through 6 under ["Verify ADE encryption settings through Azure portal"](#portal) to locate the component that you want to analyze.
# An unattended desktop flow run fails with the MSEntraMachineAlwaysPromptingForPassword error
10
10
@@ -29,7 +29,29 @@ Your unattended desktop flow run fails with the "MSEntraMachineAlwaysPromptingFo
29
29
30
30
Power Automate for desktop can't validate your Microsoft Entra ID (formerly Azure Active Directory) credentials on the machine. This issue is typically caused by a group policy setting on your machine.
31
31
32
-
## Resolution
32
+
## Resolution 1: Use Microsoft Entra authentication for Remote Desktop with a user certificate
33
+
34
+
This resolution requires Power Automate for desktop version 2.50 or later and must be used when no [multifactor authentication (MFA) exception](~/power-platform/power-automate/administration/conditional-access-and-multi-factor-authentication-in-flow.md#details) can be granted to the desktop flow connection account.
35
+
36
+
For steps on how to set up Microsoft Entra certificate based authentication for Power Automate, see [Configure certificate-based authentication (preview)](/power-automate/desktop-flows/configure-certificate-based-auth).
37
+
38
+
## Resolution 2: Use Microsoft Entra authentication for Remote Desktop with a username and password
39
+
40
+
This resolution requires Power Automate for desktop version 2.49 or later. If you don't have MFA enabled for the account used by the desktop flows connection, you can set up Microsoft Entra authentication using a username and password instead.
41
+
42
+
1. Open the Registry Editor (regedit) with administrative privileges. Navigate to the following registry path, create a new DWORD-32 value with the name `UseRdsAadAuthentication`, and then set the value of `UseRdsAadAuthentication` to **1**.
2.[Hide the consent prompt dialog for a target device group](/power-automate/desktop-flows/run-unattended-desktop-flows#admin-consent-for-unattended-runs-using-cba-or-sign-in-credentials-with-nla-preview).
49
+
50
+
3. Restart the Power Automate service.
51
+
52
+
4. Use a Microsoft Entra ID connection with username and password credentials. Note that an MFA exception is required for this account.
53
+
54
+
## Resolution 3: Disable fPromptForPassword
33
55
34
56
To solve this issue, check the group policy setting on your machine.
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Error code occurs when running an attended or unattended desktop flow
3
3
description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
|UnattendedUserSessionDisconnected|400|Unattended|For more information about this error code, see [UnattendedUserSessionDisconnected](troubleshoot-desktop-flow-run-queue-errors.md#unattendedusersessiondisconnected).|
29
29
|UnattendedUserSessionLocked|400|Unattended|For more information about this error code, see [UnattendedUserSessionLocked](troubleshoot-desktop-flow-run-queue-errors.md#unattendedusersessionlocked).|
30
30
|SessionNotFound|400|Unattended|The Windows session on the machine for the given run can't be found. This issue can occur in the following cases:<br>- The machine reboots during the run.<br>- You're using a virtual machine that was cloned after installing Power Automate. If it was cloned after the installation and was registered, delete your machine from the Power Automate portal and re-register the machine.|
31
+
|SessionNotFoundAfterCreation|400|Unattended|The Windows session on the machine for the given run can't be found after the session is created. This issue can occur if the Power Automate service ([UIFlowService](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account)) doesn't have the rights to enumerate remote sessions. To solve this issue, ensure the account running the Power Automate service (UIFlowService) is in the "Remote Desktop Users" group and not removed by group policy.|
31
32
|TooManyActiveSessions|400|Unattended|Windows Server only.</br>You need to sign out at least one active session on the machine.|
32
33
|SessionHasLoggedOff|400|Unattended|To solve this issue, see [SessionHasLoggedOff occurs during a desktop flow run connected with the cloud](session-has-logged-off-troubleshooting.md).|
33
34
|SessionHasLoggedOffWithMaxIdleTime |400|Unattended|To solve this issue, see [SessionHasLoggedOffWithMaxIdleTime occurs during a desktop flow run](desktop-flow-max-session-duration-error.md).|
|UnattendedUnsupportedWithOldConnection|403|Unattended|You need to create a new connection on the portal.|
38
39
|RDPIsNotEnabled|400|Unattended|You need to enable Remote Desktop on the machine.|
39
40
|UIFlowAlreadyRunning|429|Attended</br>Unattended|A desktop flow is already running on the machine. You need to wait for its completion. For more information about this error code, see [UIFlowAlreadyRunning](troubleshoot-desktop-flow-run-queue-errors.md#uiflowalreadyrunning).|
40
-
|AadLogonFailure|400|Unattended|You need to disable Network Level Authentication (NLA) on the machine if you want to use Microsoft Entra credentials.|
41
+
|MSEntraLogonFailure|400|Unattended|To resolve this issue, see [Desktop flows run failed with the MSEntraLogonFailure error code](ui-flows-run-failed-with-aadlogonfailure-error.md).|
41
42
|Win10AlreadyHasActiveSession|400|Unattended|Windows 10 only. You need to sign out from the active session on the machine.|
42
43
|UIFlowAgentNotAvailable|400|Attended</br>Unattended|You need to confirm that the service uiflowservice is up and running on your machine. If you have the following error when trying to start uiflowservice, see [Desktop flows failure](https://support.microsoft.com/help/4564550/):</br>**Windows could not start the UIFlowService service on Local Computer. Error 1069: The service did not start due to a logon failure**|
43
44
|UnableToCallCrlEndpoint|400|Attended</br>Unattended|You need to ensure the revocation list for the certificates can be checked. Ensure that the CRL services aren't blocked on the target machine. The services that must be contacted are listed in this article: [Limits for automated, scheduled, and instant flows](/power-automate/limits-and-config#ui-flows-required-services)|
- Ensure that you can remote desktop to the machine from another machine on your network. If you're using Windows Server, you can try to remote desktop to "localhost" from the local machine itself when logged in as another account. If these actions fail, see [General Remote Desktop connection troubleshooting](../../../windows-server/remote/rdp-error-general-troubleshooting.md).
54
54
- If you have a legal notice enabled for login, work with your system administrator to try disabling it. To see if the legal notice is activated, open Registry Editor and go to `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`. If `legalnoticecaption` or `legalnoticetext` isn't empty, work with your system administrator to disable the legal notice.
55
55
- Ensure that no third-party software is installed that might affect login or interfere with creating a remote desktop connection.
56
+
- If you use a domain account (DOMAIN\user) to connect, connectivity issues with the domain controller might prevent the session from opening correctly. Work with your system administrator to examine connectivity logs. If you're on a Microsoft Entra joined or Entra hybrid joined device, try using a UPN (`[email protected]`). To see if you can use a UPN, go to **Start** > **Run**, and run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. If you see `AzureAdJoined: YES` under `Device State`, try changing the user specified in the connection to the `[email protected]` format.
Your unattended desktop flows run failed with the error code **AadLogonFailure**.
19
+
Your unattended desktop flows run failed with the error code **MSEntraLogonFailure**.
20
20
21
21
## Cause
22
22
23
23
Desktop flows failed to validate your Microsoft Entra credentials on the machine.
24
24
25
-
## Resolution
25
+
## Resolution for Power Automate for desktop version 2.49 or later
26
+
27
+
You need to [configure Microsoft Entra authentication for Remote Desktop](/power-automate/desktop-flows/run-unattended-desktop-flows#admin-consent-for-unattended-runs-using-cba-or-sign-in-credentials-with-nla-preview).
28
+
29
+
## Resolution for Power Automate for desktop version 2.48 or earlier
26
30
27
31
You need to disable Network Level Authentication (NLA) on the machine.
0 commit comments