Power Apps Portals Licensing Clarification Request

[atp]

I've been looking at some of the posts that discuss Login capacity and looking for clarification.

If we have the following scenario:

There are 200 external users who could potentially login to our portal.

If all 200 users login at least once a month but only 50 users login on any particular day and overall page views are under 100k per month

Is it correct that would be covered by 1 Login Capacity ($200 per month for 100 daily login sessions) and  1 Page view capacity ($100 per month for 100,000 page views) ?

Then the next question is say a one-time notification goes out to the 200 users and on that one specific day 101 users try to login.  How is that handled?  Would the 101st user and beyond be able to login?  If so, would we accrue a second Login Capacity charge?

[v-siky-msft · Accepted solution]

Hi @atp ,

Let me clarify the meaning of logins.

A login provides the access for authenticated user to a single portal for only 24 hours. That's means, if an authenticated user logins to the portal two days in a row, this will be counted as two logins.

Aside from this, the unit capacity of the add-on is 100 logins per month, not per day, so you should purchase appropriate capacity aligned with peak monthly anticipated usage( 200 logins at least, so far), that means at least 2 units of 'Power Apps portals login capacity add-on' is required.

While occasional and reasonable overages will be tolerated,  if exceeding purchased capacity, you should adjust your purchase quantity per standard Microsoft terms to remain in compliance.

For more reference: Microsoft Power Apps and Power Automate Licensing Guide 

Hope this helps.
Sik

[atp]

Oh, wow, the wording in Power Apps pricing does a terrible job making that clear..  Im not sure how how anyone would conclude that “$200 per month for 100 daily login sessions” really means 100 logins per month.  

Thanks for sharing the link to the licensing guide.  Glad to have been corrected on the login issue before I dramatically miscalculated what it would cost to move our customer portal to Power Apps Portals vs custom development on our existing portal solution.