Power BI A SKU vs EM SKU with Azure Active Directory

[xabikos]

For the needs of our multitenant SaaS application we are using Power BI and we are investigating which dedicated capacity we should go for, for production environement.

Our web application is using Azure Active Directory as Identity Provider and we would like to have a deep integration between the three components, our application <-> Auzre Active Directory <-> Power BI. We are following the user owns data scenario which means that our goal is to have the credentials of the current logged in user to flow all the way to Power BI when viewing the report so to apply RLS automatically.

My question is that if the scenario described above should affect our decision on the capacity. I would like to highlight here that we don't have any need to embeed the reports in third party applications like SharePoint, or give users access to Powerbi.com itself. All the interactions, import/view, will happen through our web application.

According to our understanding A SKU is suffectent enough and we don't have to use EM SKU.

Any thoughts on it? 

[v-ljerr-msft · Accepted solution]

Hi @xabikos,

---

According to our understanding A SKU is suffectent enough and we don't have to use EM SKU.

---

Yes, if you just need to embed PBI Reports in your own application, the A SKU is enough. But please note that A SKU is billing hourly, while EM SKU is billing monthly. So if 24/7 availability is required, you may wish to switch to an Premium EM capacity. 

Regards