►
Description
In this 15-minute demo delivered by Kerem Yuceturn, Admins get an early look at the latest search box changes for OneDrive and SharePoint (and by extension Microsoft Teams). Microsoft engineering is adding a Microsoft Search scoping control to the Modern search box that optionally, you may add Microsoft Search to Classic sites. The new component allows for scoping wider, not lower (from Site to Hub to Whole organization), respects the SearchScope setting, and delivers suggestions matching the scope selected. The presenter shows search configuration. Capability release is slated for CY20Q3. This PnP community demo is taken from the monthly SharePoint Community (PnP) call recorded on June 9, 2020.Demo Presenter: Jyoti Pal (Microsoft)
Demo presenter: Kerem Yuceturk (Microsoft) | @maychief
Resources:
• Learn more about the Microsoft 365 developer community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Community (PnP) YouTube channel: https://aka.ms/m365pnp-videos
A
B
Wanted
to
talk
to
you
briefly
about
the
searchbox
changes
that
are
coming
as
part
of
Microsoft
search
in
onedrive
and
SharePoint.
My
name
is
Graeme
Jeter
I'm,
a
program
manager
with
the
onedrive
and
SharePoint
team
and
I.
Look
after
mostly
the
integration
with
Microsoft
search,
and
here
are
some
of
the
things
that
you
can
look
forward
to
over
the
next
quarter.
B
B
Whatever
occurs
in
in
the
enterprise
search
center
and,
of
course,
to
connect
their
information,
that
is
also
becoming
added
as
custom
verticals
as
well,
so
that's
kind
of
giving
users
a
better
sense
of
where
they're
searching.
So
this
is
a
big
change
for
onedrive
for
business,
because
today
there
is
only
one
way
to
search
in
onedrive
for
business
and
that's
like
a
hybrid
model
of
the
files.
B
I
recently
worked
on
or
files
shared
with
me,
plus
the
things
in
my
onedrive
for
business,
and
this
will
kind
of
provide
a
little
more
clarity,
hopefully
for
those
different
scopes
and
provides
the
folder
scoping,
which
is
kind
of
important.
The
other
thing
we're
excited
about
for
onedrive
for
business
is
the
shared
libraries
that
appear
in
onedrive
for
business.
B
You
couldn't
search
in
those
and
with
this
affordance
you
you'll
also
be
able
to
use
the
current
folder
affordance
to
go
and
search
for
things
in
those
area,
and
the
scoping
control
is
also
coming
to
the
search
boxes
in
SharePoint.
So
if
you're,
in
a
library
or
if
you're
in
the
site
you'll
be
able
to
scope
things
to
the
current
site
to
all
sites.
In
the
hub,
if
a
site
is
connected
or
associated
with
a
hub
and
again,
the
same
whole
organization
concept
is
here
where
you'll
be
able
to
jump
to
the
same
place.
B
So
it's
kind
of
disputed
versa.
Universality
of
Microsoft,
search
wherever
you
start
from
there's
a
context,
rule
thing
and
then
there's
the
ability
to
jump
to
the
whole
organization
as
needed,
and
similarly
current
folder
current
library
will
work
in
a
library
or
list
and
then
you'll
be
able
to
jump
to
the
sites,
the
hub
and
the
whole
organization
again
using
the
scoping
control
there.
So
some
things
to
call
out
this
kind
of
works
for
scoping
wider
and
not
narrower
or
lower.
B
So
you
can
go
from
site
to
hub
the
whole
organization,
but
you
can't
once
you're
in
the
hub.
You
can't
really
drill
down
into
a
site,
because
you
don't
have
a
way
of
selecting
that
site.
Hopefully
that's
obvious.
We
have
a
setting
called
search
scope,
which
we
will
I
will
remind
everybody
about
in
two
slides
over
that
allows
you
to
say:
hey
I
want
my
site
to
start
searching
at
the
hub
level
or
at
the
whole
organization
level,
and
if
any
of
these
settings
are
set,
then
you'll
see
only
those
options
here.
B
So
if
you
set
it
to
hub,
for
example,
for
a
site
that
is
associated
with
the
hub,
you'll
only
see
the
all
sides
in
hub
and
whole
organization
scopes.
You
want
see
the
current
site
scope
and
then,
if
you
set
it
to
whole
organization
again,
whole
organization
will
be
the
scope,
and
so
you
won't
see
the
scoping
visual
since
you
can't
change
it
further
down
and
then
the
suggestions
that
we
show
will
match
the
scope
selected.
B
So
if
you're
switching
over
to
current
folder,
for
example
in
a
library
or
in
your
onedrive,
you
see
suggestions
from
that
scope.
If
you're
switching
to
hub
or
whole
organization,
you
get
the
suggestions
for
that
for
that
selection.
So
it
will,
it
will
match.
The
suggestions
that
appear
under
the
search
box
will
match
those
things
and
there's
a
subtle
line
here
that
you
may
notice.
So
this
is
kind
of
like
hey
you're,
jumping
out
into
another
experience
indicator
for
the
scoping
control.
B
Similarly,
if
you're
in
a
folder
in
a
library
in
SharePoint
sites-
and
then
you
switch
to
current
site
or
old
sites,
will
open
a
new
tab
and
go
to
the
site,
search
experience
or
the
hub
search
experience
and
leave
the
library
experience
behind.
So
that's
kind
of
a
subtle
indicator
that
you'll
switch
to
a
new
tab
for
for
these
scopes
here
and
if
you
set
a
custom
results
page
for
the
new
search
box,
those
that
will
continue
to
work.
B
So
we
will
always
take
you
to
custom
results
page,
but
you'll
have
to
punch
in
the
scope
accordingly
and
then
switch
that
up.
If
you,
if
you
need
to
alright
moving
on
the
other
feature,
I
wanted
to
tell
you
about,
is
Microsoft
search
for
classic
sites,
so
this
is
also.
This
was
expected
in
this
quarter
that
we're
in
but
we're
in
July
in
June,
and
you
may
have
been
suspicious
that
you
haven't
heard
that
this
was
coming
already.
B
We
aren't
having
a
little
delay
there
with
the
rollout
of
the
Microsoft
search
search
box,
but
we
are
now
testing
this
inside
Microsoft.
So
I
expect
this
to
rollout
to
targeted
release
in
the
third
quarter
of
the
year
and
then
to
broader
production
customers
as
well.
So
the
concept
here
is
relatively
simple,
but
it's
a
little
difficult
to
pull
off
so
but
I'll
try
to
explain
it
and
then
I'll
go
into
the
next
slide
and
go
through
some
of
the
details
of
how
you
can
kind
of
manage
this
experience.
B
So
the
idea
here
is
that
hey,
if
you
have
classic
sites
that
are
not
customized,
there's
no
reason
they
shouldn't
be
using
Microsoft
search.
We
are
already
indexing
all
the
content
in
your
classic
sites
in
Microsoft,
search
and,
ideally,
you'll
be
able
to
use
the
Microsoft
search
experience,
which
offers
a
little
better
relevance
and
ranking
experience
and
is
consistent
with
the
modern
experiences
that
you're
getting
on
your
classic
sites
too.
B
In
those
cases,
we
will,
by
default,
try
to
remove
the
search
box,
that's
built
into
the
basic
master
page
and
then
add
the
microsoft
search
search
box
to
the
top
of
the
page
and
as
your
users
are
using
this,
it
will
kind
of
work
the
same
way
as
the
search
box
that
you'd
find
in
a
modern
site,
and
it
will
take
you
to
the
modern,
Microsoft
search
search
results
go
up
to
that
site
and
show
you
the
results
from
there.
Now,
of
course,
we
may
have
multiple
reads
why
you
wouldn't
want
that.
B
For
example,
if
you
customize
your
search
experience-
and
you
know,
you've
added
experiences
like
custom,
display,
templates,
etc,
and-
and
you
don't
want
to
switch
your
experience-
you'll
be
able
to
opt
out
of
that
experience
so
that
classic
pages
are
not
touched
or,
of
course,
showing
using
the
concepts
that
you
presented
earlier.
You
would
be
able
to
also
implement
some
of
those
customizations
in
modern
and
and
start
using
those
as
well.
So
there's
a
there's.
You
know
a
bit
of
a
optionality
there.
B
We
are
not
going
to
try
to
automatically
upgrade
sites
that
have
publishing
turned
on
at
the
site
level
or
have
a
custom
master
page
with
a
different
name
than
Seattle
dot
master
or
a
Autobot
master,
and
we
will
not
attempt
to
upgrade
those
since
they
may
have
other
customizations
in
there
that
that
we
don't
want
to
break
with
the
custom
master
pages.
In
those
cases,
everything
will
continue
to
work,
but
you
will
be
able
to
opt
in
if
you
still
want
the
Microsoft
switch
experience
there
using
our
search
box
in
navbar
setting.
B
So
how
would
that
work?
Let
me
quickly
go
over
that
and
then
I'll
try
to
take
any
questions
if
we
get
time
or
I
can
follow
up
with
questions
later.
So,
as
you
know,
we
have
two
web
and
site
collection
level
settings
that
is,
that
is
available
now.
Actually,
so
this
is
available
for
you
that
you
can
set
these
settings
today.
The
first
one
is
the
search,
scope,
web
doc,
search
scope
setting.
B
This
is
also
available
through
several
helpers
in
the
PNP
powershell,
but
this
is
the
one
that
allows
you
to
set
the
default
scope
to
be
at
the
site
level
at
the
hub
level
or
the
whole
organization
level
for
a
given
SharePoint
sites.
So
this
continues
to
work.
There
isn't
much
change
here.
It
kind
of
has
a
bearing
on
the
scoping
control
that
we
just
covered
earlier.
B
So
this
is
the
site
collection,
teddie,
and
this
is
the
site
setting
the
web
espy
web
setting,
and
this
will
overwrite
the
broader
thing
if
this
is
set
to
default
or
if
this
is
set
to
default,
you
can
override
it
using
the
site,
collection
level,
but
if
the
site
has
set
something
at
one
of
these
settings
and
the
web
can
override
that
by
setting
one
of
these
settings
explicitly
as
well.
So
it
kind
of
gives
you
a
bit
of
flexibility
in
how
to
combine
those
two,
the
site
collection,
level
and
the
site
level.
B
So
zero
is
the
default
setting,
and
this
is
the
behavior
that
I
was
telling
you
about
where
we
will
try
to
upgrade
the
team
sites
that
don't
have
the
publishing
feature
turned
on
or
don't
use
a
custom
master
package
and
the
search
box
will
just
move
to
the
top
removed
from
the
page
and
then
you're
starting
to
use
the
setting
there
and
any
sites
that
have
the
site
publishing
feature
turned
on
or
have
a
custom
master
page.
They
do
not
have
it,
they
do
not
see
any
change.
B
For
those
cases,
the
number
two
option
is
an
opt-out,
so
if
you're
in
the
first,
if
you're
in
the
bucket,
where
you're
in
a
team
site
you're
using
classic
pages
but
you're,
not
using
the
publishing
feature
at
the
site
level-
and
you
don't
have
a
custom
master
page
and
you
want
to
make
sure
that
you
continue
to
use
the
classic
experience.
This
is
your
opt-out.
B
You've
set
this
for
your
web
or
your
site
collection
and
none
of
the
none
of
those
sites
with
this
set
or
the
the
site
collection
with
this
set
will
be
upgraded
to
Microsoft
search.
So
this
is
kind
of
an
opt-out
model
and
then
last
but
not
least,
I
know
some
of
us
and
some
customers
want
to
make
sure
that
there
is
no
search
box
and
they
want
to
provide
their
own
search
box
or
they
want
to
disable
search
all
together
for
a
given
site
or
site
collection.
B
And
this
last
setting
is
to
hide
the
search
box
that
we
provide
in
the
street
a
navigation
bar.
And
when
you
set
this,
then
we
will
not
admit
the
search
box
into
the
page
and
you'll
be
free
to
do
whatever
you
want,
using
SharePoint
framework,
extensions
or
any
other
mechanism
that
you
may
be
using
note
that
this
will
only
affect
modern
pages
classic
pages,
because
you
already
have
a
way
to
modify
the
master
page,
we're
not
going
to
touch
those
and
try
to
do
anything
there.
So
this
is
kind
of
a
hide.
B
A
Much
pretty
much
did
the
only
question.
Karen
was
that's
the
kind
of
a
thing
which
came
from
Frank
corner
and
few
others
is
text
and
stability
story
under
the
new
controls.
Are
they
weight
parts
or
are
they
something
which
can
be
connected
to
other
web
parts
as
well?
If
you
are
tea
or
somebody
can
actually
answer
on
done
so,
are
they
if
their
weight
parts,
then
they
have
webpart
connections,
and
then
people
can
extend
to
experience
torture,
that
model
meaning.
B
Jody
as
far
as
I
know
feel
free
to
jump
in,
but
they
are
not
well
quite
right.
This
is
basically
a
configuration
that
the
search
page
reads
and
it
is
kind
of
a
component
that
Microsoft
runs.
So
it's
not
they're,
not
individual
web
parts.
On
that
page,
it's
kind
of
a
monolithic
search
results
page
that
has
those
components
on
it
and
with
the
configuration
the
admin
experience.
A
Absolutely
yes,
okay,
so
yeah
an
annuity
and
so
that
that
there's
no
customization
at
one
point
for
now,
but
it
might
be
good,
let's
say
as
a
Cheston
to
have
an
extensibility
point
in
those
things.
So
you
cannot
then
potentially
add
new
webparts
on
a
page,
and
so
you
wouldn't
actually
have
to
overwrite.
Once
we
have
an
out-of-the-box,
you
just
extend
what
we
have
out
of
the
box.
So
but
again
that's
coming
later.