I’ve always developed and ran scripts locally through VS Code. I’m just getting started with Azure Automation and am not a fan of waiting for the job to complete before seeing my results. In fact, it’s very frustrating. I’d rather develop and test my script locally first before running it in Azure Automation.

I’m using a user-managed identity to run scripts against Exchange Online. VS Code has an Azure Automation plugin that provides an option to run script locally, but the script bombs out when attempting to use the user-managed identity, as the user-managed identity may only be run in Azure.

For those of you who use Azure Automation, I can’t imagine that you develop significant portions of the script and wait for automation jobs to complete each time to verify changes.

How do you develop locally? Do you use an app registration w/ client secret in key vault and call that from your local machine? Do you have a process for developing locally for scripts that specify managed identities?

Thanks everyone!

  • pwshguy (mdowst)@programming.devM
    2·
    1 year ago

    Just a heads up, I received confirmation from the product team that the AZUREPS_HOST_ENVIRONMENT environment variable is going away. They are moving the backend to containers. Also, the COMPUTERNAME one that was always “client” is going to change too. The COMPUTERNAME will now be “Sandbox-###” with # being random numbers. I started using the code block below in my runbooks to find if they are running in Azure or hybrid worker/locally. It accounts for the current and the updates that will be rolling out in the near future.

    $isHybridWorker = $true
if (($env:computername) -eq "CLIENT") {
    $isHybridWorker = $false
}
elseif ($env:USERNAME -eq 'ContainerAdministrator') {
    $isHybridWorker = $false
}
``