Forum Discussion
Analysis Services Connector limitations
Internet latency is also something to consider. You can use Fiddler to identify where the requests are going do, and then evaluate what kind of altency you have with regards to performance. You may not be able to do a whole lot about it, but it may give you some idea if things seem sluggish as it can contribute to that.
A gap in the functionality of the SSAS connector is also that it cannot connect to an HTTP pump end point. This makes is hard to support ISV's who host customer tabular and dimensional data sources on their cloud for u;sers. The way it works now and the way it seems to have been envisioned is to serve IT departments who synch to AD Azure and not for an ISV who supports hundreds of different customers and also use a different type of authentication. Also, it assumes that the security on the cubes are role based, rather than dynamic security based on DAX or MDX filtering. Microsoft needs to allow connections to HTTP SSAS Pump endpoints as Excel or other tools always have - With this approach ISV's or anyone not able to synch with Azure AD to manage the connection as well as mapping to internal identity through an httphandler proxy. Allowing this, rather than thinking that EffectiveUserName will work in lieu of Azure AD synching. We have thousands of users that use Excel to get to tabular models this way now. We would love to able to offer the same capabilities thru Power BI. I have discussed this with some MSFT folks already. I really hope this is being considered as it's a main showstopper for us. A large problem is also that some of these are European customers and they do not want to move their data to 'yet another cloud provider'. MSFT please consider resolving this issue soon. It will open up the capabilities for your ISV's and also get more Power BI subscribers.
thank you,
Luis