►
Description
Microsoft 365 platform community call delivered on October 18th. Two demos - Introduction to Microsoft Graph Search API and Build your first Command bot in C# for Microsoft Teams with Teams Toolkit for Visual Studio. Register for Microsoft Teams App Camp online training on October 20th, https://aka.ms/TeamsAppCamp. 31+Microsoft 365 platform related articles and 2 conversations (Microsoft 365 PnP Weekly and Microsoft 365 Developer Podcast) delivered this week. The host of this call was Vesa Juvonen (Microsoft) | @vesajuvonen. Q&A takes place in chat throughout the call.
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365/community
A
B
Today
we
will
have
the
Jupiter
sites
and
typical
intros
on
how
to
get
started
and
what
are
the
assets
which
are
available
and
let's
continue
having
discussions
in
a
chat
during
that
time,
and
that's
always
one
of
the
big
benefits
of
this
course
as
well,
and
then
we'll
have
the
group
photo
and
after
that
we'll
have
two
demos,
so
Neary
and
I'm
pronunciating
your
name
in
the
wrong
way.
I
do
apologize,
it's
going
to
talk
about
the
introduction
to
Microsoft
Graph,
Search
API,
so
what's
available
in
there.
B
Thank
you
for
that
and
looking
forward
on
that
and
then
Aisha
passed
is
to
kind
of
talk
about
building
your
first
Common
bot
in
C,
sharp
for
Microsoft
teams,
with
teams
toolk
and
visual
studio.
Now
Carrie
did
the
similar
kind
of
storyline.
It
was
a
week
ago,
two
weeks
ago,
but
that
was
not
with
J
sharp,
because
now
we
actually
have
the
visual
Microsoft
teams,
teams
toolkit
also
in
visual
studio.
B
B
We
have
the
developer
video
channel
where
we
have
in
quotes
official
videos
coming
from
marketing
Cloud
Advocates,
and
then
we
have
the
community
YouTube
channel,
where
we
have
all
of
our
community
call
recordings
demos
and
a
lot
of
other
stuff
in
that
channel
as
well.
So
there's
historical
reasons
why
we
have
two
of
this:
don't
worry
about
it
subscribe
to
both
of
them.
That
is
the
right
way
of
approaching.
B
We
have
a
lot
of
Open
Source
assets
available
in
multiple
GitHub
organizations,
but
as
it
might
be
a
bit
difficult
to
find
the
relevant
sample
for
you,
we
actually
started
creating
a
sample
Galleries,
and
then
we
created
our
unified
sample,
Gallery
app,
which
is
the
first
URL
in
the
sample
calories.
But
if
you're
looking
into
specifically,
for
example,
team
samples
or
SPF
examples,
you
can
absolutely
go
to
those
other
URLs
as
well
or
script
samples
and
so
on.
B
Now
we
do
have
quite
a
few
Community
course,
and
just
to
recap
on
that
one
as
well.
We
have
this
Tuesday
one
which
is
the
which
is
the
one
where
we
always
have.
Microsoft
presenters
happening
every
single
Tuesday
at
8
in
Pacific
time,
then
we
have
few
monthly
calls
adaptive
card
micro,
high-ended,
the
platform
office,
settings
and
Power
Platform
call
platform
call
is
by
the
way
happening
this
Wednesday
8,
AM,
Pacific
time.
If
I
remember
correctly.
B
David
can
actually
remind
me
on
that
one
on
the
chat,
and
then
we
have
the
Thursday
series,
which
is
happening:
7,
A.M,
Pacific,
Time,
on
every
single
Thursday.
It's
either
Microsoft
365,
Power,
Platform,
Community,
call
or
Viva
connection
share
my
favorite
Community
course,
and
mainly
that
we
see
Community
Demos
in
those
course
now
we
have
a
lot
of
assets
available
for
getting
started
in
Microsoft
365
development.
First
of
all,
on
the
developer
program,
a
developer
program
is
once
again
enabled
so
it
is
available
for
you
to
subscribe
to
new
tenants
to
that
channel.
B
B
Surprise,
surprise:
every
single
week
as
well
and
the
podcast
of
the
video
is
getting
populist
every
single
Tuesday,
and
this
week
we
had
Paulo
piolorsi
talking
about
his
latest
contributions
in
open
source
across
to
multiple
different
areas
and
a
lot
of
other
discussions
as
well.
That
one
is
hosted
by
me
and
waldec
Mastercards.
B
Now
we
do
have
that
unified
sample
Gallery
available,
which
we
already
mentioned.
We
I
should
actually
double
check
the
number.
We
are
getting
all
the
time,
a
lot
of
a
lot
of
new
samples
available
on
that
Gallery,
and
it
is
the
easiest
way
to
find
a
relevant
starting
point
for
you
if
you're
building
anything
for
Microsoft
teams,
bot
framework,
ship
and
framework
script
samples-
and
all
of
that
is
available
from
one
this
one
centralized
location
rather
than
try
and
Define
those
samples
across
the
GitHub
gifts.
That
might
be
a
bit
confusing.
B
So
that's
a
really
good
viewable
to
remember
now
as
to
find
a
sample.
You
might
be
thinking
okay,
what
now?
How
would
I
actually
start
using
the
sample
or
what?
If
I,
would
still
want
to
contribute
on
the
sample
I'm?
Finding
a
small,
typo
or
something
else,
that's
why
we
have
our
sharing
is
caring
initiative
and
I
will
let
David
Warner
to
talk
about
what
this
is
all
about?.
A
Is
warm
today
it
is
I.
Would
trade
for
cold
weather
with
anyone
yeah
absolutely
so,
as
vessel
mentioned,
we
have
a
plethora,
a
plethora.
I've
said
it
again,
a
plethora
of
samples
over
1100.
How
does
that
happen?
It's
not
magic.
It's
not
little
elves
or
Oompa
Loompas
It
Is
by
all
of
you,
and
you
may
be
wondering
if
you're
new
to
the
community.
Well
I
want
to
be
in
that
group,
and
you
absolutely
can,
but
there
are
GitHub
landscape
that
GitHub
Galaxy.
That
VES
is
talking
about,
can
be
a
little
bit
hard
to
navigate.
A
You
don't
want
to
get
lost
in
space.
So
sharing
is
caring.
Is
a
program
that's
been
set
up
to
provide
you
Hands-On
guidance.
So
what
does
that
mean?
It
means
that
we're
going
to
join
in
live
sessions
together.
These
are
safe
space
opportunities
for
you
to
ask
any
and
all
questions
that
you'd,
like
they're,
not
recorded,
so
you
don't
have
to
be
like
my
question,
got
to
get
recorded
and
everybody
gonna
hear
not
at
all.
You
don't
got
to
worry
about
it.
A
We're
there
to
learn
together
and
we're
going
to
take
the
steps
together
and
we've
got
a
variety
of
topics,
we're
starting
to
get
everything
scheduled
again.
Now
that
we've
come
out
of
some
busy
seasons
for
us
and,
as
you
all
may
have
seen
last
week
in
ignite
power
pages
with
GA,
so
Hugo
Bernier
is
giddy
is
a
little
Schoolboy
and
he
is
going
to
be
setting
up.
Another
sharing
is
caring,
two-parter
for
power
Pages,
and
we
absolutely
want
to
invite
everyone
to
that
so
keep
an
eye
on
it.
A
We're
also
gonna
be
creating
some
videos
because
I
know
everybody's
busy.
We
want
to
share
the
goodness
that
has
come
from
the
sharing
is
caring
program
sessions
and
we're
going
to
start
creating
some
videos
on
demand
for
you
to
be
able
to
get
whenever
is
convenient,
for
you
don't
hesitate
to
keep
an
eye
out
for
those
new
events
being
scheduled,
AKA
dot,
Ms
forward.
Slash
sharing
is
caring,
Bessa
back
to.
B
You
excellent
Helsinki
is
catching
the
ball
and,
let's
continue.
This
is
pretty
wild
when
I
think
about
technology
enables
us
to
do
this
worldwide.
It's
a
super
super
cool.
Now,
on
the
the
upcoming
week,
we
also
have
a
special
ad
Camp
event.
This
is
an
online
event
happening
on
October
20th
So
within
that's
on
Thursday
today
is
Tuesday
unless
I'm
completely
mistaken.
B
Now
then
we
move
into
the
news.
So
as
we
can
imagine,
it
was
an
ignite
week
and
there's
a
lot
of
news.
So
we're
not
going
to
mention
all
of
the
news
I'm
just
going
to
call
out
a
few
of
them,
because
there's
a
lot
of
a
lot
of
a
lot
of
announcements.
Last
week
it
was
a
bit
of
an
overwhelming
and
for
a
lot
of
us
for
sure,
a
lot
of
a
lot
of
great
stuff
on
the
Microsoft
365
developer
site
and
going
across
the
Microsoft
teams.
B
Craft
Microsoft
teams,
craft
apis
planner
got
a
app
only
apis
and
all
of
that
announced
as
well.
So
a
lot
of
art
of
cool
stuff
on
that
side,
again
not
going
to
mention
all
of
those
on
the
other
blog
posts
which
are
mentioned
in
the
top
right
corner,
and
we
also
had
tremendous
amount
of
new
announcements
across
the
Microsoft
teams,
features,
capabilities
and
the
the
virtual
avatars
was
mentioned
and
that
they're
available,
maybe
we'll
start
seeing
them
in
this
school
as
well.
B
B
C
Yeah
thanks
Michelle,
hello,
everyone
I
would
walk
you
through
the
platform
in
the
documentation
updates
here.
So,
let's
start
with
the
platform
dates
on
the
website,
so
the
first
update
is
on
live
share,
canvas
so
in
conference
rooms
and
classroom
across
the
globe.
Whiteboards
are
the
pivotal
part
of
collaboration
in
modern
times.
However,
whiteboard
is
no
longer
enough
with
numerous
digital
tools,
such
as
PowerPoint
being
the
focal
point
of
collaboration
in
modern
era.
C
It's
essential
to
enable
the
same
creative
potential
to
enable
more
seamless
collaboration,
Microsoft,
created,
PowerPoint
live,
which
has
become
instrumental
to
how
people
work
in
teams.
Presenters
can
annotate
over
slides
for
everyone
to
see
using
pens,
highlighters
and
the
laser
pointers
using
live
share.
Canvas
your
app
can
bring
this
power
of
PowerPoint
live
inking
tool
with
the
minimal
efforts,
so
we
have
shared
the
documentation
link
here.
We
are
also
linked
to
sample
in
the
documentation
which
you
can
set
up
locally
and
play
around
with
live
share.
C
Canvas
now
the
let's
move
to
the
doc
updates
on
the
right
side.
So
we
got
a
lot
of
feedback
on
the
teams
meeting
since
pretty
module.
So
we
are
revamping
the
scene,
so
we
revamped
the
content
to
ensure
there's
a
Clarity
of
steps
and
procedure.
We
explain
different
features,
added
requirements
and
corrected
technical
process,
improve
the
discoverability
of
content
by
correcting
the
TOC
structure
and
the
pH
names.
Please
go
and
take
a
look
if
you
have
anything
to
share.
Please
share
your
feedback,
so
these
were
overall
updates
on
the
platform
we
have.
C
B
Thank
you
on
that
one
and
I
just
reinforced
what
what
Jade
was
saying.
Please
please,
please
give
us
feedback
if
you
have
ideas
or
suggestions
or
something
isn't
working
or
there's
a
issue,
maybe
in
the
documentation
or
something
please
let
us
know,
we
are
doing
our
best
to
make
sure
that
everything
is
up
to
date
and
we
are
trying
to
assume
all
of
the
guidance.
What
you
want
to
have,
but
having
your
input
would
be
super
super
valuable
for
us
now,
then,
let's
move
to
the
together
mode
section.
B
So
for
those
who
are
willing-
and
you
can
and
now
enable
the
video
I
will
set
together
mode,
enabled
and
I
will
share
my
screen
and
then
we'll
capture
the
screen
from
here.
One
second,
so
get
the
bit
time
on
making
things
to
work.
Here
we
go,
we
have
50
seats
in
a
room.
I
will
put
my
camera
on
as
well.
Let's
do
the
typical
white
one
today
few
more
rows.
If
people
are
willing
to
put
the
video
on-
let's
not
not
yet
not
yet
wait,
wait,
wait,
wait,
wait,
wait!
Wait!
B
Oh
I
can
see
a
few
people
doing
waves.
So
this
is
good.
This
is
good
one
few
more
seats
in
the
room
with
three
more
seats.
Oh
there's,
the
front
row
humor
says
three
more
states:
do
we
get
it
full
routes
and
we
are
not
yet
recording
I
will
put
the
recording
on
one
three
two
one
and
let's
do
some
hand
framing
everybody.
Thank
you
for
joining
once
again
on
the
community.
Call
super
super
cool,
really
really
valuable.
B
To
have
you
here
and
thank
you,
George
amazing,
on
the
background
thanks,
everybody
awesome
to
have
you
on
a
call,
and
hopefully
we'll
see
you
in
the
in-person
experiences
this
year
as
well.
Thanks
everybody
good.
So
let
me
go
back
in
the
slides
and
to
introduce
I
can
actually
recap.
What
are
the
demos
today
so
Neri
and
I
do
apologize.
I'm,
probably
a
pronunciation
is
not
precise.
It's
going
to
cover
the
introduction
of
Microsoft
craft
search
apis
and
please
correct
me
on
the
writing
pronunciation
there
and
then
Aisha
is
going
to
continue
after
that.
D
D
It
all
right
so
I'm
gonna
go
ahead
and
share
my
screen
so
hi
everyone.
Today's
call
will
be
an
introduction
to
the
Microsoft
search
API,
but
a
focus
on
what's
new
in
the
search.
Api
I'm
really
excited
to
come
to
you
today.
My
name
is
and
Jerry
grievius
I
am
a
senior
product
manager
working
on
Microsoft,
search,
apis
and
programmability.
D
D
You
know
back
in
search
experiences
that
power
Outlook
team,
SharePoint
and
other
M365
client
experiences.
However,
if
you
don't
want
to
leverage
some
of
these
experiences
out
of
the
box
and
you're
looking
for
more
customized
flexibility
via
apis,
that's
where
the
Microsoft
search
API
comes
into
play
and
where
we
try
to
bring
some
of
the
same
one-piece
search
experiences
to
your
fingertips
in
3p.
So
you
know
we
particularly
are
during
this
presentation
towards
developers,
so
you
can
learn
how
to
support
different
applications
and
experiences,
and
so
that's
what
I'll
be
covering
today.
D
I've
included
my
contact
information
here
and
I'll
kind
of
go
over
all
this
information
at
the
end.
Just
so,
you
know
where
to
find
more
resources,
so
as
for
an
agenda,
I
want
to
kick
off
with
you
know.
What
is
the
search
API?
How
does
it
work?
I
then
want
to
go
into
what's
new,
so
some
of
the
features
that
we
recently
released
and
that's
where
I'll
walk
into
really
a
deep
dive
into
the
API
structure
and
a
feature
demo
and
then
we'll
close
out
with
some
resources
that
you
can
take
with
you.
D
D
We
know
that
this
is
important
because
we
spend
so
much
of
our
working
days
just
searching
for
important
information,
and
that
being
said,
there
are
actually
many
different
options
that
you
have
today
at
Microsoft.
In
order
to
leverage
search
for
your
scenario
knows
particularly
if
you
want
to
leverage
search
apis
for
building
custom
use
cases,
so
I
wanted
to
kind
of
give
you
a
lay
of
the
land
in
terms
of
what
maybe
some
of
the
search
apis
you
might
be
familiar
with
today.
D
So
we
can
make
this
a
little
bit
interactive
but
feel
free
to
use
the
raise
hand
or
the
reaction
features
and
teams
to
kind
of
show
if
you
recognize
any
of
the
apis
that
I
am
showing
here
on
my
screen.
These
are
different
types
of
search
apis
that
you
might
be
familiar
with
today,
and
so
really
the
kind
of
question
that
we
come
to
is
why
another
search
API
API,
and
why
this
Microsoft
search
API.
D
So
what
really
differentiates
the
search
API
from
some
of
the
apis
I
just
showed
you
is
that
it
is
a
single
search
endpoint
that
allows
you
to
search
across
all
M365
workloads,
and
so
you
can
see
a
little
diagram
here.
There
are
all
these
different
workloads,
clients
and
experiences
that
you
have
access
to
in
M365,
and
this
endpoint
is
designed
to
be
a
centralized
place
for
you
to
access
data
across
as
many
of
those
campuses
as
possible.
D
We
also
are
working
on
exposing
Microsoft
search
intelligence
and
that's
a
really
important
part
of
what
differentiates
this
API
as
well,
so
I
see
having
this
little
green
box
here.
What
the
endpoint
looks
like
and
we'll
kind
of
dive
into
how
to
understand
this
endpoint
and
what
the
API
structure
is
a
little
bit
later,
but
before
we
go
into
that,
I
did
want
to
kind
of
talk
a
little
bit
about.
How
does
this
search
API
work?
D
So
this
Microsoft
search
API
sits
on
Microsoft
graph
and
if
you
are
unfamiliar
with
the
graph
today
pretty
much
you
know
the
graph
allows
you
to
access
a
lot
of
different
intelligence
and
data.
So
these
are
intelligence
across
different
m3c5
experiences
and
clients,
as
well
as
data
sources
that
can
either
come
from
your
first
party
experiences,
either
exchange
or
kind
of
OneDrive
or
SharePoint
resources,
as
well
as
any
connected
content
that
you
bring
in
via
you
know,
Microsoft
graph
connectors.
D
So
with
that
being
said,
the
search
API
itself,
it
sits
on
Microsoft
graph
and
pretty
much.
The
graph
Universe
contains
the
search
index
that
is
populated
with
all
that
data
from
M365
and
the
search
API
allows
you
to
Plum.
You
know
make
sure
that
it's
supporting
your
application
using
all
of
the
information
that's
available
in
the
graph,
so
I'll
walk
you
through
some
of
the
experiences
that
we
have
enabled
recently
in
the
search
API
that
can
help
power.
Your
application,
your
use
case,
your
experience
variants.
So
that
way,
it's
a
customized
search
capability.
D
So
this
is
kind
of
something
that
is
really
really
powerful.
Given
that
you
can
use
this
API
to
make
sure
that
you
have
really
well-rounded
experiences
and
are
able
to
Leverage
The
Power
of
graft
and
we'll
go
through
how
this
API
is
scoped
by
entity
and
produces
and
returns
graph
entities
itself
and
make
sure
that
you
have
graph
consistency
through
authorization
and
Authentication.
D
So
what's
really
new
in
this
Microsoft
search
API
that
we're
going
to
talk
about
today?
Well,
as
I
mentioned,
it
is
workload
agnostic
and
we're
working
on
growing
the
API
to
support
more
workloads
as
well
as
more
capabilities.
So
here
I
have
a
list
of
some
of
the
different
workloads
that
we
support
right
now.
So,
for
example,
you
I
have
access
to
Outlook.
D
There
are
the
messages
entity,
type
and
Outlook
the
events
in
calendar
external
items
and
connected
content
through
connectors,
as
well
as
your
classic
OneDrive
in
SharePoint
entity
types,
which
are
your
file
types
that
I've
listed
here.
But
what
I'll
be
walking
you
through
today
are
some
of
the
new
features
that
we've
recently
enabled
allowing
you
to
search
teams
content.
D
So,
as
we
can
see,
we
are
really
thinking
about
growing
this
API
to
support
as
much
as
it
can,
and
we
definitely
look
forward
to
showing
you
what
that
power
really
looks
like,
and
so
the
features
that
we
are
going
to
show
you
we've
recently
shipped,
and
so
these
features
include
the
ability
to
search
teams
messages.
We
also
have
shift
and
ability
to
use
powerful,
ranking
to
be
able
to
rank
your
search
results
and
then
also
we
support
certain
answers.
Types
and
all
this
documentation
is
live.
D
What
I've
noted
here
in
yellow
is
that
there
are
some
capabilities
that
we're
exposing
in
this
search
API
that
are
really
unique
to
this
API
and
that's
what
differentiates
it
so
now
that
we
have
a
little
bit
of
context
on
what's
new
I
do
want
to
walk
through
how
the
API
is
structured.
So
that
way,
you
have
an
understanding
if
you
are
not
already
familiar
with
the
search,
API
and
kind
of
what
the
lay
of
the
land
is.
D
So
for
the
most
basic
search,
query
requests
you
do
need
to
provide
an
entity
type,
which
is
why
I
listed
all
those
different
entity
types
along
with
their
corresponding
workloads,
so
pretty
much
what
you
need
in
a
request.
The
search,
API
endpoint
is
the
entity
type,
a
query
string
and
any
additional
information
like
fields
that
you
might
want
to
get
back
in
response
Etc,
and
so
this
is
kind
of
the
syntax
and
the
structure
of
how
this
works.
D
D
There's
several
different
hits
that
you
get
as
I
mentioned,
and
so
in
each
hit.
There
are
unique
aspects
such
as
the
hit
ID,
the
rank.
That
tells
you
the
the
actual
score
of
the
search
result.
It
represents
the
position
in
the
set
and
then
a
summary
which
is
a
fragment
of
text
before
and
after
the
search
term,
and
then
the
resource
itself,
which
can
contain
a
lot
of
different
information
and
contains
the
graph
entity
that
we
can
kind
of
specify
based
on
how
we
structure
our
search
request
body.
D
So
now
that
we
have
an
understanding
about
the
basic
anatomy
and
syntax
of
a
request
and
response,
I
do
invite
you
to
you
know
code
alongside
me
if
you'd
like
to
and
open
up
graph,
Explorer
or
postmap
in
to
kind
of
walk
through
some
of
the
new
features.
No
obligation
to
do
this,
but
I
did
want
to
flash
here
that
in
graph
Explorer,
you
can
see
the
exact
samples
of
what
I'm
demoing
today.
So
that
way
you
can
go
ahead
and
check
them
out
yourself.
D
We
also
have
a
postman
collection
that
we
continuously
work
to
keep
up
to
date.
So
that
way,
you
can
go
ahead
and
try
and
Postman
as
well.
This
search,
API
endpoint
is
available
in
beta
in
B1
and
the
Futures
that
I'm
going
to
be
showing
you
today
are
available
in
beta.
So
let's
go
ahead
and
Dive
Right
In
I'm,
going
to
walk
you
through
just
conceptually
some
of
the
just
a
few
features
first
and
then
we're
going
to
go
over
to
graph
Explorer.
So
I
can
walk
you
through
what
this
means.
D
So
here
we're
going
to
go
through
feature
by
feature
and
use
very
simplified
examples,
and
so,
if
you
need
to
go
back
to
any
of
these
examples,
graph
Explorer
does
have
links
to
the
documentation
and
I'll
also
give
you
resources
at
the
end,
so
you
can
walk
through
it
as
well.
So
the
first
feature
that
I've
mentioned
is
teams
message
search.
This
allows
search
of
one-on-one
chat
messages
as
well
as
Channel
messages
and
also
supports
basic
kql,
and
so
I
will
show
you
briefly
in
graph
Explorer.
D
What
this
looks
like
in
a
second
and
then
after
that
we'll
also
look
through.
You
know
what
this
also
here
is
a
little
demo
actually.
So
that
way,
you
can
see
basically
what
it
looks
like
and
we'll
kind
of
see
what
that
looks
like
in
graph
Explorer
and
then
there's
another
feature,
X
rank
which
will
allows
for
powerful,
boosting
of
the
dynamic
rank
of
items
without
changing
the
terms
in
that
query,
and
there's
a
bunch
of
different
information
about
this,
that
you
can
look
up
and
we'll
walk
through
an
example
of
this
live.
D
D
So
what
you
get
back
in
the
response
is
what
you'd
expect
and
each
hit
the
resource
actually
contains
information
about
who
sent
that
message.
Any
information
about
the
channel
ID,
the
team
ID
and
the
chat
ID.
So
that
way,
it's
easily
easily
retrievable,
based
on
what
you're
able
to
kind
of
get
in
this
response
result,
and
so
this
is
also
kind
of
compatible
with
kql.
D
So
if
I
wanted
to
see
results
that
correspond
to
being
delivered
from
a
certain
sender,
I
can
also
see
that
there
are
certain
senders
that
might
give
me
certain
Channel
and
chat
messages
and
I
can
see
that
in
the
response
body
here.
Additionally,
we
have
another
feature
which
you
could
see
a
sample
for
here,
which
is
X
rank
in
this
particular
example.
D
We're
going
to
understand
how
the
X-Wing
feature
works,
it
can
get
pretty
complicated,
there's
a
whole
bunch
of
documentation
that
exists
on
how
the
x-rank
operator
actually
works
and
all
the
different
parameters
that
you're
going
to
need.
But
for
the
purposes
of
this
example,
we're
actually
going
to
look
at
pretty
much
what
a
basic
X
rank
structure
might
look
like
and
we're
going
to
use
one
of
the
parameters
which
is
called
constant
boost,
which
allows
you
to
boost
certain
information
that
is
relevant.
D
So
here
I
just
want
to
kind
of
show
you
a
lay
of
the
land,
if
I,
only
search
for
I
I'm,
a
big
fan
of
cats
and
dogs.
So
you're
going
to
see
a
lot
of
animal
related
examples
here
and
you'll
notice
that,
as
I
run,
this
query
I
included
Fields
here,
and
this
is
what
I
was
mentioning
earlier-
that
in
your
request
body,
you
can
include
certain
fields
that
you
want
to
get
back.
So
I
get
my
cat
related
documents,
which
is
great
because
I
love,
cats
and
I
can
see.
D
I
get
my
title
and
my
author
here
and
this
is
without
X
rank,
but
what
if
I,
was
to
go
ahead
and
include
x
rank
here
by
default?
This
constant
boost
factor
is
set
to
zero
and
so
anything
I
put
after
X
rank
to
boost
certain
strings.
It's
not
going
to
have
an
effect
because
we
have
set
that
default,
so
I'm
going
to
get
the
same
order
of
my
different
cat
documents
here.
D
However,
if
I
set
this
boost
to
an
integer
above
zero
I'm
able
to
see
that
certain
results
might
be
boosted
more
than
others,
because
I
have
specified
that
so
give
it
a
second
to
run.
As
we
know,
demos
can
be
interesting.
Okay,
great
so
I
was
able
to
boost
the
information.
So
I
can
get
another
document,
that's
related
to
just
general
information.
Instead
of
all
my
cat
results
at
first.
So
this
is
just
a
very
simplified
example
of
what
you
can
expect
with
the
X
rank
feature.
D
There's
extensive
documentation
available
on
how
this
works
in
depth,
as
well
as
more
complex
examples.
So
moving
on
I
do
want
to
return
to
our
slide.
We
have
more
features
that
are
related
to
answers
that
we've
rolled
out
as
well.
So,
as
you
know,
in
the
admin
portal,
you
can
configure
your
answers,
and
today
we
allow
search
of
answer
types
that
are
bookmarks
and
acronyms.
D
So
I
want
to
walk
you
through
the
syntax
of
this.
So
that
way
you
understand
so,
as
we
know,
bookmarks
can
help,
pin
certain
results
and
allow
you
to
pretty
much
find
important
sites
and
tools,
and
so,
in
this
request,
body
you're
able
to
use
the
entity
type
bookmark
and
then
specify
your
query
string.
D
So
there
are
I'll
kind
of
show
you
some
of
the
really
interesting
words
that
you
can
leverage
in
order
to
figure
out
what
abbreviation
means,
and
so
in
the
response
you're
going
to
get
back
some
similar
information,
the
display
name,
the
description,
but
you're
also
going
to
get
back
a
stands
for
Value.
That
shows
you
what
the
abbreviation
actually
stands
for
as
well
as
the
URL.
So
with
that
being
said,
let's
go
ahead
and
try.
D
This
out
together
so
here
in
graph
Explorer,
we're
able
to
see
that
we
can
look
at
the
sample
for
bookmark,
which
is
great
amazing.
We're
going
to
go,
look
at
what
a
bookmark
looks
like,
and
so
some
of
the
same
information
I
showed
you
in
that
sample
response
body
is
what
you're
going
to
get
over
here
as
soon
as
it
loads.
This
is
a
classic
demo
experience
here,
but
you
can
see
it's
going
to
return
some
of
the
same
information
that
we
saw
earlier.
So
we're
going
to
wait
for
that
to
come
back
to
us.
D
Okay,
perfect,
wonderful,
just
in
the
nick
of
time.
So
we
see
the
display
name.
We
see
the
description,
and
so
this
is
really
really
helpful
because
you
can
actually
configure
certain
categories.
So
maybe
I
wanted
to
call
this
category
social
which
I
can
configure
in
the
admin
portal
and
then
I
can
go
ahead
and
see
that
category
shown
up
here
if
I
was
to
change
that
separately,
there's
acronyms
and
so
what's
really
interesting
about
acronyms
is
that
you
can
actually
use
a
bunch
of
different
types
of
query
string
terms
to
help
Define.
D
So
those
are
the
features
I
wanted
to
demo
for
you
today,
I'm
going
to
go
back
to
my
slide
deck
here.
So
that
way
we
can
close
out
so
I
wanted
to.
Thank
you
all
for
this
opportunity
to
walk
you
through
a
little
bit
about
what
the
search
API
does,
what
it
means
and
what
differentiates
it
from
other
apis
as
well.
I
invite
you
to
go
to
our
short
link,
AKA
dot,
Ms,
slash
graph
search,
query
to
be
able
to
try
all
of
this
out.
D
This
points
you
to
the
documentation
as
well
as
where
to
get
started
with
graph
Explorer,
as
well
as
our
Postman
collection,
so
you
can
try
it
out
in
Postman
and
feel
free
to
reach
out
with
any
questions
or,
if
you'd,
like
additional
information
with
more
complex
examples,
or
you
just
want
to
learn
more
I
really
appreciate
the
time
today.
Thank
you
all.
B
E
Perfect
so
I
prepared
a
little
presentation
today,
but
it's
not
the
first
Slide
the
first
slide,
even
though
I
joined
the
community
call
before
I
realized
I
didn't
properly
introduce
myself
before
so
I'm.
Just
gonna
do
that
in
the
school
hi.
Everyone
probably
met
most
of
you
in
the
community,
but
if
I
haven't
met
with
you
before,
my
name
is
Aisha
bash
I'm,
a
senior
Cloud
Advocate
at
Microsoft
and
M365
advocacy
I'm
based
in
Dubai
and
I
love,
Building
Solutions,
including
Microsoft
graph
Microsoft
teams,
and
my
background
is
also
Azure.
Before
joining
the
advocacy.
E
I
was
a
premier
field
engineer
at
Microsoft,
so
I
also
worked
a
lot
with
Azure
functions,
Bots
and
everything
related
with
developer
services
on
Azure.
Pretty
much
and
I
share
a
lot
on
Twitter
and
Linkedin.
If
you're
interested
in
connecting
and
sharing
what
we
learn
between
each
other
feel
free
to
connect
from
the
socials
as
well.
Today
the
search
agenda
first
off
we
will
talk
about
teams
toolkit
for
official
Studio
I
will
show
you
how
you
can
install
the
teams
toolkit
for
visual
studio.
E
E
I
will
just
walk
you
through
the
code
a
little
bit,
how
we
run
the
Adaptive
card
and
how
basically
the
bot
looks
like
on
visual
studio
and
afterwards
we
will
just
take
a
look
at
how
we
can
implement
the
new
comments
and
which
part
of
the
code
we
need
to
basically
add
more
and
so
on,
and
then
finally,
I'll
share
the
resources
with
you.
If
you're
interested
in
the
comment
Bots
with
teams
toolkit
for
visual
studio
code
last
week,
my
colleague
Gary
actually
demoed
about
comment
Bots
for
teams
took
it
for
visual
studio
code.
E
You
can
check
out
his
presentation
in
the
community
YouTube
channel
and
you
will
learn
more
how
you
can
do
the
exact
same
thing
on
Visual
Studio
code,
okay,
so
let's
get
started
with
the
team
toolkit
for
visual
studio,
so
I
already
launched
the
installer.
If
you
know
the
visual
studio,
we
need
to
first
off
install
the
visual
studio
2022
and
then,
if
you
modify,
if
you
haven't
installed
teams
toolkit
yet
then
we
actually
have
under
the
asp.net
and
web
development.
You
will
see
Microsoft
teams,
development
tools.
E
If
you
install
this
as
well,
then
you
will
get
all
the
required
debugging
items
and
as
well
as
creating
teams,
app
tools
with
this,
and
once
you
install
this,
you
are
pretty
much
good
to
go.
I
already
did
that
and
I'm
just
going
to
close
the
step.
Okay,
I
started
wanting
Visual
Studio
2022
and
the
first
thing
we
will
do
is
creating
a
new
project.
E
Once
you
you,
must
you
install
the
Microsoft
teams
development
tools?
Then,
when
you
search
about
teams,
you
will
see
this
item
coming
automatically,
which
is
a
project
template.
You
can
create
a
project
by
for
Microsoft
teams.
Just
selecting
this
and
then
next
it
automatically
did
that
in
the
previous
one,
so
I
just
got
get
back.
Okay,
let's
say
Community
called
what
and
then
I'll
just
create
this
now
I
need
to
choose
what
kind
of
what
type
of
teams
app
I
want
to
create.
We
have
notification,
Bots
comment,
bot,
Tab
and
messaging
extension.
E
We
already
talked
about
notification
bots
in
the
previous
Comedy
Calls,
and
we
also
show
how
to
build
tabs
in
the
visual
studio
with
the
team
still
kit.
Now
today
we
will
just
talk
about
the
comment
bot
first
off
to
start
with
what
is
command
bot,
it's
actually
the
simple
version
of
the
bot.
It
is
when
you
write
something
bot
replies
back
with
the
response:
it's
a
pretty
much
Hello,
World
style
bot.
When
you
say
hello,
it
says
hi
back
and
you
can
edit
the
responses.
Accordingly,
it's
really
good
practice.
E
If
you
have
bunch
of
FAQ
questions,
especially
if
you
want
to
use
q
a
make
recognitive
service
in
your
Bots,
then
comment.
Bot
is
a
really
good
place
to
store
portraits
with
the
team's
app
development.
Let's
create
this,
and
then
we
will
talk
more.
What
comment
bot
is,
if
you
haven't
tried
this
before
it
already
comes
with
some
question
type
and
not
exactly
question,
but
the
comment
to
trigger
the
answer,
and
then
it
also
provides
you
an
answer
with
an
Adaptive
card.
It's
also
pretty
good.
E
If
you're,
starting
from
scratch,
you
heard
when
you
first
run
with
F5
you'll,
see
some
results
and
afterwards
you
can
deep
dive
in
the
code
and
understand
how
the
code
structure
works.
Okay,
so
the
good
thing
is
when
you
first
start
off:
if
you're
new,
there's
a
really
good
get
started
text
file,
it
says
that
download
and
install
and
rock,
if
you
I,
don't
know
if
you
work
with
engrock,
but
it
is
providing
a
tunneling
a
resource
if
your
Bot
is
not
published.
E
Yet
you
will
have
to
create
this
tunnel
in
the
background,
so
you
will
have
to
run
and
rock
with
HTTP
5130
I
already
have
engrock
and
I
need
to
run
this
before
I
prepare
my
bot
for
the
dependencies.
Let
me
just
select
and
rock
and
if
you're
new,
to
engrock
concept,
you
can
actually
search
for
help
and
it
will
bring
all
the
resources
that
you
can
call
for
the
engrock
all
the
types
you
can
create
a
tunneling
and
so
on.
E
For
us
we
will
just
copy
paste
and
grog
HTTP
5130,
and
then
it
should
work
for
us.
Okay
and
it's
free
I
haven't
paid
anything.
It's
just
running
tunneling,
localhost,
51
30
for
me
and
then
I
will
start
preparing
my
bot
okay.
So
it
already
says
in
here
when
you
run
engrock,
just
go
ahead,
right
click
to
the
project
and
then
select
teams
toolkit
and
prepare
teams
app
dependencies.
Let's
do
that
and
it
also
says
sign
in
with
Microsoft
365
account
for
the
teams
organization.
E
E
This
is
the
account
I
created
as
a
demo
account
if
you
want,
if
you
don't
want
to
test
teams,
app
on
your
company
account
or
school
account,
it's
the
best
to
just
go
to
M365
developer
program
and
create
your
own
account
to
test
out
this
style
of
apps
it's
for
free
and
it
creates
you
a
Sandbox
to
play
around
with
bunch
of
users
and
emails
and
so
on.
It's
a
really
good
development
environment.
I
will
continue
with
this
and
I.
E
Will
let
my
bot
prepared
in
My
Demo
account
it
automatically
registers
the
bot
in
the
active
directory,
so
both
provisioning
is
also
done
for
us.
We
don't
have
to
worry
about
going
to
Azure
and
creating
bot
registration
and
registering
it
so
on
and
so
forth.
All
of
the
preparations
are
done
for
us
through
the
teams
toolkit.
If
you
want
to
check
out
what
is
provisioned,
you
can
take
a
look
at
the
code.
We
will
do
that
in
a
second.
E
Let's,
just
first
try
the
app
and
see
what
it
is
providing
and
lastly,
it
says
over
here
that
press,
F5
or
select
the
Box
start
debugging
and
don't
forget.
We
have
to
say
hello
world
to
trigger
the
response
in
here.
We
will
just
need
to
click
this
button
and
you
can
choose
the
browser
of
your
choice:
I'm
going
to
choose
Microsoft,
Edge
and
click
over
here.
E
This
will
automatically
start
running
teams
on
Microsoft
Edge,
and
then
it
will
come
with
already
authorized
user.
I
chosen
the
preparation,
you
remember
it's
ichabus
at
n365,
Advocates
account
teams
comes
with
the
login
user
and
when
it
is
ready
it
will
pop
the
app
that
we
would
like
to
run.
We
will
just
click
on
ADD
and
then
app
will
start
running
on
our
personal
chat.
If
you
want
to
change
that,
you
can
also
just
test
this
out
in
the
channel
or
group
chat,
so
on
so
forth.
E
E
We
already
know
what
we
will
say
to
the
bot
as
a
trigger
it's
hello
world,
but
we
don't
know
the
outcome
yet
I
will
just
test
it
out
first
and
then
I
will
show
you
where
the
response
is
coming
from,
and
here
we
already
have
suggestions,
which
is
a
great
thing,
if
you're
starting
from
scratch,
or
even
for
your
users,
it's
great
to
provide
a
suggestion
so
that
they're
not
confused
what
to
do
in
the
first
place.
I
will
just
send
hello
world
and
expect
what
to
respond
back
with
a
message.
E
Hopefully
adaptive
card
yeah.
So
we
have
an
Adaptive
card
here,
ready.
It's
saying:
congratulations,
your
hello
world
bot
is
running
and
it
provides
two
links
once
one
of
the
links
will
go
to
both
framework
docs
and
the
other
one
is
the
teams
toolkit
docs,
which
is
great.
You
can
exactly
do
the
same
thing
for
your
own
questions
and
answers,
and
as
I
mentioned,
this
is
really
useful
comment.
Bot
is
really
useful
when
it
comes
to
using
q
a
maker
with
it.
E
If
you
have
bunch
of
bunch
of
questions
on
your
website
and
you
can
literally
copy
paste
the
link
of
your
website
q,
a
maker
will
generate
automatically
questions
and
answers
for
you.
You
will
just
need
to
use
the
Q
a
maker
API
in
your
comment,
bot
and
you're
good-
to
go
all
right,
let's
deep
dive
in
the
code.
This
is
pretty
much
what
we
can
do
so
far,
because
we
didn't
edit
the
bot.
Let's
understand
where
the
response
is
coming
from.
E
First
off
I'm,
just
gonna
close
this,
and
so
here
we
have
commands
and
we
have
Hello
World
comment
handlers.
Yes,
this
is
the
place
we
actually
rendered
it
adaptive
cards
and
we
read
the
adapt
card
as
a
response
to
the
trigger.
As
you
can
see
here,
we
have
trigger
patterns.
This
is
where
we
Define
the
trigger
for
our
comment.
Handler
a
here,
we
say
hello
world,
but
we
can
literally
change
this
to
Ping
and
then,
when
we
write
ping,
then
what
will
respond
back
with
answers
of
the
Adaptive
card?
E
It
is
defined
as
hello
world.json
and
it
stays
under
the
resources
over
here.
Let's
quickly
take
a
look
at
the
Json,
so
this
is
the
Adaptive
cards
template
we
are
using.
They
literally
have
title
description
which
is
defined
as
buddy,
and
we
have
two
buttons
over
here,
but
if
you
want
to
create
your
own
adaptive
card
and
if
you
don't
want
to
write
by
hand
manually,
you
can
just
go
to
Adaptive
cards.io
and
you
can
there's
also
a
designer.
You
can
drag
and
drop
buttons
and
descriptions.
E
You
can
literally
build
your
own
adaptive
card
and
the
only
thing
you
need
to
do
is
just
copy
paste
of
the
Json
file
over
here
and
then
the
Handler
will
mainly
read
your
own
adaptive
card
when
you
define
it
over
here
once
we
trigger
the
command
bot
with
hello
world,
let's
scroll
back
down-
and
here
is
the
handle-
comment
async.
This
is
the
part
that
we
handle
the
comment
and,
as
you
see,
you're
actually
logging
the
message
of
the
user,
a
message.
The
text
in
here
is
user's
message,
which
is
hello.
E
World
I
already
wrote
hello
world
in
a
it
is
logged
by
the
bot,
our
code
and
after
that,
once
we
are
done
login.
We
will
just
read
the
Adaptive
core
template,
which
is
a
template
we
defined
on
top
over
here,
a
hello
world
card,
and
it
should
be
defined,
yeah,
adapter
card
file,
path,
yeah,
it's
defined
over
here
adaptive
card
template
and
then
render
the
card
content
and
we
are
able
to
fill
the
card
content
by
ourselves.
E
That
means
that
if
you
want
to
reuse
the
same
adaptive
card
template
hello
worldcard.json,
the
only
thing
you
need
to
do
is
just
creating
multiple
models
like
title
and
the
body
and-
and
you
can
give
different
responses
to
the
different
questions
in
here.
It
says
title
your
hello
world
bot
is
running,
but
then,
by
defining
a
new
trigger
on
top,
you
can
literally
just
have
a
new
model
by
using
the
same
adaptive
card.
You
can
just
give
another
response
to
the
user.
E
It
means
that
if
you
have,
let's
say
hundreds
of
different
answers
to
hundreds
of
different
questions,
you
don't
have
to
create
different
adaptive
cards
for
each
and
every
one
of
them.
You
can
literally
pass
and
render
the
same
adaptive
cardboard
just
defining
the
parameters,
and
we
built
the
attachment.
E
That's
the
microsoft.card
Adaptive,
and
this
is
a
classic
bio
calling
the
Adaptive
card,
and
then
it
will
just
send
the
response
and
if
I
need
to
walk
you
through
the
rest
of
the
code,
we
actually
have
that
effects
file
which
we
have
the
states
of
the
user
when
we
right
click
to
the
bot
and
go
to
teams
toolkit
and
prepare
teams
app
dependencies.
It
literally
creates
this
local
dot
user
data,
which
includes
all
of
the
active
directory
and
the
bot
provisioning
information
about
my
bot.
E
And
if
you
delete
this,
you
will
have
to
regenerate
and
prepare
the
dependencies
from
scratch.
It's
important,
because
if
you
want
to
remove
the
Bots
and
test
it
out
as
from
scratch
like
Incognito,
you
will
have
to
delete
this
and
test
it
out
again.
Let's
close
the
comments,
because
we
know
hello
world
comment
handlers.
Yes
already,
we
have
a
bot
controller
over
here
which
has
two
logs.
We
are
keeping
the
conversation
and
the
Bots
pretty
much.
We
are
passing
two
of
them.
E
These
two
are
quite
important
for
us
and
we
also
have
model
if
you
want
to
design
a
new
adaptive
card
and
pass
new
information.
Let's
say
instead
of
title
and
body,
you
can
pass
username
user,
ID
user,
email
address
and
stuff.
You
will
just
have
to
create
a
new
adaptive
card
and
then
the
new
model
for
your
adaptive
card.
This
is
only
used
for
filling
out
the
information
that
we
Define
in
that
episode
card.
As
you
can
see,
we
use
dollar
sign
and
the
title
dollar
sign,
curl
bracket
and
body.
E
We
can
reuse
the
same
card
again
again.
Finally,
we
have
the
templates.
One
template
is
for
app
package,
which
includes
our
manifest
for
teams,
and
then
we
have
app
resources.
It
is
totally
changeable
if
you
want
to
define
a
image
for
your
own
teams
app
and
if
you
want
to
change
the
Manifest
for
your
teams
up,
you
can
do
it
from
here
and
we
have
Azure.
This
has
all
the
provisioning
biceps
for
bot
service
identity,
web
app
and
also
we
have
teams
FX.
E
We
need
to
handle
all
these
I'm
just
showing,
but
these
are
the
parts
that
are
already
automated
with
biceps.
So
when
you
run
the
app
dependencies
for
your
Bot,
so
sorry
when
you
right
click
to
the
bot
and
then
teams
toolkit
and
then
prepare
teams
app
dependencies,
these
parts
are
all
handled
by
the
teams.
Okay,
you
don't
have
to
worry
about
setting
up
any
of
these.
E
But
after
that
you're
pretty
much
good
to
go
and
you
can
Define
your
own
resources.
What
I
recommend
highly
if
you
already
practice
comment
bots
on
Visual,
Studio,
Visual,
Studio
code,
I,
highly
recommend
you
to
test
out
comment
bot
with
the
Q.
A
maker
this
will
make
a
big
difference
in
terms
of
defining
thousands
of
questions
and
thousands
of
answers.
It
automatically
gets
all
the
questions
and
answers
from
an
Excel
file
or
website,
or
some
other
place
that
you
can
copy
paste
the
URL
and
it
will
Define
all
the
questions
and
answers.
E
B
That
was
a
lot
of
stuff,
I
chopped
so
really
really
cool
and
a
good
to
walk
through
this
scenario
as
well.
So
now
we
have
two
different,
create
demo,
videos,
first
from
Gary
and
then
from
I
shop
on
the
different
scenarios,
but
one
was
for
the
donut
node.js
and
vs
code,
and
this
one
was,
with
our
studio
code,
IDE,
so
really
cool
to
see
that
getting
G8
as
well
awesome
stuff,
thank
you
Aisha.
B
So
we
are
pretty
much
good
to
go
from
this
week,
so
just
to
recap
and
Cherry
had
to
create
demo
related
on
the
introduction
on
Microsoft
craft
search
apis,
and
thank
you
for
having
that
context
and
guiding
people
on
the
topic,
really
really
cool
stuff
and
same
for
Aisha,
a
really
really
cool
great
demo
on
how
to
build
those
Microsoft
teams
bots
in
the
visual
studio
and
which
is
the
newest
way
of
doing
things
in
the
visual
studio
toolkit
so
awesome
stuff.
Thank
you,
Paul
for
the
great
demos.
B
Now,
let's
jump
in
here
and
the
recording
will
be
available
in
24
hours
in
the
Microsoft
365
Community
YouTube
channel.
This
is
akms
M365
videos.
You
should
be
subscribing
that
one,
so
you
will
get
the
notifications
when
there's
new
videos
available.
We
do
release
at
least
one
new
video
every
single
day,
every
single
weekday
to
be
precise,
not
on
weekends.
So
it
is
a
great
channel
of
getting
to
know
how
to
do
extensibility,
Microsoft
365
with
the
community
at
recorded
call
recordings
and
Community
demos
and
a
lot
of
other
stuff
as
well.
B
You
can
also
follow
us
on
Twitter
at
Microsoft,
365,
Dev
or
M365
PMP,
and
the
next
micro
365
platform
called
is
on
October
25th,
we're
already
in
the
end
of
October.
It's
pretty
amazing
at
8am
Pacific
time,
so
that
is
the
Tuesday
call,
every
single
Tuesday,
8
AM,
Pacific
time
cool
demos
by
Microsoft
by
PMS
or
Cloud,
Advocates
or
other
people
in
general.
B
All
of
our
calls
are
available
for
downloading
as
a
recurrent
invite
from
akms
m365s
forward,
slash
course,
and
thank
you
David
for
sharing
the
links
in
the
chat
as
well
really
really
awesome
demos
today,
but
that's
all
we're
going
to
do
today.
So,
let's
say
a
few
more
minutes.
Few
minutes
for
everybody's
time
and
close
up
the
call.
Thank
you
for
joining
and
thank
you
for
awesome
feedback
and
discussions
throughout
the
call.
It's
been
really
active
chat,
which
is
exactly
what
we
want
to
have
in
this
course.
Thanks.