Managing SharePoint on-premises is tedious and problematic, and I can't wait to completely abandon on-prem and move to SharePoint Online. But basic Power Pivot support isn't even close as a "Corporate" BI solution. Excel Services & Power View without external data refresh has just been a deal-breaker.
Now we (will sometime fairly soon) have "Power BI for Office 365", but I can't see where it's going to change anything for me. My understanding is that Power BI includes the "Data Management Gateway", which enables Power Pivot models to refresh against on-prem SQL Server relational data sources. But I can't see any reasonable way to employ this architecture to deliver dozens of workbooks (each containing PivotTable, PivotChart, and/or Power View reports built against a central-but-continuously-evolving data model), to dozens of users with varying permissions.
I've pondered some crazy scenarios, but fundamentally, I can't come up with any solution that isn't some ridiculous concoction of hundreds or thousands of Power Pivot workbooks, all of which have to be modified whenever I want to make a change to the model that they all share.
What I want can be summed up like this:
1) build and continuously evolve a model in one place 2) design PivotTable and Power View reports against that model. if i make a breaking change to the model, then i'll have to update a lot of these reports, but only once, not for each user's instance of each report... 3) when users view those reports, they see only the regions, territories, products, etc that they are authorized to see 4) deliver this through SharePoint Online
Am I missing something, or does Power BI get me no closer whatsoever to that utopia?