Microsoft took a significant step in its blockchain-as-a-service strategy on September 25, 2016, with the release of Project Bletchley 1.0 — an Ethereum-based framework designed to let enterprises deploy consortium blockchain networks in minutes rather than weeks. The announcement marked one of the most ambitious corporate blockchain initiatives of the year.
TL;DR
- Microsoft released Project Bletchley 1.0, its Ethereum-based consortium blockchain technology on Azure
- The platform reduces multi-node consortium Ethereum network deployment from three weeks to 5-8 minutes
- Bletchley uses a template of just 8 questions to configure globally distributed blockchain infrastructure
- Microsoft planned integration with Azure Active Directory, Key Vault, and additional blockchain protocols
- The move came as major tech companies including IBM raced to establish blockchain-as-a-service offerings
From Three Weeks to Five Minutes
According to Marley Gray, principal program manager at Microsoft Azure Blockchain Engineering, Project Bletchley 1.0 represented a dramatic simplification of what had been an arduous process for enterprises. Setting up a globally distributed multi-node consortium Ethereum network previously took an estimated three weeks of intensive configuration work. Bletchley compressed that timeline into a streamlined process requiring answers to just eight questions and between five and eight minutes of automated deployment time.
“Not only does Bletchley v1 automate the setup of the network infrastructure but it sets up a portal for rapidly getting started developing applications on Ethereum,” Gray explained in a blog post announcing the release.
Consortium Blockchains Explained
At the heart of Project Bletchley was the concept of consortium blockchains — a hybrid approach that sits between fully public networks like Bitcoin and completely private ledgers. According to the Ethereum Foundation’s taxonomy, consortium blockchains feature consensus processes controlled by a pre-selected set of nodes. Microsoft offered an illustrative example: imagine a consortium of 15 financial institutions, each running a node, where 10 must sign every block for it to be valid.
These consortium networks could be configured in several ways — as public networks accessible to everyone, restricted networks with controlled access, or partially decentralized architectures tailored to specific use cases. This flexibility made them particularly attractive for industries like finance, supply chain management, and healthcare, where participants needed the benefits of blockchain without the openness of public networks.
Azure Integration Strategy
Christine Avanessians, senior program manager at Microsoft Azure, outlined the company’s philosophy of releasing early and often to gather developer feedback. The roadmap included deep integration with Microsoft’s existing cloud services, including Azure Active Directory for identity management and Azure Key Vault for cryptographic key management.
“We are releasing early and releasing often to provide you with the latest updates quickly and to get your feedback throughout the development of the service,” Avanessians said. “Keep an eye out for further updates including support for additional Microsoft services and other blockchain protocols.”
The integration with Azure’s broader ecosystem was a key differentiator. Enterprises already using Azure for cloud computing could add blockchain capabilities without leaving the platform or managing separate infrastructure, a compelling proposition for the large enterprise customers that formed Microsoft’s core business.
The Corporate Blockchain Race Heats Up
Microsoft’s announcement didn’t happen in a vacuum. The summer of 2016 saw a wave of major technology companies making significant blockchain bets. IBM had launched its own secure, cloud-based blockchain service using LinuxONE systems with firmware-level protection that prevented even root users and system administrators from accessing protected data. In August 2016, IBM followed up by creating an Industry Platforms business unit specifically to oversee its blockchain initiatives.
IBM CEO Ginni Rometty described the vision: “The Industry Platforms business will bring clients radically optimized processes and marketplaces that leverage Watson, IBM Cloud, IBM Systems, blockchain, deep domain expertise and ecosystems of partners and developers.” The inclusion of Watson, IBM’s artificial intelligence platform, alongside blockchain signaled the company’s belief that these technologies would converge in enterprise applications.
Microsoft had first unveiled Project Bletchley in June 2016, positioning it as middleware that would enhance its blockchain-as-a-service offering on Azure. The September release of version 1.0 demonstrated that the company was moving quickly from concept to production-ready tooling.
Why Ethereum as the Foundation
Microsoft’s choice of Ethereum as the underlying blockchain platform was telling. While Bitcoin’s blockchain was primarily designed for cryptocurrency transactions, Ethereum’s Turing-complete smart contract capabilities made it far more suitable for the complex business logic that enterprise applications required. With ETH trading at $13.10 and the broader crypto market capitalization hovering around $11.5 billion according to CoinMarketCap data from the same day, the technology was still in its earliest stages — yet Microsoft saw enough potential to invest significant engineering resources.
The decision to build on Ethereum rather than creating a proprietary blockchain also reflected a broader industry trend toward open-source collaboration. By leveraging Ethereum’s existing developer ecosystem and tooling, Microsoft could offer enterprises a familiar development environment while focusing its own efforts on the infrastructure and integration layers where Azure excelled.
Why This Matters
Project Bletchley was one of the earliest signals that enterprise blockchain adoption would be driven by cloud providers rather than grassroots crypto communities. Microsoft’s bet on Ethereum as an enterprise platform proved remarkably forward-looking — today, enterprise Ethereum solutions process billions of dollars in transactions across supply chains, financial services, and healthcare. The consortium blockchain model that Bletchley championed became the blueprint for countless private and permissioned network deployments, and the integration of blockchain with cloud services like identity management and key storage has become standard practice. In September 2016, it was ambitious; today, it reads as a roadmap that the industry largely followed.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Past performance is not indicative of future results.
bletchley 1.0 on azure changing how fast teams spin up chains
Microsoft dropped blockchain from Azure entirely by 2019. Project Bletchley was a 2 year experiment that proved enterprises dont actually need consortium chains
eight questions template was simple but ibm and microsoft both raced and dropped it later
5 to 8 minutes to deploy a consortium network in 2016 was genuinely impressive. most blockchain deployments today still take longer than that
azure dropping deploy time from 3 weeks to 5-8 minutes on ethereum consortium is huge
the irony is Microsoft built this on Ethereum and then quietly dropped blockchain from Azure entirely. enterprise blockchain became a solution looking for a problem
enterprise blockchain in 2016 was all hype because nobody had a real use case beyond supply chain pilots that never launched
8 questions to deploy a consortium network. that UX was ahead of its time, shame it went nowhere
66948 8 questions to deploy was ahead of its time. terraform modules for k8s clusters still take longer than that to configure
8 question template sounds too simple but maybe thats the point
azure_vet it was ahead of its time but the real problem was no enterprise actually wanted to run a consortium chain. they wanted to say they used blockchain, not actually use it
8 questions to deploy a network in 2016 was wild. most devops teams still cant do that now without a 3 week sprint
114823 the real problem was no enterprise wanted to run a consortium chain AND maintain it. deployment is 5 min, ops and governance is forever
3 week sprint is generous. most enterprise blockchain projects died in the requirements gathering phase
five to eight minute deploy beat the three week sprint most projects died on
IBM and microsoft racing for blockchain-as-a-service in 2016. neither won. the space just moved differently
ibm went all-in on hyperledger while microsoft bet on ethereum. neither got the adoption they predicted
hyperledger fabric is still around actually. most enterprise CBDC pilots run on permissioned variants of it. microsoft just gave up before the market materialized
i’ve seen too many projects like this fail, but this one feels different