I am researching how to create environments in Power Platform. I notice that someone would have to visit license admin center for assigning licenses to users before trial environments can be created.
Here is the list of plans in https://learn.microsoft.com/en-us/power-platform/admin/create-environment#who-can-create-environments:
What is the difference between Power Apps plan and Power Apps trial? Does Power Apps plan include an ability to create trial environments?
Does Power Apps trial actually expire 90 days and the user cannot create trial environments after 90 days?
What I really would like to know is what licenses are assigned to admins who, in turn, will assign trial environments to users?
You can refer this link to know the latest policies about licenseing a power apps. you can go through the description given in the plan's card. it will allow you to choose best option for your specific solution.
Power apps plans and licensing
Related
My team plans to build a web platform which gathers data in a DB about different crypto transactions. I am planning to use Power BI to get that data from the db and build some reports which will be embedded into the web platform, reports which will be accessed by users who log in in the web platform.
Is this possible, taking into consideration the following aspects?
I want to apply row level security access so that users who log on the web platform will be able to see only data related to them?
Should I assign a Power BI Pro license to each user who registers the platform in order to be able to see the data or is there any other solution to this?
How often may I set-up data refreshes/updates? 30 minutes?
I am looking to apply row level security access and have users access the reports based on their web platfrom login credentials. Hopefully this is possible. I read something about Power BI Report for Customers using App Owns Data. Is this the right solution?
For the App Owns Data, you will be building a portal on top of an embedded capacity. I assume that you will be using an 'A' Sku.
I want to apply row level security access so that users who log on the
web platform will be able to see only data related to them?
Yes you can use RLS to control what users see what data, in an embedded context . (See here)
Should I assign a Power BI Pro license to each user who registers the
platform in order to be able to see the data or is there any other
solution to this?
No, you don't need a PBI Pro license for each user for your platform, this is handled by the capacity. You'll only need Pro for those who are developing the reports. Your other users, handled by your web portal will be 'read only'.
How often may I set-up data refreshes/updates? 30 minutes?
You can set up the report schedule as normal in the portal, up to 48 times per day with a capacity based Power BI Dataset.
I would take a look at the MS documentation here for more details on the what embedded can do, and also capacity planning for your users.
My company has been using free office 365 accounts, so they can neither share nor see each others Power BI reports/dashboards/ whatever. How do I work around this without paying for pro account 'If' such a workaround is possible.
Sharing is a Pro feature. With Free accounts you can use only Publish to web (Public), which is very limited feature, makes the data publicly available (so it is definitely not suitable for your use case) and must be explicitly enabled by your tenant administrator, or to share .PBIX files internally with your collogues (by e-mail, network share, or something similar).
As a conclusion, your best option is to start paying for it. If your company has development skills, you can also embed these use app owns data scenario, which is normally used to share Power BI elements with your customers outside of your organization, to share the reports with your co-workers.
To share without Pro licenses you can’t share using the Power BI service. But you’re free to share your .pbix files with your colleagues using a file share, SharePoint, OneDrive, etc. They will need Power BI Desktop to open the files.
I have a Power BI Pro License which I used to publish the report to Power BI service.
I used a Service Principal in Azure and Power BI Pro licensed master user to embed that report in a web-site in DEV environment.
The source of the report is one of our own production database.
I went through the following documents to understand the costs I have to incur when i move the web-site to production.
https://learn.microsoft.com/en-us/power-bi/developer/embedded/move-to-production
https://learn.microsoft.com/en-us/power-bi/admin/service-premium-what-is
https://learn.microsoft.com/en-us/power-bi/developer/embedded/embedded-faq
I am still unsure about the cost of having this embedded report in my production web-site.
I think one cost will be that of a Power BI Premium License.
Will I have to also purchase and pay for any reserved capacity or shared capacity.
I want to keep costs at the minimum as the same report content has to be shown for all users.
Can you please help me understand the costs incurred in using this embedded report in my production web-site.
Also, suggest the most cost-effective way to implement my use-case.
Thanks,
Gagan
You need as a minimum a 'A SKU' Power BI Embedded Capacity. This is purchased via Azure, and can be paused, so you only pay when the capacity is running. The pricing starts at $1 per hour, or $735 per month (but that is the cost running 24 hours per day)
https://azure.microsoft.com/en-us/pricing/details/power-bi-embedded/
As mentioned you can pause A SKU's only to reduce the cost. for example during business hours. As you have seen in the documentation, you do not need a Pro license assigned to the users to consume reports.
You only need a Power BI Pro license when creating or deploying reports or when developing your website to host the reports. Not using a capacity, and continuing to use the Power BI Pro method in a productionable way breaks the terms of the license, but you'll also run out of embedded tokens (like here), as it is limited.
There is no longer a pay to click method of deploying Power BI Embedded, it was replaced by the capacity model about three/four years ago.
At a minimum you need a Power BI Pro license, for yourself, to create/manage/share reports.
Depending on the amount of users that will be consuming your reports you will need to decide whether buying capacity (unlimited users, because you are buying computing resources versus user licenses) or buying individual pro licenses for these users and assigning them workspace access is a more cost-effective and scalable approach.
Let me know if this is helpful.
Just requiring some help and clarification around sharing Power BI apps.
We have an app created inside an EM1 premium capacity workspace, and we are wanting to share the app with user's within our organisation. My understanding is that if the app is published in a premium workspace all user's inside my organisation should be able to view it, providing it is shared with them.
However, only those of us with a pro license are able to view the app. Those with free licenses get a pop up message saying they'll need a pro license. No where online states this, hence my belief any user should be able to see the app.
We have given user's the "Viewer" role within the Power BI workspace, and even tried to give them admin role, neither let them see the app.
Can anyone clear this up/ help please? Many thanks.
Unfortunately "Premium" is a bit of a mess, which isn't quite easy to clearly understand. In this case, you incorrectly assumed that "Premium" EM SKUs will give you rights to share contents with Power BI Free users - this is given only with "Premium" P SKUs. Quote from the original docs:
While there is a lot of overlap in features for the two SKU families, only the P Premium SKU gives free users the ability to consume content hosted in the Premium capacity. EM SKUs are used for embedding content.
If you want this, you must upgrade to P1 SKU (or higher), which is 7-8 times more expensive and comes with annual commitment.
We would like to empower our power users by giving them a self-service BI option. The issue now seems to be of compliance.
Just to be clear - I'm not a full fledged PowerBI developer or Administrator. From what I know, there is a MyWorkspace and Several Workspaces for the various environment such as Dev/QA/Stage/Production and eventually PowerBI Apps which the Business Users get to use; the artifacts gets published from Dev to Stage to Prod.
Compliance (Audit Team) is concerned that the Power-Users might make unwarranted change in the DataSets, Reports and Dashboards in the Production WorkSpace (Pointing to the Production Database) and publish these to the Apps which will eventually get consumed.
Can others share how they have addressed it in their respective environments?
For a workspace, you can set users to be one of four types, Admin, Member, Contributor and Viewer. For full details of what each role can do, see here.
What you need to to is set users as read only, they will not be able to edit or change any of the items in the workspace. I would also recommend in the Power BI Admin portal setting a defined group that allows people to download, export to pdf and those sort of options to stop users modifying locally on their Power BI Desktop.
In the workspace overview, that list the items in the workspace, go to the 'Access' option, you will then get a list of the users and their current defined roles and the ability to set them to one of the four roles.