Troubleshoot Nerdio Manager Azure Runbook Installation

• If nmwInstall Azure Automation runbook fails during Login to Azure Resource Manager (see below), then the Admin user account specified during the deployment from Azure Marketplace is either incorrect or has MFA/Conditional Access enabled.

• 

• Make sure that the user account is excluded from all MFA and Conditional Access (CA) policies that could be blocking Azure Automation's ability to execute the runbook.

• If it is not possible to disable MFA/CA for this user account, then there are the following options:

  • Use the PowerShell script method instead of Azure Runbook. Select Download Script on the Nerdio Manager app page.

  • Create a temporary account with Global Administrator role in Entra ID and Owner role on the Azure Subscription with MFA/CA disabled. Use this account for the installation. Once everything is configured, delete or disable it because is not needed for Nerdio Manager to operate on an ongoing basis.

• If you want to change the user account, or retype the password, do the following:

  • In the Azure portal, search for nmw-app-automation.

  • In the blade on the left side, select Credentials.

  • Select runAsCreds.

  • Edit the username and/or password.

• Be sure that the user account you are using is a member of the same Entra ID tenant as the Nerdio Manager deployment. External users, even with admin access, do not work.

• Ensure that the user account you are using is a Global Administrator in Entra ID and is an Azure Subscription Owner.

• Once you've made the changes above:

  • In the Azure portal, search for nmw-app-automation.

  • In the blade on the left side, select Runbooks.

  • Select nmwUpdateRunAs.

  • Select Start.