Microsoft Fabric consulting
Fabric is a capable platform and a fast moving one. The value of independent advice is knowing which parts are ready for your workload, which are not yet, and what that means for the estate you already run.
Aurora Data works with organisations adopting Microsoft Fabric, whether that is a first workspace, a migration from an existing SQL Server or Synapse estate, or a review of a design already in flight. The work is architectural: capacity and workspace structure, lakehouse layering, ingestion patterns, semantic modelling, and the tenant settings that quietly decide who can do what.
Engagements are led personally by the principal architect, so the person advising your executive is the person reviewing your architecture. The intent is always a platform your own team can operate once the engagement ends.
What the work covers
-
Capacity, workspace and domain design
How capacity is sized, split and charged back, and the workspace structure that keeps teams out of each other’s way.
-
Lakehouse and warehouse layering
Layered design in practice, and the decision about which engine serves which workload rather than defaulting to one.
-
Migration from SQL Server, Synapse and legacy estates
Sequencing a move that keeps existing reporting alive while the new platform is stood up beside it.
-
Semantic modelling and Power BI
Model design that holds up under real concurrency rather than in a demo, including where Direct Lake fits.
-
Governance and tenant settings
Sensitivity, lineage, deployment pipelines and the settings most tenants leave at their defaults.
How an engagement runs
-
Architecture review
A focused engagement producing a written assessment of the current design, the risks in it, and what to do first.
-
Target state and roadmap
Target-state architecture, platform decisions and a sequence your team can fund, staff and defend internally.
-
Design authority through delivery
Hands-on architectural direction alongside your team as the build lands, including review of the work in flight.
Questions people ask
Do you advise, or implement?
Both. Most engagements begin with architecture and continue as design authority alongside the team doing the build, because a design nobody stays close to tends to drift during delivery.
Is Fabric the right choice over Databricks or Synapse?
That depends on your workloads, your licensing position and the skills already in your team. Aurora Data works across Microsoft Fabric, Azure Data Services and Azure Databricks, and the point of an independent architect is a recommendation that is not tied to selling one of them.
Do you work outside Brisbane?
Yes. The practice is based in Brisbane and works with organisations across Australia.
Talk it through
Engagements start with a conversation about what you have and what is actually in the way. If that sounds useful, send an email and describe the situation in a paragraph or two.
Background on the practice is on the home page, and on the architect leading it on the profile page.