The error indicates you have reached a quota limit in your subscription:  "Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus2, Current Limit: 10, Current Usage: 6, Additional Required: 8, (Minimum) New Limit Required: 14."    You can see the quota requirments listed here: https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaaksfaq/n09skbpwwk7m4vn122eufqzw4mgr.htm Request a quota increase in the Azure portal: https://learn.microsoft.com/en-us/azure/quotas/quickstart-increase-quota-portal   ... View more

You can execute the 'baseline' tasks independently using the "baseline" tag. This won't touch any of your Viya components.  Something like this:    ansible-playbook \ -e CONFIG=$HOME/ansible-vars.yaml \ -e TFSTATE=$HOME/viya4-iac-aws/terraform.tfstate \ viya4-deployment --tags "baseline" -vvv https://github.com/sassoftware/viya4-deployment/tree/main/roles/baseline/tasks ... View more

There are two sides to this equation.  The first is the one that you mentioned, that is the Network Security Group that surrounds your AKS Cluster as well as all the other resources. This controls things like client access to your cluster with a kubeconfig or ssh into a bastion/jump server.  The other is the ingress nginix load balancer source range that controls the web traffic into the application. This would be modified on the nginx controller (or in the viya4-deployment https://github.com/sassoftware/viya4-deployment/blob/main/docs/CONFIG-VARS.md#base). To change this in the poral you would go to the AKS cluster and look under 'Services and ingresses' and find ingress-nginx-controller.  An example for what you are looking at can be found here: https://learn.microsoft.com/en-us/azure/aks/load-balancer-standard#restrict-inbound-traffic-to-specific-ip-ranges   Hopefully that helps!  ... View more

The error reported by the application indicates that your subsection is limited by enterprise IT deny assignment rules for: resource 'kubernetes' was disallowed by policy.  It is missing something called a "guardrails tag" and provides an link to an internal service-now exemption form that I am not able to share in a public forum.  ... View more

It appears there is an issue with the availability zone in Azure.  https://learn.microsoft.com/en-us/azure/reliability/availability-zones-service-support Can you try a different Avialability Zone listed in the link above (West US 2 or West US 3) ?   I received this error from your deployment:  {"code":"ApplicationDeploymentFailed","message":"The operation to create application failed. Please check operations of deployment 'viyaappp' under resource group '/subscriptions/***/resourceGroups/mrg-sas-viya-on-azure-20230615112603'. Error message: 'At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.'","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"InvalidTemplateDeployment\",\r\n \"message\": \"The template deployment 'viyaappp-aks' is not valid according to the validation procedure. The tracking id is '4d39c332-ef77-45fa-b551-3f0b4bec3c0c'. See inner errors for details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"AvailabilityZoneNotSupported\",\r\n \"message\": \"Provisioning of resource(s) for container service my-viya-aks in resource group mrg-sas-viya-on-azure-20230615112603 failed. Message: Availability zone is not supported in region westus.. Details: \"\r\n }\r\n ]\r\n }\r\n}"}]} ... View more

FILENAME Statement: Azure Blob Storage (ABS) Access Method Enables you to access data in Microsoft Azure Blob Storage: https://go.documentation.sas.com/doc/en/pgmsascdc/default/lestmtsglobal/p1arsjiowdszd8n1qk8mqg5p2uhv.htm Is that what you are looking for?  ... View more

I have completed several succesfull marketplace deployment in australiaeast over the last few days without issue. I am not able to replicate the error that you are seeing. It might be something specific to your subscription setup. Are you aware of any custom security policies that are present in your Azure subscription?  ... View more

Are you trying to reuse the ARM template on the same managed application or resource group? The ARM template will run into conflicts like the ones show above if you keep trying the deployment in the same resource group. Can you delete the managed application, so the managed resource group is also deleted and try again.  It appears there is some conflict with an existing resource.    How do I delete SAS Viya?https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaaksfaq/n09skbpwwk7m4vn122eufqzw4mgr.htm#n04ku6g8ykp3mkn1n0vykcvnv9vf ... View more

This documentation should help you to answer your questions:  https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaaksfaq/n11i9beot4opr1n17hn455nzkfe8.htm ... View more

I was not able to replicate your issue. I completed a deployment in UAE North yesterday evening without error. Have you tried a new deployment to test if this was an intermittent Azure issue?   ... View more

It appears to be getting hung up on the creation of a runbook resource. This could either be a temporary service availability issue in the region that you are deploying to or a permissions issue on your subscription. Are you able to create an 'Automation Account' with a runbook outside of the Viya deployment?    Quickstart: Create an Automation account using the Azure portal https://learn.microsoft.com/en-us/azure/automation/quickstarts/create-azure-automation-account-portal ... View more

What region are you deploying to?   Azure only supports regions with availability zones for SAS Viya.  Please check the list of regions with availability zone support:  https://learn.microsoft.com/en-us/azure/reliability/availability-zones-service-support#azure-regions-with-availability-zone-support   ... View more