►
From YouTube: Why build Power Platform Solutions in Microsoft Teams?
Description
Microsoft Teams is built for hybrid collaboration and delivers contextual information, automations and actions. Power Platform delivers bespoke functionality, connection to data and workflows. Microsoft is focused on bringing elements of Teams and Power Platform Suite together. In this 15-minute developer focused demo, delivered by Stuart McCarthy and Marcus Castro hear about app integration in Fabrikam Airport work shift management example and how to identify Power platform apps ripe for Teamifying. Preview 3 app integration features, deep dive next week.
This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on April 25, 2023.
Demo Presenters
• Stuart McCarthy (Microsoft)
• Marcus Castro (Microsoft)
Supporting materials
• Documentation - Create apps in Microsoft Teams by using Power Apps | https://learn.microsoft.com/power-apps/teams/create-apps-overview
• Documentation - Create low-code custom apps for Teams | https://learn.microsoft.com/microsoftteams/platform/samples/teams-low-code-solutions
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms/community/home
A
A
I
am
the
customer
PM
for
the
UK,
so
I
work
with
all
of
our
strategic
customers
to
help
them
get
the
most
added
teams
and
Marcus
is
my
partner
in
crime
for
Europe
and
doing
all
things
Solutions
and
and
development
and
Power
Platform
within
teams
as
well.
So
what
we're
keen
to
talk
to
you
about
today
is
why
build
Power
Solutions
inside
teams,
and
why
does
that
matter
to
our
end
users
and
to
our
customers
and
and
to
the
product?
A
But
we
have
a
way
to
go
for
collaboration
and
it's
really
bringing
in
some
of
the
contextual
information
from
applications
into
those
calls
and
chats
and
meetings
that
our
customers
are
having
at
an
Enterprise
level,
and
that
goes
for
your
third-party
tools,
but
also
for
your
line
of
business
tools
as
well.
So
when
we
think
about
applications
in
teams,
what
we've
found
is
that,
on
average,
people
have
about
10
apps
open
a
day,
they'll
be
switching
between
those
apps
like
25
times
a
day.
Now?
What
does
that
mean?
A
If
you
have
invested
in
a
Power
Platform
solution
outside
of
teams?
It
means
that
you've
got
this
unique
process.
You've
got
everyday
tasks
being
handled
by
That
Power
Platform
solution,
but
what
we're
regularly
seeing
is
that
people
are
going
to
be
jumping
across
that
application,
consuming
some
data
jumping
back
into
teams
and
calling
their
colleagues
and
having
a
conversation
about
it.
So
there's
lots
of
copy
and
pasting.
There's
lots
of
screenshots
of
information.
A
There's
lots
of
sharing
your
desktop
and
driving
that
that
meeting,
based
on
what
they're
seeing
inside
that
third-party
solution
and
use
this
kind
of
act
on
that
information.
So
they
might
make
a
decision
in
that
meeting
or
in
that
chat
about
something
they
want
to
do.
But
then,
when
it
comes
to
actioning,
it
they've
got
to
jump
back
into
that
power
solution
again.
A
They've
maybe
got
to
have
three
or
four
people
all
looking
at
the
same
information
in
that
Power
Platform
Solution,
that's
a
lot
of
waste
of
time
and
it
really
isn't
bringing
context
to
those
those
two
solutions
together.
So
what
we
really
want
to
do
is
encourage
our
customers
to
be
thinking
more
about
how
they
can
create
a
solution
both
with
the
Power
Platform
and
with
teams
coming
together
to
make
a
solution.
That's
better
than
some
of
its
parts.
A
It's
using
those
collaboration
features
inside
teams
to
enable
people
to
chat,
but
it's
bringing
that
bespoke
information
that
bespoke
functionality
that
someone's
created
within
the
Power
Platform.
So
we
can
streamline
access
to
chat
to
calling
meeting
features
of
teams.
We
can
enhance
the
existing
chats
and
meetings
and
side
teams,
avoiding
that
copy
and
paste.
A
So
if
we
have
a
look
at
an
example,
I've
been
working
with
airports
in
London,
where
they
have
a
program
of
work
called
here
to
help.
So
the
idea
behind
that
is
that
all
of
their
office
staff
are
supposed
to
sign
up
to
several
hid,
help
sessions
throughout
the
year
and
they
go
into
the
airport
and
they
will
support
their
security
team
or
their
customer
service
team
in
helping
with
customers
and
and
moving
the
process
forward
through
the
airport.
A
They'll
they'll
have
to
do
this
at
points
during
the
year
anyway,
but
often
when
there's
busy
periods,
Christmas
Easter,
that
sort
of
thing
they'll
be
pulled
into
Health
as
well.
So
they
used
to
do
this
by
creating
a
power
app
which
they
use
to
manage
all
of
their
shifts.
People
will
go
and
they
would
sign
up
to
a
shift
and
then,
when
their
shift
was
due
to
start
a
shift
manager
would
create
a
team
group
chat.
They
would
pull
in
people
from
that
shift.
A
Obviously,
there
are
some
shortfalls
here,
it's
great
that
they've
got
this,
this
power
app
driving
that
behavior
they're,
not
using
pen
and
paper
anymore,
which
is
the
main
thing,
but
by
by
not
automating
that
the
team
side
of
that
chat,
there's,
obviously,
errors
that
could
be
introduced
here.
We've
had
issues
before
where
people
haven't
been
added
into
the
chat,
so
they've
got
confused
about
what's
going
on,
there's
lots
of
duplication,
there's
lots
of
people
working
in
a
silo
and
not
really
understanding,
what's
going
on
a
lot
of
the
time.
A
So
what
we
did
with
this
customer
was
we
introduced
the
concept
of
bringing
their
Power
Platform
solution
and
teams
together
and
to
create
something
that
was
a
little
bit
more
automated
and
not
working
in
silos
anymore.
So
the
thing
that
we
did
initially,
as
you
can
see
on
the
left
here,
is
we
you
know
we
we
did
wrap
and
pin
that
up.
A
We,
we
said:
okay,
let's,
let's
grab
that
power
up,
let's
put
it
inside
a
team,
because
there
was
already
a
program
team
where
people
were
going
and
learning
about
the
program
learning
about
shifts
they
could
sign
up
to
so
we
figured
let's,
let's
get
the
app
in
the
place
where
they're
used
to
going
so
at
least
it's
easy
to
find.
That
was
step
number
one
to
make
it
easy
to
access
step.
Number
two
was
all
around
what
happens
once
that
shift
has
started
so
at
the
beginning
of
a
shift.
A
We
automatically
now
post
an
Adaptive
card
with
some
information
about
that
shift
into
a
channel,
so
different
different
channels
for
different
Terminals,
and
we
have
a
tag
automatically
created
based
on
the
people
who
are
assigned
to
that
shift.
So
we
post
the
Channel
with
information.
We
have
mention
people
in
the
tag,
which
means
everybody
inside
that
team
that
signed
up
as
a
program
they're
going
to
get
a
notification
if
they've
signed
up
to
that
shift
today,
they
can
then
have
conversations
based
on
that
shift.
They've
got
context
of
the
shift.
A
They
can
have
a
conversation
about
where
they
need
to
be
tell
people
if
they're
running
late
click,
a
button
that
they're
confirmed
on
site,
etc,
etc.
But
the
idea
here
is
we're
we're
letting
teams
breathe,
so
we're
able
to
do
things
like
share
FAQs
share
the
floor
plan
into
the
file
section
of
that
channel,
because
they
don't
change
they're
going
to
be
consistent
anyway,
so
we
may
as
well
just
have
them
then
be
similar.
We
can
also
have
people
scroll
up
and
see
the
previous
shift.
A
So
if
there's
anything
hanging
around
from
earlier
in
the
day,
issues
that
went
went
on
that
people
might
need
to
know
about
it's
very
easy
for
them
to
find
out
what
happened
and
and
therefore
perform
accordingly.
So
normally,
if
something
goes
wrong
with
with
the
automation
process,
people
can
self-serve.
If
I
know,
I'm
meant
to
be
on
a
shift
in
Terminal
5,
but
I
didn't
get
my
notification.
A
I
can
just
go
into
that
team,
see
Terminal
5
and
send
a
message
to
the
shift
leader
to
say:
hey
I
didn't
get
this
tag,
but
I
am
here
I'm
going
to
be
turning
up
today.
Let
me
know
where
you
want
me:
I
can
also
move
from
Terminal
5
Terminal
4
really
seamlessly.
So
we're
really
opening
up
a
lot
of
value
just
by
bringing
these
two
products
together
and
we've
been
getting
really
good
feedback
from
from
the
airport
about
how
this
is
going
to
work.
A
So
if
we
were
to
pin
our
tab
our
app
that
we
just
saw
inside
the
terminal,
5
Channel,
we
could
let
that
app
know
that
it's
in
the
terminal,
5
Channel,
it
could
behave
accordingly.
So
that's
that's
kind
of
Step
One
step
two
is
to
consider
what
would
it
look
like
if
we
pushed
information
from
the
app
into
teams?
So
if
I
had
a
shared
teams
button
inside
that
application?
A
What's
the
top
three
pieces
of
information
I
might
share
to
my
colleague
normally
I'm
going
to
give
them
a
call
I'm
going
to
tell
them
about
it?
But
this
is
a
bit
more
automatic.
We're
going
to
be
automating
that
so
one
of
those
three
bits
of
information
I
want
to
share
I
might
want
to
share
the
next
is
what
are
the
three
actions
that
we
might
then
do
after
we've?
Had
a
conversation,
do
I
find
a
task
to
myself
do
I
order
more
stock?
Do
I
close
something
as
done.
A
Those
sorts
of
things
really
help
us,
because
what
we
can
then
do
is
we
can
create
an
Adaptive
card
with
that
top
information
that
we
want
to
share
with
our
colleague
and
some
action
buttons
as
well,
so
that
once
we've
had
a
discussion
about
the
data
inside
that
card,
we
can
act
on
it
right
away
without
having
to
bounce
backwards
and
forwards
of
the
app
and
then
we
can
also
add
a
more
details.
Button,
and
the
important
thing
to
remember
is
that
we're
augmenting
this
app.
A
Now
we're
not
going
to
be
moving
all
of
the
punctuality
into
teams.
It
makes
sense
to
still
go
back
into
the
app
and
deep
link
into
a
certain
part
of
data
based
on
that
that
card
that
we
saw
there.
So
we've
we've
kind
of
done.
The
push
the
push
from
the
Athens
teams
now
we
think
about
the
other
way
around
what
if
I'm
pulling
information
from
Power
Platform
into
teams,
so
I
might
do
that
automatically.
Something
might
happen
where
I
want
to
set
a
trigger,
so
say
something
in
a
factory
goes
wrong.
A
A
So
if
I'm
having
a
discussion
with
my
colleagues,
I
might
want
to
click
on
my
message:
extension
and
pull
information
out
of
my
application
and
then
push
that
into
teams
again
using
the
same
adaptive
card
and
then
finally,
if
we're
thinking
about
contact
information
within
that
power
application,
maybe
there's
a
way
that
I
could
quickly
link
to
that
information
from
the
app.
So
if
I
have
a
phone
number
for
example,
or
a
chat
button,
so
I
can
very
easily
click
on
that
button.
B
Yep
thanks
short
yeah.
If
you
can
see
the
other
side
yeah
so
next
next
week,
I'm
gonna
be
here
again
to
present
a
sample
application
that
we
developed
and
that
basically
brings
life
everything
that's
towards
just
this
set
here.
So
at
this
example,
we
have
an
instance
application
and,
as
you
can
see,
we
have
a
team
there,
the
instance
team
with
different
channels.
They
have
a
saved
HR
and
supply
chain,
and
what
this
app
is
doing
is.
Is
that
context
aware
app?
B
So
it
knows
it's
running
on
the
instance
team,
and
it
knows
it's.
The
health
and
safety
channel,
so
I
can
filter
the
instance.
It
should
show
you
know
if
I
open
this
app
in
the
health
and
safety
team
I
want
to
see
only
health
and
safety
incidents.
So
what
that
does?
Is
that
saves
usage
time?
You
know
they
can
focus
only
on
the
information
that
they
need
to
see
and
they
need
to
work
on.
B
So
that's
totally
possible
to
do
with,
with
perhaps
by
using
the
teams,
integration
object
and
next
week,
I'm
gonna
actually
show
that
and
I
can
go
more
deep
on
the
technical.
How
you
can
do
that
yeah
other
thing
that
we
have
implemented
in
this
application
is
a
share
functionality.
So
imagine
I
have
a
gallery.
I
click
on
one,
instant
and
I
want
to
share
that
with
a
colleague
to
have
a
discussion
about
it
right.
B
So
we
just
click
one
button
there
and
we
have
the
option
to
share
with
someone
or
sharing
a
channel,
and
when
you
do
that,
we
trigger
a
power
automate
flow.
That's
gonna
send
an
adapt
card
like
this
one
in
the
middle
there,
and
it
has
all
the
import
most
important
information
about
the
incident.
So
you
know
people
can
straight
away,
have
a
read
on
and
have
a
context
of
what's
going
on
and
we
provide
an
assignment
button.
B
So
that's
what
we
meant
about
having
some
quick
reactions,
so
the
user
doesn't
have
to
open
that
search
for
the
incident
to
then
assign
that
instead
to
them
with
one
click
one
under
that
card,
they
can
do
that
straight
away
from
there
and
also
they
can
have
discussions
there
right.
They
can
mention
people
and
have
that
contextual
conversation
about
that
instead,
so
other
thing
that
they
can
do
is
click
that
view
details
button
and
that
is
basically
a
deep
link
to
the
power
app.
B
So
if
you
click
that
view
details,
button
is
basically
a
deep
link,
so
it
opens
the
app
in
a
personal
scope
and
it
could
be
on
the
on
the
channel
as
well,
but
it
opens
straight
away
on
that
instant
and
again,
this
just
saves
time
for
the
user
to
go
straight
away,
but
they
need
to
go
other
thing
that
we
recommend
using
a
lot
is
like
providing
a
quick
button.
Should
we
start
a
shot
with
someone.
B
So
in
this
case,
if
they
instant
someone
shared
that
with
you
or
someone
is
assigned
to
that
instant,
just
provide
one
action
there
with
one
click.
Your
redirect
to
a
chat
with
that
person
that
again
just
saves
user
time
and
yeah
looks
very
cool,
so
yeah
next
week,
I'm
going
to
present
all
of
that
and
go
a
little
bit
more
deeper
on
the
technical
side
of
how
you
can
Implement
that
and
the
simple
app
we're
going
to
upload
that
to
GitHub
as
well
and
make
as
a
sample
that
you
all
can
download
from
GitHub
news.