Runbook Not Working in Account Automation

Manuel Alfonso Naranjo Higuera (HOGAR SÍ) 0

For a week now, the runbook that I had programmed in the automation account has stopped working. I created another automation account to check if the problem was with the automation account itself, but the problem persists. Can anyone help me?

tbgangav-MSFT 10,421 Reputation points

2024-03-15T11:49:53.2533333+00:00

Hi @Manuel Alfonso Naranjo Higuera (HOGAR SÍ) ,

Can you please share more context?

What is the runbook or script intended to do?

Share your runbook by removing any PII so I can try to reproduce the issue in my lab.

Also, when you say runbook stopped working, are you seeing any error? If yes, whats the error?

If you are not seeing any error, did you configure runbook output and messages streams? If yes, are you getting any insights out of it?
Manuel Alfonso Naranjo Higuera (HOGAR SÍ) 0 Reputation points

2024-03-15T12:03:52.6233333+00:00

Hi thank you so much for your quick reply. I have programmed and published a Runbook that performs the functions of turning the Power BI Embedded service on and off. This script has stopped working since last Friday, March 8th. The content of the script is as follows:

# Disable-AzureRmContextAutosave –Scope Process

$connection = Get-AutomationConnection -Name AzureRunAsConnection

Connect-AzureRmAccount -ServicePrincipal -Tenant $connection.TenantID `

-ApplicationID $connection.ApplicationID -CertificateThumbprint $connection.CertificateThumbprint

$AzureContext = Select-AzureRmSubscription -SubscriptionId $connection.SubscriptionID

Resume-AzureRmPowerBIEmbeddedCapacity -Name Service Name

The errors shown are as follows:

Get-AutomationConnection : RunAsAccount not found. To create this RunAsAccount, navigate to the RunAsAccount blade and create a RunAsAccount. Refer doc for more details (https://docs.microsoft.com/azure/automation/create-runas-account) At line:3 char:15 + $connection = Get-AutomationConnection -Name AzureRunAsConnection + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [Get-AutomationConnection], AssetManagementClientException + FullyQualifiedErrorId : 3,Orchestrator.AssetManagement.Cmdlets.GetAutomationConnectionCmdlet

Connect-AzureRmAccount : Cannot validate argument on parameter 'Tenant'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. At line:4 char:50 + ... nnect-AzureRmAccount -ServicePrincipal -Tenant $connection.TenantID ` + ~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (:) [Connect-AzureRmAccount], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Azure.Commands.Profile.ConnectAzureRmAccountCommand

Set-AzureRmContext : Cannot validate argument on parameter 'Subscription'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. At line:7 char:60 + ... Select-AzureRmSubscription -SubscriptionId $connection.SubscriptionID + ~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (:) [Set-AzureRmContext], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Azure.Commands.Profile.SetAzureRMContextCommand

Resume-AzureRmPowerBIEmbeddedCapacity : The term 'Resume-AzureRmPowerBIEmbeddedCapacity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:9 char:1 + Resume-AzureRmPowerBIEmbeddedCapacity -Name pbihogarsi + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Resume-AzureRmPowerBIEmbeddedCapacity:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
tbgangav-MSFT 10,421 Reputation points

2024-03-16T06:18:08.3433333+00:00

Hi @Manuel Alfonso Naranjo Higuera (HOGAR SÍ) ,

As per the error "Get-AutomationConnection : RunAsAccount not found" and as per your runbook, looks like you are still intended to use Run As Account. However, as per this and as per below screenshot, Run As Accounts are retired and are replaced with Managed Identities. So, I recommend you to migrate to Managed Identities and tweak your runbook to use Managed Identity.
Manuel Alfonso Naranjo Higuera (HOGAR SÍ) 0 Reputation points

2024-03-16T20:14:18.39+00:00

Hello, thank you so much for your quick response.

It's true that I have the notice in my automation account but I hadn't noticed.

With the new requirement, could you help me with the creation of the new script structure so that the service works properly with the new parameters needed?

I look forward to your reply,

Best regards
Manuel Alfonso Naranjo Higuera (HOGAR SÍ) 0 Reputation points

2024-03-16T20:16:22.97+00:00

Hello, thank you so much for your quick response.

It's true that I have the notice in my automation account but I hadn't noticed.

With the new requirement, could you help me with the creation of the new script structure so that the service works properly with the new parameters needed?

I look forward to your reply,

Best regards

2 answers

tbgangav-MSFT 10,421 Reputation points

2024-03-25T15:38:30.8966667+00:00
Hi @Manuel Alfonso Naranjo Higuera (HOGAR SÍ) ,

Please follow the steps mentioned in the link from my earlier comment i.e., this document.

If you have already taken care of creating managed identity, the new script could be something like shown below.

try { "Logging in to Azure..." Connect-AzAccount -Identity } catch { Write-Error -Message $_.Exception throw $_.Exception } Resume-AzPowerBIEmbeddedCapacity -Name Service Name

This sample script is also generated from the same document that I have referred earlier. Also, note that I have replaced Resume-AzureRmPowerBIEmbeddedCapacity cmdlet to Resume-AzPowerBIEmbeddedCapacity as AzureRm is not recommended to use. So, before you use Resume-AzPowerBIEmbeddedCapacity cmdlet, please ensure that the cmdlet related module (Az.PowerBIEmbedded) is imported in your Azure Automation account. For more information with regards to it, please refer this document.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Manuel Alfonso Naranjo Higuera (HOGAR SÍ) 0 Reputation points

2024-04-05T19:16:02.6+00:00

Hello,

I need help to be able to adapt the code to the new requirements of Azure so that the automation works correctly again.

Could you help me with that?

I look forward to your reply
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

Runbook Not Working in Account Automation

2 answers