So I have a SQL2012 server where I have used SQL Configuration Manager to disable Named Pipes as usual.
However I noticed in the errorlog shortly afterwards that there were some connection\access (infrastructure) errors, probably from our monitoring software (SCOM) that checks DB health every 15 minutes.
So I gave the relevant account 'connect' on the TSQL Named Pipes endpoint (which it allowed even though it’s disabled)
And after that the login errors disappeared. I can also see these successful logins now using profile trace, as:
Audit login -- network protocol: Named Pipes
However Named pipes is still disabled in SQL Config Mgr so how come I can grant the endpoint, and it allows named pipes connections?