I’m using a Proxy for SSIS executions in SQL Server Agent with a stored credential (domain user, “Mydomain\SSISExecutor”). The proxy works fine in SQL Server Agent, when authenticating to SQL servers, fileshares etc.
I’ve added an Azure File Share credential to the “Mydomain\SSISExecutor”s credential manager using cmdkey, but jobsteps configured to use the SSIS Proxy running packages that tries to access the Azure File Share fails with “The username or password is incorrect”.
Adding the same credential, using cmdkey, to the domain user that is running the SQL Server Agent service, “Mydomain\SQLSrvAgentRunner” – and then executing the job step with SQL Server Agent – the package succeeds in accessing the Azure File Share.
It seems like the Proxy is not reading the credential manager when executing the job step, but the SQL Server Agent does.
How can we set this up so that the Proxy can use the stored credentials in the Credential Manager when executing SQL Agent Job.