Again, this is specific to a SAS Azure Pay-Go managed deployment and I suspect it won't be the same or necessary for other deployments. I ultimately solved this by setting for all SAS Job Execution Computes. You can navigate to the setting through: Top Left Corner Menu of SAS Studio Select ADMINISTRATION > Manage Environment Select Contexts (Looks like a wrench infront of a database) Change your view to Compute Contexts Select SAS Job Execution compute context Edit -> Advanced Write the below line in the options section -azureauthcacheloc "/export/sas-viya/data"
... View more