We have an Azure worker role - .NET 4.0 - that runs fine when deployed to Azure on osFamily=\"2\" (Server 2008R2). However, when we deploy with osFamily=\"3\" (Server 2012)
From Azure Support Engineers:
After digging deeper, I found the difference: In OS Family 2, WaWorkerHost is running by a temporary account (with a GUID name) generated by Role initialization process, this account has permission to access certificate private key; In OS Family 3, WaWorkerHost is running by “NETWORK SERVICE” account, this account doesn’t have private key access permission.
I’m contacting production group, we will investigate this issue deeper. I will keep you posted.