►
From YouTube: Getting started with Power Apps ALM
Description
In this 24-minute citizen developer-focused demo, Phil Topness and Mike Ochs – members of the Power CAT team share recently built ALM Accelerators for Business Maker (Makers) and Advanced Maker audiences. The 2 Accelerators automate the process of packaging up a Power Apps Solution and all supporting components for complete and documented movement between environments – Dev, Text, Prod. Source control in GitHub or Azure DevOps. Makers Accelerator is available now in CoE Starter Kit. ALM for Advanced Makers is in Private preview. This PnP Community demo is taken from the Microsoft Power Apps community call - March 2021, recorded on March 17, 2021.
Demo Presenters:
• Phil Topness (Microsoft) | @topness
• Mike Ochs (Exalents) | @MikeFactorial
• Marc Scgweigert (Microsoft) | @devkeydet
Supporting documents:
• Site – Make.PowerApps | http://make.powerapps.com
• Site - This X Does Not Exist | https://thisxdoesnotexist.com/ (AI generated images)
• Documentation - Use the ALM Accelerator for Makers app | https://docs.microsoft.com/en-us/power-platform/guidance/coe/almaccelerator-components
• Documentation - CoE Starter Kit modules | https://docs.microsoft.com/en-us/power-platform/guidance/coe/starter-kit-explained
Stay connected:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog
A
So
we'll
do
a
quick
round
of
introductions
we
actually
have.
Three
people
here.
Mark
is
hiding
behind,
so
we're
gonna
have
the
real
expert
handling
the
chat
for
your
questions,
and
so
I'll
start
by
introducing
myself
my
name
is
phil
topness.
I
work
on
microsoft's
powerapps
customer
advisory
team,
we're
a
small
team
that
works
on
the
largest
deployments
of
power
platform
around
the
world
and
then
you'll
hear
us
mike
speak
next.
B
C
A
And
put
some
urls
on
the
screen
too.
If
you
want
to
see
some
of
more
about
powercat,
we
have
a
couple
video
series
and
of
course
you
probably
know
the
coe
starter
kit,
which
is
also
owned
by
powercat
as
well
so
mike,
and
I
are
going
to
break
this
in
two
parts:
I'm
going
to
talk
about
the
foundation.
A
So
if
you
don't
have
a
foundation
in
solutions
and
some
of
the
core
concepts
of
alm
for
power
platform,
I'm
going
to
give
you
that
foundation
and
then
I'll
turn
it
over
to
mike
who's,
going
to
talk
about
some
of
the
ways
that
we're
automating
this
more
broadly,
but
we'll
start
talking
about
alm
in
general.
First,
and
so
I
always
like
to
alm
means
a
lot
of
different
things
to
different
people.
So
I
always
like
to
raise
the
question
you
know
what
is
it
and
I
always
think
about
it
like
this.
A
If
you
have
ever
gotten
an
email
from
your
tester
who's,
hopefully
in
their
own
test
environment
and
they
found
a
bug
and
you
try
to
replicate
that
bug
in
your
environment
and
you
start
typing
those
five
words:
we've
all
typed.
It
works
on
my
machine
right.
That's
one
of
the
things
that
we
need
alm
to
help
prevent
right.
The
goal
is
to
automate
those
processes,
so
you're
not
chasing
phantom
bugs
or
real
bugs
that
you
can't
find
because
they
just
don't
happen
in
your
dev
dev
environment
now.
A
Another
reason
we
need
alm
is
if
you've
ever
delayed,
putting
your
app
into
test,
because
you
wanted
to
squeeze
in
one
more
feature,
and
it
just
took
too
long
to
deploy
to
test
or
you
worse.
Yet
you
you
waited
to
put
real
features
in
users,
hands
in
productions
because
it
just
takes
too
long
to
put
it
into
prod.
These
are
all
the
types
of
things
that
we
need
alm
to
systematize,
so
that
we
can
do
more
rapid
releases,
but
also
make
sure
those
releases
are
consistent.
A
So
we
get
the
same
results
each
time,
and
so
we're
going
to
talk
about
how
to
use
the
alm
capabilities
in
the
platform,
but
also
how
to
automate
it
and
then
put
an
app
layer
on
top
of
it
to
make
it
easy
for
me.
But
before
we
do
that,
we're
going
to
watch
this
dude
stick
the
landing
all
right,
export
solution,
import,
publish,
nailed
it
all
right.
A
A
Now
I
can
put
that
in
my
test
environment
by
importing
the
msap
file
replicating
the
table
table
differences,
you
know
importing
the
flows,
I'll
probably
get
it
wrong,
and
so
that
means
what
my
tester's
testing
is
not
what
I
built,
and
so
what
solutions
allow
us
to
do
is
to
take
everything
in
one
package,
import
it
into
tests
and
important
depth.
So
it
makes
a
lot
more
sense
if
we
can
see
them.
So,
let's
take
a
look
at
if
you've
never
heard
of
solutions
before
how
you
can
start
using
them
with
any
app.
A
A
I
didn't
consider
solutions
when
I
built
this,
so
it's
not
in
a
solution,
but
it's
okay.
I
can
still
add
it
to
a
solution
by
going
to
make.powerapps
coming
into
solutions
and
creating
a
new
solution.
So
this
solution
is
really
just
a
a
container
for
different
power.
Apps
capabilities,
which
is
my
dev
environment,.
A
All
right
so
now
I
have
my
mic
set
solution,
so
here
I
can
add
existing
components,
even
if
I
didn't
know
about
solutions
before
this,
and
so
I
can
add
my
existing
canvas
app
here,
which
is
my
mic,
topper
app
and
so
from
there
now.
I
can
bundle
in
other
things
and
export
it
and
move
it
into
other
environments
and.
D
A
Show
a
more
sophisticated
app
here
is
my
catfisher
app.
This
is
a
little
more
complicated
app.
It
uses
dataverse
for
storing
images.
I
click
here.
It's
going
to
download
a
new
ai
generated
image
of
a
cat
and
just
while
that's
loading
that
image
just
to
show
you
these
are
I
just.
This
is
total
site.
This
has
nothing
to
do
with
power
platform.
A
These
apps.
These
images
come
from.
This
cat
does
not
exist.
I
like
to
go
here.
This
person
does
not
exist.
These
are
ai
generated
images
of
people
that
don't
exist.
This
is
the
trippiest
thing
I
mean
I
you
can
spend
I
I
can
spend
an
hour
just
hitting
refresh
on
this,
but
this
app
saves
you
the
time
of
hitting
refresh
for
cats
all
right.
So
we'll
name
this
one
mike
we're
gonna
rate
it
five
stars,
it's
a
handsome
cat,
it's
gonna
store
it
all
into
database
and
so
behind
the
scenes.
A
All
right,
it's
all
expected
there
we
go
so
here
is
here,
are
all
the
elements
of
my
solution
right,
so
I've
got
a
cam.
The
canvas
app
we
were
just
looking
in.
I've
got
connection
references.
So
as
I
move
this,
the
connection
stays
specific
to
my
environment.
I've
got
a
couple
flows,
one
that
sends
me
an
email
when
a
five-star
rated
cat
like
mike
comes
through
I've
got
environment
variables
so
that,
as
this
moves
between
the
environment
that
kitty
gram
email
goes
to
a
test.
A
A
It
runs
power
platform
checker,
which
is
a
step
by
skip,
so
we
can
force
these
consistent
practices
on
our
apps,
including
stopping
the
pipeline.
If
it
has
errors
that
are
higher
critical,
which
is
what
I'm
doing
here
and
then
what
this
does
too.
Is
it
unpacks
that
file,
because
it's
really
just
a
zip
file
full
of
configurations
for
the
app
and
it
puts
it
into
source
control
repo?
So
now
we
can
use
source
control
and
track
changes
and
and
and
go
back
in
time
with
our
no
code
apps.
A
I
can
also
set
up
a
release
pipelines
to
deploy
to
my
qa
environment
and
with
approval
from
qa,
deploy
it
to
my
prod
environment
or
more
environments,
and
I
can
do
all
of
this
in
github.
Github
2.
here
is
all
the
components
of
my
solution:
file
in
github
source
control
and
the
power
platform
actions
for
github.
B
Thanks
phil,
all
right,
so
essentially,
what
phil
just
walked
us
through
is
the
basis
for
all
alm
within
power
platform.
So
once
you
have
the
understanding
of
how
solutions
work
and
what
it,
what
components
our
solution
enabled
we,
our
decision
was
to
take
that
a
little
bit
further
and
build
a
couple
of
reference
applications
on
top
of
the
alm
that
exists
for
power
platform
and
what
we've
done,
because
we
we
understand
that
there
is
a
need
for
this.
In
you
know,
in
the
power
platform
world
there's
a
lot
of
guidance
out
there.
B
However,
there's
not
a
a
ton
of
sort
of
material
that
you
can
use
and
take
and
make
your
own
and
actually
get
started
with
it.
So,
as
the
power
cat
team
took
it
upon
themselves
to
build
out
reference
implementations
of
how
you
can
do
good,
alm
and
good
alm
means
you
start
with
a
solution.
You
put
all
of
your
components
into
a
solution.
You
take
that
solution
and
you
source
control
that
solution
into
you
know,
be
it
github
or
get
in
in
azure
devops.
B
And
then,
ultimately,
you
have
a
history
of
the
changes
that
you've
made
to
your
application
that
you
can
look
at
differences
between.
If
something
goes
wrong,
you
can
go
back
to
a
previous
version
and
then
ultimately
push
that
into
different
environments
right.
So
when
phil
was
showing
the
video
you
know
of
all
the
steps
that
it
takes,
it's
the
goal
of
the
power
cat
team
and
this
alm
accelerator
project
to
make
that
to
give
that
an
easy
button.
B
So
we've
built
two
reference:
implementations
reference
applications
built
in
power,
apps
that
target
those
two
personas,
so
the
first
one,
the
one
we're
looking
at
here
is
for
that
business
maker
persona
and
the
idea
behind
this
is
that
the
business
maker
may
or
may
not
understand
solutions.
They
probably
don't
understand
how
to
do
deployments,
and
you
know,
source
control
their
work,
but
they
want
to
get
started
with
building
something.
B
To
build
something
cool,
maybe
they're
gonna,
you
know
build
the
mic
topper
app,
which
I
didn't
wear
my
hat
today
I
apologize
or
my
clown
wig
next
time
I
will
so
then
you
would
create
a
project
from
here
and
what
would
ultimately
happen
is
it
would
go
into
this
pending
state?
So
you
can
see
here.
I've
got
a
pending
community
outreach
project
in
place
here
that
will
trigger
a
power
automate
flow
in
the
background
that
actually
sends
an
email
to
an
administrator
to
approve
that
project.
B
So
there
is
a
an
approval
process
built
into
this
and
that
approval
process
goes
from
the
time
that
you
create
the
project
to
the
time
that
you
start
to
deploy
that
project
to
the
different
environments.
So
once
you
want
to
deploy
to
a
production
environment,
there
will
be
an
approval
in
place
that
similarly,
a
administrator
will
get
an
email
and
it
will
say:
hey.
Is
it
okay
to
push
this?
Has
it
been
tested?
Have
we
verified
that
it's
not
going
to
break
anything
in
our
production
environment
you
know
and
so
on
and
so
forth?
B
B
So
this
is
the
maker,
the
sort
of
business
business
user
scenario,
the
other
one
that
we
have,
that
we're
building
out
right
now
is
the
advanced
maker
or
targets
the
advanced
maker
persona
and
as
you'll
see,
this
looks
very
similar,
but
it's
got
a
few
different
bells
and
whistles
in
it
right.
So
in
this
case
we're
not
creating
a
project.
We
already
have
our
environments
in
place.
We
have
our
solutions
that
are
sitting
out
there
and
our
goal
is
the
same.
B
Our
goal
is
to
source
control,
our
solutions
to
push
them
into
downstream
environments,
and
also
our
goal
is
to
get
approval
along
the
way
to
get
consensus
from
our
development
team.
That
says:
hey.
You
know
what
I'm
gonna,
I'm
gonna
push
my
changes
here
from
this
application
into
an
azure
git
repo,
I'm
gonna
create
a
pull
request.
So
again,
this
is
the
the
persona
who
understands
sort
of
what
a
pull
request
means
that
pull
request
is
in
azure
devops
or
in
github
is
essentially.
B
I
would
like
to
pull
this
this
application
into
our
our
main
repo
or
our
main
repository
for
source
control,
but
in
order
to
do
that,
there
are
some
steps,
approval
steps
and
things
like
that
along
the
way
that
have
to
be
done.
So
when
you
create
a
pull
request
in
here
behind
the
scenes,
it's
actually
going
to.
B
B
B
You
can
see
that
we
have
a
build
validation,
and
this
is
actually
in
our
this
is
our
the
powercat
team,
using
this
application
to
do
their
alm
for
the
coe
starter
kit,
so
the
cre
starter
kit
team
is
doing
the
same
you're
using
this
application
in
order
to
source
control,
move
things
to
different
environments,
validate
the
solutions
before
they
get
pushed
out
for
others
to
consume.
So
in
this
case,
we
have
a
build
validation
check.
B
So
when
we
source
control
the
solution,
it
will
actually
go
in
and
run
a
pipeline
to
build
this,
and-
and
in
this
case
it
happened
to
fail.
So
we
know
that
this
is
there's
something
wrong
with
this
solution
that
needs
to
be
fixed
and,
as
a
result,
you
know
we
won't
be
able
to
approve
and
complete
this.
We
won't
be
able
to
move
it
into
a
testing
environment.
B
B
It
could
be
any
number
of
things,
but
the
idea
behind
this
is
that
we
all
along
the
way,
are
validating
you
know
what
we're
building
and
making
sure
that
we
run
tests
against
it
and
things
like
that
before
we
actually
push
it
to
our
other
environments.
So
we
are
about
seven
minutes
over
time.
On
the
on
the
whole
is
now
a
good
time
to
sort
of
take
questions
todd.
I
didn't
get
to
demo
a
whole
lot
of
this,
but
you
know
in
the
15
minutes
that
we
had.
D
B
Yep
good
question,
so
the
alm
for
makers,
the
alm
accelerator
for
makers,
is
actually
out
in
it's,
not
this
one.
It's
the
other.
One
is
already
out
it's
available
as
part
of
the
coe
starter
kit,
it's
a
their
alm
or
alm
components
as
part
of
the
coe
starter
kit.
So
the
first
app
that
I
showed
you
is
available
and
you
can
get
that
as
part
of
the
coe
starter
kit.
The
advanced
makers
is
currently
in
private
preview.
B
Very
very
soon
we
will
be
in
public
preview
so
trying
to
get
a
little
bit
more
feedback
on
it
from
you
know.
People
are
using
it
and
you
know
incorporating
feedback
into
the
application,
but
we're
at
the
point
right
now
where
some
of
the
blocking
issues
that
we
were
having
with
the
platform
are
being
unblocked
and
so
we're
we're
very
close
to
being
public
preview.
D
That
sounds
good
now
I
know
the
coe
is
a
big
thing
and
it
takes
a
while
to
install,
and
so
I'm
curious
and
maybe
other
people
who
have
installed
coe
before
wondering
this
as
well.
Do
you
have
to
install
everything
from
the
coa
kit
in
order
to
take
advantage
of
your
apps
here
in
the
alm
goodness,
or
can
you
install
a
subset
of
the
coe
just
to
handle
the
alm
pieces.
B
D
B
Yep,
the
setup
you
know
the
setup
of
this
app,
that's
in
private
preview
right
now
is
a
bit
involved.
I
would
tell
people
to
take
a
day
to
get
it.
You
know
set
up,
but
it's
the
the
head
start
that
you
get
from
using
this
app
is
well
worth
that
one
day,
because,
if
you're
starting
from
scratch
with
alm,
it's
gonna,
it
can
take
you
know,
weeks
or
months
to
get
going.
So
we've
solved
a
lot
of
the
issues
that
are
common.
B
You
know
to
to
people
who
try
to
get
started
with
alm
and
power
platform
and
believe
me,
I've
been
on
projects
before
this
thing
came
along
and
I
was
part
of
those
teams
getting
started
on
it
and
it
we
spent
we
spent
months.
You
know
getting
to
the
point
where
this
app
is
kind
of
already
at
there's
pipelines.
There's
the
ammo
pipelines
running
behind
this
app.
B
Independent
of
the
app
as
well
as
a
reference
for
somebody
who
you
know,
didn't
necessarily
want
to
use
the
front
end
but
wanted
to
you
know,
set
up
their
own
alm
process.
So
you
know,
even
if
you're
not
using
the
app
the
the
ymo
pipelines
that
are
behind
it
are
definitely
something
that
should
be
checked
out.
D
B
B
D
Besides
what
phil
talked
about
on
hey
here's,
a
solution
and
how
you
packaged
it
and
what
you're,
showing
on
awesome
automation
to
build
the
whole
process
out,
there's
folks
in
chat
talking
all
about
alm,
they
want
a
dedicated
alm
session.
Even
I
I
have
a
feeling
we're
gonna,
be
asking
you
guys
if
you
can
come
back
and
follow
up
more
in
depth
on
some
of
these
things
here
as
well.
This
is
really
exciting.
D
There's
a
lot
of
questions
related
to
licensing
and
other
things
like
this,
too
we're
gonna
hold
on
a
second
to
those
questions,
everybody
chuck
and
I'll
finish
out
all
the
other
slides
related
to
the
call
here,
and
then
we
can
all
discuss
those
questions
together
here
at
the
end
of
the
call
today,
thanks
a
lot
mike
appreciate
you
working
on
that.
How
long
have
you
been
working
on
that
you
said
over
a
year
now.
D
C
Yeah,
I
would
say
it's
taken
us
months
to
get
to
the
level
of
robustness
and
flexibility
that
we
have
in
the
the
alm
accelerators
and
which
is
exactly
why
we
built
it
in
the
first
place
right.
We
don't
want
people
to
have
to
spend
that
level
of
effort
to
get
up
and
running
with
enterprise
grade
robust
alm
with
the
power
platform,
and
so
you
know,
hopefully,
hopefully
it
will
serve
that
purpose.