►
From YouTube: Getting started with Microsoft Viva Topics
Description
In this 46-minute all audiences-focused demo, Naomi Moneypenny steps through the latest system and tools to help customers manage knowledge within their organizations through a conscious AI assisted strategy of connecting people and actionable knowledge. Content is ultimately rendered through the Topic web part. Topics along with aligned content and SMEs are initially discovered through AI algorithms, then confirmed and curated by humans. Topics draws on numerous product and services capabilities from across Microsoft and can be extended by you. This PnP Community demo is taken from the SharePoint monthly community call recorded on March 9, 2021.
Demo Presenter: Naomi Moneypenny (Microsoft) | @nmoneypenny
Supporting documents:
• Documentation - Set up Microsoft Viva Topics | https://docs.microsoft.com/en-us/microsoft-365/knowledge/set-up-topic-experiences
• Overview - Microsoft Viva | https://aka.ms/Viva
• Microsoft Viva Topics | https://aka.ms/Viva/Topics
• SharePoint Syntex | https://aka.ms/SharePointSyntex
• Content Services Partner Program | https://aka.ms/ContentServicesProgram
• Microsoft Knowledge & Content Services Resource Center | https://aka.ms/KCS
• Documentation - Microsoft Search Graph Content Connectors | https://aka.ms/Iwantconnectors
Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
Thank
you
folks.
I
was
going
to
talk
a
little
bit
about
how
we
get
started
with
viva
topics,
and
I
wanted
to
start
that
off
by
basically
answering
some
big
questions
that
I
get
all
the
time
and
I'm
gonna
do
that
from
the
perspective
of
both
a
customer
that
might
be
thinking
through
the
adoption
of
it
as
well
as
some
end
users.
Maybe
you've
tried
out
a
few
things
yourself
as
well,
so
I'm
just
gonna
do
that,
and
so
I
wanted
to
sort
of
talk
through
that.
A
What
I
will
say
up
front
is,
of
course
we
are
working
on
apis,
and
so
we
are
still
working
on
those,
and
I
want
to
make
sure
that
folks
do
understand
that
something
is
incredibly
important
to
the
journey
that
we're
on.
We
will
be
using.
Obviously,
the
the
microsoft
graph
is
the
source
for
all
of
those
apis
and
that's
where
you'll
be
able
to
get
that
information
from,
but
right
now
we
do
not
have
any
publicly
available
end
points
for
for
topics.
A
A
Okay,
so
let's
talk
a
little
bit
about
viva
topics
and
lisa
was
very
clear
to
sort
of
try
to
give
me
instructions
on
hey,
don't
repeat
what
we've
seen
that
ignite?
Don't
repeat
what
we've
seen
in
many
presentations
already,
so
I
thought
it
would
be
good
just
to
to
take
a
couple
steps
back
and
answer
some
of
the
key
questions
that
I
get
all
the
time.
A
So
the
first
thing
is
oftentimes
like.
Why
should
I
even
care
about
managing
knowledge
in
an
organization-
and
this
is
a
big
one,
because
it's
something
that's
maybe
been
around
for
a
long
time
if
you've
been
in
this
area
before,
if
you've
been
in
it
for
a
long
time,
you
may
recognize
this
knowledge
management
problem
keeps
coming
up
right.
You
might
have
seen
different
forms
of
it
in
different
companies,
but
it's
often
still
a
big
issue
inside
of
organizations
and
there
really
hasn't
been
a
systematic
and
scalable
way
of
doing
that.
A
There's
been
lots
of
heroic
efforts.
There
are
some
companies
who
are
really
great
at
it
inside
of
their
organizations,
and
then
there
are
other
folks
and
other
customers
who
are
like
well
it'd,
be
awesome
if
we
could
do
that,
but
we
we're
not
able
to
do
that
yet,
and
so
what
we're
trying
to
do
with
viva
topics
is
really
allow
a
place
to
to
manage
topics
and
manage
knowledge,
essentially
as
a
conscious
strategy.
A
Part
of
that
is
needing
a
system
and
tools,
basically
to
help
you
to
do
that,
and
that
conscious
strategy
of
connecting
the
right
people
at
the
right
time
is
really
about
how
we're
we're
making
that
come
to
life.
And
all
of
this
is
about
you
know.
How
do
we
create
that
that
knowledge
inside
of
the
organization
and
then
how
do
we
help
you
to
put
that
information
into
action?
And
it's
an
important
piece
of
this
because
knowledge
is,
is
not
useful
if
it's,
if
it's
not
being
used
right.
A
So
it's
one
of
those
things
where
we
might
try
to
curate
it.
You
might
have
worked
on
systems
before
in
the
past,
where
hey
we're
going
to
have
a
knowledge
base
and
we're
going
to
keep
everything
in
the
company
in
there
and
if
you
keep
that
knowledge
base,
that's
awesome,
but
you
know
folks
have
to
remember
to
go
there
and
over
time
the
knowledge
tends
to
degrade
because
it's
not
being
updated,
and
it
requires
a
lot
of
work
to
do
that
and
so
putting
that
knowledge
to
work.
A
Putting
it
into
interaction
is
really
what
drives
the
value
for
our
customers.
One
of
the
great
quotes
I
always
have
here
is
really
around.
You
know
people
spending
an
hour
or
so
a
day
searching
or
reusing
information,
and
that's
one
of
those
areas
where
searching
for
that
information
recreating.
It
is
just
a
big
part
of
of
the
work
that
we
all
do,
and
so
we
should
recognize.
You
know
seven
weeks
a
year.
It's
a
huge
thing
right.
A
If
we
can
just
make
a
dent
into
thinking
that
taking
back
some
of
that
seven
weeks
a
year,
it's
incredible
and
then
the
use
cases.
I
have
listed
here
on
information
experts,
duplication
of
effort,
duplicating
products
inside
of
a
company,
avoiding
the
cold
start
problems.
Those
are
not
things
that
I
made
up.
A
Those
are
things
that
came
from
our
preview
customers
and
so
they're
very
specific
use
cases
how
you
action
those
inside
of
an
organization
as
well,
really
help
it
to
come
to
life,
and
so
these
are
the
key
things
that
folks
have
been
looking
at
with
viva
topics.
I
will
say
you
know
this
is
a
different
offering
in
the
in
the
marketplace.
So
if
I
look
across,
you
know
lots
and
lots
of
different
amazing
companies
that
are
out
there
like
what
we're
doing
with
viva
topics,
I
think,
is
very
different.
A
It
is
a
you
know,
a
systematic
and
scalable
way
of
how
you
manage
knowledge
inside
of
an
organization,
and
it
has
lots
and
lots
of
interesting.
You
know
consequences
because
of
that
when
you're
in
sort
of
that
leadership
position
and
you're
sort
of
looking
at
hey
how
we're
helping
to
form
something,
there's,
you
know
lots
of
lots
of
good
things
that
come
along
with
that.
A
Okay,
I
wanted
to
start
with
just
a
couple
things
because
oftentimes
when
you're
implementing
these
kinds
of
tools,
the
first
thing
we
want
to
think
through
is
a
little
bit
on
the
culture
side
of
an
organization,
and
these
are
things
that
folks
should
recognize.
I
think,
inside
of
of
your
own
experiences
you
might
have
had
you
know
lots
of
different
companies,
they're
managed
in
a
different
way.
Their
culture
is
different.
Do
you
have
a
culture,
that's
about
information
sharing.
A
Does
it
even
value
some
of
those
things
inside
of
organizations
already,
and
so
I
thought
it
was
good
to
sort
of
take
a
an
approach
here
to
help
categorize
some
of
those
and
every
company
is
different
right.
Every
company's
culture
is
different,
even
within
the
same
company
right.
Those
cultures
could
be
different
right,
so
different
business
units,
different
product
lines,
etc.
They
can
all
have
their
their
own
ways
too,
but
I
thought
it
was
good
to
just
check
through
a
couple
things.
A
Atomization
is
the
first
one
that
I
have
on
the
left
and
the
reason
I
talk
about
that
is
because
atomization
is
oftentimes
happened
inside
of
an
organization
where
you've
got
very
distinct
product
lines.
Maybe
it's
a
company,
that's
grown
historically
by
acquisition,
a
lot
and
there
isn't
a
lot
of
cross-organization
synergy,
and
so,
when
you
have
that
atomization
happening
there
is
a
few
approaches
you
can
think
through
with
with
knowledge
sharing
inside
of
your
organization,
and
it's
really
around
identifying
some
of
those
key
subject
matter:
experts
for
a
specific
area.
A
Now,
there's
also
a
bunch
of
folks
around
the
hub
and
spoke
model,
and
this
is
one
I
think
you
should
all
recognize.
I
think
most
of
most
companies
feel
like
they
do
a
little
of
this
there's
lots
of
motivated
grass
roots,
so
people
are
like
yes,
if
only
we
could
do
knowledge
sharing
better.
If
only
I
could
learn
what
was
going
on
across
this
other
part
of
the
organization
you
know
these
are
these
are
areas
here,
but
oftentimes.
It
isn't
something.
That's
that's
mandated,
shall
we
say
across
the
company.
A
If
you
will
right
and
it's
an
easy
way
to
get
started
in
terms
of
here's,
the
topics
that
you
want
to
work
on.
These
are
verified
topics
in
an
organization
and
it
helps
to
scale
out
that
grassroots
effort,
while
still
maintaining
that
degree
of
control
that
folks
want
as
part
of
this
kind
of
hub
and
spoke
model,
and
then
the
connected
areas
here.
A
They
realize
afterwards
that
you
know,
in
fact,
thinking
through
a
crowdsourcing
approach
is
actually
maybe
a
better
way
to
think
this
through
and
being
able
to
trust
folks
inside
of
their
organizations
and
understand
some
of
the
responsibilities
that
come
with
that
as
well.
And
so
you
know
in
that
case,
it's
really
about
you
know,
motivating
that
champions
group
to
get
started
and
thinking
through
what
you
can
do
with
crowdsourcing.
A
The
cool
thing
is:
what
we're
doing
with
viva
topics
helps
you
adapt
to
any
of
these
structures
right,
and
so,
when
we
try
to
build
the
product,
there's
lots
of
different
options
within
there.
But
it's
important
to
say:
hey
I've
got
this
balance
of.
Maybe
I
want
to
lock
things
down
really
tightly
inside
of
my
organization,
so
I
can
just
get
started
and
just
try
this
thing
out,
or
maybe
I'm
willing
to
go.
A
You
know
look
at
the
crowdsourcing
both
of
suggested
topics,
crowdsourcing
of
curation,
of
topics
all
of
those
areas,
and
so
we
have
different
ways
and
different
approaches
within
the
same
products
to
enable
those-
and
I
think
it's
just
an
important
part
of
making
sure
that
you're
setting
up
for
success
as
part
of
this
okay,
I'm
gonna
move
on.
So
what
do
you
need
for
this?
So
you
need
lots
of
content
and
you
need
activity,
and
so
this
is
one
of
those
areas
where
we're
building
this
product.
A
For
you
know
some
of
the
the
largest
customers
in
the
world
right
now,
in
terms
of
you
know,
the
customers
we've
been
working
through
with
preview.
Now,
that's
not
to
say
it
doesn't
work
for
smaller
companies
and
smaller
businesses.
Right
we've
got
folks
who
are
medium-sized
businesses.
I
would
say
who
have
a
few
thousand
people
in
their
organization
and
they
have
lots
and
lots
of
content,
and
they
have
just
as
much.
You
know
just
as
much
issues
with
managing
knowledge.
A
As
a
you
know,
huge
multinational
organizations
do,
but
in
order
for
us
to
scale
some
of
these
problems
and
actually
to
solve
some
of
these
areas
like
we
need
lots
of
content
and
activity
inside
of
your
organization,
and
so
the
bear,
in
my
mind,
is
like
10
000.
You
know
documents
and
pieces
of
content
that
you'll
need
right.
A
You
know,
hundreds
of
thousands
is
better,
preferably
millions
is
even
better
as
well,
and
so
those
are
one
of
the
the
big
areas,
so
lots
and
lots
of
content,
and
that's
because
it
needs
to
crunch
through
all
of
this,
it's
gonna
source,
the
the
topics
from
the
content
that
you
have
so
a
demo
tenant
that
doesn't
have
a
lot
of
content
on
it
is
not
gonna
have
successful
results.
I'm
just
gonna
be
very
straight
up
with
that.
Right
if
you've
got,
you
know,
30
100
couple
hundred
pieces
of
content.
A
Even
it's
like
there's
not
enough.
There
there's
not
enough
there
there
basically
to
be
able
to
use
this,
and
so
that's
one
of
the
the
areas
here
now.
A
couple
of
questions
that
come
up-
and
I
see
the
same
questions
also
come
up
from
lou.
So
thank
you.
So
why
can't
we
test
this
out
in
dev
tenant
before
moving
it
out
to
production
tenant?
There's
a
couple
things
there.
One
is
to
say
on
the
the
developer:
tenants
there's
a
dev
tenant
that
we
as
we
would
reference
it
inside
of
microsoft.
A
Right
has
special
characteristics.
Those
dev
tenants
are
something
where
we're
trying
to
figure
out
how
to
get
the
trial
licenses
to
actually
be
used
on
there,
and
so
that
is
a
problem.
It's
a
dome
problem
and
we're
working
on
that
if
you
just
have
a
demo
tenant,
as
I
mentioned
like-
and
you
only
have
you
know
a
few
pieces
of
content
on
there
and
you
just
want
to
do
a
30
day
trial.
Frankly,
you're
not
going
to
get
a
successful
result
right.
I'm
just
going
to
be
straight
up
about
that.
A
If
you
just
have,
you
know
less
than
100
pieces
of
content,
which
is
what
most
demo
tenants
do,
there's
not
a
lot
of
actual
content
within
those
pieces
of
content
either
because
they're,
usually
just
a
demo,
starter,
packs
type
of
stuff
right,
then
you
know:
that's,
that's
not
the
right
kind
of
data
set.
What
I
would
recommend
is
that
you
know
if
this
is
not
something
on
a
production
tenant
here
where
you
need
to
you
can
lock
down
essentially
from
a
production
tenant.
A
You
can
actually
do
all
of
the
indexing
that
you
want
to
do
for
knowledge.
You
could
see
that
only
one
person
need
to
have
access
to
actually
look
at
the
topics,
for
example,
and
so
you
can
actually
do
this
in
a
very,
very
tightly
controlled
way,
and
I
on
your
production
tenants
so
that
you
can
see
the
results
of
what's
happening
with
knowledge.
Indexing,
no
end
user
need
to
ever
see
anything
right.
A
A
What's
about
the
approach
for
smaller
organizations
right
so
with
smaller
organizations,
it
really
depends
how
much
content
you
have
and
the
kinds
of
usage
you
have
so
like
I
said,
we've
got
some
customers
who
are
have
been
working
with
us,
who
are
a
few
thousand
users
if
you're
100
users
inside
of
a
company
right,
you're,
100
people
in
the
company
and
you've
got
active
usage,
maybe
you're
a
law
firm
and
you
have
tons
and
tons
and
tons
and
tons
of
documents
right.
Then
that's
a
good
fit
for
that
right.
A
If
you're,
a
small
business
where
you
have
a
small
amount
of
folks,
but
not
a
lot
of
content,
this
isn't
going
to
be
a
great
fit
right.
It
needs
to
have
a
body
of
content.
It
needs
to
have
that
organizational
activity
around
it
basically
to
to
help
with
that,
and
so
I
want
to
sort
of
add
some
of
those
questions
there.
So
hopefully
that
helps
try
to
demystify
some
of
these.
A
These
areas
here-
and
you
know
one
of
the
the
things
I
will
say
from
a
direction
perspective
like
questions
we
get
asked
are
usually
about
the
extremes
right.
Nobody
ever
asked
me
and
say:
hey
naomi,
you
know
I've
got
you
know
a
company
of
a
few
thousand
users
and
we've
got
you
know
a
terabyte
of
information.
Is
this
going
to
be
a
good
thing
right?
That's
fine
right!
What
people
ask
me
about
is
the
extremes
of
like
hey.
A
I
have
five
users
in
this
company
or
three
users
in
this
company
or
it's
just
my
personal
demo.
Tenant
right
or
you
know
we're
the
largest
company
in
the
world
and
we
have
hundreds
of
thousands
of
employees
right.
Can
you
scale
to
that
right,
and
so,
when
we're
looking
at
the
the
topics
and
the
way
that
we've
developed
the
product
right,
we
have
to
serve
both
ends
of
the
spectrum,
but
right
now
the
scale
is
the
big
issue
right.
A
So
we
want
to
make
sure
that
we're
scaling
to
those
largest
customers
in
the
world
and
then
afterwards,
it's
actually
an
easier
process.
If
you
will
to
scale
it
down
so
bear
with
us
as
we
as
we
do
more
and
more
to
to
make
those
happen.
But
right
now
we're
definitely
looking
at
the
you
know.
How
do
we
scale
this
to
the
largest
customs
of
the
in
the
world
and
we're
feeling
good
and
confident
about
that
piece
of
it?
Okay,
so
I
wanted
to
sort
of
talk
through
a
couple
things
there
all
right.
A
The
other
area
here
is,
I
often
get
lots
of
questions
on
security
compliance
privacy.
What
else?
What
else
about
you
know,
topics
and
things
that
are
that
are
private
and
sensitive
inside
of
our
organizations?
Okay,
the
first
thing
here
is:
this
is
a
knowledge
sharing
system.
It
is
its
purpose.
Right
is
to
share
knowledge
inside
of
your
organization,
and
so
I'd
really
love
folks
to
to
look
at.
You
know
the
the
search
that
they
have,
for
example,
inside
of
their
organizations
right
now.
A
If
you
have
an
issue
with
search
right
now,
inside
of
your
company-
and
you
say:
hey
I've
got
a
lot
of
permissions
that
maybe
have
been
incorrectly
permissions.
I've
got
documents
there
right,
adding
viva
topics
on
top
of
that
is
not
going
to
help
right.
So
I'll,
just
be
very
clear
on
that.
So
the
same
permissions,
the
same
apples
that
you
have
on
documents,
the
same
groups,
everything
else
that
you
have
that's
applied
right
now.
A
Those
are
things
that
viva
topics
completely
respects
as
part
of
this,
and
so
I
would
ask
folks
to
really
think
through.
Like
understanding
hey,
you
know,
this
is
a
knowledge
sharing
system.
You
should
have
an
exclusion
list
of
things
that
you
don't
want
to
ever
find
if
there's
been
human
error
or
something
has
been
incorrectly
permissioned.
So
if
you
have
some
pending
merger
and
acquisition
inside
of
your
organization-
and
you
have
some
project
code
names
for
those
things
right,
please
have
a
list
of
those
code
names.
A
Usually
your
legal
folks
have
those
those
that
list
of
code
names
and
you
can
actually
put
that
directly
into
the
admin
controls
so
that
it
will
never
ever
be
discovered.
Even
if
you've
put
you
know,
even
though
somebody
has
incorrectly
put
those
documents
in
a
place
where
they
they
were
public,
and
so
I
think
that's
a
piece
there,
and
so
I
just
want
to
make
sure
that
folks
understand
that,
like
there
is
a
bunch
of
exclusion
controls
right,
we
listen
very,
very
deeply
to
lots
and
lots
of
customers
on.
A
A
A
So
it's
a
knowledge
management
system,
it's
a
knowledge
sharing
system,
and
I
wanted
to
sort
of
just
take
a
minute
here,
because
this
is
a
more
technical
audience
and
talk
through
a
little
bit
about
what
kinds
of
ai
is
this
so
there's
that
piece
of
it.
So
what
ai
is
this
questions
I
get
here?
Is
this
the
same
as
azure
cognitive
services?
No,
it
is
not.
A
There
is
a
huge
group
of
different
tools
and
technologies
that
we
have
had
to
bring
together
across
microsoft,
all
the
way
from
microsoft,
research
and
great
work
that
they've
been
doing
all
the
way
through
the
different
organizations
that
we
have
inside
of
the
company,
everything
from
bing
to
many
of
the
m365
components.
Putting
all
of
these
things
together
to
make
this
this
system
work,
and
so
different
types
of
ai
is
really
good
at
different
aspects
of
this,
and
so
having
been
in
ai
machine
learning.
A
So
first
thing
I
wanted
to
mention
here
is
that
topic,
identification
and
conflation.
So
just
finding
the
name
of
the
topic.
How
do
we
even
figure
out?
What
is
the
topic
inside
of
your
company
right,
and
so
that's
where
all
of
that
content
and
that
richness
that
you
have
in
activity
inside
of
your
organization
really
makes
a
difference.
So
topics
are
generated
from
the
seed
documents
that
are
in
there
right
we're.
A
Looking
through
all
the
documents
that
are
in
there,
you
get
to
specify
the
scope
of
that
indexing,
essentially
to
which
sharepoint
sites
that
you
want
right
now
to
have
as
part
of
that
and
it's
that
base,
basically
that
primordial
soup.
If
you
will
right
that,
is
it's
basically
going
through,
and
it's
looking
through
all
of
that
information
and
from
there
it
figures
out
topics
right:
it
doesn't
generate
them
against
the
list.
It
doesn't
generate
them
against
some
other
pre-trained
model
that
we
have.
That
has
all
the
topics
in
the
universe.
A
Somehow
right,
it's
it's
generating
them
specifically
for
your
organization,
and
it
is
a
function
of
the
content
that
is
put
into
the
system
right,
and
so
I
want
to
be
very
clear
on
that.
Now
there
are
other
things
you
can
do
to
kick
start
it
right.
We
want
to
be
bring
in
manage
metadata
services
like
if
you've
invested
in
mms
and
you
have
a
whole
list
of
of
product
names
or
regions
or
whatever
else
that's
important
inside
of
your
company
right.
A
A
You
can
do
that,
but
it's
basically
viva
topics
is
generating
that
from
that
source
documents
like
the
the
original
content
of
that,
which
is
why
we
we
want
to
look
at
you
know
the
every
single
one
of
those
documents
in
your
company
has
to
be
re-crunched,
essentially
right
and
figure
out.
What
are
the
topics
within
there
and
it's
got
to
look
for
all
these
different
kind
of
aspects
within
that,
and
so
it's
looking
for
different
facets
around
the
same
topic.
Is
this
the
same
information?
A
Is
it
being
reworded
in
different
and
new
ways
as
part
of
this,
and
so
that's
that's
what
it's
doing,
and
so
that
crunching
that
goes
on
there.
The
alternative
names
extraction,
the
acronyms
that
we're
doing
again,
those
are
being
sourced
from
the
content
directly
inside
of
that
too,
and
I
think
it's
just
a
very
important
piece
because
identification
that's
a
whole
different
set
of
algorithms,
how
we
do
acronyms
and
alternate
areas
here.
Those
are
different
set
of
algorithms.
A
How
we
think
about
conflation
of
like
how
are
these
two
topics
similar
or
the
same?
Could
they
possibly
be
the
same
all
of
those
areas
too,
and
so
those
are
definitely
all
different
pieces
together
now
the
definition
extraction
is
something
that
happens
from
the
documents
themselves,
and
this
is
an
important
aspect
of
everything
that
we're
doing
right.
We've
got
people
and
ai
at
every
stage.
The
ai
here
is
not
supposed
to
be
a
magic
bullet.
I
have
always
talked
about
this.
Hopefully
you
all
have
heard
me
over
the
last
couple
years.
A
Explain
a
little
bit
about
this.
It's
people
and
ai
together,
ai,
is
supposed
to
be
getting
us.
You
know
70
of
the
way
there
right
and
it's
helping
you
take
the
first
cut
so
that
it's
easier
for
people
to
come
up
to
speed
and
then
be
able
to
take
a
curation
essentially
around
it
and
help
to
edit
it,
and
the
reason
for
that
is
because
we
know
that
ai
is
not
going
to
be
perfect
right,
but
it's
easier.
A
If
something
is
able
to
create
a
first
draft
of
it
and
then
you
can
come
in
and
edit
it,
and
so
what
we're
trying
to
do
is
like
hey
people.
We
want
you
to
be
doing
the
high
value
work
here.
Taking
it,
you
know
to
the
the
end
level.
That's
it
that's
needed,
but
we
want
ai
to
take
that
first
cut,
and
so
I
kind
of
think
of
it
as
kind
of
a
robot
intern.
A
Essentially
right
so
you
know,
we've
all
been
interns
before
there's
a
bunch
of
things
that
you
have
to
do
to
crunch
through.
You
know
data
on
behalf
of
someone
else
and
it's
kind
of
doing
that
right,
and
so
you
should
think
about
it
in
that
way.
It's
not
supposed
to
be
a
perfect
silver
bullet
right.
Sometimes
it's
amazing,
and
sometimes
it
gives
me
incredible
results
and
I'm
like
wow.
It's
amazing.
A
It
just
did
all
of
that
by
itself
and
then
there
are
other
days
where
I
see
something-
and
I
was
like
that
was
just
you
know-
really,
not
very
good.
So
you
know
so
it
tells
you
that,
and
so
it's
the
same
kind
of
approach.
Right,
it's
ai
right,
so
it
is
learning
it's
understanding,
a
little
bit
more
about
the
content
every
single
day.
It's
understanding
for
the
feedback.
The
signals
that
you
give.
It
is
also
really
important
as
part
of
this
too.
A
So
I'm
just
kind
of
trying
to
hit
the
questions
here
and
make
sure
I
don't
go
over
time,
so
they
better
stop
me
as
well.
If
I
do
so
once
topics
are
curated
by
smes.
Do
future
calls
of
data
affect
the
the
cards
yeah,
so
jen.
So
this
is
a
great
question
so
on
the
topic
page
itself,
right
where
we
have
the
suggested
people
and
the
suggested
content,
and
then
there's
pinned
files
and
people
right.
So
the
pinning
piece
is
the
part,
the
subject
matter.
A
Experts
go
in
and
curate
and
that
those
links
will
always
stay
there
because
a
human
came
in
and
did
that
and
said
hey.
These
are
really
important
to
be
a
part
of
part
of
that,
but
the
suggested
files
and
content
and
suggested
people
will
continue
to
update
right
all
the
time
and
that's
what
we
want
ai
to
do
right.
A
We
want
it
to
go
off
and
actually
do
all
of
that
that
mining
essentially
for
us,
we
wanted
to
keep
the
page
up
to
date,
because
that's
the
part
we
have
a
hard
time
with
right
and
then
as
a
as
an
expert,
you
can
go
in
and
curate
it
later.
So
you
will
see
those
results
change
if
that
sme
has
not
pinned
something
directly
onto
that
page.
A
Okay,
related
people
and
then
related
documents.
It's
another
important
angle
here,
because
these
are
again
different
sets
of
algorithms
that
help
with
with
what
we're
doing
here,
so
that
suggested
people,
obviously
using
a
lot
of
the
insights
and
activity
that
we
have
in
the
microsoft
graph
that
you
all
know
and
love
so
much
and
then
the
same
thing
is
true,
with
related
documents
right
we're
looking
at
people
who
are
actively
collaborating
on
this,
we
are
not
inferring
that
these
people
are
experts
on
a
subject.
I
just
want
to
be
clear
about
that.
A
Okay,
a
couple
things
here
and
then
it's
a
good
question
alex
so
my
little
screenshot
here
and
I'll
show
your
demo
in
just
a
second.
So
here,
for
example,
on
the
the
news
page,
it
shows
a
little
bit
alex
is
asking
where
the
topics
links
show
up
on
sharepoint
pages
emails,
etc.
So
this
is
an
extraction
here
you
can
see.
A
So
hopefully
that
helps
to
understand
a
little
bit
more
there.
Okay,
I'm
gonna
go
quicker,
and
so
I
wanted
to
also
just
take
a
minute
to
understand
just
these
different
types
of
technologies
that
we're
using
behind
the
scenes
again,
because
there's
many
many
different
levels
as
part
of
this,
so
lots
of
statistical
models
that
you
might
expect
right.
There's
frequency
and
use
usage
and
recency
and
that's
you
know
a
simple
way.
Basically,
it's
a
very
basic
way
to
look
at
that
information.
A
On
top
of
that,
we
are
doing
a
whole
bunch
of
things
around
template-based
discoveries
of
patents,
and
so
we've
tried
to
look
at
different
patterns
that
we
see
for
topics
across
an
organization
trying
to
help
encode
that
into
models,
and
you
can
see
how
that
influences
acronyms
and
alternate
names
and
things
that
are
untyped
topics
right
now
and
topic
types
is
something
that
we're
also
working
hard
on
as
well
and
then
representational
learning.
So
this
is
another
piece
of
this.
A
When
you
have
these
heterogeneous
entities,
you
need
to
be
able
to
extract
out
of
those
heterogeneous
identities
to
say
entities.
Excuse
me
to
get
the
phrases
out
of
there.
So
that
means
when
I'm
looking
at
specific
documents
like,
I
need
to
be
able
to
extract
what
the
definition
is.
Even
when
something
isn't
saying,
you
know
what
is
project
cortex,
for
example,
right
and
then
there's
a
question
right.
That's
a
very
simple
question
and
answer
type
of
series.
A
What
we
want
to
be
able
to
do
is
be
able
to
take
out
that
definition
automatically
from
a
set
of
content,
and
so
that's
one
of
the
areas
where
we
we
do
a
lot
of
work
there
and
then
clustering
itself.
All
of
that
conflation
work
here
conflation
is,
is
incredibly
difficult
problem,
as
you
might
imagine
right,
lots
of
things
called
the
same
thing
inside
of
an
organization.
Many
acronyms
stand
for
a
lot
of
different
things.
A
Okay,
what
license
is
hamid
asks?
What
license
do
you
need
for
these
ai
features?
So
you
need
a
viva
topics
license
which
currently,
this
price
is
five
dollars
per
user
per
month
in
the
united
states
at
least,
and
then
it
gets
obviously
translated
into
your
local
area
as
well.
Hopefully
that
helps
okay,
so
people
on
ai
right.
These
are
things
where
we
one
again
take
that
first
assistance
of
this
too
and
so
topic
identification.
A
We
want
to
do
that
first
cut
right
and
be
able
to
make
sure
that
we're
identifying
the
knowledge
inside
of
organization
helping
to
identify
topics
themselves,
and
then
we
want
you
to
be
able
to
curate
that
information
right.
Our
goal,
of
course,
is
amazing:
to
have
some
suggested
topic
pages
that
are
totally
filled
out
already
and
give
you
a
great
start,
but
we
always
want
to
believe
in
the
power
of
people
to
come
in
and
help
curate
that
information
right.
You
have
a
context,
you
have
a
different
learnings.
A
You
have
a
subject
matter:
experts
who
are
you
know
really
motivated
by
this
area,
but
it's
always
easier
when
something
has
taken
the
first
draft
right
and
that's
really
what
that
ai
is
all
about
and
then
topic
discovery
itself,
so
discovering
knowledge
in
the
apps
and
then
thinking
through,
like
you
know,
what
are
these
topic
cards?
How
can
you
think
about
discovering
topics
in
the
everyday
work
right?
So
when
we
have
all
this
knowledge
again,
we
don't
want
to
silo
it
off
into
a
knowledge
base.
A
It's
really
difficult
to
get
to
how
you
ever
know
that
the
knowledge
exists
there,
and
so
you
know
we
want
to
bring
those
experiences
directly
into
where
you're
doing
work,
so,
whether
it's
outlook,
whether
it's
teams,
whether
it's
yammer,
whether
it's
sharepoint
and
and
many
other
canvases
inside
of
microsoft,
365,
all
of
those
things
want
to
be
lit
up
as
part
of
that
too.
Okay.
So
let
me
go
through
here
and
look
at
them.
A
Look
for
other
questions
here,
so
people
in
the
ai
there
are
these
different
roles,
so
within
those
cultural
tenants,
as
I
established
at
the
beginning,
there's
different
kinds
of
organizations,
the
different
kinds
of
cultures
that
you
want
to
support
inside
of
your
company.
There
are
some
roles
inside
of
here
as
well,
and
so
you
know
understanding,
there's
these
topic.
A
Contributors,
they're
the
subject
matter,
experts
essentially
folks,
who
can
help
curate
that
everyone
in
the
organization
should
be
helped
to
have
access
eventually
to
topics
right,
to
be
able
to
discover
knowledge
and
be
able
to
be
a
consumption
of
that
and
then
there's
kind
of
a
knowledge
manager
role
in
there.
And
so
you
might
have
multiple
knowledge
managers
inside
of
a
very
large
organization,
and
they
were
looking
at.
A
You
know:
topic
management,
creating
and
editing
et
cetera,
doing
some
work
there
and
then
there's
a
knowledge
admin,
basically
who's,
helping
with
that
too
who's
heading
up
originally
on
those
areas
too.
Okay,
let
me
switch
my
screen
over
and
do
a
couple
things
here.
So
first
one
I
wanted
to
show
you
is
just.
Let
me
show
you
one
of
these
experiences
here
and
just
understanding
a
little
bit
more.
So
this
is
an
example.
This
is
just
again
a
demo
tenant,
so
we
have
limited
data.
A
We
have
the
same
same
issues
here,
so
we've
got
limited
data
here,
but
you
do
see
some
suggested
topics
and
suggested
areas.
So
the
first
thing
is
this:
is
a
web
part
right,
so
I
just
want
to
be
very
clear
here.
This
is
the
extensibility
piece
of
of
sharepoint
normal
sharepoint
extensibility,
because
it
was
very
important
for
us
to
create
web
parts
because
customers
ask
us,
we
don't
want
to
create
another
large
another
destination
right,
another
silo
essentially
inside
of
organizations.
We
want
to
build.
A
On
top
of
what
we
already
have
right,
and
so
we
already
have
lots
of
places
in
our
intranet,
we
have
lots
of
great
content,
obviously
inside
of
sharepoint
and
sites.
Where
could
we
just
put
this
this
topics
web
part
where
we
need
it,
and
so
this
topics
web
part,
helps
you
to
understand
your
connection
to
topics,
and
so
that's
where
you
see
these
ones
that
say
suggested
topic
here:
it's
because
ai
is
saying
hey.
A
This
is
kind
of
things
I
found
and
you
can
see
that
sometimes
it's
it's
got
great
results,
and
sometimes
it
hasn't
got
a
description,
for
example
in
this
case,
but
it
thinks
there's
a
thing
there
so
remember:
it's
figured
these
things
out
by
themselves,
right
and
so
graphic
design
institute.
In
this
case,
we've
got
an
alternate
name.
It's
figured
that
out
from
from
this
proposal
document
here
and
it's
very
clear
where
it's
sourcing,
this
information
from
same
thing
is
true
here
with
driscoll
right.
You
can
see
it's
it's
extracted
this
information.
A
A
This
is
not
like
a
I
have
found
this,
and
then
you
don't
understand
where
it
got
that
information
for
it's
important
as
part
of
that
people
and
ai
pace
here,
to
make
sure
that
people
trust
what
they're
seeing
and
so
every
time
we
have
something
that
ai
has
been
generating.
We
give
you
the
evidence
for
why
it
has
generated
that
right,
and
that
explanation
here
on
the
page
is
important
so
from
these
marketing
goals
right
it
came
from
this
document.
A
This
is
where
it
got
this
particular
project
name
from
this,
this
particular
extraction
here
to
help
you
understand
what
this
this
project
is
right.
It
extracted
it
from
this
document
right
and
it's
not
because
somebody
told
it
to
it-
just
figured
it
out
by
itself
right
to
do
that,
and
then
these
suggested
people
are
based
again
on
the
activity
that
is
going
on.
So
it's
very
hard.
You
know
again
for
us
to
generate
activity
outside
of
an
organization.
That's
why
I
was
recommend
to
think
through.
A
You
know
how
you
can
run
this
on
on
the
your
daily
driver
tenant.
If
you
will,
because
you
need
that
activity
and
then
basically
to
get
started
you
want
to
you,
can
limit
it
to
a
very
small
amount
of
people
who
can
see
that
information
so
suggested
files
and
pages
here.
So
you
can
see
here
again.
These
are
things
that
it's
found
it
found
these
automatically.
A
It
will
keep
updating
this
list
constantly
until
someone
and
somebody
wants
to
pin
something
as
a
subject
matter,
expert
you're
able
to
curate
those
resources
here,
but
those
suggested
files
and
pages
are
important
and
then
again
the
reason
you're
seeing
those
things
right.
We
have
this
thing
here.
It
says
activity
right
and
it
says
why
did
I
find
this
thing?
Why
is
it
being
shown
here
right?
A
It's
actually
topic
four
times
being
mentioned,
et
cetera,
et
cetera,
right,
there's,
a
reason
that
we're
showing
you
this
information
right,
and
it's
just
trying
to
explain
you
so
that
you
you
understand
where
it's
coming
from:
it's
not
ai,
just
making
it
up
somewhere
in
the
corner
right.
So
it
came
from
your
document
right,
so
that's
part
of
that,
and
then
we
have
related
sites,
obviously,
as
part
of
this
too
again,
based
on
the
resources
that
it
found
and
be
able
to
to
show
all
those
areas
too.
A
As
part
of
this,
so
let's
see,
let's
see
the
other,
I'm
trying
to
look
at
some
other
areas
here,
all
right
so
with
driscoll
here
so
with
that
suggested
topic,
I
can
come
in
here
and
I
can
edit
this
information
right.
So
if
I
go
into
editing
this
information,
I
will
get
the
the
normal
controls
I
have
on
top
of
sharepoint
right.
This
is
again
it's
a
sharepoint
page,
so
I
can
actually
get
information
here
and
include
web
parts
etc.
As
part
of
that.
A
So,
if
I
want
to
customize
the
look
of
this
page,
I
can
do
that.
It's
a
sharepoint
page.
It
has
some
special
sections
on
here
as
well
as
to
to
so.
If
I
wanted
to
put
in
some
alternate
names,
I'm
able
to
do
that.
I
could
say:
project
disco
is
new,
so
so
and
and
a
great
way
to
share
best
practices
or
something
like
that.
Inside
of
my
company,
so
I
can
edit
this
page
basically
to
to
whatever
I
need
here
and
then
you'll
see
immediately.
A
Maybe
they
really
are
part
of
this
project
or
something
that
I
want
to
make
sure
that
they're
here
and
I
have
the
opportunity
to
either
remove
the
suggestion
altogether,
because
maybe
it's
somebody
who
worked
on
something
two
years
ago,
it's
moved
on
to
a
different
role.
I
can
do
that
easily
or
maybe
I
can
pin
people
so
in
this
case
I'm
going
to
pin
patty
here
and
then
I
get
the
opportunity
you
can
see.
We
get
those
little
check
mark
here
and
helps
me
to
understand.
A
Like
you
know,
it's
pinned
by
you
and
it's
pinned
now
and
I
can
also
even
change
the
ordering
of
folks
if
I
have
a
whole
bunch
of
folks
on
the
page
here
and
then
I
can
describe
so
how
paddy
is
connected,
so
I
can
say:
she's
the
lead
project
manager,
for
example,
okay,
so
I
can
do
all
of
that,
and
it
helps
me
describe
that
connection
now.
Here's
that
area
jen,
where
you
were
asking
earlier,
like
your
subject
matter
experts,
if
I
say
hey,
this,
is
an
overview
document.
This
is
a
great
document.
A
A
So
this
new
content
is
being
created,
it's
going
to
add
them
in
here
and
then
they
can
be
coming
and
get
curated
as
well
or
you
can
just
leave
it
to
you
know
to
do
that
that
work,
and
so
folks
can
see
that
information
as
it
comes
in
okay.
So
I
could
do
that
and
then
I
can
also
build
out
that
topic
map
and
so
right
now.
This
is
a
connected
topics
area,
so
you
can
actually
put
in
other
topics
and
include
those
connections
within
there.
A
So
if
I
wanted
to
add
in
you
know
other
things
I
don't
know,
one
of
the
other
topics
is
in
here,
but
I
think
there's
one
called
albert,
so
you
can
see
here.
I
can
connect
to
that
related
topic
and
I
can
add
this
here
and
then
I
can
say
help
other
people
understand
how
these
two
topics
are
connected.
So
similar
customer
oriented
projects
whatever
it
is,
that's
right!
So
I'm
sorry,
I'm
just
putting
some
text
right.
So
I
can
update
those
things
and
then
that
connection
is
clear
for
other
people
too.
A
Now
we're
working
on
a
ball
bunch
of
tuck
and
to
help
do
this
automatically
as
well,
but
we
want
to
importantly,
make
sure
that,
subject
matter,
experts
again
have
time
to
curate
this
information
and
are
able
to
put
all
of
this
in
here
as
well,
so
important
part
of
all
that.
Okay.
So
when
I
publish
this
information
out
because
I've
now
human
curated
this,
essentially
I
want
to
make
sure
that
the
topic
permissions
you
know
make
sure
that
things
are
actually
available
to
people
across
my
organization.
A
If
that's
my
intention
or
if
I'm
just
trying
to
keep
it
locked
down
again,
I
can
just
use
the
site
permissions
on
here
as
well
so
say:
I'm
doing
a
bunch
of
things
like
curating
pages
before
we
go
live
right.
You
might
want
to
do
that.
You
keep
the
psych
permissions
on
it
just
the
same
as
you
normally
would
in
sharepoint
and
then
you're
able
to
to
control
the
release.
If
you
will
of
those
topics
too,
so
it's
all
good
yeah
and
that's
what's
important
right
that
mind.
A
Mapping
type
of
thing
is:
there's
a
really
important
part
of
that.
So
it's
a
good
good
point
there.
So
there's
areas
too.
Okay,
so
I'm
gonna
make
sure
that
you
understand
around
those
areas.
So
how
we
do
that
that
that
role
as
a
subject
matter
expert
now,
let's
look
at
sort
of
a
topic
manager,
role
and
so
with
topic
managers.
Here
I
get
these
suggested,
confirmed,
published
and
removed.
There
is
a
life
cycle
associated
with
these,
and
so
you
suggested
topics
are
always
ones
that
ai
has
created
basically
right.
A
It's
trying
to
mine
through
all
of
that
content
and
make
sure
that
you're
able
to
to
use
that
as
well
and
then
here's
with
those
ways
to
help
you
parse
this
information,
because
there's
kind
of
that
curve
that
goes
with
it
right,
there's
a
curve
that
goes
with
what
we
implement
with
viva
topics
and
it
starts
off
with
oh,
I
don't
have
any
topics.
Why
is
it
taking
so
long?
A
You
know
taken
the
first
cut
of
these
things
and
I
think
it's
pretty
good,
and
so
it's
a
great
way
to
be
able
to
spend
your
time
and
focus
your
time
here.
The
other
area
here
is
about
the
impressions
and
so
that's
actually
generating
that
for
based
on
the
the
organization
as
well.
So
this
is
just
the
amount
of
times
that
people
have
have
seen
a
topic.
A
So
these
are
topics
that
are
being
highlighted
in
content,
so
in
a
news
page,
for
example,
automatically
or
have
been
shown,
the
search-
and
it
just
helps
you
to
parse
your
time
as
a
knowledge
manager.
So
you
can
be
focused
on
the
things
that
are
most
impactful
and
the
topics
are
most
impactful
inside
of
there
as
well,
and
then
I
can
see
here,
you
know,
suggested
people
I
can
say
yes,
this
isn't
a
topic,
I
could,
you
know,
decline
it
immediately
and
if
it's
removed,
I
think
one
of
the
questions.
A
I
couldn't
miss
the
question
exactly,
but
if
it's
a
removed
topic
in
this
case,
yes,
you
can
actually
restore
it
back.
You
can
confirm
the
removal
once
you've
confirmed
the
removal
it's
gone,
but
then
you
can
say
review
and
publish
if
you
want
to
get
it
back
again
if
that
helps
as
well.
So
I
apologize
I
missed,
who
asked
the
question
here
too.
So
all
of
those
pieces
here
so
once
the
topic
has
been
confirmed
here,
it's
now
again
that
other
life
cycle
stage
here.
A
So
these
confirmed
topics
here,
there's
always
this
nice
little
info
bubble
that
helps
you
understand
that
the
knowledge
manager
sees
the
things
that
they
have
access
to
right.
There
is
no
permission
that
allows
you
unless
the
person
has
access
to
every
piece
of
content
on
the
entire
tenant.
There
is
no
permission
that
says:
hey
the
knowledge
manager
is
able
to
to
see
all
of
those
topics
across
your
organization,
and
you
are
always
going
to
see
the
page.
A
You
know
per
your
security
permissions,
so
if
I
only
have
access
to
three
of
these
documents
right,
because
those
are
the
nature
of
the
documents
I
have
already,
I
will
only
see
those
three
as
part
of
those
suggested
files
and
pages
unless
a
person
has
come
in
and
said
no
pin
this
onto
this
onto
the
the
page
here
right.
So
these
ai,
these
ai
pieces
here
that
have
been
generated
and
suggested,
are
always
making
sure
that
we're
able
to
use
those
same
security
permissions
now
confirmed
means
that
a
person
has
confirmed
it.
A
It's
the
same
as
that
suggested
is
all
ai
confirmed,
means
that
somebody
says
yes,
this
is
a
real
topic
and
that
matches
up
with
this
area.
Here,
for
example,
if
I
wanted
to
say
hey
on
this
graphic
design
institute
one.
If
I
click
through
and
look
at
this,
I
have
no
idea
what
I'm
gonna
see
but
we'll
see.
Whatever
content
comes
up
on
this,
I
can
actually
confirm
this
as
a
topic.
Maybe
I
see
it
as
a
highlight
inside
of
my
organization,
and
I
can
confirm
it
in
there
as
well.
A
You
can
see
it's
got
information
once
this
has
been
confirmed.
It
means
the
topic
is
a
real
thing
by
a
human
right.
So
a
human
who
says
yes,
this
is
a
real
thing
inside
of
there.
So
publishing
means
that
somebody
has
actually
come
through
and
edited
this
as
well,
so
these
topics
have
been
published
out
and
said.
Yes,
somebody
has
looked
at
this
page
and
published
it
and
there's
a
reason
for
that
right.
A
It's
like
we've
got
an
ai
generated
page
and
there
are
different
stages,
basically
to
having
human
curation
as
part
of
it,
and
so
that's
why
that
life
cycle
is
there
and
so
there's,
hopefully
that
helps
with
that
too.
Okay
and
then
within
that.
Obviously
we
also
have
this
life
cycle
here
around
removed
two
okay.
A
So
if
you
think
there's
a
specific
set
of
sites
that
you
never
ever
ever
want
to
have
knowledge
indexing
happen
for
you're
able
to
do
that,
and
so
I
wanted
to
be
very
clear
about
that.
So
you
can
say
only
just
these
sites.
If
you
say
no
sites,
nothing
will
happen
basically,
so
there
will
be
no
indexing
at
all
for
knowledge,
and
so
the
product
won't
work.
So
if
you
say
all
except
selected
sites,
that's
a
good
option
too,
and
then
only
selected
sites
means
you
specify
a
specific
list
here.
A
So
we
use
a
bunch
of
signals
right
now
we're
looking
at
topic
discovery
on
the
contents
within
sharepoint.
We
use
a
bunch
of
signals
that
are
coming
from
other
parts
of
microsoft
365,
but
we
don't
actively
go
index
content
in
there.
So,
for
example,
I
think
folks
were
asking
about
email
earlier.
We
use
that
as
part
of
the
activity
piece
of
it,
but
we
don't
ask
for
it
as
part
of
the
topic
discovery
piece
of
it.
A
Okay,
and
so
this
would
be
the
other
areas
here.
So
topic
visibility.
This
is
the
part
again
when
you're
first
getting
started,
that
you
have
the
opportunity
to
say
who
can
see
topics
so
only
selected
people
or
security
groups
right-
and
this
is
the
part
where
you
should
control
and
say:
hey
when
you're
first
getting
started,
switch
it
on
for
all
sites
inside
of
your
organization
and
then
just
have
just
a
few
people
in
this
area
right.
A
So
these
are
the
folks
who
will
see
the
results
essentially
of
that
indexing
and
that's
a
great
place
to
start,
and
so
once
you're
in
there,
you
can
add
groups
if
you
need
to,
as
you
expand
more
confidence
in
the
system,
you're
able
to
do
that.
But
I
think
it's
a
great
way
to
get
started
inside
of
your
organization,
basically
see
the
full
breadth
of.
What's
being,
there
again
depends
on
your
permissions
as
a
knowledge
manager.
A
Your
permissions
of
the
documents,
we'll
we'll
see
what
you
can,
what
you're
able
to
see
as
topics
as
well
and
then
success.
You
know
for
topic
permissions
you
can
actually
specify
here
who
can
create
and
edit
topics
as
part
of
this
and
who
can
manage
topics
so
who
are
topic?
Managers,
knowledge,
managers
in
the
organization
and
creating
and
editing,
is
part
of
that
too,
and
then
the
first
time
through
the
gate,
you
will
need
to
to
create
a
topic
center
and
the
reason
to
have
that
is.
A
So
all
these
different
areas
together,
I
do
want
to
draw
your
attention
to
the
fact
that
we
have
a
bunch
of
great
documentation
out
there
as
well,
and
so
please
do
check
out
and
please
make
edits
as
well
and
suggest
edits
as
you
need
to
too.
So
we
have
things
around
setup
and
administration.
We
have
a
bunch
of
things
around
visibility,
some
nice
videos,
as
well
as
part
of
that
too,
and
so
definitely
always
appreciate
the
feedback
on
that
too.
B
A
I
did
want
to
say
you
know,
there's
a
couple
things
to
remember
here:
topic
identification
improves
when
there's
more
content
available
right,
so
hence
the
you
know.
I
would
recommend
the
scoping
for
all
sites.
Inside
of
your
organization.
We
always
look
at
the
security,
privacy
and
location
of
your
data.
Right,
always
the
same
trust
promise
that
we
have
with
microsoft.
365.
A
nothing
changes
because
of
that
with
viva
topics.
In
order
to
see
the
topic
cards,
the
topic
pages,
the
highlights
all
of
those
pieces
users
do
need
a
license
and
right
now
we
only
work
in
english
right
and
we're
working
on
lots
of
other
different
languages.
But,
as
you
can
imagine,
all
of
those
different
algorithms
that
I
talked
about
have
to
be
language
focused,
and
so
it
actually
takes
a
long
time
to
make
all
of
those
pieces
too.
Okay,
saeed
has
looked
through
all
of
them
awesome.
A
Do
you
have
any
feedback
for
us
on
the
documentation
and
then
just
last
resources
here
as
well.
So
I
just
wanted
to
make
sure
that
folks
are
aware
of
the
content.
Services,
partner
program
is
a
great
way
to
connect
if
you're
looking
at
you
know,
building
on
top
of
these
experiences
in
the
future
as
well,
and
then,
of
course,
we
do
have
the
resource
center
all
up
as
part
of
this
too
so
lots
of
stuff.
A
C
A
Oh
exactly
sorry,
I
meant
to
mention
that,
and
I
didn't
I
apologize,
but
yes,
it's
a
good
question,
so
the
microsoft
graph
content
connectors.
They
are
the
way
that
we
are
going
to
bring
in
information
here.
So
it's
not
quite
there
yet,
but
we
we
do
have
it
working
in
one
of
the
rings.
So
what
we
want
to
do
is
use
the
microsoft
search
graph
content,
connectors,
aka
dot.
Ms
slash,
I
want
connectors
right
those
connectors
so
the
same
way
as
you
bring
in
servicenow
results,
media,
wiki,
etc
into
the
microsoft
search
rate.
A
That
is
the
way
that
we're
going
to
bring
in
that
content
into
viva
topics
and
so
we'll
be
able
to
basically
expand
the
knowledge
indexing
across
those
connected
content
as
well,
and
so
you
know
when
that
corpus
is
there
it's
a
great
way
to
bring
in
all
of
that
information.
So
definitely
excited
for
that
too.