Power BI tenant limitation - 10 change detection measures

What is the strangest technical limitation you have ever encountered in Power Platform? This is a question I was recently asking myself as through the last few years, I definitely encountered some quirks. My personal favorites are definitely related to #SharePoint and #PowerBI. Here's one of them: 👉 There can only be a maximum of 10 models with change detection measures in a Power BI tenant. 👈 IT IS PER TENANT. WHY? I can't comprehend why it's enforced like that, especially from the perspective that top SKU of F capacity can cost hundreds of thousands of dollars per month. In this case, cost shouldn't be a driving factor, so there is definitely a better solution for that, but it was never addressed by Microsoft. Assume you have a 100k-person organization and want to develop a handful of reports in Power BI. You really want to implement this feature on one of the most business-critical dashboards and you learn that random developers in your organization crossed the threshold of 10 reports with automated change detection. It will be really hard to track and remove them. The larger your organization is, the more impossible it will be to implement proper change detection for reports based on Direct Query. What are you stuck with then? Using automatic intervals will be a solution here, but it will have a way bigger impact on your database, report performance, and overall UX. Sometimes I even wonder if it's not better to implement small change detection based on Power Apps visual and then use PowerBIIntegration.Refresh() to force data to reload whenever needed. 👇 Link to documentation source in the comments 👇 ___ 👉 Automatic page refresh limitations - Microsoft Learn documentation: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-automatic-page-refresh#considerations-and-limitations