Brazil is not currently an available market as a result of the Tax details for commercial marketplace publishers.  There have been some recent changes in how SAS and Microsoft handle Brazil from a tax perspective.  I will review these changes with the SAS Finance team and report back with what I find.  ... View more

To grant access to an Azure group or user to start and stop SAS Viya using the "...automation/StartStopViya" runbook, you can use Azure Role-Based Access Control (Azure RBAC). In Azure Automation, access is granted by assigning the appropriate Azure role to users, groups, and applications at the Automation account scope. You can grant role-based access to users using the Azure portal, Azure Command-Line tools, or Azure Management APIs. For more detailed information, you can refer to the Manage role permissions and security in Azure Automation guide. The following section shows you how to configure Azure RBAC on your Automation account through the Azure portal and PowerShell: Configure Azure RBAC for your Automation account  ... View more

We’ve reviewed the security vulnerabilities highlighted by Microsoft Defender. While we plan to address several issues, we may not resolve all, especially those involving additional Azure services that increase costs. An independent third party has verified our security and conducted a thorough vulnerabilities scan. We appreciate your understanding as we balance security with cost-effectiveness. ... View more

We understand the frustration of redeploying SAS Viya on Azure Marketplace to access new features. We're actively exploring an update mechanism for the Marketplace in collaboration with Microsoft. While I can't share a specific timeline at this moment, your feedback is highly valuable and helps us prioritize these improvements.   ... View more

Thank you for providing an update. I am glad that you were able to resolve the private link issue.  I will take a look at the ODBC connection configuration.  ... View more

Thank you for bringing the Azure security recommendations to our attention. We are conducting a review of the recommendations to ensure that the high severity vulnerabilities are addresses first. I will provide an update when that review is complete. Note that some of the medium and low alerts may trigger additional infrastructure costs for additional Microsoft security products or services.  ... View more

Thank you for bringing the issue with the private link connection to our attention. We understand the importance of seamless integration with third-party databases, such as Denodo, especially when they are hosted on different subscriptions. We are conducting a review of the managed node group’s configuration to ensure that the necessary permissions are in place for creating private endpoints within the SAS Viya Resource group. I will provide an update when that review is complete.  ... View more

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