With the rise of blockchain popularity, more and more people seek to implement blockchain technology into their projects. The most common way is to use an existing blockchain stack, such as the Azure Blockchain Workbench or Oracle Blockchain Platform. While blockchain technology is well protected by its algorithms, it is still vulnerable because its privacy relies on regular cryptography. And mistakes or vulnerabilities in key management protocols can affect even the most secure blockchain projects. This article considers the question of vulnerabilities within the Azure Blockchain Workbench key management system. We describe potential threats for each stage of the key management lifecycle based on public reports and then assess how likely those threats are to be realized within the Azure Blockchain Workbench environment based on the technical documentation for the Azure Blockchain Workbench and Azure Key Vault. Finally, we compile the results of our assessment into the key management threat table with three distinct degrees of protection: fully protected, partially protected, and not protected.