diff --git a/_posts/private-sector/2019-03-08-microsoft.md b/_posts/private-sector/2019-03-08-microsoft.md
index e405797b..bb58d927 100644
--- a/_posts/private-sector/2019-03-08-microsoft.md
+++ b/_posts/private-sector/2019-03-08-microsoft.md
@@ -16,6 +16,7 @@ last_modified_at: 2019-07-11
 
 ![](https://i.imgur.com/MEN8iSn.png)
 
+6/16 — [Microsoft Building Open Blockchain-Based Identity System With Blockstack, ConsenSys](https://bitcoinmagazine.com/articles/microsoft-building-open-blockchain-based-identity-system-with-blockstack-consensys-1464968713/)
 
 [![](https://imgur.com/l0NEfjrl.png)](https://www.microsoft.com/en-us/security/technology/own-your-identity)
 * [microsoft.com/en-us/security/technology/own-your-identity](https://www.microsoft.com/en-us/security/technology/own-your-identity)
@@ -91,4 +92,4 @@ Standardization continues
   >CredMan unsurprisingly centers on the concept of a Credential.  Actions on Credentials are requested by a relying party using JavaScript and fulfilled by a user agent (generally a browser). Credentials can be created stored, retrieved for validation by a relying party and so on.  In addition to actions, CredMan defines standardized dictionaries that communicate context.  Note that the CredMan API itself does not use the term ‘relying party’ but instead refers to a developer that would write code using the navigator.credentials JavaScript control.  Since we are identity architects, we will assume that developed code is deployed and running as a service at a specific origin and that the developed code will call the CredMan API as part of user registration and authentication activities.   
 
 
- 
\ No newline at end of file
+