{"id":82,"date":"2026-06-11T19:14:49","date_gmt":"2026-06-11T18:14:49","guid":{"rendered":"https:\/\/josepineiro.com\/?p=82"},"modified":"2026-06-11T19:14:49","modified_gmt":"2026-06-11T18:14:49","slug":"when-legacy-becomes-a-roadblock-my-growing-frustration-with-power-bi-and-fabric","status":"publish","type":"post","link":"https:\/\/josepineiro.com\/index.php\/2026\/06\/11\/when-legacy-becomes-a-roadblock-my-growing-frustration-with-power-bi-and-fabric\/","title":{"rendered":"When \u201cLegacy\u201d Becomes a Roadblock: My Growing Frustration with Power BI and Fabric"},"content":{"rendered":"<span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time: <\/span> <span class=\"rt-time\"> 3<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>\n<p class=\"wp-block-paragraph\">Microsoft has always been good at pushing its ecosystem forward\u2014but lately, the Power BI and Fabric transition feels less like progress and more like a forced march. As someone who has built solutions on Power BI, I\u2019m used to change. I\u2019m not opposed to new features, new paradigms, or even new licensing models. But what I <em>am<\/em> opposed to is confusion, broken workflows, and a user experience that seems intentionally designed to funnel customers into a paid Fabric capacity whether they need it or not.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And right now, that\u2019s exactly what it feels like.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Disappearing Act: Dataflows Gen1<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s start with the most immediate pain point: <strong>Dataflows Gen1<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the new Power BI UI, Dataflows Gen1 has been buried so deeply it feels like Microsoft doesn\u2019t want you to find it at all. It\u2019s been slapped with a \u201clegacy\u201d label, but here\u2019s the kicker\u2014<strong>there is no viable alternative for customers who don\u2019t have Fabric capacity<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re not paying for Fabric, your choices are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep using Gen1 (if you can find it)<\/li>\n\n\n\n<li>Or\u2026 nothing<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s not a transition plan. That\u2019s a dead end.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And it\u2019s not just an inconvenience. Many organizations\u2014especially smaller teams or those with strict governance\u2014depend on Dataflows Gen1 for ETL pipelines, scheduled refreshes, and shared semantic logic. These aren\u2019t \u201cnice to have\u201d features. They\u2019re foundational.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u201cYou Can See Fabric, But You Can\u2019t Touch It\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Microsoft\u2019s documentation doesn\u2019t help either. In fact, it often makes things worse.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"471\" src=\"https:\/\/josepineiro.com\/wp-content\/uploads\/2026\/06\/dataflows.jpg\" alt=\"Power BI dataflows\" class=\"wp-image-83\" style=\"width:528px;height:auto\" srcset=\"https:\/\/josepineiro.com\/wp-content\/uploads\/2026\/06\/dataflows.jpg 800w, https:\/\/josepineiro.com\/wp-content\/uploads\/2026\/06\/dataflows-300x177.jpg 300w, https:\/\/josepineiro.com\/wp-content\/uploads\/2026\/06\/dataflows-768x452.jpg 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Take this line, which Copilot summarized perfectly:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">\u201cPremium customers with Fabric access\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Sounds straightforward, right? Except it\u2019s not.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What this really means is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your <strong>tenant<\/strong> can enable Fabric<\/li>\n\n\n\n<li>Your <strong>users<\/strong> can see Fabric features and UI<\/li>\n\n\n\n<li>But you <strong>cannot actually use<\/strong> those features unless your workspace is backed by Fabric capacity<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">So you get the illusion of access\u2014buttons, menus, and options everywhere\u2014but the moment you try to do anything meaningful, you hit a wall. It\u2019s like being invited to a showroom where everything is behind glass.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is not clarity. This is marketing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Real Problem: A Transition Without a Bridge<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Microsoft\u2019s own documentation highlights the limitations of Dataflows Gen1 and Gen2, but it also unintentionally exposes the core issue: <strong>there is no smooth migration path for customers who aren\u2019t ready\u2014or able\u2014to adopt Fabric capacity<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Just look at the official limitations page: <a href=\"https:\/\/learn.microsoft.com\/en-us\/power-bi\/transform-model\/dataflows\/dataflows-features-limitations?utm_source=copilot.com\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/learn.microsoft.com\/en-us\/power-bi\/transform-model\/dataflows\/dataflows-features-limitations<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A few standout realities:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Gen1 and Gen2 have <strong>different capabilities<\/strong>, not a clean superset<\/li>\n\n\n\n<li>Gen2 requires Fabric capacity for many features<\/li>\n\n\n\n<li>Some Gen1 features simply don\u2019t exist in Gen2<\/li>\n\n\n\n<li>Certain connectors, transformations, and refresh behaviors differ<\/li>\n\n\n\n<li>Not all workloads migrate cleanly\u2014or at all<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This isn\u2019t a \u201cnew version.\u201d It\u2019s a different product with different rules, different infrastructure, and different licensing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And Microsoft\u2019s answer to all of this seems to be: <strong>\u201cJust buy Fabric.\u201d<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Pressure to Upgrade Is Not Subtle<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s be honest: Microsoft is nudging\u2014no, pushing\u2014users toward Fabric capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How?<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>By hiding Gen1<\/li>\n\n\n\n<li>By labeling it \u201clegacy\u201d without offering a replacement<\/li>\n\n\n\n<li>By surfacing Fabric UI to everyone, even those who can\u2019t use it<\/li>\n\n\n\n<li>By making documentation vague enough to <strong>imply access you don\u2019t actually have<\/strong><\/li>\n\n\n\n<li>By tying core data transformation features to a capacity SKU many organizations don\u2019t need<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This isn\u2019t a natural evolution. It\u2019s a funnel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And it\u2019s frustrating because Power BI has always been a tool that scaled <em>down<\/em> as well as up. It empowered small teams, individual analysts, and organizations without enterprise budgets. Fabric, in its current form, breaks that promise.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Microsoft Needs to Fix<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If Microsoft wants this transition to succeed\u2014and avoid alienating a huge portion of its Power BI user base\u2014it needs to address three things:<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">1. <strong>Clear, honest documentation<\/strong><\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Spell out exactly what users can and cannot do without Fabric capacity. No more ambiguous phrasing.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">2. <strong>A real migration path<\/strong><\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">If Gen1 is \u201clegacy,\u201d then Gen2 must be accessible to everyone\u2014or there must be a supported alternative.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">3. <strong>A UI that reflects actual capabilities<\/strong><\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Don\u2019t show features users can\u2019t use. Don\u2019t bury the ones they rely on.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why This Matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Power BI became a market leader because it was accessible, flexible, and transparent. Fabric has enormous potential\u2014but right now, the rollout feels rushed, confusing, and dismissive of existing customers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I\u2019m not against Fabric. I\u2019m against being forced into it without a plan.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Until Microsoft provides a clear path forward, many of us will be stuck in limbo\u2014trying to maintain \u201clegacy\u201d solutions while staring at shiny new features we can\u2019t touch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And that\u2019s not innovation. That\u2019s friction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p><span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time: <\/span> <span class=\"rt-time\"> 3<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>Microsoft has always been good at pushing its ecosystem forward\u2014but lately, the Power BI and Fabric transition feels less like progress and more like a forced march. As someone who has built solutions on Power BI, I\u2019m used to change. I\u2019m not opposed to new features, new paradigms, or even new licensing models. But what &#8230; <a title=\"When \u201cLegacy\u201d Becomes a Roadblock: My Growing Frustration with Power BI and Fabric\" class=\"read-more\" href=\"https:\/\/josepineiro.com\/index.php\/2026\/06\/11\/when-legacy-becomes-a-roadblock-my-growing-frustration-with-power-bi-and-fabric\/\" aria-label=\"Read more about When \u201cLegacy\u201d Becomes a Roadblock: My Growing Frustration with Power BI and Fabric\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":86,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[21,20,22],"class_list":["post-82","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-fabric","tag-microsoft","tag-powerbi"],"_links":{"self":[{"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/posts\/82","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/comments?post=82"}],"version-history":[{"count":3,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/posts\/82\/revisions"}],"predecessor-version":[{"id":87,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/posts\/82\/revisions\/87"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/media\/86"}],"wp:attachment":[{"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/media?parent=82"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/categories?post=82"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/josepineiro.com\/index.php\/wp-json\/wp\/v2\/tags?post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}