►
From YouTube: Application Lifecycle Management (ALM) for Cloud Flows
Description
In this 28-minute video, Chris Garty (Senior Product Manager for Power Automate) gives an overview of Application Lifecycle Management (ALM) from a Cloud Flows perspective including solutions and pipelines, as well as roadmap such draft flows and Power Platform Catalog. This video was taken from the February 8, 2023 Power Platform Integrations / Connectors LABs Call.
Chris Garty (Microsoft) | www.linkedin.com/in/chrisgarty/
Supporting Materials
https://learn.microsoft.com/en-us/power-platform/alm/overview-alm
https://learn.microsoft.com/en-us/power-platform/alm/basics-alm
https://learn.microsoft.com/en-us/power-platform/alm/solution-concepts-alm
https://learn.microsoft.com/en-us/power-platform/alm/pipelines
A
Yeah
so
hi
I'm,
Chris,
gardie,
I'm,
a
senior
product
manager
on
the
power
automate
team,
specifically
on
cloudflows
team,
and
my
team
specifically
deals
with
Administration
and
life
cycle,
so
the
life
cycle,
part
of
that
mandate,
is
application.
Lifecycle,
management
or
Alm
I'm,
going
to
give
you
a
little
bit
of
a
cloud
flows
perspective
on
on
that
today,.
A
Right
so,
let's
talk
about
Power,
Platform
ilm,
so
I'll
run
through
Alm
I'll
run
through
kind
of
Power,
Platform
ilm,
and
then
I'll
talk
about
some
Alm
related
improvements
and
then
I'll
just
open
it
up
for
questions
afterwards,
justly
mentioned
that
you're
a
fairly
chatty
Bunch,
so
yeah.
Let's,
let's
have
some
q
a
at
the
end
as
well,
so
Power
Platform
Alm.
What
is
Alm
so
it's
the
life
cycle,
management
of
applications
includes
governance,
deployment
and
maintenance.
We
aim
to
drive
efficiency
through
predictable
and
repeatable
software
delivery.
A
The
tools
facilitate
collaboration
between
teams
and
departments.
It
can
be
as
simple
as
a
maker
building
an
app
or
a
flow
and
then
just
asking
an
administrator
to
deploy
it
to
production
So
within
the
Power
Platform
Alm
spans
me
at
multiple
teams.
It's
a
very
you'll
hear
about
Alm
and
about
Alm
fans
from
multiple
teams.
So
my
power,
automate
team
is
just
one
of
the
teams:
that's
building
maker
experiences
for
Power
Platform
products
and
contributing
to
this
ecosystem,
but
there's
a
number
of
other
teams.
A
There's
a
team
within
the
powerapps
that's
dedicated
to
application
lifecycle
management,
there's
a
team
that
creates
the
solutions
UI
within
the
dataverse
team.
They
manage
the
the
solutions,
model
and
kind
of
experience
as
well
yeah.
So
there's
multiple
teams
that
that
deal
with
Alm
within
the
Power
Platform.
A
So
the
basic
view
of
Alm
is
moving
a
maker,
creating
something
making
changes
to
something
and
then
moving
it
from
a
development
environment
through
the
test
testing
it
moving
it
back
to
development
as
needed
and
then
eventually
moving
it
through
to
production.
Once
the
testing
passes,
some
environments,
environments
and
environment
strategy
are
a
really
important
part
of
Alm
within
the
Power
Platform
environments,
or
a
space
to
kind
of
store
and
manage
and
share
your
organization's
data
apps
and
business
processes,
so
they
form
containers
within
the
Power
Platform
So
within
each
environment.
A
A
So
Solutions
are
another
important
part
of
Alm
Solutions
used
to
transport,
apps
and
components
from
one
environment
to
the
next.
They
can
be
used
to
apply
customizations
to
existing
apps.
They
include
metadata
and
entities
with
configuration
data
components
as
well,
but
they
don't
contain
business
data
yeah,
so
they're
used
for
moving
things
around
between
environments.
A
So,
with
the
with
build
tools
and
Source
control,
you
can
automate
Alm
Source
controls
where
you're
going
to
have
your
single
source
of
Truth,
your
all
of
the
resources
that
you're
creating
inside
of
your
environments.
You
want
to
get
those
into
Source
control
and
then
be
able
to
move
those
to
the
appropriate
environment
from
Source
control.
A
A
So
there
are
some
build
tools
that
are
available
for
the
Power
Platform.
They
can
be
used
to
automate
common,
build
and
deployment
tasks.
They
create
a
pipeline
that
allows
you
to
generate
build,
artifacts,
move
things
to
Downstream
environments,
provision
and
deep
provision.
Environments
perform
static
analysis
checks
using
the
solution.
Checker
and
and
automation
is
one
a
key
goal
of
what
you're
trying
to
do
with
application
lifecycle
management
to
improve
the
productivity,
the
reliability,
the
quality
and
the
efficiency
of
of
what
you're
doing,
try
and
take
the
the
human
element
out
of
it
somewhat.
A
We've
got
a
whole
learn
site
dedicated
to
Alm
with
a
ton
of
documentation
and
that
will
in
Turn
Point
you
to
a
specific
documentation
about
power,
automate
aspects
and
powerapps
aspects,
and
things
such
as
this,
but
the
other
things
to
be
aware
of
related
to
kind
of
applications
and
application,
lifecycle
management
and
Moving
Solutions
and
your
automations
in
terms
of
flows
around
between
environments.
Our
licensing
considerations,
so
you're
going
to
need
to
be
aware
of
which
licenses
things
are
running
under
you're,
going
to
want
to
be
aware
of
governance
administration.
A
So
what
are
some
Alm
related
improvements
that
we've
been
working
on
recently,
so
the
the
First
Dimension
is
is
something
that
we're
referring
to
as
pipelines.
So
today,
maker
and
pro
developer
deployments
are
kind
of
disjointed.
So
for
makers
you
have
an
experience
inside
of
the
maker
portal.
It's
simple.
It
allows
you
to
export
Solutions
import
Solutions,
you
can.
A
The
maker
can
set
up
their
connections,
they
can
deal
with
putting
values
into
environment
variables,
but
you
need
to
have
you
need
you
to
be
able
to
move
something
into
tests
and
production
environments?
You
need
to
have
make
permissions
in
those
environments
and
that's
not
something
that
we've
recommend
and
it's
not
something
that
administrators
at
large
customers
are
willing
to
provide.
A
There
is
also
no
backup
versioning
audit
history
or
governance
controls
related
to
the
kind
of
simple
abilities
to
export
and
import
Solutions.
So
it's
kind
of
an
incomplete
picture
for
makers
and
then
for
pro
developers
you
can
have
frequent
automated
deployments
with
Enterprise
level
governance
and
it's
really
powerful
leveraging
the
Power
Platform
build
tools
to
facilitate
that,
but
dealing
with
connections
and
deployment
settings
is
difficult.
A
There
is
a
deployment
settings
file
that
you
can
leverage
to
pass
deployment
settings
across
connections,
kind
of
need
to
be
created
in
the
environment
before
you
do
the
deployment
and
then
you
can
use
deployment
settings
to
kind
of
point
at
those
connections
and
make
use
of
them.
But
it's
not
it's
not
maker
friendly.
A
So
what
we've
recently
made
available
is:
is
pipelines
Power,
Platform
pipelines.
There
was
a
blog
post
about
this
in
December.
There
is
documentation
available
in
that
at
that
Alm
learn
site
that
I
referenced
previously,
specifically
for
pipelines,
and
you
can
do
a
Bing
search
or
a
Google
search
for
Power
Platform
pipelines
to
learn
more
it's
currently
in
public
preview,
and
it's
going
to
GA
in
June,
it's
largely
about
yeah.
So
if
I
can
summarize,
it
administrators
will
set
up
a
pipeline.
A
It's
very
easy
to
set
up
a
pipeline,
there's
currently
a
modeled
app
that
you
use
to
to
set
up
the
pipeline.
That
experience
will
change
over
time
and
and
kind
of
come
into
the
into
the
maker
and
admin
portals
and
then
makers,
citizen
developers
they
can
initiate
deployments
so
inside
of
the
solutions
experience
inside
of
the
solution,
Explorer
when
you
click
into
a
solution
on
the
left
side.
A
In
addition
to
being
able
to
see
your
objects
and
your
history,
you'll
have
a
pipelines
Tab
and
that
pipelines
tab
will
give
you
access
to
the
pipelines
that
your
administrators
have
defined
and
then
you'll
be
able
to
move
that
solution
into
along
the
stages
of
the
pipeline
as
you're
moving
it
into
the
stages
of
the
pipeline.
That
maker
will
then
be
able
to
set
up
connections
as
needed
for
the
the
solutions
to
Leverage.
A
And
developers
produce
can
also
run
those
pipelines
for
your
CLI
and
in
the
near
future,
there'll
be
capabilities
coming
out
that
allow
you
to
create
extensions
to
those
pipelines
such
as
running
flows
immediately
before
or
after
something
is
deployed
to
set
things
up
or
send
notifications.
It's
really
going
to
be
a
great
advancement.
A
So
over
the
last
year
we've
been
doing
a
lot
of
Alm
improvements
related
to
cloudflows
I've
listed
off
a
number
of
them
here
and
kind
of
listed
off
the
the
months
that
those
became
available,
a
few
key
ones
to
mention.
We
made
it
so
that
solution
flows
now
show
up
in
the
myflows
experience,
so
the
myflows
experience
previously
would
have
only
shown
non-solution
flows
now
solution
flows
where
the
definitions
is
stored
in
dataverse.
A
Those
will
show
up
in
the
my
flows
experience
and
when
you
click
into
one
of
those
flows,
you'll
get
a
Solutions
card
that
will
show
you
any
of
the
solutions
that
that
flow
is
contained
within
in
the
future
will
improve
that
Solutions
card
to
to
make
it
so
that
you
can
move
flows
between
Solutions
and
and
kind
of
change
which
Solutions
the
flows
are
in.
But
this
is
a
is
a
great
start.
Now,
we've
also
started
making
available
the
ability
to
have
service
principal
application,
users
own
and
run
flows.
A
A
On
this,
it's
going
to
become
public
in
February,
we're
still
working
on
some
license
enforcement
pieces
related
to
this
once
those
are
complete,
then
we'll
have
a
blog
post
and
documentation
and
kind
of
more
information
about
the
service
principle
support
but
I
know
a
large
number
of
customers
have
asked
for
the
service
principle
support,
so
I
wanted
to
at
least
mention
it
here.
This
is
something
that's
kind
of
coming
out
in
the
next
few
weeks.
A
A
Now
a
private
preview
of
this
available
now
for
cloudflows,
we
are
in
the
process
of
kind
of
finishing
up
that
work,
yeah
and
it'll
be
available
shortly
and
and
we'll
have
a
blog
post
related
to
this.
So
this
will
allow
the
first
kind
of
milestone
for
this,
we'll
facilitate
blank
flows
and
flows
created
from
template
to
be
added
into
dataverse
by
default
when
dataverse
is
available.
A
That,
from
the
solution
of
your
choice,
certainly
speeds
up
the
the
Alm
process
and
then
in
the
near
future,
and
kind
of
March
and
April
will
be
adding
support
for
all
of
the
integration
entry
points,
such
as
teams
and
SharePoint.
Instead
of
databases
in
those
environments.
It
will
also
create
those
flows
on
the
side
of
database
by
default.
A
Additionally,
we
are
just
starting
work
on
something
that
has
been
asked
about
a
lot.
It
was
the
second
most
requested
idea
on
the
power
to
make
ideas
site
last
year,
and
that
is
support
for
two
things.
I'll
talk
about
the
first
and
that's
being
able
to
have
draft
and
draft
flows
being
able
to
create
draft
blows
and
publish
them
and
being
able
to
change
flows
and
have
them
in
a
draft
mode
and
be
able
to
save
changes
to
a
flow.
Even
if
there
are
errors
yeah.
A
So
we're
we're
actively
working
on
this
support.
Right
now,
the
support
is
being
added
into
dataverse
using
the
component
State
capability.
So
we're
excited
to
be
working
on
this
with
the
with
the
dataverse
team
of
the
draft
version
of
a
flow
Will
Will
just
always
be
turned
off
in
the
published
version
of
the
flow
that
will
be
the
one
that
end
users
see
and
when
you're
ready
to
publish
the
draft
flow.
A
Okay,
it
sounds
good
yeah.
When
you
read
it
a
publish
that
draft
flow,
then
you
just
hit
the
you'll,
be
able
to
hit
the
publish
button
and
then
users
will
start
seeing
that
flow.
That
flow
will
be
the
one
that
will
start
running
on
a
schedule.
However,
that
flow
runs
related
to
this.
We're
also
going
to
be
adding
flow
versioning,
so
versioning
for
cloudflows,
so
makers
will
be
able
to
change
and
publish
so
maker.
Yeah
maker
changes
and
publish
operations
will
be
visible
in
a
version
history.
A
So
all
of
this
versioning
capability
is
being
implemented
via
solution
components,
so
this
will
be
available
for
solution.
Cloud
flows
and
cloudflows
is
the
first
place
that
this
versioning
support,
this
dataverse
versioning
support
is
being
added
and
then
you'll
see
other
solution,
components
moving
to
this
version.
Versioning
Support
over
time,
all
of
the
version
information
will
be
stored
in
dataverse,
and
then
the
database
team
is
also
planning
to
do
Source
control
integration
with
dataverse
in
the
future
as
well.
A
Something
else
that's
just
in
the
early
stages:
we've
just
started
talking
about
it
and
we
have
a
private
preview
of
the
developer
tools
related
to
it
is
the
Power
Platform
catalog.
So
this
is
something
that
we're
working
on
an
organization-wide
catalog
of
Power
Platform
components.
This
will
enable
Pro
developers
and
makers
to
easily
share
Power
Platform
artifacts
with
their
colleagues
to
help
solve
business
problems
and
then
we'll
provide
capabilities
for
administrators
to
be
able
to
configure
approvals
and
kind
of
decide
which
things
they
allow
into
the
Power
Platform
catalog
yeah.
A
A
So,
that's
that's
something
really
exciting
related
to
Alm
and
really
allows
makers
to.
We
talked
about
pipelines
enabling
makers
to
kind
of
self-service
themselves
in
terms
of
pushing
things
to
different
environments.
The
Power
Platform
catalog
will
allow
makers
to
kind
of
self-service,
facilitate
getting
things
into
environments
via
a
pull
mechanism,
so
it
should
be
a
really
exciting
to
to
see
that.
A
B
C
A
It's
just
that
default
solution,
yes
yeah.
So
for
those
that
don't
know,
there's
a
default
solution
that
isn't
really
a
solution.
It's
really
just
a
view
of
all
of
the
the
components
solution,
components
that
have
been
added
into
dataverse
in
some
solution,
we're
adding
it
into
that
solution.
The
just
the
default
solution,
so
you'll
be
able
to
find
those
solution,
components
and
then
add
them
into
the
Your
solution
of
choice.
A
If
there's
there's
a
caveat
there,
if
you,
you
can
always
go
into
a
solution
and
Define
it
directly
in
that
solution
and
then
the
other
thing
is:
if
you
have
a
solution
context
and
then
you
go
and
start
creating,
just
just
in
the
mindfulness
experience,
start
creating
some
flows
and
apps
those
will
drop
into
that
solution
context.
So
we
will
leverage
the
solution
context
when,
when
it
is
available
that
sounds
cool.
D
Yeah
I
think
there's
the
well
there's
two
default
Solutions.
Isn't
there
does
the
the
default
Solution?
That's
everything
and
then
there's
a
common
data
services
default
solution
which
has
nothing
in
it
from
what
I
can
see.
I
believe
it's
that
second
solution.
Isn't
it
the
common
data
services
default.
A
That's
right:
we
were
originally
planning
to
do
that.
I
I,
must
say.
I
I
need
to
double
check
on
that
detail.
I
haven't
seen
that
Behavior
happening
recently,
so
yeah
I
think
we
might
have
changed
our
minds
on
that.
So
the
the
common
data
services
default
solution
is
one
that's
heavily
leveraged
with
the
team's
integration,
so
yeah
yeah
I
need
to
double
check
on
that
sorry.
Yeah.
A
Yes,
so
the
dataverse
team
is
still
working
out
exactly
how
the
the
version
information
will
be
stored,
but
yes,
likely
it'll
it'll
just
be
in
the
workflow
table.
Yeah
yeah
I!
Don't
have
specifics
on
that,
like
it's
literally
in
development
right
now,
but
yes,
the
the
version
information
will
be
available
in
dataverse.
If
it's
it's
not
directly
in
that
that
workflow
table
it'd
be
in
a
in
a
linked
table,
so
you'll
be
able
to
grab
that
information.
B
Chandra
asked
a
question
about:
are
any
updates
on
supporting
service
principle
for
more
connectors.
It
is
a
conversation
we
are
having.
It
is
definitely
somewhere
in
our
roadmap
and
something
I've
actually
spoken
about
just
this
week
with
regards
to
distinct
timeline
or
date,
I'm,
not
sure.
But
yes,.
A
B
Actually,
a
common
conversation
for
a
lot
of
things
that
have
to
do
with
connector
enhancement
for
certain
things
where
you
know
it's
enabled
for
a
few
connectors.
It
may
have
originally
been
coded
so
that
it
was
individually
enabled
for
each
of
those
very
few
connectors.
So
for
us
to
go
back
and
then
fix
them
on.
E
E
A
A
Don't
have
a
a
super
clear
answer
for
this,
so
the
LM
accelerator
app
is
something
that's
available
for
those
that
don't
know
is
something
that's
available
via
the
cue
starter
kit
and
it
can
facilitate
deployments
and
makers
can
run
it
to
request
deployments
so
in
much
the
same
way
that
you
can
that
you
can,
with
pipelines
they're
very
similar
capabilities,
there's
still
some
capabilities
that
are
available
via
the
Alum
accelerator
that
aren't
in
the
pipeline.
So
the
solution
pipeline
space,
the
I
guess
the
question
would
be.
A
B
A
There's
talk
about.
There's
active
discussions
going
on
related
to
this.
So
there's
discussions
about
SharePoint
being
able
to
kind
of
point
at
different
environments,
yes,
being
able
to
point
at
a
different
environment,
the
there's
a
there's,
a
kind
of
a
sub
question
there
of
like
what
about
multiple
environments.
There
have
been
discussions
about
that
as
well
being
able
to
see
flows
in
multiple
environments
and
be
able
to
run
those
in
the
context
of
a
SharePoint
site.
B
Thank
you
so
much
Chris
for
all
of
these
updates
and
explanations.
I
actually
put
a
question
in
the
chat
that
was
like
use
me
as
a
like
button.
If
we
want
Chris
to
come
back
and
talk
about
admin
stuff,
because
you
and
I
were
discussing
that
yesterday
and
you
got
some
some
likes,
so
maybe
we
shall
bring
you
back
because
I
know
there
are
a
good
quantity
of
makers
here,
but
apparently
there
are
also
some
admin
personas
as
well
in
this
audience.
So
perhaps
we
shall
see
Chris
again.