Microsoft has not retired Azure Synapse dedicated SQL pools, but it points every new warehouse at Fabric and ships a migration assistant for Synapse. When moving to Fabric makes sense, when staying is fine, and when a company whose applications are on AWS should move the warehouse there instead.
Microsoft's guidance is that new warehouses should start on Fabric Data Warehouse, and existing Synapse dedicated SQL pool workloads can upgrade to Fabric for its newer capabilities. There is a Fabric Migration Assistant for Data Warehouse that converts dedicated pool artifacts. Dedicated SQL pools themselves are not being retired; some surrounding pieces have been, such as the Synapse Data Explorer preview in October 2025.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Redshift for the warehouse, or Iceberg tables in S3 queried by Athena and Redshift if you want an open format.
Zero-ETL from Aurora, RDS and DynamoDB removes the pipelines that copied application data into the warehouse.
Power BI can stay. It connects to Redshift and Athena, so BI can move later or never.
Move pipelines last. Rebuild them against the new warehouse rather than translating Data Factory pipelines one to one.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Power BI Premium P SKUs Are Retiring: Moving to Fabric F SKUs Without Losing Access or Overpaying
Each Power BI Premium capacity subscription retires at the end of its current agreement, and there is no automatic migration. P1 maps to F64, but F SKUs bill through Azure, can pause, and only F64 and above let free users view reports. The mapping, the 30/90-day cliff, the cost math and the right-sizing most teams skip.
Read
Leaving AWS Amplify and AppSync: When It Is Time, and How to Do It Without a Rewrite
Amplify gets a startup to launch fast. The trouble starts later: list queries that scan, resolvers that can't throw or call out, a 30-second ceiling, and a data model that was never designed. The signs it is time to leave, what to move to, what to keep, and a cutover that doesn't log anyone out.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.