Certification evidence
Current public-package, Azure Databricks, browser data-path, and promotion evidence—with target boundaries and observation status.
This page separates three claims that are easy to confuse:
- Shipped means the capability exists in a published artifact and has automated coverage.
- Live-gated means Fabric has executed it against the named infrastructure and retained structured evidence.
- Certified for promotion means the complete scheduled observation window has passed without a failure.
The exact capability status is maintained in the compatibility matrix. This page records the current operational evidence behind it.
Publicly reproducible evidence
| Evidence | Current result | How to reproduce |
|---|---|---|
| Published package installation | Passed with @fabricorg/databricks-testkit@0.3.0, @fabricorg/databricks-bdd@0.5.0, and @fabricorg/experiments@0.8.0 | Install the packages in a clean TypeScript project and run fx targets list; the release workflow also installs and executes the published CLI from an empty project. |
| External consumer CI | Passed on July 16, 2026 | View the public workflow run. |
| Documentation | Published for release v0.11.0 on July 16, 2026 | Open this page, the BDD quickstart, and the Quality Center guide; all are served from Cloudflare. |
The consumer repository is deliberately separate from the product monorepo. It detects unpublished workspace dependencies, missing exports, peer-dependency errors, and tarballs that behave differently from source builds.
Fabric-operated live evidence
The summary below gives evaluators the target and boundary without presenting private CI artifacts as customer-accessible links.
| Gate | Last verified | Result and scope |
|---|---|---|
| Azure serverless required suite | July 15, 2026 | Passed SQL, Delta, Unity Catalog, Lakeflow, Volume, Lakebase, Databricks App, notebook, dbt, performance, failure-recovery, rotation, backup/restore, and rollback checks using a restricted workload identity. |
| Azure classic compute | July 15, 2026 | Passed a disposable single-node, single-user notebook probe on DBR 16.4.x-scala2.12 with Standard_D2ds_v6; cleanup passed. |
| Browser-to-Studio path | July 15, 2026 | Passed browser emission → Cloudflare Queue/R2 → Auto Loader/Delta → aggregate API → authenticated Studio, including Bayesian, CUPED, time/depth, and segmented result assertions. |
| Clean-checkout Cloudflare staging deployment | July 15, 2026 | API, Studio, and edge workers built and deployed from a clean checkout. |
| Tenant-scoped Quality Center publishing | July 16, 2026 | Passed BDD, Databricks live-suite, and generic CLI evidence publication using Databricks OAuth at the App gateway plus an organization-bound, expiring Fabric API key. The verification key was revoked afterward. |
| Lakeflow Jobs target pack | July 16, 2026 | Passed a basic Azure serverless two-task notebook dependency run and produced JSON and JUnit target-pack evidence. Conditions, loops, retries, cancellation, and repair remain outside the certified scope. |
Evidence artifacts include JSON, JUnit XML, BDD HTML, rerun manifests, captured failure attachments, resource identifiers, durations, and cleanup results. Secrets are redacted before evidence is written.
Observation window
The full staging path is currently certifying: 1/7 consecutive scheduled nights. Manual green runs prove the path works but do not increment the consecutive-night counter. Production promotion remains blocked until seven scheduled runs pass in sequence; a scheduled failure resets the counter.
This distinction prevents a one-time successful demo from being presented as operational maturity.
Certified targets
| Cloud and compute | Status |
|---|---|
| Azure Databricks serverless SQL and managed workloads | Live-gated |
Azure classic job cluster: DBR 16.4 LTS, single-node Standard_D2ds_v6, single-user | Live-gated |
| AWS Databricks | Not a certified target |
| Google Cloud Databricks | Not a certified target |
Similar REST APIs do not establish cloud portability. AWS or Google Cloud moves to certified only after identity, storage, node types, networking and the complete live suite have evidence on that target.
What evaluators should verify themselves
Fabric's evidence establishes the release baseline. Before production adoption, run these checks in your own workspace:
- Complete the local and live quickstart.
- Add one representative Job, pipeline, notebook or dbt scenario.
- Prove an allowed and denied Unity Catalog access path.
- Retain JUnit, HTML and JSON evidence in your CI system.
- Run the required checks repeatedly under expected workload contention.
- Exercise backup/restore and rollback on disposable objects.
Use the advanced playbook to design those gates and the live-check reference for configuration.