Hi Justin .We’re definitely planning to allow this soon! Stay tuned and you should see it appear in the coming weeks!
to remove the connection name from the list, uninstall the appropriate Connector. This will remove the entry from the list in the Get Data page of Power BI.
To answer your first question, we are looking at ways to change the server name when the server is moved to a different machine. I do not yet have a timeline to share, but we'll get to it soon.
We already support connecting to Azure SQL database, Table, Blob from Excel/Power Query.
You can then upload this workbook to Power BI & do analysis on this data.
Read more here - http://support.powerbi.com/knowledgebase/articles/424871-excel-data-in-power-bi
You can schedule periodic refreshes on this dataset. Read more here - http://support.powerbi.com/knowledgebase/articles/474669-refresh-data-in-power-bi
Hope this helps!
Thanks for the suggestion, Teo! Is anyone else in a position where they can’t use the SSAS Connector because they aren’t using AD Synchronization? If so, please add your vote here!
You really don't need dirsync for this. Check if the result on whoami\upn works with SSMS. Try connecting to SSMS using that result as the effective user name. If that works, the Connector will work. If the SSMS test fails, the connector unfortunately as of now will not work!
We are looking into ways to provide custom mapping so that we do not have to rely on effective user name.
I am not sure I understand your scenario completely. It is not clear to me whether you have already installed the AS Connector to connect your tabular server to Power BI.
Take a look at this blog post - http://blogs.msdn.com/b/powerbi/archive/2015/03/11/power-bi-analysis-services-connector-deep-dive.aspx
If you have installed & configured the AS Connector but cannot use it with Power BI, let us know & we can help you out.
While we are working on improving this experience, the alternate option is for the new admin to install the AS Connector. This will take over the Connector from the previous admin to the new admin.
We do support connecting to external Tabular models from Power BI. It is a live connection to the model.
You can read more here -
You should see an option to vote next to the main title of this suggestion.
Thank you for the feedback. We understand the consistency part and this feature is on the backlog. User voice is a great way for us to figure out the priority in which we should execute & release features. So keep voting :)
Mapping identities is a tricky feature but we understand the power/benefit it has. We hope to enable it soon.
At the moment, the msmdpump is not a supported scenario for the AS Connector. We have it on our backlog & we'll prioritize it accordingly.
For your scenario to work, we need to provide a way for you to provide a custom mapping of user identities. As you pointed out, the Connector currently is locked down to work with the effective user name passed from Power BI only. It cannot accept requests from other applications (or proxies) & hence you cannot provide a custom mapping.
It is not something we plan to get started on soon, but if we receive feedback from multiple users we'll definitely expedite this scenario.
Hope this helps!
What is your scenario? Can you share more details? Can you access the AS server from Excel or SSMS?
Thanks for this suggestion. We are looking into this scenario. Most users typically have one Power BI account & use that to sign in. We do understand that there could be cases where the user wants to sign in with a different Power BI account.
In the time being, the work around for you is to delete the cookies from your browser. Then try installing the connector again. Hope this workaround helps!