►
From YouTube: Microsoft Teams community call - March 2021
Description
This month's community call featured a look at the Teams Community Sample Repository, then two Community Sample Showcase entries: 1) Business to Citizen Consumer Communication Bot and 2) Bot Composer, followed by a presentation on Utilizing Mobile First Device Capabilities for Teams Apps and 10 minute Q&A. The call was hosted by Jun Pak (Microsoft). Microsoft presenters included Wajeed Shaikh, Sathya Raveendran, Arun Kumar Anaparthi, Bob German, Anuj Bahl and Shubham Chauhan. Recorded on February 16, 2021. Thank for attending the call or viewing on demand.
Stay connected:
• Full post for this call - https://aka.ms/m365pnp/community/blog
• Twitter - https://twitter.com/microsoft365dev
• YouTube - https://aka.ms/M365DevYouTube
• Blogs - https://aka.ms/M365DevBlog
• Microsoft 365 PnP Blog - https://aka.ms/m365pnp/community/blog
• Recurrent Invite - https://aka.ms/microsoftteamscommunitycall
A
A
Then
we'll
move
on
to
our
couple
pair
of
community
sample
showcases,
where
satya
and
aaron
will
be
going
over
the
business
to
citizen,
consumer
communication
bot
and
then
the
next
showcase
will
have
our
very
own
bob
german,
who
will
go
over
the
his
bot
composer
and
then
lastly,
we'll
have
a
session
where
I'll
have
shebam
and
anuj
from
our
mobile
platform
team.
Who
will
go
over
utilizing
mobile
first
device
capabilities
for
teams
apps.
B
Hi
everyone
good
morning,
my
name
is
vajid
and
I'm
a
program
manager
for
developer
community
responses.
We
answer
queries
posted
on
dev,
community
forums
like
stackoverflow,
github
and
microsoft
qna.
Today,
I
am
going
to
showcase
our
consolidated
sample
code,
repo
for
microsoft
teams
platform
going
forward.
This
is
going
to
be
the
place
for
all
the
official
sample
codes.
B
B
All
these
samples
are
divided
based
on
platform
capabilities.
So
you
can,
you
can
easily
find
them.
Each
of
the
sample
has
a
deep
link
to
a
specific
folder
and
you
could
click
on
that
to
go
to
that.
Folder
individual
sample
code
have
their
own
readme
file.
You
can
look
through
the
readme
file
and
this
contains
step
step-by-step
guide
for
setting
it
up
locally.
B
B
Please
go
ahead
and
try
this
out.
Please
watch
the
repo
for
the
changes
which
are
coming.
If
you
find
any
issue
in
sample
while
trying
out
please
raise
it
in
issues
section.
If
you
have
any
feedback
or
suggestion,
please
go
ahead
and
use
the
discussions
tab
and
you
could
add
it
there.
You
could
suggest
new
sample
code
ideas
on
that
as
well.
B
A
C
I
am
also
a
pm
as
part
of
teams
ensuring-
and
I
have
arun
from
my
team.
All
of
us
who
is
going
to
be
presenting
along
with
me
for
this
particular
sample
showcase.
What
we
have
in
this
month's
community
showcase
is
a
business
to
citizen
communication
chat
app.
This
particular
sample
is
extremely
powerful
to
light
up
multiple
different
real-world
applications
before
we
move
on
to
the
actual
app
itself
or
a
demo
part
of
it.
I
want
to
be
very
clear
on
what
we
mean
by
citizen
user.
C
Here,
a
citizen
user
is
basically
a
user
who
might
not
have
a
teams
app
on
their
phone
or
even
a
team's
license.
They
use
consumer
chat,
applications
native
mobile
apps
and
they
might
be
using
these
kind
of
like
chat
applications
to
talk
to
businesses.
Imagine
someone
talking
to
a
customer
support
center
using
a
native
mobile
app
of
that
particular
business
or
using
one
of
the
business
accounts
in
any
of
the
consumer
chat
applications
right.
C
These
are
the
citizen
users
and
they
have
no
reason
to
have
a
team's
license
or
even
a
team's
mobile
app
installed
on
their
mobile
with
those
definitions.
Out
of
our
way,
let's
take
a
look
at
the
capabilities
that
we
have
as
part
of
the
sample
app
using
this
app.
You
can
develop
a
bot
that
is
accessible
over
a
web
interface
and
a
team's
interface.
Think
of
bot
as
this
one
central
circle.
On
one
side,
you
have
a
teams
channel
basically
a
way,
an
interface
for
your
teams
to
talk
to
the
bot.
C
On
the
other
side,
you
have
a
web
channel,
a
web
interface
to
talk
to
the
bot
it.
It
uses
microsoft
bot
framework
to
establish
a
real-time
chat
between
a
citizen
user
who
has
no
team's
license
and
a
business
licensed
user
who
uses
teams.
The
citizen
user
in
this
samples
case
is
using
is
going
to
be
using
a
web
page
as
their
interface.
C
The
sample
shows
the
use
of
graph
apis
to
quickly
create
meetings
and
share
meeting
join
information
with
both
parties.
It
also
makes
use
of
graph
apis
to
allow
transfer
of
files.
Because,
often
when
you
chat
between
two
parties,
there
is
going
to
be
a
transfer
of
files.
So
how
can
that
transfer
happen
between
a
citizen
user
and
the
business
user
is
something
that
we
will
show
in
the
sample
app?
And,
lastly,
it
show
it
showcases
the
righteous
use
of
channel
threats.
C
We
have
threaded
conversations
in
channels,
as
you
all
know
how
we
can
use
that
effectively
to
have
parallel
conversations
with
different
users.
At
the
same
time.
That's
that's
something
that
we
will
show
here
with
that.
Let's
move
on
to
the
demo
of
the
app
itself.
What
you
see
over
here
is
basically
the
app
in
action
on
the
right
side
that
you
see
over
here
is
basically
a
web
interface.
C
If
you
see
it's
a
normal
website,
we
have
gone
into
a
website,
and
in
this
website
there
is
a
bot
that
allows
users
to
start
a
chat
request,
and
in
this
case
this
particular
user
raises
a
chat
request
with
entering
their
name,
the
information
related
to
their
phone
number,
their
email
id
and
a
preliminary
request,
a
query
that
they
want
to
get
addressed.
Now
this
is
a
citizen
user.
C
They
don't
have
teams,
so
they
are
using
a
normal
website
and
when
they
post,
that
particular
request
appears
on
the
left
side
on
teens
for
a
licensed
user.
Imagine
an
agent
is
sitting
over
here
now.
This
agent
is
at
mentioning
the
bot
over
here
and
talks
back
to
the
app
now.
What
you
see
over
here
is,
in
addition
to
just
posting
it
as
a
query.
The
bot
also
shows
the
person's
name.
It
takes
the
first
name
and
last
name
from
here
and
does
a
user
attribution
over
here?
That's
something!
C
C
The
agent
can
actually
open
the
pdf
file
directly,
which
is
stored
on
sharepoint
and
answer
on
top
of
it
by
mentioning
the
bot
again.
So,
essentially,
what
you
see
is
actually
a
live
chat.
That's
happening
between
someone
who
is
using
a
web
browser,
a
bot
on
a
browser
and
someone
who
is
using
a
teams
as
an
interface
now
chat
is
good.
It's
good
to
have
real-time
chat,
but
imagine
like
you
want
to
escalate
it
into
a
call.
In
this
case
they
have
identified
a
problem.
C
They
have
verified
that
problem
using
file
sharing
and
all
of
that
now
they
want
to
have
a
quick
resolution
by
getting
on
an
actual
call.
It
could
be
a
video
call,
audio
call
whatever
you
desire,
and
then
they
want
to
map
it
out
over
in
the
call,
and
that's
what
you
see
over
here,
clicking
on
schedule,
painting
you
have
meeting
joint
information
thrown
on
both
sides
of
the
chat
and
both
parties
can
get
on
an
ad
hoc
call
in
this
manner.
C
Now
the
thing
that
you
need
to
keep
in
mind
is
this
person
is
not
going
to
be
licensed,
so
they
can
join
as
a
guest
user.
As
you
see
over
here,
they
can
just
type
in
their
name
and
join
as
a
guest
user,
and
they
will
have
all
the
capabilities
in
terms
of
like
a
video
call,
audio
call
over
teams.
Maybe.
C
In
addition
to
that,
this
is
not
just
on
web
client
I'll
show
a
mobile
client
as
well
over
here.
What
this
app
also
does
is
all
the
files
that
you
share
over
here
is
neatly
organized
in
the
files
tab.
If
you
see
over
here
in
this
particular
screenshot
you'll
be
able
to
see
for
this
particular
chat
session,
a
folder
is
created
and
within
that
folder
all
the
files
shared
by
this
user
is
neatly
organized,
so
it
also
uses
file
apis.
C
To
does
this,
and
that's
also
an
interesting
thing,
and
it's
not
applicable
just
for
a
desktop
or
web
client.
You
can
actually
access
the
browser
via
mobile
pens
as
well
on
the
on
the
interface
and
the
user.
Experience
remains
the
same
users
can
talk
to
the
agents
on
the
team
site
and
they'll
be
able
to
get
real-time
chat
information
from
both
sides.
C
This
is
something
that
shows
the
mobile
usage
of
this,
and
the
last
part
that
I
wanted
to
talk
about
in
this
particular
example.
Is
it
the
we
have
used
made
use
of
channels
over
here
to
post
new
requests,
so
each
request
that
gets
created
by
this
person
over
here
gets
created
as
a
new
channel
thread
on
this
side.
So
you
can
have
multiple
conversations
in
parallel.
C
Imagine
there
is
a
customer
one
with
the
problem
customer
two
with
another
problem
and
customer
three
with
the
problem
all
of
this
gets
created
as
different
channel
threads
and
by
mentioning
the
bot
as
a
reply
to
that
particular
thread.
The
app
intelligently
understands
that
they
are
speaking
to
this
particular
customer,
not
another
customer
and
routes,
the
replace
to
the
right
window
over
here.
C
C
Now
what
you
see
over
here
is
basically
a
construct,
a
framework
and
and
that's
what
a
sample
app
is
right.
It's
essentially
a
building
block
using
which
you
can
essentially
light
up
multiple
scenarios
across
different
different
industries.
Think
of
this
in
a
finance
and
banking
industry,
the
business
and
the
person
who
is
on
the
team
side
could
be
a
banking
relationship
manager,
whereas
from
the
customer
end
could
be
a
banking
customer
who
is
on
the
bank's
website
and
talking
to
a
board
and
asked
to
be
contact
to
an
agent
in
a
healthcare
site.
C
This
could
be
someone
a
doctor
on
the
team
side
who,
who
is
doing
a
virtual
consult
for
a
patient
who
is
on
the
hospital
hospital
website
or
hospital
mobile
app
in
a
retail
way.
You
can
have
a
customer
who
is
shopping
on
a
website
on
the
retail
customers
website,
and
then
they
have
a
query.
They
want
to
get
content
to
a
shopping
assistant,
an
associate
and
they
can
create
a
request
on
the
bot
and
they
can
get
connected
with
the
assistant
right
over
who
is
who
is
working
on
teams.
C
The
same
goes
for
other
industries
as
well.
What
you
saw
here
is
basically
a
basic
framework,
but
by
simple
customization
and
extending
it
is
applicable
across
multiple
scenarios
in
different
industries
and
just
to
highlight
that
point
over
here
right.
What
you
saw
is
basically
a
citizen
user
on
this
side,
an
agent
on
this
side,
and
we
used
one
outreach
channel
the
website
channel
that
you
saw
over
here
and
we
use
the
communication
methods.
All
of
this
that
you
see
over
here
now,
in
addition
to
that,
based
on
your
own
requirements.
C
Basically,
if
you
are
designing
it
or
you
are
etching
and
extending
it
for
a
particular
customer,
you
can
have
the
channels
in
which
the
customer
is
already
present
if
they,
if
they
are
already
present
in
in
different
consumer
channels,
you
can
have
this
work
in
other
channels
as
well,
not
just
in
web
chat,
and
in
addition
to
that,
you
can
also
provide
value
added
services.
In
this
case,
we
currently
have
the
sharing
and
receiving
files.
C
Information
is
something
that
we
have
added
as
a
value
added
services,
but
you
can
actually
connect
this
to
a
crm
and
show
up
the
incoming
customers
information
during
the
meeting
for
the
agent
to
better
prepare
an
answer
for
a
question,
even
even
more
informed.
So
all
of
these
value-added
services
are
ideas
that
I
am
proposing
to
you.
You
can
make
use
of
this
base
framework
the
sample
app,
that
we
are
providing
to
add
all
of
this
and
make
it
as
a
full
enriched
solution.
D
Hey
hi,
all,
as
I
said,
we
used
to
complete
this
sample
conversation
id
to
identify
the
channel
threads
so
based
on
the
conversation
id
we
are.
You
know
giving
a
reply
to
that
particular
message.
So
for
that
we
have
not
used
any
graph
api
for
that,
so
we
used
a
bar
dot
conversation
id
in
that
channel
thread
and
we
stored
that
information
into
cosmos
db
and
based
on
that,
we
are
trying
to
replay
that
so
that's
the
first
one
we
used
as
part
of
the
sample
for
creating
a
new
folder
or
creating
a
files.
D
We
use
this
folder
graph
api
with
the
delegated
permission.
At
this
moment,
everything
I
worked
on.
My
sample
are
delegated
permission
because
we
are
just
demonstrating
for
one
user
account
so
to
create
any
file
and
to
update
the
same
file.
So
we
use
this
create
new
folder
in
a
drive
and
graph
api.
So
with
this
help
we
are
able
to
create,
or
we
can
update,
also
the
file
in
the
same
folder.
D
Based
on
that,
so
based
on
the
conversation
id
I
created
one
folder
inside
that
folder,
I
pasted
all
the
files
and
all
and
the
last
one
is
create
event
file,
which
we
already
explained
in
my
last
sample
as
part
of
meeting
extensibility
channel.
So
using
create
online
event
meeting
you
can
create
a
online
craft
api
meeting
and
both
the
parties
can
join
the
call
and
they
can
talk
and
they
can
resolve
that
issue.
D
C
So,
thank
you.
So,
in
addition
to
the
channel
that
we
had
shown
in
addition
to
the
web
chat,
the
microsoft
bot
framework
can
also
be
extended
to
work
in
other
channels.
That's
available
in
this
documentation,
which
is
provided
in
the
github
sample
as
well,
so
feel
free
to
take
a
look
at
this.
Take
a
look
at
all
the
samples
and
see
if
your
customer
or
if
the
person
that
you're
building
this
for
has
presence
in
other
channels.
You
can
also
extend
it
to
other
channels
over
to
youtube.
A
E
Yeah
I'll
just
jump
right
in
there,
hello,
everyone,
so
yeah
I'm!
This
is
a
little
bit
of
a
different,
maybe
a
little
bit
of
a
change
of
pace,
but
I
recently
became
more
acquainted
with
bot
composer
and
since
I
don't
think
it
gets
really
a
ton
of
love,
I
want
to
actually
build
a
demo
in
front
of
you
right
now
and
show
you
how
easy
it
is
to
build
a
bot
for
teams
that
has
custom
logic
in
it
and
that
calls
the
microsoft
graph.
E
So
let's
just
do
it.
Here's
the
bot
composer,
if
you've
never
seen
this
before
it
is
available
as
both
a
desktop
application
and
as
a
web
service.
So
you
could
install
it
on
your
own
web
server.
If
you
want
I'm
going
to
make
a
brand
new
bot
from
scratch
and
I'll
go
ahead
and
give
it
a
name-
and
it's
just
a
very
simple
little
bot
and
okay-
and
this
is
what
the
composer
looks
like
so,
if
you're
familiar
with
bots
at
all,
underneath
of
the
first
simple
bot,
that's
the
bot.
E
There
is
a
dialog
called
simple
bot
and
a
greeting
inside
that
dialog.
The
first
thing
I'm
going
to
do
is
to
simplify
it,
I'm
just
going
to
go
over
to
the
regex
recognizer.
This
is
what
recognizes
what
the
user
means
when
they
type
something
the
default
is
lewis,
which
is
a
great
choice,
but
for
the
purposes
of
a
very
quick
demo,
and
also
not
requiring
you
to
stand
up
louis
necessarily
just
going
to
use
regex
here
and
notice
the
greeting-
and
this
will
look
familiar
to
people
who
have
used
other
low
code
tools.
E
It's
just
going
to
loop
through
this
is
a
this
is
actually
triggered
by
a
thing
called
a
conversation
update.
So
whenever
anyone
enters
or
leaves
the
conversation,
it's
going
to
loop
through
all
the
members
of
the
conversation
and
send
them
all
a
greeting
message.
So,
let's
add
another
trigger
here
and
this
trigger
is
going
to
be.
I
recognized
an
intent
and
just
the
word,
how
are
the
word?
How
will
trigger
it?
It's
just
a
super
simple.
I
just
want
to
get
something
going
kind
of
hello,
world
type
example.
E
E
E
You
have
to
copy
it
somewhere,
safe,
and
so
that's
the
other
thing
that
you'll
need
for
bot
composer.
Okay,
so
our
bot
is
registered.
Let's
go
back
to
the
bot,
I'm
going
to
go
into
the
tools
and
paste
in
that
app
id
that
I
saved
before
and
then
I'll
put
in
that
app
password.
So
you
do
want
to
store
this
somewhere
safe.
As
you
can
see,
I'm
trying
to
do
that
here
do
you
know,
demonstrate
the
best
practices
and
then
I'm
just
going
to
restart
the
bot.
E
E
And,
as
you
can
see,
it
works
okay,
great,
so
now
let's
go
and
make
an
app,
so
I'm
sure
you've
seen
app
studio
about
a
gazillion
times,
so
I'm
going
to
go
really
quick,
but
I'm
just
going
to
create
a
new
app
for
this.
Nothing
too
special
about
it.
I
do
have
to
fill
in
all
these
fields.
Teams
won't
and
it's
it's
good
teams.
Keep
me
honest
here
can't
like
half
fill
in
this
form.
E
All
these
different
things
have
to
be
filled
in
or
it
won't
take
the
app,
and
so
you
probably
already
know
that,
but
I'm
just
trying
to
explain
as
we
go
and
we
need
the
developer
information
and
we
need
the
app
urls
and
I'm
just
going
to
use
my
company's
urls
for
that
and
I'll
skip
the
branding.
Let's
just
go
right
over
to
bots
in
the
interest
of
time
and
set
up
our
bot.
E
So
this
is
an
existing
bot.
I
just
registered
it.
I
showed
you
the
registration
right,
I'm
just
going
to
paste
in
that
app
id
the
bot
id
this
one's
for
personal,
only
and
all
right
now,
let's
go
ahead
and
distribute
that
just
going
to
install
it
locally,
and
that
should
do
it
so
that
you
can
see
that
I'm
still
talking
my
conversation
from
the
earlier
test
is
still
there
and
it
is
still
working
awesome
all
right
so
now.
E
So
I'm
just
going
to
go
back
into
my
bot,
I'm
going
to
add
another
trigger,
and
this
one
I
have
a
how
intent,
let's
make
a
who
intent?
Who
am
I,
and
so
all
I'm
going
to
do
here-
is
report
back
a
little
bit
of
information
from
the
user's
profile
to
do
that,
I'm
going
to
call
an
external
resource
and
I'm
going
to
start
with
the
login,
so
the
user
does
have
to
log
in
occasionally
this
is
not
the
new
teams
sso!
E
This,
who
am
I
dialog,
is
running
so
once
the
user's
logged
in
I'm
just
going
to
do
a
get
request
of
everybody's
favorite,
url
graph.microsoft.com
1.0,
slash
me
and
I'm
going
to
pass
that
auth
token
in
and
notice
that
I'm
going
oauth.token
and
there's
a
little
syntax
there
that
you'll
end
up
learning
in
the
bot
composer,
which
is
to
expand
that
property.
I
have
to
use
a
dollar
sign
and
squiggly
brackets,
but
not
too
much
that's
fancy
here.
E
Actually,
let
me
yeah
go
right
into
teams,
and
I'm
just
going
to
say
who,
who
am
I
and
there
we
go?
We
got
a
login
prompt.
As
I
say,
you
only
get
these
occasionally
now
I
forgot
to
do
something,
so
it's
not
working.
So
let
me
go
fix
that
all
I
need
to
do
here
is
add
to
the
team's
manifest
and
aren't
you
glad
that
teams
is
keeping
us
safe
right,
like
it's
keeping
me
from
going
to
arbitrary
urls
that
might
be
from
somewhere
nefarious
unless
I
put
them
here
under
valid
domains.
E
A
All
right,
moving
on
to
our
next
portion
of
the
call
and
now
I'll
be
turning
it
over
to
a
new
agent
to
go
over
utilizing
mobile
first
device
capabilities
for
teams
apps.
So
whenever
you're
ready
ship
them,
I
can
just
kind
of
click
through
the
slides,
just
kind
of
guide
me
when
you
want
me
to
move
on
to
the
next
one.
F
Today,
we're
going
to
specifically
talk
about
device
capabilities,
and-
and
these
are
essentially
hardware
capabilities
that
come
on
your
phone.
We
want
to
showcase
the
various
scenarios
or
to
you
on
how
extensible
app
developers
can
utilize
these
capabilities
to
build
richer
mobile
first
applications.
F
I
want
to
briefly
talk
about
the
various
platform
constructs
and
how
they
essentially
look
on
mobile.
I'm
sure
most
of
you
would
be
familiar
with
this,
but
we
have
bots,
which
are
conversational
entities
that
perform
a
certain
specific
set
of
tasks.
So
bots
can
register
with
the
ms
bot
framework
and
can
and
then
act
as
essentially
any
other
member
as
part
of
a
chat
or
a
team,
and
bots
can
communicate
with
users
respond
to
their
questions
proactively.
Notify
them
about
changes,
etc.
F
Then
we
have
tabs.
These
are
canvases
that
can
be
used
to
share
content,
whole
conversations
and
third-party
services,
and
these
are
essentially
nothing
but
web
views
that
load
a
website.
Url
messaging
extensions
is
a
construct
that
users
can
use
to
aid
themselves,
while
they're
composing
a
message
and
on
mobile
it
sort
of
comes
up
when
you
open
up
the
the
compose
extension
tray
and,
lastly,
we
have
personal
apps,
and
these
are
similar
to
tabs,
which
just
exists
in
the
personal
scope.
F
So
while
you
have
tabs
that
can
be
configured
and
designed
to
be
more
collaborative
in
nature,
as
they
can
be
pinned
to
a
particular
chat
or
channel
users
can
use
personal
apps
to
increase
their
own
productivity
and
that's
what
comes
up
when
you
swipe
up
or
on
the
home
page
in
the
in
the
more
menu
all
right.
So
before
I
hand
over
to
shubham,
I
just
want
to
talk
a
bit
about
why
we're
really
investing
heavily
in
mobile-first
capabilities
before
the
pandemic.
F
The
usage
of
teams
is
sort
of
restricted
to
north
america,
but
in
the
last
year,
or
so,
we've
seen
the
usage
grow
in
other
parts
of
the
world
of
students,
front-line
workers
and
other
blue
collared
workers
that
don't
have
access
to
large
screen
devices
use
mobile
on
an
everyday
basis
and
mobile.
Only
users
today
account
for
close
to
20
of
our
teams.
Users,
and
this
is
one
of
the
fastest
growing
user
segments,
and
we
do
expect
this
growth
sort
of
continue
in
the
near
future
as
well.
F
G
Yeah
thanks
thanks
a
nudge
here.
One
shubham
here
work
with
android
on
the
platform,
so
I'll
just
jump
right
into
the
device
capabilities
which
we
have
developed
over
the
past
couple
of
months,
as
well
as
we'll
also
look
into
some
capabilities
that
we
are
currently
working
and
will
be
releasing
in
the
future.
So
here's
a
quick
road
map
of
how
things
have
been
over
the
past
and
how
it
looks
in
the
future.
G
We
started
off
with
the
image
capture
and
you
know
photo
gallery
picking
kind
of
scenarios
first,
so
the
first
two.
There
are
the
first
two
items
here
on
the
timeline
represent
the
same.
We
have
used
office
lens,
which
is
like
a
powerful
tool
that
microsoft
leverages
two
power
scenarios
around
capturing
images
through
a
camera,
then
the
third
one
here
is
recording
audio
using
a
microphone.
This
again
is
a
kind
of
a
very
common
scenario.
G
Our
control
here
we'll
go
into
details
of
this,
I'm
just
quickly
going
through
the
timeline
for
now,
then
till
now
we
have
only
talked
about
the
mobile
capabilities,
but
some
of
these
capabilities
we
thought,
would
also
make
sense
to
have
the
desktop
counter
counterparts
supported
as
well.
So
then
we
kind
of
work
to
gain
parity
in
terms
of
functionality
on
desktop.
So
around
this
quarter
we
have
been
working
on
the
first
two
set
of
capabilities,
around
images,
camera
location
and
making
sure
that
it
also
works
in
desktop.
G
So
this
is
our
current
work
that
we
are
doing
then.
At
the
end,
the
last
two
are
around
a
people:
picker
hvc
hvc,
meaning
a
high
value
control,
so
they
are
very
common
scenarios
in
which
you
would
want.
You
know
a
control
that
allows
an
end
user
to
select
a
user
say
from
a
chat
or
channel
or
within
the
org,
in
order
to
say,
assign
a
particular
task
to
a
user
or
just
add
the
user
in
the
in
a
particular
workflow.
G
We
believe
that's
a
very
common
workflow,
and
we
also
wanted
to
make
sure
that
this
kind
of
control
is
added
to
the
client
sdk
itself,
so
that
the
developers
can
directly
leverage
it.
Instead,
you
know
using
their
own
putting
in
their
own
effort
and
building
such
a
control
that
can
be
easily
leveraged
directly.
Then
the
last
one
is
around
video
capture
capability,
which
we'll
be
picking
up
sometime
next
quarter,
I'll
be
going
into
quick
demos
of
how
these
capabilities
currently
work.
So
the
first
one
here
is
around
image
apis.
G
So
here
we
just
wanted
to
demonstrate
the
power
that
office
lens
provides
so
june.
If
you
can
just
play
the
demo
I'll
just
this
doesn't
have
an
voiceover
so
I'll.
Just
walk
you
into
what's
happening
so
here
we
just
created
a
sample
app
to
demonstrate
the
power
that
office
lens
provides
in
terms
of
the
edit
functionalities
and
kind
of
high
high
level.
G
G
You
know
access
certain
functionalities
which
are
natively
available
and
the
parent
is
able
to
either
click
an
image
from
camera
or
just
select
one
from
gallery
and
then
office
lens
provides
a
host
of
functionalities
such
as
you
know,
you
can
add
a
text
annotations,
you
can
add
filters,
you
can
add
free
free
hand,
drawing
on
top
of
the
images.
Basically,
you
can
have
all
the
functionalities
which
everyone
is
kind
of
very
familiar
with
now,
and
that
can
be
added
to
the
image
before
sharing
it
right
back
to
the
underlying
web
app.
G
So
this
is
more
about
it.
Then
it's
kind
of
standard
stuff.
We
can.
We
can
pause
this
demo.
It's
just
submitting
the
image
to
the
web
app
and
move
to
the
next
one,
so
this
demo
was
around
demonstrating
how
powerful
office
lenses
in
terms
of
high
level
edit
functionalities
over
images.
The
next
demo.
We
have
that's
a
common
demo.
That
kind
of
demonstrates
three
of
the
capabilities,
including
the
one
that
we
talked
about,
which
is
image
and
then
location
and
mic.
G
F
The
help
of
number
of
device
capabilities
now
enabled
on
teams
platform
contoso,
has
enabled
a
tab
app
that
lets
fail,
agents
record
information
easily
on
teams
itself
that
is
instantly
viewable
on
the
contoso
repair
channel.
The
feed
agent
can
quickly
create
a
new
inspection
item
and
raise
the
ticket.
F
F
Using
the
multiple
image
support,
the
field
agent
can
upload
multiple
images
of
the
car.
At
the
same
time,
they
also
have
the
option
to
choose
and
pick
the
current
location
of
the
customer
by
dropping
a
pin
at
the
map
interface
instead
of
typing
out
a
description
of
the
car.
The
field
agent
can
record
an
audio
description
of
the
car
itself
on
recording
the
audio
successfully.
G
Yep,
so
that
was
a
short
demo
of
a
simple
app.
We
built
that
leverages
three
of
our
capabilities
around
image,
location
and
audio
or
mic.
The
last
demo
that
we
have
at
least
for
this
area,
is
around
a
qr
barcode
scanner
capability.
We
just
went
live
last
month,
so
yeah
this
again
has
a
voiceover,
so
I'll
mute
myself
june.
You
can
play
the
demo.
Here's
a
demo
showcasing
qr
and
barcode
scanner
capability,
that's
being
added
to
the
team's
client
sdk.
G
G
G
This
makes
the
process
of
raising
support
ticket
much
simpler
and
after
entering
the
issue,
description
max
just
hits
submit
to
generate
a
fresh
support.
Ticket
max's
life
is
easier
now,
thanks
to
qr
and
barcode
scanner
capabilities
present
in
the
team's
client
sdk,
so
that
was
around
the
qr
barcode
scanner
capability,
which
just
went
live
around
last
month.
G
So
so
this
is
a
control
that
we
are
currently
working
on.
So
this
is
again
something
that
we
have
been
hearing
a
lot
from
our
developer
community
and
especially
our
3p
partners,
who
all
of
them
had
had
a
requirement.
A
control
which
can
be
used
leveraged
to
you
know,
pick
people
it's
it's
not
an
easy
process
to
do,
and
if,
if
something
like,
this
can
be
extended
right
out
of
the
team
stand
sdk,
then
that
would
add
a
lot
of
value
to
the
developer
community.
G
In
general,
so
we
listen
to
that
feedback
and
yeah
his
his
kind
of
the
I
work
that
we
are
currently
doing,
and
these
are
just
box
for
now,
but
it's
under
progress.
So,
as
you
see,
here's
a
sample,
a
purchase,
approval
kind
of
workflow
wherein
one
of
the
steps
is
to
select
the
approver.
So
the
second
and
the
three
third
screens
that
you
see
here
these
represent
the
experience
that
would
again
be
coming
in
in
form
of
an
api
in
the
client
sdk.
G
So
this
entirely
would
be
just
one
epa
call
away,
so
developers
can
just
leverage
that
call
that
capability
and
you'll
have
you
don't
have
to
invest
as
much
in
building
a
people
picker
on
your
own.
So
here
on
the
second
and
third
screens,
the
end
user
selects
the
respective
approver
and,
as
you
see
in
the
last
screen,
the
name
of
the
approver
and
relevant
details
get
shared
back
with
the
underlying
app
and
the
end
user
hits
send
and
the
workflow
gets
completed
yep.
G
G
Viewer
control
as
well
so
select
media
is
the
api
that
you
will
need
to
invoke
or
call
to
kind
of
capture
or
let
users
capture
and
attach
images
to
the
underlying
web.
So
so
I
just
wanted
to
cover
the
configurations,
also
real,
quick,
quick,
so
we
kind
of
understood
that
there
are
different
requirements
or
use
cases
coming
in
from
from
mobile.
G
First
scenarios,
such
as,
for
example,
there
was
a
scenario
which
one
of
our
customers
was
asking
that
you
know
we
want
to
create
a
check-in
kind
of
app
wherein
the
user
is
restricted
to
capture
image.
Only
using
the
front
camera.
We
don't
want
users
to
use
rotate.
The
camera
at
all,
or
there
were
scenarios
like
you
know
this.
We
have
the
scenario
that
we
want
users
to
scan
a
picture
instead
of
capturing
a
picture,
and
then
there
were
scenarios
around.
You
know
in
in
quality,
check
or
quality
inspection
kind
of
scenarios.
G
They
wanted
to
do
a
free
hand
annotation
over
the
image
before
submitting
it
to
the
app
so
different
scenarios
kind
of
translate
here
to
different
configurations
that
we
have
kind
of
provided.
So
you
can
change
this
configurations
as
per
your
need
of
the
app
and
respectively,
the
control
would
make
sure
that
it
opens
in
a
relevant
configuration,
so
the
first
second
one
here
is
a
number
of
medias
that
can
be
attached
pretty
straightforward.
G
Third
one
is
the
source
source
means
whether
you'd
like
to
let
users
capture
an
image,
or
you
know
pick
an
image
from
the
gallery
or
you
know
let
the
users
choose
which
one
they
want
to
do
then.
The
fourth
one
here
is
the
start
mode.
So
office
length
supports
a
couple
of
scan
modes
as
well,
instead
of
like
standard
image
capture
kind
of
mode,
so
it
supports
document
scanning,
whiteboard
scanning
and
business
code
scanning.
G
So,
if
you
want,
if
you
have
a
scenario
wherein
the
control
should
open
in
a
particular
scan
mode,
then
that
too
is
available
in
form
of
configuration,
then
the
fourth
last
one
is
around
cameras
which
are,
if
you
want
to
default,
to
front
or
back
camera
or
want
to
restrict
users
to
use
only
a
particular
camera.
Then
this
is
the
configuration
to
use
the
last
three
are
around
editing,
so
inking
applying
text
stickers
and
applying
filters.
So
these
are
just
boolean
boolean
configurations.
G
If
you
set
them
to
true
these
capabilities,
which
will
just
show
up
in
the
camera
control,
then
the
last
thing
I
want
to
cover
is
around
a
view,
images,
a
view.
Image
is
another
api
that
we
have
added
to
the
sdk,
which
can
directly
directly
be
leveraged
to
you
know,
have
a
image,
viewer
kind
of
control
so
that
you
can
just
use
an
inbuilt
control
instead
of
building
your
own
image
viewers
to
preview
the
attached
images.
G
So
the
coming
to
the
location,
apis,
there's
just
two
pretty
straightforward
apis
here
one
is
get
location,
one
is
show
location
get
location
is
you
would
be
used
to
capture
user's
location?
We
have
configurations
which
kind
of
let
the
developers
decide
whether
they
want
to
show
a
map
or
not
show
a
map,
and
if
they
want
to
show
a
map,
then
would
the
user
be
allowed
to
move
around
the
map
and
pick
any
location
on
the
map
or
are
they
restricted
to
submit
they
only
their
current
location?
G
So
all
of
them
are
the
configurations
that
can
be
created
by
using
allow
choose
location
and
show
map
variables,
which
are
the
configurations
that
we
currently
support.
So
a
large
use
location
would
mean
you
know
a
map
would
open.
This
again
is
coming
from
a
mobile
first
scenarios
that
we
have
heard
a
lot.
For
example,
in
some
scenarios
the
apps
just
want
to
show
the
map
as
a
confirmation
screen,
and
they
want
the
user
to
submit
only
their
current
exact
location
for
verification
kind
of
scenarios.
G
So
listening
to
those
kind
of
feedback,
we
have
this
configuration
that
restricts
our
user
to
either
submit
the
current
location
only
or
maybe
enables
users
to
pick
any
location
on
the
map
and
share
with
the
underlying
web.
App
and
show
map
is,
is
just
a
com
like,
as
the
name
suggests
it
it's
a
configuration,
if
set
to
true
it
would
show
the
map
if
set
to
false,
then
this
is
kind
of
a
scenario
which
is
also
currently
enabled
by
the
html5
get
current
position
kind
of
api,
so
it
just
kind
of
fetches.
G
The
current
coordinates
from
the
gps
of
the
device
and
shares
with
the
underlying
web
app
without
showing
any
particular
map
on
the
ui,
then
the
other
api
store
location.
It
would
just
open
a
particular
location
that
you
provide
to
this
api
on
on
the
native
mobile,
supporting
app
so
coming
to
the
last
capabilities
that
we
have
rolled
out
for
now.
Microphone
is
again
very
simple.
G
There's
just
one
api
which
we
have
already
discussed
so
select
media
is
kind
of
an
umbrella
api,
so
we
have
just
extended,
select
media,
which
we
discussed
earlier
to
also
support
my
capability.
So,
basically,
the
interface
is
same
as
as
seen
in
the
demo
using
this
api,
a
small
kind
of
bar
would
appear
at
the
bottom
of
the
screen,
wherein
you'll
the
end
user
will
have
the
option
to
stop
the
recording
whenever
the
user
feels
like
ending
the
recording
and
the
recorded
audio
stream
gets
shared
with
the
underlying
gap.
G
So
the
only
configuration
here
is
max
duration,
which
kind
of
is
limited
currently
at
10
minutes,
and
if
you
set
this
duration
to
say
one
minute,
then
the
recording
would
automatically
terminate
after
that
set
period,
then
the
last
capabilities
around
barcode,
qr
code
scanner,
again
just
one
api,
which
is
called
scan
barcode.
The
only
configuration
we
have
is
timeout
intervals
in
second,
it's
currently
marked
at
60
second
and
default
is
30
second,
but
it
can
be
configured
for
the
needs
of
of
the
end
user.
G
All
the
experiences
were
kind
of
demonstrated
back
in
the
demos
so
yep,
I
hope
everyone
can
relate
which
apis
correspond
to
which
capability
and
we
just
post,
we
just
shared
a
blog
post
recently
on
all
the
four
capabilities
we
just
talked
about,
which
is
to
summarize,
which
is
around
image
apis,
which
is
capturing
an
image
or
picking
an
image
from
gallery
or
viewing
image
then.
Secondly,
around
location,
which
is
getting
a
user's
location
or
showing
a
location
on
a
map.
G
Third
is
around
audio
or
mic,
which
is
recording
audio
on
using
the
device
microphone
and
the
final
one
was
around
qr
barcode
scanner,
which
is
again
being
added
being
added
to
the
client
sdk
as
a
ready
to
use
control
right
or
out
of
the
box.
So
you
can
just
check
out
this
blog
post.
The
link
is
ak
dot
ms
device
capabilities
and
also
respective
documentations.
G
So
that's
all
we
had
from
the
device
capabilities
area.
I
hope
everyone
did
find
some
value
in
what
we
have
been
developing
from,
especially
looking
at
the
mobile
first
vision
that
the
team
currently
has
do
share
our
feedback
on
the
chat
and
yep
also
share
any
questions
on
the
chat.
If
you
have
any
thanks,
what
do
you
choose.
A
Awesome,
thank
you
shivam
thank
you,
anurch,
and
I
should
have
mentioned
on
that
blog.
You
can
find
all
of
the
the
resources
and
the
dev
documentation
that
they
mentioned
as
well,
so
be
sure
to
check
out
that
link
I'll.
Let
me
go
back
so
that
you
guys
can
have
it
again
in
front
of
you
if
you
haven't
copied
it
already,
but
aka
dot.
Ms
slash
device
capabilities.
A
Thank
you
guys.
So
much
before
I
move
on
to
q
a
you
know
in
the
spirit
of
continuous
improvement
and
development,
you
know
we
wanted
to
ask
if
you
could
complete
a
quick
survey
for
us
just
to
kind
of
help
us
help
describe
your
experiences
with
the
m365
developer,
ecosystem
right
from
onboarding
and
onto
the
platform
all
the
way
to
measuring
and
tracking
success
of
your
application.
You
know
this
will
help
us
a
long
ways
as
to
kind
of
improving
the
experience
for
developers
building
on
the
platform.
A
So
if
you
have
a
moment,
you
know
please
check
out
aka
dot.
Ms
slash
developer.
Success.
That'll
really
help
us
out
here.
So,
thank
you
so
much
so
I'll
pause
on
here
for
just
a
second,
for
you
guys
to
take
a
look
at
the
links
and
then
now
I
will
turn
it
over
to
q
a
so
you
know.
If
you
have
any
questions,
please
use
the
raise
your
hand
feature,
and
then
we
can
kind
of
call
upon
you
or
please.
A
If
you
feel
more
comfortable,
asking
a
question
in
the
chat,
please
do
so
and
we'll
just
kind
of
go
through
questions
as
much
as
we
can.
So
I
will
turn
it
over
to
the
audience
and
I
see
a
question
in
the
chat
not
sure
if
folks,
on
the
call
have
the
answers
for
this,
but
is
adaptive
cards
1.3
supported
in
teams.
H
Thanks
just
quick
question
about
your:
you
know
that
chatbot
scenario
got
me
thinking
about
another
thing
that
I've
tried
to
do
that
hasn't
worked.
Are
there
plans
to
allow
a
bot
to
receive
and
react
to
media
to
chat
messages
in
meetings,
because
I
can
join
a
meeting?
I
can
get
the
audio
from
the
meeting
in
a
call,
but
I
can't
see
or
contribute
to
the
meeting
chad
is
bought.
D
A
A
I
do
see
a
question
from
michael
asking:
when
will
adaptive
cards
1.4
with
the
universal
action
model
be
available?
I
think,
michael
for
that
question.
We
can
loop
back
with
our
adaptive
cards
colleagues
to
to
see
if
they
have
any
information
that
they
could
bribe,
but
we'll
kind
of
loop
back
with
them.
For
that,
and
then
lisa
asked
a
question
not
related
to
this
topic,
but
do
we
know
when
they
will
activate
notifications
from
shifts
in
the
team's
desktop
app
currently
available
on
mobile,
but
not
on
desktop
lisa
for
that
one
or
yeah?
A
If,
folks,
on
the
call
don't
have
an
answer,
I
can
always
loop
back
with
my
frontline
worker
colleagues
to
see
if
I
can
grab
an
answer
for
you
for
that.
You
know
it's
a
follow-up
and
then
christian
asked
when
will
bot
features
be
available
for
direct
routing,
satya
or
aaron,
or
maybe
even
bob
any
quest
any
thoughts
on
that
one
by
chance.
A
E
H
I
might
be
able
to
answer
that
for
you.
Actually,
you
can
actually
use
that
with
direct
routing
like
you
can
assign
a
direct
routing
number
to
a
bot,
and
you
can,
if
it
bought,
is
assigned
a
online
voice
writing
policy.
It
could
make
a
call
via
an
outbound
call,
can
go
out
by
a
direct
writing
spc,
so
it
does
work.
H
H
J
Nope,
unfortunately,
not
not
my
graph,
not
by
using
graph
just
you
know
you
get
the
call
id
and
then
you
say:
okay,
I
want
to
be
able
to
answer
this
call
and
you
know
transfer
it
to
someone
else
or
whatever
I
want
to
do
with
it.
But
but
maybe
we
can
talk,
you
know
outside
this
community
if
that's
kind
of
out
of
scope
for
this
call.
H
E
F
H
H
J
I'm
writing.
I'm
I'm
capable
of
getting
psn
calls
directly
to
my
team's
client,
but
but
you
know
adding
the
the
virtual
license
and
phone
number
that
works.
Like
a
charm
I
mean
so
the
thing
is,
I
can
see
I
can
see
via
the
web
groups
that
the
call
is
coming
in.
I
get
a
call
id
and
based
on
that,
if
you
look
at
documentation,
you
should
be
able
to
grab
that
call
based
with
on
the
id
and
then
do
something
with
manipulate
it.
J
J
H
The
troubleshoot,
the
troubleshooting
on
some
of
that
stuff
is
not
great,
so
yeah
it
it
it
should.
I
guess
the
the
answer
I
don't
know
like
it,
should
work,
but
great
so
yeah,
so
yeah.
If
you
want
to.
If
you
want
to,
if
you
want
to
keep,
I
would
I
would
try
just
getting
it
to
answer
a
call
and
play
a
message
back
or
something
before
you.
B
J
J
J
H
H
A
A
K
I
have
two
questions.
I
need
to
show
a
tab
only
for
mobiles
on
my
app
and
another
thing
is:
I
need
to
know
if
a
user
have
seen
a
message
sent
by
my
bot.
I
need
to.
I
need
to
know
if
he
he
did.
He
did
see
the
message
because
they
are
asking,
I
said,
and
we
are
putting
this
to
power
bi
this
information
to
power.
Bi-
and
I
don't
know-
I
don't
know
how
to
get
this
information.