I had similar issue. My solution was to register "Microsoft.Compute", which is required to create/update SSH keys.
I adjusted the quotas I could find but still can't deploy !!!
Error details
The template deployment 'StephenBrainData2025-aks' is not valid according to the validation procedure. The tracking id is '8481c706-b3df-4f55-aaef-510592e2c641'. See inner errors for details. (Code: InvalidTemplateDeployment)
Preflight validation check for resource(s) for container service braindata2025-aks in resource group mrg-sas-viya-on-azure-20241011130043 failed. Message: Insufficient vcpu quota requested 20, remaining 10 for family standardEDSv4Family for region australiaeast.. Details: (Code: ErrCode_InsufficientVCPUQuota)
"Message: Insufficient regional vcpu quota left for location australiaeast. left regional vcpu quota 0, requested quota 44."
NEXT problem. How do I fix this?
So I added to quotas so many times and repeated the deployment attempts that I now get this error. I tried to delete the resource group ...1039 but couldn't.
(Code: DeploymentFailed, Target: /subscriptions/36efa6a2-ce6f-4094-a0e3-0cda7a743e04/resourceGroups/mrg-sas-viya-on-azure-20241010212403/providers/Microsoft.Resources/deployments/stephenbrainsapp2-automation), {
"code": "BadRequest",
"message": "Account already exists in another resourcegroup in a subscription. ResourceGroupName: mrg-sas-viya-on-azure-20241010131039."
multiple iterations and the quotas now fixed i think. But so many attempts left me with 8 resource groups and I want to tidy that up
So I repeated the deployment attempts so many times to add to quotas that I now get this error. I tried to delete the resource group ...1039 but couldn't.
(Code: DeploymentFailed, Target: /subscriptions/36efa6a2-ce6f-4094-a0e3-0cda7a743e04/resourceGroups/mrg-sas-viya-on-azure-20241010212403/providers/Microsoft.Resources/deployments/stephenbrainsapp2-automation), {
"code": "BadRequest",
"message": "Account already exists in another resourcegroup in a subscription. ResourceGroupName: mrg-sas-viya-on-azure-20241010131039."
For the deletion process, please refer to https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group?tabs...
To address the error regarding the existing automation account name during your new deployment, it is important to note that this issue arises from using a deployment name that has already been utilized in a previous deployment. This name cannot be reused for future deployments unless the old resources are deleted. Therefore, it is essential to ensure that the “Deployment Name” chosen for the new deployment is unique and does not match any of the existing SAS Viya resources from previous deployments.
@Lillioja Hope using the deletion links and different name for each deployment as suggested above helped with the problem. If it did not solve the problem, it could be a different issue based on the error message you have posted. It says the automation account is already exists. It could be related to the recent changes by Microsoft on the restrictions of only 2 automation account can be created per region, see the link below.
Pay-as-you-go, MPN, Azure Pass subscriptions can create 2 Automation accounts per subscription in any of the regions supported by the service.
A possible solution could be to try your deployment in a different region if you are still facing issues.
There are a lot watching this thread so I glad to announce that I can now log into a SAS STUDIO page.
(for support your local SAS techs will NOT be able to help, and the Microsoft help though willing, is unfamiliar with this SAS deployment. Indeed Microsoft help needs you select your issue out of hundreds of entries in a list of techspeak 😰)
For those struggling as I was:
watch https://www.youtube.com/watch?v=kHYaj5qiPow
this is just a start.
Be careful selecting your region because you get offered ones on the drop down list that don't exist ( for those that do exist see https://learn.microsoft.com/en-us/azure/reliability/availability-zones-service-support#azure-regions... ).
BUT
Rich Main must have set things up on an in house SAS computer because he misses a whole lot in the middle and newbies will get stuck trying to create SSH keys.
THEREFORE
See the posting about Microsoft.Compute (there are two steps needed 1. activate, and then
2. disseminate)
THEN
Set the Quotas. Most you can do from your home page. I set them 50 to 100 which was high I think. But I had to redeploy so many times to get it right that I went high - the deployment errors will alert you). There was one that the system would not let me adjust (standardEDSv4Family) and I had to put in a technical request. That Quota is not easy to find by the way, but you need to make sure you select just your region to do the search, not the thousands from the whole globe).
Good Luck.
This programming is not for the homework client and I decided I can't afford it.
SAS probably doesn't charge much but they assign you to top flight servers and Microsoft or who else do charge a lot for them, so beware. So far I spent $600 without running a single line of code.
Congratulations!
To minimize the cost, the instruction to start/stop SAS Viya is very helpful.
Greetings, I need some assistance please and trust that someone on this Forum may have experienced the same issue before. Trying to deploy SAS Viya (pay-as-you-go) on Azure Marketplace. The error I receive states:
"
"
Registration is now open for SAS Innovate 2025 , our biggest and most exciting global event of the year! Join us in Orlando, FL, May 6-9.
Sign up by Dec. 31 to get the 2024 rate of just $495.
Register now!