Closed MPenny-nCipher closed 5 years ago
@MPenny-nCipher Thank you for your feedback . We will review and get this updated.
@MPenny-nCipher As per the referenced pull requests above, I have updated most of the references that I can find and where I had access to update however , there may still be some which i might have missed. Please wait for 24-48 hours for the changes to show up as per next release cycle. If you still find references to Thales , please continue to report them on the page itself as document feedback as there are different teams and multiple repositories and no single team has access to them all . Hence I request you to continue to report them.
We will close this issue now. The changes should be visible on the main page in the next 24 hours or 48 hours maximum. Should you still have any query on this , feel free to tag me or @barclayn to your reply and we will happily help you . alternatively you can always open a new issue with us. Thank you.
Hello
References on this page ought to be changed from 'Thales' to 'nCipher' as the nShield product line that the article refers to for HSMs is now owned by nCipher Security.
This comment applies to any other pages where 'Thales HSMs' are referenced in the context of Azure Key Vault. These are now nCipher HSMs.
Thanks.
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.