Awesome. Looks like that was published awhile ago, so don't know why I could not find it. Thanks for the help.
While we're relatively new to PowerBI, I sure find that the pieces do not hang together very well. From an embedded standpoint, the pricing is just stupidly high for low volume scenarios. I have given up attempting to get one of my workspaces associated with a PowerBI instance. 3 people at MS failed to ever explain why, so we gave up.
Low volume scenarios with pausing the SKUs are cheap? 1$ /hour on a minute basis for A1 core.
Just create many resources for different tiers of users maybe?
* 1 tier A1 for everyday use like maybe marketing and purchasing.
* 1 tier A6 for accounting/strategy/logistics desicions to use at Quarterly critical business moments?
Start/Stop upon Report render in your app.
Depends if you have to start services for 500-100 users at different times and such though..
If you don't need the ability for Crossfiltering, data discovery, edit and save cababilities and seamless Excel 2016/PowerPoint 2016 compatability then yeah Power BI is not the only way: Mongo dB Node.js backend - Angular 5 Frontend - Some java graphs like: https://www.fusioncharts.com/dev/chart-guide/pie-and-doughnut-charts/creating-pie-and-doughnut-chart...
My struggles with Power BI embedded has also been beyond reasonable 2weeks now.
After 45 mails, 3 calls and 4 Microsoft support contacts I finally got a tech that knew a thing or two about Azure and Power BI Embedded.
Microsoft Sign in - auto created accounts based on outlook accounts, created personal accounts instead of work/edu, Workspace Collections was still visible and available in Azure with documentation being outdated and not showing the new steps to take.
I have incorrectly managed via backdoor Microsoft CLI commands from Powershell create all the old resources but at the end nothing worked since Workspace Collections and Workspaces had been removed and I just received errors.
The next steps to take are scary and I fear will be as troublesome: How does Power BI PRO integrate with the new Embedded SKU solution. Almost all videos "GuyInTheCube" and Microsoft Docs/videos showcase the pre 2017-07-01 ways of embedding Reports.
If I ever get through this hell.. I will defenitely post a complete video on Youtube named "Pitfalls of Azure and Power BI Embedded - a complete Step by Step guide"
Frankly, we've spent more on trying to wire up embedded than we did on creating the functionality and still have no clue that what we have running is maintainable or proper licensing, etc. I've yet to find anyone at MS that really has the full picture on this.
I fear your video may be an extended length version since it focuses on "pitfalls"! PowerBI is not a bad tool but if you can't use it in real-world scenarios, it is not of value.
We're an ISV and would like to use it to replace some dashboards we have done using Google visualizations but keep hitting brickwalls. MS pricing takes the view, it seems, that PowerBI is going to be a monolithic solution. We just want to use it just as part of complex applications we develop and sometimes to quickly put together complex data we have in SQL for easier consumption by data analysts that work at our customer locations. I even get conflicting information from supposed licensing gurus that sell Office 365 as to whether PowerBI is part of E3 licensing or not. MS hurts themselves by making this so frustratingly obtuse and difficult, IMHO.
Was the availability of this API to pause/resume capacity announced on the Power BI blog?
It would be great if the team could communicate the addition of these features!
Each new feature or addition we release is being announced in the monthly developer update for Power BI.
Be sure to follow up there for all new additions.
I'm troubled to hear about the pitfalls you are encountering.
To get started, use this documentation and follow the steps described there- https://docs.microsoft.com/en-us/power-bi/developer/embedding
I would be happy to hear more on specific problems you faced and what you think should be the solution.
If you have the time; these are the potential pitfalls (and I think I stumbled on every single one):
Your link doesn't help much for most ISV users since I'ts in C#. We use MEAN stack for instance
I prefer the API POST/GET method since It Isn't code language dependant.
Microsoft login (Both Azure and Power BI).
The old login experience took into account that you always want to choose your account type edu/work/personal upon login.
The new MS login is flawed in some ways:
Azure account type
Your tech support did not know the prerequisit for Azure to allow access to resources - SKU or workspaces.
This led to:
Power BI embedded docs
Thanks for the thorough feedback.
It is important for us to hear your problems and suggestions.
While some of the bullets are not related directly to PBI, we will try to pass it forward.
Adding some notes to the last part:
Power BI embedded docs
We have a monthly blog with all updates. See the relevant one- https://powerbi.microsoft.com/en-us/blog/power-bi-embedded-capacity-based-skus-coming-to-azure/
It's still pretty new. Again, you can find it through our monthly blog post. Here is what you are looking for- https://docs.microsoft.com/en-us/rest/api/power-bi-embedded/
We will look into it.
Starting June 2017, PBI Embedded supports all of the data sources that Power BI supports. The API itself can support SQL Azure/On-prem and AS Azure/ On-prem in all relevant connections. See November blog post- https://powerbi.microsoft.com/en-us/blog/power-bi-developer-community-november-update/
Thanks for the feedback, we will look into it
Anyone discover any way to schedule an stop for Power BI Embedded?
This is pretty straightforward... create a Powershell script that you can use within an Azure Automation runbook. This Powershell script should use the latest version of the Azure RM Powershell module that the Power BI team have added pause/resume capacity commands to. Then you schedule the runbook to run at the appropriate time of day/day of week.
It is probably easiest to create two separate runbooks; one for pausing, one for resuming - but you could add parameters to your script/runbook and handle both situations in the one script. Plus you might want to add parameters to indicate which capacity to pause/resume or maybe just hard-code this if appropriate.
It appears that the capacities pause and resume pretty quickly - but that might depend on time of day/region/capacity size, etc. Any insight from the Power BI team here would be great!
Join us in the third Triple A event!
It’s the start of a new Super User season! Learn all about the new Super Users and brand-new tiered recognition system.
Make sure you didn't miss any of the things that happened in the community in January!