►
Description
Power Platform Integrations / Connectors LABs Call delivered on February 8.
Hosted by Jocelyn Panchal (Microsoft) - @JocelynP_PM, linkedin.com/in/jocepan00/
Agenda:
0:00 - Intro and What's New
8:59 - Application Lifecycle Management for Clouds - Chris Garty (Microcosft) | linkedin.com/in/chrisgarty
37:47 - Microsoft Learn Independent Publisher Connector Demo - Sean Kelly | linkedin.com/in/seanke11y/
Learn more about Power Platform Connectors
https://github.com/microsoft/PowerPlatformConnectors
https://learn.microsoft.com/en-us/connectors/
Want to join the next LABs Call? Fill out this form: forms.office.com/r/VN6uEuYKnK
A
Awesome
good
morning,
good
afternoon,
good
evening
from
wherever
you
guys
are
tuning
in
from
thank
you
so
much
for
coming
to
this
month's
Power
Platform,
connectors
and
Integrations
Labs
call,
and
it
is
February
8th,
just
a
reminder
that
this
call
is
indeed
recorded
and
will
be
posted
on
YouTube
as
part
of
the
I'm
365
Community
Channel,
and
we
shall
get
into
it.
I
shall
drop
my
links
in
the
links
of
our
other
presenters
today
in
the
chat
for
you
guys
to
feel
free
to
connect
with
us
just
an
introduction.
I
am
Jocelyn.
A
It
is
so
nice
to
meet
you
all
for
all
of
the
new
faces.
I
was
originally
from
the
east
coast
in
New,
York
and
New
Jersey,
and
that's
actually
where
I
am
right
now
visiting
my
family,
but
I
also
live
in
Seattle
I
went
to
University
of
Washington
with
a
mechanical
engineering
and
degree
and
Spanish
minor,
which
is
a
little
bit
atypical
for
the
computer
science
space.
A
Just
to
set
the
stage,
as
we
start
talking
about
connectors
today,
I
just
want
to
do
a
quick
recap
of
the
types
of
connectors
so
that
everything
makes
sense
as
we
get
going.
Power
Platform
connectors
span
three
separate
products
and
technically
a
little
more,
but
predominantly
power,
apps
power,
automate
and
Azure
logic.
Apps
we
have
one
type
of
connector,
which
is
the
custom
connector.
These
connectors
are
curtailed
to
your
specific
environment
and
can
be
deployed
in
that
space.
Then
we
have
shared
connectors,
which
are
the
ones
that
we
are
predominantly
going
to
be
focusing
on.
A
Today.
They
include
first
party
connectors
connectors
that
were
made
and
deployed
from
Microsoft,
so
think
about
SharePoint
Excel
Outlook
those
types
we
also
have
third-party
verified
Publishers.
So
those
are
external
Publishers
that
own
the
API
that
they
are
leveraging.
Some
really
good
examples
of
those
include
Adobe
and
DocuSign.
They
Leverage
The
API
that
they
own
in
order
to
make
and
share
this
connector.
So
it's
publicly
available
to
all,
and
the
last
is
the
independent
publisher
connector.
A
These
connectors
are
made
by
the
non-api
owners
leveraging
open
source
code
in
order
to
create
connectors
and
share
with
everybody.
We
call
these
oftentimes
Community
contributions
and
we
actually
will
have
an
independent
publisher
demo,
his
connector
with
us
today,
Sean
Kelly,
is
here,
and
he
leveraged
the
Microsoft
learn
API
to
create
a
connector
just
maybe
two
months
ago,
right
Sean,
pretty
recent,
so
super
excited
to
have
that
demo.
Today,
as
always,
we
will
do
a
connector
count,
update
just
to
share
with
you
guys.
A
So
in
December
we
cross
the
900
total
shared
connectors
threshold
with
you
guys,
and
it
has
been
less
than
two
months
and
we
have
already
garnered
40
more
internally.
This
is
a
huge
huge
deal
because
we
had
a
goal
of
growing
to
a
thousand
total
connectors
by
July
of
2023,
with
an
internal
goal
of
hitting
900
by
end
of
2022,
so
that
basically
means
that
we
are
40
of
the
way
of
our
goal
only
a
month
and
a
week
into
2023.
A
So
we
are
really
doing
a
fantastic
job,
and
that
is
much
due
to
the
contributions
of
you
guys
as
community
members,
as
well
as
our
incredible
certification
team
I
actually
want
to
give
a
quick
shout
out
to
I'm
Jed
I'm
Jed
is
our
certification
program
manager.
For
some
of
you
guys,
you
probably
will
recognize
his
name
in
our
GitHub
repo.
He
actually
has
published
three
of
his
very
first
connectors
as
well
this
month,
so
awesome
shout
out
to
amjad
since
the
last
time
we
spoke
a
month
ago
on
I
believe
January
11th.
A
We
have
added
27
New
connectors
into
our
total
ecosystem.
So
again,
this
spans
powerapps
power,
automate
and
Azure
logic,
apps,
13
of
which
are
from
Community
contributions
of
independent
Publishers.
We
now
have
almost
the
same
quantity
of
independent
publisher
connectors
as
we
do
first
party
connectors,
which
is
really
incredible.
That
just
shows
how
involved
the
community
is.
We
are
at
232,
IP,
233,
first
party
and
475
from
verify
Publishers.
So
those
are
those
core
API
owners.
A
If
we
keep
going
I
just
wanted
to
show
you
guys
some
screen
recordings
that
I
took
from
a
really
awesome
demo
by
an
independent
publisher.
So
a
lot
of
times
a
feedback
or
criticism
of
the
independent
publisher
program,
which
is
entirely
not
valid,
is
that
these
these
connectors
are
fluffy.
These
connectors
don't
have
business,
use
case
scenarios
and
that
could
not
be
further
from
the
truth.
A
A
couple
of
months
ago,
Robin,
one
of
our
independent
Publishers,
contributed
by
creating
an
open,
AI
connector,
and
this
came
out
months
back,
but
you
know
what's
hot
right
now:
nothing's
hotter
than
open
AI
right
now,
so
we
actually
have
on
YouTube.
You
can
find
in
our
in
our
demos
playlist
a
demo
from
Robin
of
his
connector,
but
I
took
some
screen
recordings
of
this.
Just
to
show
you
guys
how
awesome
this
use
case
is
hi
Daniel
I
see
you
just
popped
in
showing
off
the
open,
AI
connector.
A
We
are
so
here
it
is
being
leveraged
in
a
flow
and
he's
looking
at
the
open,
AI
connector
and
using
the
gpt3
action
so
from
here.
He
asked
it
in
a
prompt.
What's
your
favorite
animal
and
why
and
also
I
want
you
to
tell
me
about
the
size
and
weight
of
this
animal.
He
goes
and
he
runs
the
flow
and
it
takes
a
few
seconds
to
run
and
from
here
it's
going
to
give
him
back
a
response.
A
So
the
gpt3
has
completed
the
prompt
and
he
can
scroll
down
and
see
the
question
he
asked
and
the
answer
is:
elephants
are
my
favorite
they're,
intelligent
and
loyal,
and
they
can
weigh
six
or
seven
tons.
So
this
is
pretty
awesome,
it's
exactly
just
like
qpt3,
and
that's
only
one
of
the
three
use
case
scenarios
that
he
was
able
to
share
with
us.
Let's
keep
going
the
next
one
is
he
integrates
gpt3
into
a
powerapps
and
it
kind
of
is
reminiscent
of
a
power
virtual
agent
actually
because
creates
a
little
chat
bot
with
it.
A
He
asks
it
what's
your
favorite
movie
and
he
says
that
his
favorite
movie
is
Shawshank.
Redemption
did
I
just
gender,
the
chatbot
I
did
the
general
bot
says
it's:
their
favorite
movie
is
Shawshank
Redemption,
which
is
actually
my
dad's
favorite
movie
as
well.
Then
Robin
asked
for
a
short
synopsis
of
Shawshank
and
he's
able
to
give
him
back
a
whole
paragraph
about
why
Shawshank
is
awesome.
A
And
the
last
use
case
I
wanted
to
share
with
you
all.
Is
this
sample
data
generator
that
Robin
made?
Also
in
a
powerapps?
This
one
is
really
cool,
because
there
were
two
separate
filtering
capabilities
that
were
added
to
this
sample
data
generator.
So
initially
Robin
asked
for
capitals
of
European
cities
and
he
gets
Paris
London,
Rome,
Madrid
and
Berlin.
A
A
A
A
Let's
go
to
the
next
slide
and
the
last
thing
I
wanted
to
share
with
you
all
is
that
upcoming
this
month
in
about
I
believe
two
and
a
half
weeks
is
the
global
Power
Platform
boot
camp
takes
place
from
February
24th
to
February
25th,
and
you
can
find
out
more
about
it
on
powerplatformbootcamp.com.
Why
is
this
Global?
Well,
as
we
were
talking
about
before
the
call?
One
of
the
events
are
taking
place
in
New
York,
actually
in
the
Times
Square
Microsoft
Office,
but
there
are
I
believe
something
like
60.
A
Other
cities
at
this
event
is
taking
place
in
so
you
can
probably
find
an
event
to
attend.
This
event
is
a
live
event,
so
you
can
actually
go
in
network
meet
other
people
on
the
Power
Platform
Community,
it's
being
hosted
by
externals,
predominantly
MVPs
and
community
members
super
involved
with
the
Power
Platform
and
we'll
have
basically
an
entire
day
of
speakers
and
sessions,
so
that
you
can
learn
more
about
topics
of
your
interest
and
it's
not
officially
official
yet,
but
you
may
find
find
somebody
familiar
aka
me
in
the
Times
Square
Edition.
A
A
B
Is
yeah
yeah,
so
hi
I'm,
Chris,
guardi,
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,
foreign.
B
So,
let's
talk
about
Power,
Platform
ilm,
so
I'll
run
through
Alm
I'll
run
through
kind
of
Power,
Platform
Ln,
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
lifecycle.
Management
of
applications
includes
governance,
deployment
and
maintenance.
We
aim
to
drive
efficiency
through
predictable
and
repeatable
software
delivery.
B
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.
B
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.
B
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
aln
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.
B
B
So
Solutions
are
another
important
part
of
Alm
solutions.
They
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.
B
So,
with
the
with
build
tools
and
Source
control,
you
can
automate
Alm
Source
control
is
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.
B
B
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.
B
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.
B
Of
the
the
things
that
you
move
in
between
environments.
Security
is
an
important
concept
using
permissions
and
security
to
make
sure
that
the
things
that
are
in
environments
are
only
accessed
by
the
people
that
you
want
and
then
there's
a
kind
of
merging
capability
around
analytics.
And
so
in
the
last
year
we
made
available
a
tenant-wide
analytics
and
reports
for
Power
Platform
resources,
so
those
are
those
are
certainly
a
useful
tool
to
be
aware
of.
B
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.
B
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
test
and
production
environments.
You
need
to
have
maker
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.
B
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.
B
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.
B
So
what
we've
recently
made
available
is:
is
pipelines
Power,
Platform
pipelines.
There
was
a
blog
post
about
this
in
December.
There
is
a
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.
B
So
if
I
can
summarize
it
administrators
will
set
up
a
pipeline,
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.
B
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.
B
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.
B
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.
B
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.
B
B
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.
B
B
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
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.
B
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.
B
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.
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.
B
Okay
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.
B
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.
B
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.
So
that's
that'll
be
something
fun
to
look
forward
to
and
then
definitely
an
a
help
in
terms
of
Alm
capabilities
where
things
would
just
show
up
in
Source
control
automatically.
B
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.
B
B
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
pool
mechanism,
so
it
should
be
a
really
exciting
to
to
see
that.
B
A
C
B
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.
B
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.
D
B
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.
B
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.
A
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,.
B
E
A
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
B
B
There's
some
interplay
there,
some
extensibility,
that
the
the
the
team
is
still
working
on
will
pipelines
replace
the
Alum
accelerator
app,
not
in
the
near
term
in
the
yeah
I.
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
here.
B
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.
If
you
were
starting
today,
would
you
would
you
be
able
to
use
the
the
Power
Platform
pipelines
solution
pipelines
instead
of
the
AMX
Alm
accelerator,
app
I?
F
A
B
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.
A
Awesome,
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.
B
A
D
D
Now
I'll
I'll
just
plug
some
of
these
I'm
not
going
to
go
through
all
the
docs
or
anything
but
I'll
plug
them
into
the
into
the
charts.
If
people
want
to
read
afterwards,
but
basically
you've
got
this
API
endpoint,
which
is
going
to
access
all
of
that
content,
it's
a
huge,
a
huge
Json
object.
It's
just
that
single
endpoint.
So
if
you
want
to
access,
if
you
want
to
access
certifications
or
learning
paths
or
modules
or
whatever
it
is
from
that
catalog,
you
hit
that
endpoint
and
you
you
provide
a
type.
D
If
you
want
to
filter
it
down
right.
So
that's
basically
what
what
the
custom
connector
wrapped
around
so
coming
into
the
the
custom
connector
definition.
Basically
here
we
we
have
this
independent
publisher
one.
This
is
a
Microsoft
API,
but
I
published
a
connector.
Therefore
independent
publisher,
So
within
this
we've
got
a
single
action,
because
we've
got
that
single
endpoint
to
hit,
and
then
we
pass
in
parameters
the
critical
one
really
is
the
type.
D
If
you
don't
want
to
return
everything
from
that
catalog,
you
need
to
provide
a
type
I've
tried
to
kind
of
give
detailed
description
so
that,
if
you're
in
power
automate
or
in
powerapps,
using
this
that
you'll
get
those
prompts
including
examples.
So
you
can
say:
okay
well
the
example.
Here
it's
a
comma
separated
string.
D
This
would
return
modules
and
learning
paths,
so
you're
not
restricted
to
returning
a
single
type,
for
example,
and
it's
the
same
for
basically
all
of
these
and
you've
got
levels
rules
products
if
you're
familiar
with
going
into
Microsoft,
learn
I
hope
most
of
you
are,
and
you
can
filter
down
for
different
products.
You
know
beginner
Advanced
intermediate.
All
of
those
are
basically
represented
here
as
parameters,
so
that's
basically
what
the
connector
does.
D
So
I've
got
a
a
flow
here
that
I
just
created
earlier
and
I've
always
wanted
to
say
here's
one
I
made
earlier.
So
there
we
go
and
we've
got
the.
This
is
just
an
instant
flow
and
I've
I've
got
a
trigger
here
and
I'm
basically
want
to
capture
the
type
from
the
user,
because
I
don't
want
to
return
everything
from
that
from
that
API.
So,
basically
I've,
provided
you
know
a
text
drop-down
list
that
would
be
kind
of
captured
from
the
user.
D
I'll
probably
just
delete
this,
and
just
add
it
again
just
to
show
it's
not
that
difficult,
but
adding
a
new
Step
we're
going
to
look
for
the
Microsoft,
learn
connector
and
then
we've
got
all
of
the
kind
of
documentation
gets
returned
there.
If
I
select
this,
you
can
see
it's
just
that
single
action,
that's
there,
but
then
we've
got
all
of
this,
and
this
is
just
the
exact
same
text
that
we
saw
from
the
documentation
right.
So
that's
just
coming
through.
D
So
if
you
hover
over
any
of
these
you'll
get
a
kind
of
description
about
what
what
is
expecting
with
an
example
of
what
would
be
acceptable
at
the
end.
So
in
this
case,
I've
got
a
parameter
here
called
content
type.
So
that's
for
my
type
property,
so
I'm
going
to
come
in
here
and
just
dynamically
grab
the
content
type
from
the
input
and
that's
fine
I
won't
do
any
further
filtering
here.
I'll
show
you
further
filtering
in
the
canvas
app.
So
if
I
save
this.
D
So
let's
just
hit
that
endpoint
and
if
we
look
at
the
output,
we
should
just
see
courses
Okay.
So
we've
just
returned
courses
from
that
API
and
we've
got
the
various
different
courses
there
and
you'll
see
it
provides.
It
returns
a
lot
of
metadata
there
as
well.
So
it's
quite
useful
if
you
want
to
build
your
own
LMS,
for
example,
and
then
let's
try
another
one,
so
I'll
just
test
it
one
more
time
and
grab
some
learning
paths
or
all
learning
paths.
In
this
case.
D
Okay,
there
we
go
so
very
simple
and
then
in
the
learning
Parts
we've
got.
You
know
the
metadata
there,
like
the
summary,
what
rows
it's
for,
what
products
it's
applicable
for
the
subjects,
the
unique
identifier
and
other
things
like
the
modules
so
we've
in
for
this
particular
one
which
is
related
to
Azure.
We've
got
these
six
modules
and
that's
the
unique
identifier
of
the
modules
so
I'll
be
kind
of
I'm
using
that
in
in
the
canvas
app.
D
So
that's
kind
of
why
I'm
pointing
that
out
right
now,
so
that's
it
very
simple
how
you
use
it?
Hopefully,
hopefully,
the
if
you
are
using
it
and
you
know
the
the
tooltips
and
the
description
should
kind
of
clarify
how
to
use
it.
My
details
have
been
shared,
so
if
anybody
gets
stuck,
I
reluctantly
agree
for
you
to
contact
me
for
support.
D
So,
let's
see
so
next
up,
we've
got
I
want
to
show
a
canvas
up,
so
I've
built
a
canvas
app
that
that
that
basically
accesses
the
the
content
and
displays
it
really.
It's
just
a
single
page
canvas
up
or
a
single
screen
with
a
few
galleries
in
place.
So
we've
got
a
couple
of
galleries
here
for
learning
Parts
modules
I'll
get
into
how
I
connected
to
the
connector
to
to
kind
of
populate
these
in
a
second.
D
But
if
I
jump
in
over
into
play
mode
now,
basically,
we've
got
the
the
it's.
It's
loading
all
learning
paths
by
default
and
then
it's
it's
applying
these
two
filters.
So
I've
got
a
couple
of
combo
boxes
here,
one
for
levels,
one
for
Rose,
as
we
saw
in
the
in
the
connector
in
the
parameters,
there's
probably
what
eight
or
nine
of
them
so
I
could
I
could
have
added
a
lot
more
I'm,
just
a
bit
lazy.
So
I
just
picked
these
as
a
start
point,
so
you
can
filter
change.
D
You
know
change
to,
say:
intermediate
developer
and
you've
got.
You
know,
integrates
with
power,
automated
flows.
You
can
see
it's
making
a
call
there
to
retrieve
the
actual
module
information,
because
one
thing
we
don't
get
in
the
learning
path
response
is
the
details
of
the
module.
We
only
get
the
unique
identifier
of
the
module,
as
we
saw
in
the
previous
step,
but
here
I
can
open
in
Microsoft,
learn
and
so
from
there
I
can
launch
the
learning
path
or,
if
I
want
to
launch
an
individual
module,
I
can
go
there
and
launch
the
module.
D
D
So
how?
How
do
we
leverage
that
that
connector
that's
been
published
to
access
this
content?
Well,
if
we
jump
back
into
edit
mode
again,
there's
the
the
two
main
galleries:
there's
the
gallery
for
the
learning
path
here
on
the
left
and
there's
a
gallery
on
the
right,
lower
right
there
for
modules.
So,
if
I
go
into
learning
paths,
the
first
thing
to
to
look
at
is
the
items
property.
D
So
this
is
the
that
single
endpoint
on
the
connector
get
learning
content
the
exact
same
endpoints
that
we
just
saw
in
power
automate,
and
then
we
can
optionally
pass
as
many
parameters
as
we
want
from
what
was
the
original
docs.
So
we've
got
all
of
these
different
parameters,
so
we
can
say
only
give
me
learning
paths
modified
in
the
last
X
days
or
since
the
last
date
or
give
me
them
with
this
role
or
this
level
Etc.
D
So
in
this
case,
I've
passed
in
the
Locale,
the
type,
the
level,
the
role
the
product
and
you
can
see
the
level
and
the
role
are
just
coming
from
that
combo
box,
the
the
level
combo
box
and
the
Royal
combo
box,
or
whatever
is
selected
on
the
screen.
There
you'll
also
see
there's
a
variable
for
a
product.
If
we
get
time,
I'll
show
you
how
that
works,
but
we're
basically
saying
from
that.
We
want
to
retrieve
learning
paths.
Okay,
so
that's
what
we're
presenting.
D
D
If
we
remember
the
response
that
we
get,
we
have
this
array
of
modules
so
I'm
just
using
that
to
then
go
off
and
get
the
details
for
the
modules,
because
I
want
I
want
more
information
other
than
the
unique
identifier.
So
that's
what
I'm
doing
in
the
on
select
for
the
for
the
gallery,
so
in
the
on
select
I'm,
basically,
I've
got
this
learning
path,
modules,
variable
and
I'm,
our
collection,
sorry
and
then
I'm
saying
for
each
module.
That
was
in
the
response
from
the
learning
path.
D
Call
so
remember
in
this
one:
it's
what
five
or
six
objects
in
that
array
so
for
each
of
those
modules.
I
want
to
Loop
through
with
the
unique
identifier
and
and
populate
this
collection
from
that
same
endpoint,
the
get
learning
content,
but
I
want
to
use
that
unique
identifier
that
we
got
previously
in
the
learning
path,
call
and
then
return
the
modules
and
that's
going
into
the
collection.
And
then,
if
we
go
over
here
now
we
see
the
collection
items.
Property
is
just
set
as
that
are
the
items
property
for
this.
D
So
when
I
come
here,
it's
these
kind
of
these
kind
of
buttons.
Here.
If
these
message
these
things
here,
so
that's
a
gallery
just
with
the
appended
levels
of
roles
and
products
just
to
kind
of
recreate
what
you
see
in
Microsoft
learn
because
they
do
the
same
thing
so
yeah
and
then
the
final
thing
I
wanted
to
talk
about
in
this
app
in
in
the
three
minutes.
That
I've
got
is
the
the
products
so
in
the
items:
property
I'm
using
a
variable
called
Product,
and
why
am
I
doing
that?
D
You'll
see
that
I'm
doing
some
things,
but
in
in
particular,
I
want
to
kind
of
look
at
the
the
product,
so
I'm
setting
a
default
product
of
Power
Platform.
That's
why
the
app
response
Returns
the
Power,
Platform
learning
Parts
by
default,
but
then
I'm
saying
if
you
are
passing
a
channel
ID
if
this
app
is
receives
a
channel
ID
then
change
that
product
depending
on
the
channel
and
that's
a
that's
a
channel
in
teams.
D
So
if
I've
got
the
dataverse
or
common
data
service
channel
in
teams,
I
only
want
to
return
the
common
data
service
or
dataverse
products
same
for
AI,
Builder
or
powerapps
Etc.
So
then
we
can
come
over
and
then
this
this
ID
here.
This
is
the
unique
identifier
of
the
channel
and
team,
so
I've
hard
coded
these
channels
from
my
particular
teams
instance.
So
if
I
jump
over
to
teams,
I've
got
a
Power
Platform
learning
team
with
all
of
these
channels.
D
This
should
be
passing
in
power-ups
as
the
product
in
that
variable
based
on
the
teams
channel.
So
I'm
only
getting
that
and
then,
if
I
go
to
Power
automate
I,
don't
have
it.
It's
quite
easy
to
add,
though
I
can
say,
add
a
power
up
and
then
I've
got
my
learn.
Catalog
save
and
now
this
should
be
passing
in
power.
Automate
I
had
to
do
that,
because
power
automate
was
the
subject
earlier.
I
didn't
want
them
to
feel
left
out
the
power
automate
product
team,
and
now
we've
got
our
our
product
being
set
there
right.
D
B
D
So
it
doesn't,
it
doesn't
return
the
document,
the
full
documentation
set,
it's
all
learning
content
based.
So
it's
learning
paths
and
underneath
that
modules
and
underneath
that
units
so
they're
the
kind
of
granularity
for
learning
paths
and
then
you've
got
certifications
and
things
like
that.
But
you
don't
actually
have
access
to
the
wider
documentation
base.
What
was
formerly
docs.microsoft.com,
so
you,
wouldn't
you,
wouldn't
return
all
of
the
Alm
pages,
for
example,
but
you
could
do
that
scenario
for
the
content
that
is
stored
there,
like
learning
paths
and
stuff
nice.
D
Well,
actually,
I'll
go
to
my
documentation,
so
the
I've
got
it
here.
So
supported
values
are
this?
So
that's:
what's
that's
what
you
can
return
from
the
API?
So
when
we're
thinking
about
Microsoft,
learn,
learning
path,
so
you've
got
learning
paths
at
the
top
can
contain
many
modules
and
each
module
can
contain
one
or
more
units.
So
you've
got
learning
paths,
modules
and
units.
You
can
also
return,
certifications
and
exams.
D
So
if
you
visualize
the
certifications
page
or
the
exams
page,
it
gives
you
metadata
back
there
with
the
related
products
and
stuff
like
that.
Everything
else
is
kind
of
like
metadata
like
the
levels,
the
roles,
the
products,
the
subjects
they're,
those
kind
of
filtering
attributes
so
that
they're
smaller.
F
D
Yeah,
you
could
go
in
and
just
change
the
type
to
exams,
and
then
it
would
return
all
exams
or
if
you
know
the
uid
at
the
unique,
unique
identifier
for
pl400.
You
can
pass
in
the
uid
parameter
with
that
with
that
pl400
uid,
and
it
will
just
return
that
single
exam
with
all
of
the
date.
The
details
of
that
exam,
not
the
questions
and
answers,
though.
F
A
A
The
wrong
button,
very
relatable,
I,
hope
you
all
enjoyed
this
stay
tuned
for
the
next
session.
We
run
I
believe
the
second
Wednesday
of
every
month,
so
next
time,
she'll
be
March
8th,
as
always
as
we
posted
on
LinkedIn
and
I
finally
found
a
way
to
send
this
to
you
guys
all
as
a
calendar
invite,
so
you
should
be
able
to
actually
go
and
save
that
locally
as
well.