From the webjobs there are no issues the Powershell implementation runs correctly. But the same implementation when moved to Azure functions throws issue like 'SQLCMD.EXE is not recognized as an internal command". But I can see SQLCMD.exe is available azure functions host instance via Kudu and the same is available as a Path variable in the Instance. But still this is throwing issue.I am not sure this is the issue with Azure functions or Poweshell. Would like to have a idea on this.
sqlcmd.exe has nothing to do with this library or PowerShell. That is a CLI utility found with SQL Server tools and also would not exists in Azure Functions setup.
From the webjobs there are no issues the Powershell implementation runs correctly. But the same implementation when moved to Azure functions throws issue like 'SQLCMD.EXE is not recognized as an internal command". But I can see SQLCMD.exe is available azure functions host instance via Kudu and the same is available as a Path variable in the Instance. But still this is throwing issue.I am not sure this is the issue with Azure functions or Poweshell. Would like to have a idea on this.