Dextre modules

Dextre for Microsoft Fabric

In development · capabilities below are planned, not yet live

Dextre is AIM's AI software-delivery platform. The Fabric module adds the ability to design, build, test and release Microsoft Fabric solutions in a customer's own tenant, with a named person approving each change before it runs.

How it works

Every Fabric change follows the same six steps

These six steps are the Fabric module's approval flow.

1

Brief

The team describes what they need and picks an approved target workspace.

2

Check

Dextre checks access, capacity and what already exists before planning anything.

3

Plan

Dextre writes the solution and a change plan listing every step it will take.

4

Approve

Person decides

A named reviewer approves that exact plan. Change the plan and the approval no longer counts.

5

Build and test

Only approved steps run. Data is checked before results are published.

6

Hand over

An evidence record, audit trail and handover report go to the customer.

Coverage

Built to work across Fabric, not one corner of it

Any customer, new or existing work

A customer's administrator connects their Fabric once, with no password stored by Dextre. Dextre reads an existing workspace first and reports what it can safely change. Every solution lives in source control, and changes arrive as pull requests for review.

Data engineering

  • Spark notebooks, Spark jobs and environments
  • Lakehouse files and OneLake shortcuts
  • Lakehouse table maintenance

Data integration

  • Data pipelines, dataflows, copy jobs and dbt jobs
  • Connections, gateways and private network links
  • Apache Airflow jobs

Data warehouse

  • Warehouse design and SQL checks
  • Data tests that run and report their real results

Databases

  • SQL database in Fabric
  • Mirrored databases
  • Cosmos DB, Snowflake and Databricks items, and warehouse snapshots

Power BI

  • Semantic models and scheduled refresh
  • Reports and paginated reports, and org apps
  • Checks that report totals match the source data

Real-time intelligence

  • Eventhouse and KQL databases
  • Eventstreams and real-time dashboards
  • Activator alerts, digital twin builder and maps

Data science and AI

  • Machine learning experiments and models
  • Fabric data agents and other AI items

APIs and shared settings

  • GraphQL APIs and user data functions
  • Variable libraries and settings that switch between environments
Control

Why a customer can let it near their data

Nothing changes without approval

A named person approves the exact plan. Approvals expire, and any change to the plan needs a fresh one.

Only approved steps run

The part of Dextre that touches Fabric runs the approved steps and nothing else. Its AI agents never call Fabric directly.

Data checked before it is published

If a data check fails, the last good results stay in place.

A record of every step

Each run produces an evidence record, a tamper-evident audit trail and a handover report.

No stored passwords

The customer grants access once through their administrator, and can withdraw it.

Recovery built in

Failed runs are cleaned up, and changes can be rolled back.

Releases

Three releases, each proven before the next

01

Build any Fabric solution

First release

  • Everything in the coverage section above
  • Works in the customer's development workspace
  • Customers move solutions to Test and Prod through their own release process
Planned
02

Release to Test and Prod

Second release

  • Moves solutions from Dev to Test to Prod
  • A second approver for production, other than the requester
  • A recovery plan for each item before any production change
  • A fresh workspace for each run, cleaned up afterwards
Planned
03

Run and govern

Third release

  • Pauses, resumes and resizes capacity within agreed cost limits
  • Monitoring and alerts for failed jobs
  • Access, labels and data access rules, each under extra approval
  • A read-only report of tenant settings
Planned
Boundaries

What stays with people

Stays manual

Installing an on-premises data gateway, tenant-wide Fabric settings, and a small number of settings Microsoft does not expose for automation.

Not part of the module

Converting code from other platforms such as Synapse or Databricks, and installing Microsoft's packaged industry solutions. Dextre builds the Fabric side of a migration.

Dextre

Questions about this module?