Concurrent Runbook execution switching to different subscription interfere with each other inspite of Disable-AzureRmContextAutosave RRS feed

  • Question

  • I have a single runbook in my automation account that deploys an ARM template in 1 or 8 subscriptions based on the input parameters. Each subscription also has a uniquely named Resource Group.

    When running multiple instances of the runbook concurrently I run into resource group not found errors even though the resource groups exists. The jobs run well when running one at a time.

    I suspect that the Select-AzureSubscription command is taking effect on all jobs in spite of using Disable-AzureRmContextAutosave at the begining of the runbook.

    Is this by design? Or am I missing some other cruicial measures to prevent the subscription from being switched across all Jobs?

    Sunday, October 20, 2019 8:22 AM


All replies