![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 73%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEP%3C/text%3E%3C/svg%3E)
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,289 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
@Ernesto Perez Welcome to Microsoft Q & A Community Forum. Based on the information provided, I understand that utilizing the ODBC Driver 17 for SQL Server is not able to be used in a standard Azure Automation sandbox due to it not being installed by default in this environment and as a result a Hybrid Runbook Worker would need to be used to achieve this purpose. While not the optimal solution, the advantage of using a Hybrid Runbook Worker on an Azure VM is allowing you to setup the environment on that machine as the sandbox when running jobs will run on that machine rather than through Azure Automation sandboxes in the cloud. For more information on HRW, refer this document.
I also would recommend you navigate here and share your feedback or suggestions directly with the responsible Azure feature team and clicking the vote button of your suggestion to raise visibility and priority on it.