Azure Trusted Research Environment

Open-source reference platform for isolated research workspaces and controlled data movement.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Terraform

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Setup Instructions ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodTerraform
InfrastructureServers / containers
Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseMIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

Azure TRE uses Microsoft Entra ID for TRE/workspace users and administrators, with separate application registrations and app-role permissions. The setup guide distinguishes tenant administration from Azure subscription administration and notes that group assignment may need premium Entra licensing.

TRE UI/API and workspace identities; not evidence that every application launched inside a workspace inherits the same SSO · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The repository supplies Terraform for core Azure resources and workspace/service templates, orchestrated by the documented deployment workflow. Register resource providers, configure identities and secrets, select a release and deploy the core before optional workspaces/services; replace the initial self-signed certificate.

Azure TRE core and separately deployed workspace templates · Source ↗ · Deployment artifact ↗ (v0.29.1) · Deployment repository setup ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The v0.29.1 core Terraform defaults include a P1v3 App Service plan and Standard_B2s resource-processor VM scale-set SKU. The core also provisions network/security and managed-service components; research workspaces and their VMs/services are additional. These defaults do not size a whole research workload or establish its cost.

Versioned Azure core defaults, not an AWS design, total resource count or HA/1-TB capacity minimum · Source ↗ · Core resource composition ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Azure Trusted Research Environment; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

Community & maintenance

The reviewed upstream contributor history includes tamirkamara, marrobi, stuartleeks, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Internal tools
Open-source reference platform for isolated research workspaces and controlled data movement.
Data & analytics
Open-source reference platform for isolated research workspaces and controlled data movement.

Compare within Internal tools

  • Appsmith Self-HostedBuild internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Budibase Self-HostedBuild operational apps and automations on customer-hosted infrastructure.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • CortezaLow-code platform for business records, workflows and configurable CRM applications.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • Mendix on KubernetesCommercial low-code application runtime operated in customer Kubernetes infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • STACKIT
    Customer-operated · vendor control plane · Commercial Only
  • NocoDB Self-HostedSpreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Railway
    Customer-operated · Source Available

Showing 8 of 10 other listings in Internal tools. These products address related workflows; read their category-fit notes before comparing scope. See all of Internal tools →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Setup Instructions ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory