What carries over
The parts of Tend that decide what to change are warehouse agnostic: demand forecasting from workload history, the policy engine that turns a forecast into a capacity ceiling, and the business constraints and approval rules you set. Those do not assume BigQuery. For how they work today, see the technology overview.
What does not
The parts that decide how to apply a change do assume BigQuery. Azure Synapse and Microsoft Fabric price capacity differently, expose different telemetry, and need their own execution adapter, their own guardrails, and their own rollback path. That is the work, and it is not started.
What support would cover
Fabric capacity unit sizing against forecast demand, pause and resume scheduling for Synapse dedicated pools, and query-level cost attribution. Nothing here is committed. Treat it as direction, not as a plan with a date.
If you run Microsoft Fabric or Azure Synapse
Tell the team. Design-partner demand is what decides which warehouse comes after BigQuery, and Microsoft Fabric and Databricks are both unstarted. For current status, see the roadmap.