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

Thanks @rich_sas ! Confirmed as described: ... View more

@ChrisHemedinger started writing ORC to ADLS for use in Databricks using libname because the write performance using JDBC / ODBC was too slow. This is fast and doesn't require a running Databricks session to access data like JDBC / ODBC does. For SAS Viya on Azure Pay-Go, I discovered that I had to set azureauthcacheloc in the context sas option field to a new path before the azure authentication JSON file would save properly.   Can you advise how I to set cas.AZUREAUTHCACHELOC to use the same authentication file as the one in the option azureauthcacheloc path?  v/r, -Brad ... View more