I haven't witnessed anyone using the Local Service account (NT AUTHORITY\LocalService) to run the SQL Server Agent service, and as it isn't supported I wouldn't recommend using it.
It can be used to start and run, each service in SQL Server must have an account configured during installation. Startup accounts used to start and run SQL Server can be built-in system accounts, local user accounts, or domain user accounts.
The Local Service account is a built-in account that has the same level of access to resources and objects as members of the Users group. This limited access helps safeguard the system if individual services or processes are compromised. Services that run
as the Local Service account access network resources as a null session without credentials. Be aware that the Local Service account is not supported for the SQL Server or SQL Server Agent services. The actual name of the account is "NT AUTHORITY\LOCAL
SERVICE".
Best regards,
Leon
I changed the service account for SQL Server Agent service to Local Service and bounced the service, it worked without any issue. Not sure why it worked as same is not supported as per MSDN. I did it on SQL Server 2017.
Just to be sure, local system and network service are also build in account but i could see them under Logins. On one machine SQL Server agent works with local service account but on another machine it just don't work.
I don't think permission is the issue, still is there a way to grant more permission to local service. We may not change the service account for many reasons ?
Appreciate your insight !!
