When deploying SAS Viya (Pay as You Go) in the Market Place on Microsoft Azure, it will deploy Automation Accounts.
More info here: Azure Automation overview | Microsoft Learn
Essentially, Automation is needed in three broad areas of cloud operations:
Deploy and manage - Deliver repeatable and consistent infrastructure as code.
Response - Create event-based automation to diagnose and resolve issues.
Orchestrate - Orchestrate and integrate your automation with other Azure or third party services and products.
From September 2024, Microsoft Azure is implementing a change to the 'limits' on creation of automation accounts.
See this link: Azure subscription limits and quotas - Azure Resource Manager | Microsoft Learn
The new limit is that:
Any PAYG subscription will have a limit of 2 concurrent automation accounts; this includes Automation Accounts in a 'soft delete' status.
Any automation account that is deleted goes into a 'soft delete ' status and is only deleted completely (Hard Deleted) after 30days have elapsed for that Account.
If an Automation Account is in a 'soft delete' status, it can be recovered. Though my experience was that I could not; this might be because the Resource Group that the Automation Account existed in has been deleted.
What's the impact to you?
If you have deployed SAS Viya (PAYG) from Azure Market Place, you can only do it twice in any 30 days. This is because when you delete the Managed Application, it also 'soft deletes' the Automation Account with it.
Therefore, incurring a deployment limit.
One work round that you can try, and is subject to sufficient permissions, is create a new subscription which resets the count.
Question
Are there alternative approaches that could be taken, given this new limit?
Request for improvement
One suggestion I have is that: the deployment allows 'creation of' or 'use of existing' automation accounts? Sometimes deployments fail, because resources are not available, and you want to delete and try again from scratch. You now have a limited re-try attempt.
