The issue has been resolved. There were 2 issues that needed to be addressed to resolve this problem. First, when deploying to the IIS web server, the certificate being used was a machine cert not a user cert so in the appsettings.json "CertificateStorePath": "CurrentUser/My" needed to be replaced with "CertificateStorePath": "LocalMachine/My". The second was the account running the IIS application pool for the site needs to be granted access to the certificate used through the management console.