Using Classic Outlook on Windows for personal email, calendar, and contact management
I can confirm that Outlook does not allow SHA-256 or AES when using a custom CSP.
I changed my certificate in my Certificate Authority to allow Any Cryptographic provider to be used with the certificate. This together with my Registry entries - in previous post in this thread - allowed me to sign an email with SHA-256 and SHA-512 and use AES encryption.
However, at the recipient the email is only signed with SHA-1 and encrypted with 3DES.
Doing research I found these articles:
and
https://technet.microsoft.com/en-us/library/cc725838(v=ws.11).aspx
which states that
Version 3 certificate templates are new in Windows Server 2008. Version 3 certificate templates function similarly to version 2 templates, and they support new Active Directory Certificate Services (AD CS) features available in Windows Server 2008. These features include Cryptography Next Generation (CNG), which introduces support for Suite B cryptographic algorithms such as elliptic curve cryptography (ECC).
Version 3 Certificate Authority templates uses the Key Storage Provider and not the CSP. The suite B cryptographic algorithms also include SHA2 and AES, meaning that you have to change to a custom KSP in order to get support for SHA-256 and AES in Outlook.