Identity and Privacy
Microsoft Azure Confidential Clean Rooms: status, features and alternatives
Published · Last updated
Next review:
Microsoft's data clean room is called Azure Confidential Clean Rooms, not "Azure Data Clean Room". Its multiparty analytics service runs Spark SQL inside hardware enclaves. It is in limited preview, and Microsoft says the preview must not process personal data or be used in production (Microsoft Learn, page dated 22 May 2026).
Contents
At a glance
Company
Microsoft Corporation (NASDAQ: MSFT)
Headquarters
Redmond, Washington, US (SEC EDGAR, accessed 9 November 2026)
Founded
Preview; first availability date n/d. Microsoft Learn page dated 22 May 2026, updated 17 June 2026
Ownership
Public company product (Microsoft Corporation)
Product category
Confidential-computing data clean room
What it does
Runs approved Spark SQL queries over several parties' datasets inside attested enclaves, with governance and audit on a confidential ledger
Deployment model
Fully managed Azure service; limited preview by application form (Microsoft Learn)
Pricing model
n/d (preview; no price published)
Key integrations
Azure Kubernetes Service, Confidential Azure Container Instances, Microsoft Azure Attestation; Azure CLI and REST API samples
Publicly named customers
None named by Microsoft
Standards supported
Confidential Consortium Framework (open source); container images and sidecars open source under the MIT licence (GitHub, Azure/azure-cleanroom)
Last verified
9 November 2026
| Field | Azure Confidential Clean Rooms |
|---|---|
Company | Microsoft Corporation (NASDAQ: MSFT) |
Headquarters | Redmond, Washington, US (SEC EDGAR, accessed 9 November 2026) |
Founded | Preview; first availability date n/d. Microsoft Learn page dated 22 May 2026, updated 17 June 2026 |
Ownership | Public company product (Microsoft Corporation) |
Product category | Confidential-computing data clean room |
What it does | Runs approved Spark SQL queries over several parties' datasets inside attested enclaves, with governance and audit on a confidential ledger |
Deployment model | Fully managed Azure service; limited preview by application form (Microsoft Learn) |
Pricing model | n/d (preview; no price published) |
Key integrations | Azure Kubernetes Service, Confidential Azure Container Instances, Microsoft Azure Attestation; Azure CLI and REST API samples |
Publicly named customers | None named by Microsoft |
Standards supported | Confidential Consortium Framework (open source); container images and sidecars open source under the MIT licence (GitHub, Azure/azure-cleanroom) |
Last verified | 9 November 2026 |
Status on 9 November 2026: limited preview. Microsoft states: "Customers should not use the preview to process personal data or other data that is subject to legal or regulatory compliance requirements" (Microsoft Learn). For live advertising data about people, it is not an option yet.
What it does
Azure Confidential Clean Rooms gives several organisations a shared, protected place to analyse their combined data. The service hides each party's raw data from the other parties and from Microsoft as the Azure operator (Microsoft Learn). Microsoft lists advertising among its target scenarios. Examples include matching an advertiser's CRM data with publisher data for targeting, and sharing audience data with measurement partners for attribution.
Microsoft also aims it at regulated sectors. Its list includes banks and insurers selling to each other's customers, banks working with retailers on offers, government departments, and hospitals studying patient outcomes. All of those use personal data, which the preview terms forbid today. The scenarios describe where the product is going, not what customers can do now.
Only Spark SQL analytics is in the preview. Teams that need machine learning training, fine-tuning or inference are asked to apply through the same form.
How it works
The engine is Apache Spark SQL, run in a confidential version. The Spark driver and executors are "fully attested policy-governed enclaves". They run as virtual nodes on Confidential Azure Container Instances inside an Azure Kubernetes Service cluster (Microsoft Learn).
Governance runs on the Confidential Consortium Framework, an open-source ledger technology. It manages who belongs to a clean room, checks that the right parties approved each query and consented to data access, and keeps a tamper-resistant audit trail.
The privacy controls are explicit:
5 of 5 rows
allowedFields | Each dataset lists the only columns that queries may see |
Pre-conditions | A query declares a minimum row count per input view; below it, the query is rejected |
Post-filters | A query declares a minimum count per output group; smaller groups are dropped |
Approval | Every collaborator whose data a query touches must approve it |
Remote attestation | Each participant can verify that known code runs on genuine confidential hardware |
allowedFields
- What it does
Each dataset lists the only columns that queries may see
Pre-conditions
- What it does
A query declares a minimum row count per input view; below it, the query is rejected
Post-filters
- What it does
A query declares a minimum count per output group; smaller groups are dropped
Approval
- What it does
Every collaborator whose data a query touches must approve it
Remote attestation
- What it does
Each participant can verify that known code runs on genuine confidential hardware
Table by AdSovereign, CC BY 4.0.
The query author sets the minimums, and the other parties review them before approving. Microsoft publishes its clean room container images and sidecars, with source code in the Azure/azure-cleanroom repository (GitHub). Their provenance can be checked through GitHub artifact attestation.
Pricing
Microsoft publishes no price for Azure Confidential Clean Rooms. The service is in a limited preview governed by the Supplemental Terms of Use for Microsoft Azure Previews, and access depends on an accepted application (Microsoft Learn). Pricing is therefore n/d until general availability.
Strengths and limits
Strengths
- Operator excluded. Enclaves and attestation keep Microsoft itself out of the data path, which is a stronger promise than access policy alone.
- Clear output rules. Column allow-lists and minimum counts before and after the query are written into the query definition, where all parties can review them.
- Open code. Container images and sidecars are open source, so a security team can inspect what runs.
- Multi-party from the start. Several data providers can share one clean room.
Limits
- Not production-ready. The preview is "intended for testing, evaluation, and feedback".
- No personal data allowed. That rules out most advertising use until GA.
- Spark SQL only. ML training and inference are not part of the preview.
- Gated access. Microsoft "might not be able to accept all requests".
Alternatives
- Decentriq: a confidential-computing clean room already in production, run from Switzerland.
- LiveRamp Clean Room: offers confidential computing rooms that run on Azure Confidential Compute (LiveRamp docs).
- Databricks Clean Rooms: generally available on Azure, with code approval instead of enclaves.
- AWS Clean Rooms: the generally available hyperscaler option with published prices.
For how the GA platforms compare on pricing and ML, see AWS Clean Rooms vs Snowflake vs LiveRamp. Enclave rooms are set against every other model in data clean room architectures compared. For hosting and jurisdiction choices on Azure and its rivals, read sovereign cloud providers compared and the identity and privacy hub.
What we could not verify
- When the preview first opened. The documentation we read gives page dates, not a launch date.
- Any date for general availability, any price, or any named customer.
- The Azure regions where the preview runs.
- Whether "Azure Data Clean Room" was ever an official Microsoft product name. We found no such product; the backlog title appears to be informal.
FAQ
What is Microsoft's data clean room called?
How much does Azure Confidential Clean Rooms cost?
Can I use Azure Confidential Clean Rooms with customer data?
Sources
- Microsoft Learn, "Perform protected multiparty data collaboration on Azure" (Azure Confidential Clean Rooms; page dated 22 May 2026, updated 17 June 2026; accessed 9 November 2026). https://learn.microsoft.com/en-us/azure/confidential-computing/confidential-clean-rooms
- GitHub, "Azure/azure-cleanroom" repository (MIT licence; accessed 9 November 2026). https://github.com/Azure/azure-cleanroom
- LiveRamp documentation, "Configure Clean Rooms: Clean Room Types" (accessed 9 November 2026). https://docs.liveramp.com/clean-room/en/configure-clean-rooms.html
- US Securities and Exchange Commission, EDGAR submissions record for Microsoft Corporation (accessed 9 November 2026). https://data.sec.gov/submissions/CIK0000789019.json
Changelog
- 9 November 2026: profile published. Name corrected from the working title "Azure Data Clean Room" to the official "Azure Confidential Clean Rooms".
Spotted an error? Tell us