►
From YouTube: New Pay as you go Features for Power Apps
Description
In this 16-minute citizen developer-focused demo, Pay as you go in Public Preview - for premium Power Apps, pay only for what you use after you use it. Kavishi Agarwal shows how to link your Power Apps environment to an Azure Subscription. The Subscription comes with base Dataverse capacity for Power Apps storage requirements and pay only for storage overages. Manage Azure Subscription and Power Apps environment from admin portal where you can add/delete apps and get usage reports. This PnP Community demo is taken from the Microsoft Power Apps community call – January 2022, recorded on January 19, 2022.
Demo Presenters: Kavishi Agarwal (Microsoft)
Supporting documents:
• Documentation – Preview: Pay-as-you-go plan | aka.ms/powerplatformPAYG
• Questions/Feedback – PowerPlatformPAYG@microsoft.com
Stay connected:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/m365pnp/videos
• Blogs https://aka.ms/m365pnp/community/blog
• Call attention to your great work by using #PowerAppsCC and #PnPWeekly on Twitter.
A
A
Apps,
which
is
pay
as
the
go
model,
so
psd
go
is
nothing
but
a
new
model
to
complement
the
existing
offerings
in
the
market
to
pay
for
your
premium
power
apps
using
pay
as
you
go,
you
only
pay
for
what
you
use
after
you
use
it,
and
that
provides
you
high
level
of
flexibility
to
get
started
with
premium,
and
this
is
based
on
a
lot
of
feedback.
We
got
from
the
community
that
sometimes
you
know
it's
hard
to
predict
the
usage
of
a
premium
app.
A
It
is
hard
to
convince
your
organization
to
adopt
premium
capabilities
because
of
the
licensing
cost
and
the
commitment
associated
with
it.
So
because
of
that,
we
introduced
this
new
way
pay
as
you
go
to
pay
via
azure
subscription
for
your
actual
usage
after
you
have
used
the
premium
capabilities
and
derived
value
out
of
it,
instead
of
pre-committing
to
the
premium
capabilities
and
paying
for
the
licenses.
A
So
today,
in
the
market,
we
have
these
two
subscription
plans
to
pay
for
powerapps
premium
apps.
You
can
do
that
either
by
purchasing
a
para
plan,
or
you
could
do
that
by
purchasing
a
per
user
plan
which
gives
you
access
to
all
premium
apps
across
all
environments
per
user,
and
these
are
the
two
ways
you
can
pay
for
power
apps
today
with
pay
as
you
go,
we
introduced
a
third
method
in
which
you
only
pay
for
what
you
use
after
you
use
it
using
your
active
azure
subscription.
A
So
one
key
thing:
the
difference
between
the
existing
subscription
plans
and
the
pay-as-you-go
plan
is
that
you
only
pay
for
the
active
users.
What
active
users
mean
is
that
your
app
could
be
shared
with
thousands
and
thousands
of
users,
but
only
if
a
subset
of
users
and
end
up
using
that
app
in
a
month,
then
you
only
pay
for
that
subset
of
users
and
we'll
talk
about
that
in
a
little
bit
of
detail.
A
So
basically
it
is
super
simple
to
use.
All
you
need
is
an
active
azure
subscription.
You
connect
your
power
platform
environment
to
the
azure
subscription
and,
as
soon
as
you
do,
that
your
environment
becomes
a
psd,
go
environment
and
any
usage
for
power,
apps
or
dataverse
within
that
environment
is
now
charged
against
azure
subscription
on
the
actuals
and
all
the
billing
details
of
how
many
apps
you
consumed.
A
What
is
the
actual
usage
that
was
consumed
for
an
app
how
much
data
was
capacity
was
used.
All
of
that
granular
information
is
available
in
the
azure
portal,
as
well
as
a
much
more
detailed
report
is
available
to
you
in
the
power
platform.
Admin
center
again
pay
as
you
go.
One
of
the
reasons
is
to
provide
you,
the
flexibility
to
try
out
powerapps
premium
understand.
What's
the
usage
pattern
in
your
organization
before
you
adopt
it,
or
there
are
certain
scenarios
where
pay
as
you
go
might
work
better.
A
A
Sometimes
it
is
hard
to
predict
the
licensing
usage,
it's
hard
to
predict
how
many
users
would
use
it
and
because
of
that,
it's
hard
to
get
the
agreement
from
the
procurement
team
to
get
started
with
powerapps
premium.
So
this
just
gives
you
a
very
easy
low
friction
way
to
get
started
with
power
ups
without
any
upfront
cost
or
commitment,
and
once
you
establish
usage
patterns
over
time,
you
can
purchase
the
prepaid
licenses.
A
If
you
know
you
get
better
discounts
or
a
better
deal
on
it,
sometimes
pay,
as
you
go,
is
actually
much
better
than
the
subscription
plans,
especially
in
cases
of
seasonal,
apps
or
occasional
apps.
For
example,
if
you
have
an
hr
app
that
needs
to
be
used
by
the
entire
organization,
but
you
know
that
it
will
only
be
used
by
a
subset
of
users
over
a
year,
so
you
don't
want
to
license
every
single
user
to
use
a
premium
license
or
a
premium
app.
A
So
in
those
cases
where
you
have
seasonal,
apps
or
location
lab
space,
you
go
works
great
because
then
you
only
pay
for
the
active
usage
using
azure
subscription
and
you
don't
have
to
license
anybody.
Finally,
this
is
one
of
the
feedback.
One
of
the
ways
customers
in
the
preview
program
have
been
using.
It
is
to
split
costs
seamlessly
within
their
units
in
the
so,
for
example,
if
hr
department
wants
to
make
sure
that
they
have
an
easy
way
to
understand
how
many
apps
and
how
many
users
do
they
need
to
pay
for.
A
Similarly,
a
different
department
wants
to
make
sure
that
they
have
easy
cost
splitting
mechanism
and
just
pay
for
the
active
usage
within
their
business
units.
Psego
is
great.
You
can
use
different
azure
subscriptions
for
each
business
unit
or
for
the
same
azure
subscription.
You
can
use
different
resource
groups
and
make
sure
that
you're
only
paying
for
the
active
usage
for
your
business
units
without
really
any
hassle
of
splitting
bills
at
the
end
of
the
year.
A
So
again,
psego
is
great
for
anybody
who
wants
flexibility
via
azure
subscription
or
anybody
who
wants
a
low
friction
way
to
get
started
with
powerapps
before
really
committing
to
powerapps
premium
or
in
use
cases
where
you
have
seasonal
or
occasional
apps,
so
now
to
understand
really
how
to
set
up
as
you
go,
because
you
know
it
provides
a
lot
of
great
value.
The
good
thing
about
psd
go.
Is
it
super
simple
to
set
up
there?
A
Isn't
a
multi-days
or
a
multi-step
process,
anybody
with
the
right
permissioning
anybody
who
is
an
environment,
admin
or
a
power
platform
admin
or
a
global
admin?
Has
the
capability
to
go
set
up
pay
as
you
go,
so
all
you
need
to
do.
Is
you
just
need
an
active
azure
subscription
and
then
you
go
and
link
that
azure
subscription
to
a
power
platform
environment?
A
You
can
do
that
in
the
par
platform
admin
center
or
within
powerapps
directly
for
the
app
that
you
really
want
to
use
for
pay
as
you
go
as
soon
as
you
connect
an
azure
subscription
to
a
power
platform
environment
that
environment
becomes
a
psego
environment.
What
that
means
is
all
the
apps
within
that
environment
are
now
charged
against
the
azure
subscription.
A
A
A
It
allows
you
to
set
up
budgets
and
it
allows
you
to
set
up
alerts
for
the
spending.
Let's
say
you
want
to
set
up
an
alert
for
a
particular
threshold
so
that
you
want
to
make
sure
you
don't
go
over
budget
for
your
organization.
You
can
easily
do
that
so
power.
Ups
psego
leverages
the
existing
cost
management
capabilities
available
in
azure
so
that
you
don't
have
to
learn
any
new
concept
to
just
leverage
how
you've
been
using
azure
subscription.
So
far
now,
in
order
to
really
understand
that,
how
are
these
charges
really
incurred?
A
How
does
the
bill
gets
generated?
How
do
you
use
it
so
think
about
it?
So
we
have
two
different
kinds
of
meters
to
make
sure
that
you
are
able
to
pay
for
powerapps
and
database
via
azure
subscription.
So
for
powerapps
meter
you
are
charged
for
any
active
user
who
uses
an
app.
An
active
user.
Is
anybody
who
opens
an
app
at
least
once
in
a
month?
A
So
let's
say
I,
as
an
user
use
the
app
10
times
in
a
month,
I'll
only
be
counted
as
a
one
active
user,
and
I
will
be
charged
only
one
time
in
a
month.
Similarly,
if
I,
as
a
user,
uses
two
different
apps
in
a
month,
I'll
be
counted
as
two
active
users
and
I'll
be
charged
for
both
the
apps
that
I
use
in
a
month,
and
I
can
repeatedly
use
the
same
app
over
and
over
again
in
a
month,
no
problem
will
only
be
charged
once
also,
if
you
already
have
a
per
user
license.
A
There
are
cases
where
you
already
are
licensed.
So
in
those
cases
we
just
exclude
you
and
you're
not
charged
again.
So
if
you
look
at
this
example
in
one
one,
only
two
users
use
an
app,
so
you
charge
twenty
dollars:
ten
dollar
per
active
user.
In
month,
three,
only
one
user
uses
an
app.
So,
as
you
see,
multiple
users
have
access
to
the
app,
but
in
different
months
different
users
are
using
the
app
so
you're
only
getting
charged
for
the
actual
usage
after
the
usage
has
already
incurred.
A
Similarly,
for
the
dataverse,
so
with
psego
as
soon
as
you
link
your
environment
to
an
azure
subscription,
you
get
1gb
database
and
1gb
file
capacity
in
your
environment,
and
this
is
to
make
sure
that
you're
able
to
use
data
verse
connected
easily
and
run
your
premium
apps.
So
you
already
get
this
capacity
free
every
month,
1gb
database
and
1gb
file
and
then,
as
your
data
needs
grow,
you
can
easily
scale
without
any
extra
effort,
and
then
you
only
pay
for
the
overages.
A
Finally,
let's
look
at
the
demo
to
understand
how
this
works
end-to-end.
So
when
you
look
at
this,
this
is
a
powerapps
portal
from
an
app
you
can
easily
go
to
the
app
setting
and
set
up
pago.
All
you
need
to
do
is
just
go
to
the
setting.
Select
pay,
as
you
go,
provide
a
name
of
a
billing
policy,
basically
provide
a
name
to
an
association
that
you
create
between
an
azure
subscription
and
an
environment.
A
You
choose
your
active
azure
subscription,
your
resource
group
and
you
click
connect
subscription.
This
connects
your
environment
to
the
azure
subscription.
Now
all
apps
within
this
environment
will
be
charged
against
azure
subscription.
So
the
process
is
pretty
simple,
so
let's
say
now
go
to
a
different
app
in
the
same
environment.
So,
as
you
see,
psd
go
is
already
set
up
and
now,
let's
say
you
want
to
add
new
environments.
You
already
have
this
azure
subscription
connected
to
one
environment.
You
want
to
add
more
or
you
want
to
remove
some
other
environments.
A
You
can
easily
go
to
the
power
platform
admin
center
from
within
powerapps,
and
you
can
edit
this
billing
policy,
which
is
an
association
between
an
azure
subscription
and
an
environment,
and
you
can
add
new
environments
or
remove
environments.
So
this
environment
is
already
added
like
we
just
created
in
power
ups,
you
can
add
a
new
environment
to
the
same
billing
policy.
So
now
both
the
environments
will
be
charged
against
azure
subscription.
A
A
Finally,
as
an
admin
right,
if
I
want
to
understand
what
am
I
being
charged
for,
who
is
really
using
these
apps
or
consuming
database
capacity
in
an
environment,
you
can
download
this
report,
which
provides
you
a
very,
very
granular
view
of
who
is
using
your
apps
who's,
consuming
the
database
capacity.
When
did
the
charges
occur?
How
much
is
the
overage?
How
are
you
being
charged?
A
C
Yeah,
let
me
see,
there's
sorry,
I
gotta
scroll
through
the
list
because,
like
I
said,
there's
a
lot,
I
don't
know
if
this
one
was
addressed
for
peter.
Is
it
possible
to
mix
pay
as
you
go
and
per
user,
or
does
users
with
per
user
license
are
also
charged
if
we
use
pay
as
you
go
on
an
app?
So
basically,
can
you
mix
and
match.
A
Yeah,
I
know
that's
a
great
question,
so,
yes,
you
can
use
psego
and
per
user
licenses
together.
So
let's
say
you
set
up
pay
as
you
go
for
one
environment
and
in
that
environment
some
users
are
licensed
per
user
licenses
and
some
of
the
users
are
completely
unlicensed,
so
you
will
only
be
paying
for
the
users
who
are
unlicensed
users
who
have
per
user
licenses
are
not
included
in
the
meters.
They
are
not
included
for
the
azure
subscription
bill,
so
you're
not
paying
for
the
users
who
are
already
licensed.
A
A
What
you
can,
however,
do
is
you
can
go
and
you
can
turn
off
pago
for
an
individual
individual
app
in
the
in
the
powerapps
portal.
So
you
can
go
to
the
settings
and
there
is
a
toggle
where
you
go
turn
off
pago
for
an
hour
but
know
that
if
you
turn
pago
for
an
app
and
you
don't
have
a
per
user
license,
then
you
don't
have
a
way
to
access
an
app
because
you
blocked
access
to
azure
subscription
and
the
user
is
not
licensed,
so
you're
really
blocking
their
access.
C
A
A
There
is
no
way
to
block
access
as
soon
as
you
exceed
a
particular
limit,
but
azure
provides
this
capability
where
you
can
set
up
alerts
so
that
you
are
informed
as
soon
as
you
know
that
you
know
you're
going
over
the
budget
that
you
have
set
up
and
then
you
can
take
the
measures
to
stop
that.
Maybe
you
can
reach
out
to
the
abusers
based
on
the
details.
D
The
way
many
azure
customers
manage
this
is
through
alerts
and
cost
management,
like
you
mentioned
alerts,
can
not
only
message
you,
but
you
can
also
script
actions
to
take
place
right.
So
a
lot
of
people
script.
I
t
admin
actions
to
take
place
and
I
thought
about
doing
a
blog
post
someday
on
how
you
would
maybe
script
some
power
platform
admin
actions
to
take
place
when
you
exceed
certain
costs,
but
in
theory
that
should
be
possible
to
customize
what
actions
you
would
like
to
take
place
based
on
what
makes
sense
for
your
organization.
E
Probably
just
hold
the
questions
for
just
following
up
in
an
email
or
continuing
in
the
chat,
so
we
can
finish
up
on
time
with
the
rest
of
the
call
yeah
look,
it
looks
like
sean
got
too
many
of
them
already
here
I
see
he
answered
a
good
four
or
five
of
them.
So
that's
great
thanks
for
coming
on
and
showing
us
that
kaviche.
I
have
a
real,
quick
question
for
you.
It
creates
a
resource
group
I
saw
in
azure.
Does
it
put
anything
inside
the
resource
group,
or
is
that
just
so?
D
Does
put
a
power
platform
account
resource
in
the
and
the
function
of
that
resource
is
purely
the
hookup
billing
to
azure.
So
we
have
a
way
to
connect
the
environments
and
power
platform
to
the
right
billing
subscription
in
azure.
That's
the
only
function
of
that
resource,
but
that
does
get
put
into
that
resource
group
as
a
hidden
resource,
but
you
can
go
and
see
it
in
the
azure
portal.