Forum Discussion

Sachin Jain's avatar
Sachin Jain
Brass Contributor
Jun 10, 2025

Organisation Linked Data Type not working

I have a feature table published on Power BI Service that was previously accessible in Excel via the linked data type. However, for the past month, this connection has stopped working, and I'm unable to fetch data from the table. It appears the issue is related to authentication. Even the promoted dataset cannot be found or accessed anymore. This functionality was working fine earlier. I suspect this is due to a change in the authentication or security layer, because when I try to connect to a Power BI dataset in Excel using the "From Organization" option for a PivotTable, I am prompted to authenticate with Azure Active Directory every time. This suggests that persistent authentication is no longer being maintained. I believe this same issue is affecting the linked data type feature in Excel. Could you please clarify

  • Has there been a recent change in the authentication model?
  • Is there a workaround or fix to restore access to the linked data types from Power BI in Excel?
  • Is the linked data type feature being deprecated?

II tested on both current channel and beta channel

If it's still working on your tenant, please do let me know or if its broken on your side as well , please update so that I can progress the issue accordingly. 

Thanks

6 Replies

  • SergeiBaklan's avatar
    SergeiBaklan
    Diamond Contributor

    I was too optimistic

    Will stop these games and shift on other solutions

  • SergeiBaklan's avatar
    SergeiBaklan
    Diamond Contributor

    I may confirm that in our case Organization data types are not synced both on Current and Beta channels on Excel Desktop. However, they are still working on Excel for web.

    Bad news is that Organization data types soon will be retired at all Microsoft Excel: Organization data types will retire - M365 Admin

    It's bit more than a month to find another solution. We are shifting on Power Query data types, but that's not suitable for all scenarios and bit slower compare to current solution.

    • Sachin Jain's avatar
      Sachin Jain
      Brass Contributor

      SergeiBaklan​

      As a trainer who has been actively teaching Microsoft Excel since 2006 and Power BI since its early days in 2014, I have witnessed and appreciated the incredible evolution of your products over the years. From the integration of Power Query and dynamic arrays to the introduction of TypeScript and Python in Excel, these innovations have empowered professionals and educators alike to deliver real value and foster digital transformation across industries.

      However, in recent times, I find myself increasingly concerned about the trajectory these tools are taking. Several once-promising features are either being limited due to security constraints or quietly deprecated. The retirement of features, rather than addressing adoption challenges, feels like a missed opportunity to build stronger engagement with a passionate user community.

      Moreover, the current architecture poses significant limitations:

      • Power Query supports GET and POST requests but lacks native support for PUT and PATCH methods.
      • In TypeScript for Excel, standard web functionalities like fetch are disabled.
      • Python integration restricts essential modules, making it difficult to apply even moderately complex logic.

      These constraints compel users to learn multiple technologies, often with limited interoperability, for use within a single software environment—creating friction instead of seamless productivity.

      The increasing fragmentation of the licensing model is also a growing concern. Users now have to navigate and pay for multiple layers: Power BI Pro, Premium, Fabric Capacity, Excel Enterprise, and now Copilot—all of which add up to a significant recurring cost. This layered pricing strategy is creating a perception that Microsoft’s ecosystem is becoming inaccessible to individual professionals, small businesses, and educational institutions.

      Having trained thousands of professionals and witnessed Microsoft’s incredible growth from Excel 2007 to today’s AI-powered versions, it is disheartening to see the community’s enthusiasm wane due to these systemic limitations and escalating costs.

      I share this feedback not out of frustration, but from a place of deep respect and long-standing association. Microsoft has led the way in digital productivity for decades. This is not the right forum but just wanted to share

Resources