►
From YouTube: SharePoint Monthly Community Call – July 2020
Description
SharePoint PnP Community monthly call – July 2020. Featured topic: Updates on Microsoft 365 Information barriers. Delivery updates include: SharePoint Framework (SPFx) v1.11 is expected to release very soon – days/hours. Released days ago - .NET Standard 2.0 version of SharePoint Online CSOM API. SharePoint engineering’s focus based on UserVoice requests is: 1) Add managed metadata term store operations to REST API and 2) Add support of SharePoint Framework solution packages to the AppSource Store. Thank you to members of this truly atypical community. The host of this call was Vesa Juvonen (Microsoft) @vesajuvonen. Q&A takes place in chat throughout the call.
Featured Topic Presenter(s):
• Sesha Mani (Microsoft) | @SeshaManiS
• Nikita Bandyopadhyay (Microsoft) | @nikbango
Learn more:
• See the full blog post for this call at: http://aka.ms/spdev-blog.
• Download invite for monthly SharePoint community call at: http://aka.ms/spdev-call.
• Learn more about the SharePoint developer community at: http://aka.ms/m365pnp
• Visit the SharePoint PnP Developer Community YouTube channel: https://aka.ms/spdev-videos
A
Welcome
everybody
to
the
SharePoint
community
call.
This
is
July
2020
and
it
is
July
14
2020
and
my
name
is
si
yuan
and
I'm
gonna
be
your
host
today.
So
it's
gonna
be
me
for
first
15
minutes
and
then
we
have
the
real
stars
of
the
of
the
day
which
are
session
money
and
Nikita
gonna
talk
about
Microsoft
resist,
describes
the
information
Perrier's.
Now
we're
gonna
start
with
a
a
quick
recap
on
what
has
happened
with
the
shipment,
accessibility
and
development.
A
So
let
us
know
it's
monthly
summary
and
other
details
what's
happening
there
and
we're
gonna
go
through
the
typical
acknowledgement
of
our
community
contributors
from
the
past
month,
and
then
we
have
the
real
stars
of
today
who
are
Nikita
and
Sasha.
We're
going
to
talk
about
the
Microsoft
raises
the
five
information
barrier.
So
first
of
all,
this
is
one
of
the
community
calls
which
is
around
share
points
and
in
this
community
cause.
A
We
also
talked
about
my
story
is
it's
about
a
and
B
and
also
contributions
crossed
not
just
to
share
point,
but
also
on
the
teams
and
craft
areas
and
so
acknowledging
the
people.
But
we
do
have
quite
a
lot
of
other
different
community
calls
and
these
are
being
presented
by
multiple
different
people,
and
so,
if
you're
interested
in
forex
there's
a
community
called
adaptive,
Microsoft
team,
specific
monthly
community
goal
and
all
done
and
you
can
absolutely
choose
which
of
these
course
you
want
to
join.
A
All
of
them
are
getting
recorded
and
all
of
them
are
available.
Then,
from
the
YouTube
channel,
typically
like
24
hours
after
the
recording.
Well,
the
2.1,
the
shipment
monthly.
One
is
getting
more
and
more
kind
of
just
that
not
just
to
be
about
extensibility,
but
also
about
features
and
capabilities,
because
I
think
there's
a
massive
demand
for
people
to
understand.
A
Just
the
basics
like
buidling
or
portals
or
information
purveyors
like
today,
so
we're
kind
of
taking
over
the
the
SharePoint
monthly,
wonderful,
DOS,
January
things,
and
then
we
still
have
much
of
365
developer
special
interest
group
happening
bi-weekly.
She
had
one
framework
happening
by
Baker
for
SharePoint
site
as
well
and
all
the
other
stuff.
Now,
if
you
think
about
all,
if
you're
wondering
on
what,
if
word
YouTube
channels,
where
all
of
this
course
are
currently
recording,
we
do
have
actually
two
of
them,
which
might
be
slightly
confusing.
A
The
one
is
to
myself
365
developer,
videos
where
we
have
developed
or
oriented
videos,
but
then
some
of
the
developer
oriented
videos
are
actually
in
our
community
video
channel.
So
we
do
you
have
to.
We
know
that
this
is
slightly
confusing,
but
some
of
the
videos
which
we
have
on
the
community
mid-air
chart
know
would
not
just
about
development
and
accessibility,
so
kind
of
trying
to
figure
out
how
we
make
this
happen
in
the
future.
A
Right
now
we
have
actually
really
nice
set
of
new
videos
into
Microsoft
raises
to
five
and
SharePoint
community
YouTube
channel,
where
we
have
checked
deeper
and
multiple
leaders
from
our
engineering
side
talking
about
the
future
of
the
Microsoft
365
collaboration,
so
please
go
and
check
them
out.
We
have
a
lot
of
open
sources,
it's
available
from
the
github,
so
get
some
SharePoint
get
a
BMP
github
office.
Ted
are
the
most
typical
ones,
we're
going
to
find
the
information
and
open
github.com.
So
that's
myself
craft.
How
did
I
miss
that
one?
A
Let's
add
that
one
there
as
well.
We
have
multiple
sample
galleries
which
were
improving
all
the
time.
You
can
easily
access
mics
of
teams,
samples
from
from
the
key
table
or
in
the
internet,
so
having
a
one
location
where
you
can
find
them
and
if
you're
wondering
and
wherever
are
all
of
these
assets
and
things,
and
why
do
I
need
to
remember
so
many
URLs?
This
is
too
difficult.
A
A
We
can
easily
access
on
all
of
our
open
source
and
none
open
source
assets
and
one
of
the
trainings
I
actually
kind
of
a
tease
about
this
one
of
the
newest
stuff,
which
you
want
to
be
aware
and
that
there's
a
new
set
of
14
different
videos
on
the
wid
service,
which
is
basically
an
on-demand
training
sessions
for
SharePoint,
one
tribe
and
teams,
the
Yammer
and
stream,
and
this
is
available
from
the
community
YouTube
channel.
So
the
Mike's
raises
to
5:00
p.m.
be
YouTube
channel.
A
We
basically
have
Jeff
deeper
Oh
Marceline,
multiple
Microsoft
themes,
leaders
and
presenting
in
this
course
turn
telling
what's
actually
happening.
Also
extensibility
is
being
covered
here,
some
in
some
of
the
course
as
well.
If
you
are
more
on
the
development
side
of
the
house
now,
one
of
the
picnic
is
within
the
last
month,
just
to
recap,
and
those
as
well
was
the
release
of
a
dope
nets,
standard
version
of
the
SharePoint
season.
Abi.
A
Now,
let
me
be
super
clear,
always
use
Microsoft
graph
when
possible,
but
if
you
hit
a
gap
in
the
Microsoft
graph,
which
we
have
not
yet
at
wrist
and
then
you're
gonna
actually
use
to
see
some
API
to
fall
back
and
and
really
this,
this
can
help
you.
Then
you
build
microsoft.net
framework,
3.0
version
or
dotnet
framework,
five
versions
of
your
solutions,
so
you
can
really
take
advantage
of
the
latest
technologies
when
you
are
implementing
stuff
in
SharePoint
Online.
A
But
again,
please
use
my
staff
draft
where
possible
then
fall
back
on
system
where
needed
on
the
SharePoint
development
side
of
the
house.
Her
per
shipment
framework
is
actually
planted.
1.11
is
plan
to
get
released
this
week
and
this
will
enable
SharePoint
framework
support
in
the
store
so
in
the
app
stores
or
in
the
classic
shipment
store.
So
this
is
currently
had
to
have
been
this
week
now.
The
might
place
till
last
minute
delays
on
that
one.
A
If
we
found
any
last-minute
things,
which
means
still
polish,
so
I'm,
not
gonna
promise
and
not
gonna
put
my
head
on
on
the
fact
that
that
we
are
shipping
this
on
this
week.
But
hopefully
that
will
happen,
but
there
that
will
also
include
some
themes:
integration
options
for
SharePoint
framework,
so
it
will
make
the
development
with
SharePoint
framework
towards
Microsoft
teams,
even
better,
because
SharePoint
framework
gives
you
the
capability
as
an
example
not
require
well
being
all
the
hosted
that
the
extensibility
they
were
going
to
be
improved.
A
Mike's
RFA
be,
is
more
per
ending
settings
and
portals
better
myself
themes
and
better
support
in
general,
and
then
there
are
other
elements
as
well,
now
I'm
being
conscious
about
a
time
if
we
have
a
look
go
into
quickly
on
the
ship
on
development
user
voice.
In
this
community,
core
we've
been
concentrating.
Having
only
talked
about
the
use
of
all
centuries,
worship
and
extensibility.
A
Maybe
should
actually
talk
about
other
user
voice
entries
here
in
the
future
and
the
number
one
issue
which
number
one
request
which
we
used
to
have
is
forced
to
see
some
dotnet
standard
version.
That's
has
been
now
shipped
for
the
SharePoint
Online
and
the
number
currently
do
not
most
requests
the
capabilities
to
be
able
to
have
editing.
Experience
is
in
the
SharePoint
framework.
A
Even
though
they're
coming
from
the
store
it's
pretty
cool,
now
quick
update,
also
in
our
open
source
and
community
work,
if
you're
interested
on
in
getting
engaged.
If
you
want
to
actually
contribute
on
to
documentation,
maybe
in
the
Microsoft
Research
device,
community
Docs
or
in
the
extensibility
Doc's
or
in
the
other
dogs,
we
have
actually
training
available
for
you.
So
if
you're
interested
on
contributing-
but
you
are
afraid
of
actually
not
under
really
understanding
what
is
a
key
top
and
how
does
all
of
this
work?
What
is
this
edit?
A
What
is
app
or
what
is
a
request,
and
how
does
this
thing
work?
We
actually
have
hands-on
training
training
available
so
on
David,
Warner
and
Hugo
Bernier
are
setting
up
their
sessions
and
there
are
multiple
other
people
helping
behind
of
the
scenes
as
well,
and
this
have
been
actually
really
really
popular.
A
So
we're
getting
up
to
twenty
to
twenty
five
people
are
attending
on
the
sessions,
which
is
really
great,
because
then
multiple
people
learn
how
to
contribute
in
the
open
source
as
well,
so
the
next
ones,
the
first
time
contributor
session
is
in
July,
24th
and
27th,
and
community
dog
sessions
on
July,
31st
and
August
3rd.
A
came
as
a
sharing
is
caring
is
the
address
for
that
one.
So
thank
you,
David
and
who
go
for
this
awesome
initiative.
Now,
one
of
the
things
which
we're
getting
a
lot
of
feedback.
A
A
A
podcast
or
I
would
like
to
have
a
video
feed,
what's
actually
happening,
so
we
have
a
DMP
weekly
that
we
actually
cover
all
of
the
latest
news
from
the
Microsoft
and
also
from
the
community,
so
we're
selecting
some
of
the
community
articles
which
have
been
interesting
within
the
past
week,
not
only
about
the
extensibility
and
development,
but
also
in
other
areas
where
we
could
talk
about
in
the
PMP
weekly
episodes,
and
these
are
like
45
to
50
minutes.
Typically,
there
are
certain
exceptions
on
that.
A
One
as
well,
where
me
and
waldek
well
like
most
regards
from
rank
or
typically
have
a
visitor,
and
we
talk
about
Microsoft
365,
and
what
does
it
mean
for
the
community?
What
does
it
mean
if
a
partner?
What
is
the
partner
ecosystem
opportunity?
Is
there?
What
does
it
mean
for
end-users
and
so
on?
So
interesting
discussions
are
interested,
July,
20,
2008
and
the
monthly
update
will
be
right
and
acknowledge.
A
A
Interesting
enough
writing.
This
blog
post
is
getting
it's
taking
more
and
more
and
more
time
every
single
month,
because
there's
more
and
more
people
actually
getting
involved,
which
is
awesome,
it's
a
positive
problem.
It
also
takes
quite
a
lot
of
time
to
actually
do
that
and
if
you
open
up
and
have
a
look
on
that
you'll
understand
how
much
information
is
in
that
blog
post.
Now
this
is
the
list
of
contributors
within
the
last
month.
A
So,
basically,
from
this
day,
one
month
before,
we
wrote
the
previous
monthly
release,
and
so
these
are
all
of
the
people.
Who've
been
involved
in
our
open
source
community
efforts,
even
country,
either
contributing
in
documentation,
samples
or
doing
a
live
demo
in
the
community
course
and,
and
the
number
of
people
is
crowing
all
the
time.
So
thank
you.
Everybody
for
showing
an
interest
helping
each
other,
because
all
girls
are
sharing,
is
caring.
One
help
each
other
be
successful
even
in
these
tough
times.
A
So
thank
you,
everybody
for
being
being
helpful
and
helping
others
in
the
community
from
a
company
side
of
the
house,
and
this
is
the
full
list
of
companies
who
have.
We
have
the
permissions
to
show
the
logo
in
this
monthly
community
call
and
from
these
companies
to
people
which
we
mentioned
in
the
previous
line
are
working
for
us.
A
So
basically
thank
you
for
these
companies
as
well,
because
they
allow
their
employees
then
contribute
in
an
open
source
in
Asia,
driven
by
or
led
by
Microsoft
and
our
MVP
community
people
and
from
Mike's
outside,
and
the
list
is
growing
as
well.
So
there's
more
and
more
people
from
the
Microsoft
side
getting
involved
in
our
open
source
efforts,
which
is
great.
So
thank
you
for
you
as
well.
A
B
That's
correct
their
visa,
so
let
me
go
ahead
and
share
my
screen
thanks
for
tuning
in
and
thanks
for
the
opportunity
visa
on
this
particular
call
for
us
to
share
Microsoft
365
information
barriers
in
SharePoint
at
one
time.
I.
Think
many
of
you
might
already
know
me:
I'm
the
satio
Molly
I'm,
a
principal
group
program
manager
in
the
SharePoint
and
onedrive
team,
in
with
the
team,
since
2011
almost
nine
years
now
and
very
well-versed
with
the
product
and
my
team
drives
all
the
investments
in
our
security
and
compliance
area.
B
All
up
and
I
have
here
with
me
today
and
Nikita
band,
your
Patty
and
she
is
a
program
manager
in
my
team
and
specifically
focusing
on
this
particular
information
barrier
feature.
So,
let's
actually
get
started.
The
agenda
that
have
you
were
thinking
to
share
with
you
is
to
share
the
top-level
industry
trends,
what
we
are
seeing
in
the
security
and
compliance
phase,
and
then
what
is
the
information?
Various
scenario?
B
Some
of
you
might
be
already
familiar
with
this
and
would
like
to
give
you
set
the
stage
for
what
is
the
scenario
a
leak
and
then,
more
importantly,
how
the
information
barrier
interplays
within
SharePoint,
onedrive
and
also
team's
experiences
as
well,
and
we
will
walk
you
through
the
clicker
demo
and
also
share
with
you
how
you
can
take
advantage
of
these
features
and
what's
next
there
and
definitely
we'll
make
sure,
there's
a
Q&A
session
at
the
end
as
well.
So
let's
get
started
of
the
industry
trends.
B
The
first
and
foremost
thing
I
would
say
here
is
the
exponential
growth
that
we
are
seeing
in
the
digital
data.
So
gone
are
the
days
where
you
really
have
physical,
informational,
corporate
information
in
the
physical
format,
but
now
everything
is
being
digitized.
Every
industry
is
becoming
a
software
technology
company
and
what
it
means
is
in
any
industries
companies.
B
The
other
key
industry
trend
that
we
are
seeing
is
increasing
the
regulatory
needs.
Compliance
and
regulations
are
definitely
increasing
in
this
digital
world,
especially
as
more
and
more
data
is
becoming
digitized
and
it
is
exponentially
growing.
The
regulators
are
watching
very
carefully
and
ensuring
that
the
governance
is
put
in
place.
B
It
actually
happens
across
all
the
different
verticals
and,
for
example,
if
you
just
take
one
example
vertical,
which
is
finance
companies,
there
is
a
compliance
called
FINRA
and
this
Authority
has
enforced
that
thin
serve
customers
being
able
to
showcase
that
they
can
stop
insider
trading
within
the
company.
What
it
means
is
so
imagine
you
have
Investment
Banking,
Department
and
advisory
department
inside
a
finance
company.
It's
a
pincer
company.
B
Now,
because
of
the
nature
of
these
two
departments,
it's
quite
possible
that
investment
bankers
who
work
with
normally
individuals
like
you
and
me,
helping
us
to
choose
right
stocks
to
trade
and
things
like
that.
They
might
have
some
additional.
You
know,
potentially
some
information
they
may
get
from
the
heart
rate
advisors,
which
are
typically
Department,
the
users
that
are
working
with
corporates,
such
as
Microsoft,
LinkedIn
and
so
on.
So
they
have
much
more
higher.
Information
like
Microsoft
is
about
to
acquire,
let's
say
LinkedIn.
B
So
if
that
kind
of
information
is
getting
leaked
or
to
the
Investment
Banking
Department
users,
then
investment
bankers
could
use
that
for
helping
their
clients
to
get
it.
This
is
what
they
mean
by
insider
trading.
It's
a
conflict
of
interest
in
their
job
duties
that
they
do
in
their
organization,
so
FINRA
and
in
the
through
the
SEC
has
required
that
customers,
especially
the
fencer
customers,
need
to
be
able
to
showcase
to
SEC
that
they
have
controls
in
place
to
block
the
communication
and
collaboration
between
these
two
departments
and
I
want
to
be
super
clear.
B
This
isn't
one
example
in
a
one
particular
vertical,
but
I'm
pretty
sure
many
of
you
are
already
having
this
kind
of
requirement
in
your
own
industries
as
well,
be
it
energy
industry
or
healthcare
industry
where
the
HIPAA
compliance
is
super.
Critical
and
also
many
other
government
agencies
is
the
other
one
too.
So
we
do
see
this
increasing
need
for
controlling
internal
collaboration
and
sharing,
just
because
of
the
nature
of
the
job
or
the
role
that
the
individual
is
playing
in
your
organization.
B
So
let
me
actually
give
you
a
quick
view
of
building
it
down
to
Microsoft
365.
So
you
imagine
that
in
an
organization
like
contoso
Bank,
Corporation,
Investment,
Banking
Department
has
their
own
teams
and
SharePoint
sites
that
they
manage
and
they
work
with
and
then
say
there
are
thousand
users
in
that
Investment
Banking
Department
and
then
you
have
corporate
advisor
Department.
Let's
say
there
are
500
users
in
that
department
and
they
have
their
own
teams
experiences.
B
There
is
investment
bankers
and
then
there
are
advises,
but
then
also,
more
importantly,
you
have
the
rest
of
the
employees
in
your
organization.
So
really
really,
if
you
think
about
this,
there
are
actually
three
segments
here.
One
is
investment
bankers,
then
advisers,
then
the
third
one
is
the
yellow.
Color
in
this
picture
is
all
the
rest
of
the
employees
in
your
organization.
B
B
Investment,
banking
resources
or
should
not
be
accessible
by
advisory
department.
Users
are
even
the
rest
of
the
employees
in
your
organization.
That's
why
the
conditional
access
information
barrier
must
match
in
order
to
access
a
Content.
A
SharePoint
site
are
one
type
of
content,
is
has
to
be
there
and
I
want
to
take
a
minute
to
call
this
particular
route.
This
is
really
the
crux
of
this
whole
feature,
which
is
all
of
you
know.
Already.
B
There
is
a
SharePoint
permissions
model,
which
is
you
can
share
a
file
or
a
site
with
a
person,
and
now
that
person
has
access
to
the
site
and
a
file.
Now
we
have
actually
added
an
additional
authorization
layer.
On
top
of
that,
it's
not
enough
to
have
authorization
permissions
just
for
the
site
and
a
file.
You
must
also
match
the
conditional
access
for
information
barrier
segments
as
well.
B
That
means,
if
a
given
SharePoint
site,
if
it
is
tagged
as
investment
bankers
site,
then
you
must
be
one
of
the
investment
bankers
to
access
that
particular
site,
no
matter
whether
you
have
permissions
already
given
to
the
site
through
some
other
means
or
not.
So
in
a
way,
it's
a
two
layer.
Authorization
is
what
we
have
introduced,
and
this
is
a
very,
very
powerful
security
permissions
mechanism,
because,
as
you
can
imagine,
no
matter
what
your
permission
says
in
the
given
site
or
a
file
the
moment
you
flag
a
site
as
investment
bankers.
B
Specific
site,
then
immediately
is
the
union
of
you
must
be
an
investment
banker
and
you
must
have
access
to
the
SharePoint
site
in
order
to
actually
gain
access
to
the
content
inside
the
site.
So
we
believe
this
is
really
a
transforming
authorization
and
permissions
model
and
will
help
many
organizations
that
are
in
need
of
this
insider
trading
related
regulations.
B
The
second
important
aspect,
I
would
call
out,
is
if
I
am
inside,
that
investment
banker
site,
who
can
I
actually
share
the
file
with
so
that
is
you're
actually
taking
the
experience
level
as
well.
So
if
I
am
an
investment
banker,
say
sure
and
now
I'm
trying
to
share
file
with,
let's
say
Nikita
and
she
happens
to
be
advisory
user.
B
Are
they
who
happens
to
be
coming
from
rest
of
the
organization
in
my
company,
then
I
will
be
blocked
from
sharing
that
particular
site
or
a
file
in
the
site,
mainly
because
I
am
the
investment
banker
and
I
am
also
working
in
the
context
of
the
SharePoint
site.
That
is
flagged
as
mint
for
investment
backers,
so
we
actually
have
done.
I
would
say
a
comprehensive
analysis
on
which
experiences
also
where
we
need
to
apply
is
investment
in
information
barrier
policy
as
well.
B
I
gave
you
a
10,000
foot
view
on
what
is
information
barrier
scenario
and
how
in
Microsoft
365
we
are
bringing
this
forward.
To
put
it
in
a
simple
terms,
you
will
be
able
to
segment
your
users
in
your
organization
based
on
your
compliance
requirements.
So,
for
example,
you
can
say
these
thousand
users
are
investment
bankers.
These
500
users
are
calculate
advisers,
and
then
you
have
restaurant
the
company
and
the
way
you
can
segment
them
and
you
get
about
walk
you
through
in
details
in
a
minute
just
based
on
your
existing
Azure,
Active,
Directory
properties.
B
B
This
is
the
compliance
segmentation
that
you
are
bringing,
so
it
is
very,
very
critical
that
it
needs
to
be
predictable,
and
that
means
a
given
user
can
become
part
of
only
one
compliance
segment
at
the
time
because,
from
a
compliance
point
of
view,
you
need
to
be
able
to
show
to
your
officers
that
satiable
ons
to
adjust
investment
bankers.
That's
his
role,
that's
what
it
does
in
my
organization.
B
The
second
thing
is,
you
can
associate
a
given
SharePoint
site
to
a
specific
segments,
because
the
resource
also
needs
to
be
attached
and
that's
how
we
bring
in
the
access
conditional
access
based
on
the
resource
Association
as
well.
Third,
one
segmenting
users,
onedrive,
is
also
is
coming
into
play
because,
if
you
misspent
banker,
s
Asia
is
investment
banker,
then
even
from
his
own
own
Drive
like
easy
allowed
to
share
with
rest
of
the
organization's
or
with
copied
advisers.
B
So
we
do
believe
we
are
bringing
the
IB
policy
enforcement
to
onedrive
as
well,
and
I
quickly
walked
you
through
the
FINRA
compliance
requirement
with
the
financial
sector.
So
with
that
I'm
going
to
now
turn
it
over
to
Nikita
to
walk
us
through
a
quick
demo
of
this
scenario
over
to
you
Nikita
thank.
C
You
so
sure,
let
me
quickly
share
my
screen:
Thank
You
Sasha.
Now,
let's
get
into
the
details
of
how
information
value
of
works
for
SharePoint
and
onedrive.
So,
like
Sasha
said
we
are
giving
you
the
capability
to
set
segments
on
a
particular
SharePoint
site.
The
whole
idea
is:
if,
in
your
organization,
you
have
certain
SharePoint
sites
that
need
to
be
protected
with
information
barrier
policies.
We
are
allowing
your
SharePoint
administrator
to
set
segments
on
those
sites.
The
sites
of
scope
are
modern
sites
as
well
as
classic
sites.
C
Today,
only
the
contents
of
the
site
are
segments
associated
all
other
group.
Resources
are
currently
not
segments
associated
access.
Like
Sasha
said
we
have
done
extensive
work
to
ensure
that
the
conditional
access
control
honors,
the
IB
policy,
which
is
associated
to
the
site,
as
well
as
the
sharing
control,
will
be
allowed
only
per
the
segments
that
are
stamped
on
the
site.
Now,
let's
see
how
all
this
takes
care
of
now
today,
with
SharePoint
information
barriers,
the
SharePoint
administrator
can
use
the
SharePoint
PowerShell
module
to
add
segments
to
a
site
on
the
screen.
C
You
can
see
that
we
have
extended
our
set
SPO
site
command,
late'
and
added
to
Nia
and
have
added
two
new
parameters:
add
information
segment
and
remove
information
segment,
using
which
the
admins
can
now
add
all
the
compatible
segments
that
they
want
to
add
to
a
site
as
well
as
if
they
don't
want
to
have
a
segment,
they
can
remove
it
using
the
remove
information
segment
command,
let
they
can
also
check
what
are
the
segments
which
are
associated
on
the
site
using
PowerShell?
This
can
be
achieved
using
the
get
SPO
site
command
line.
C
Now
also,
we
understand
that
as
a
site
owner,
you
want
to
know
what
are
the
different
properties
which
are
stamped
on
the
site.
So,
as
you
can
see
here
in
the
site,
information
panel,
the
site
owner
would
be
able
to
view
the
segment's
which
are
associated
on
the
site.
The
example
that
I
have
here
is
this
is
an
advisory
team
site
and
we
have
displayed
the
new
property,
which
is
information
segment
and
it
clearly
says
its
corporated
I
see.
C
Now,
once
the
site
is
segment
associated,
the
site
is
protected
by
Ivy
policy,
so
access
for
the
site
is
only
allowed
to
users
whose
segments
belong
to
the
same
as
that
of
the
site
and
who
also
have
site
access
permission.
So,
in
short,
the
user
needs
to
meet
both
the
condition.
One,
the
basic
site
access
permission
as
well,
as
should
have
the
same
segment
as
that
of
the
site.
If
either
of
these
conditions
are
not
met,
the
user
will
not
be
able
to
access
the
segment
associated
site.
C
This
is
a
typical
access
denied
error,
page
that
the
user
will
see
if
he
isn't
either
not
belonging
to
the
same
segment
as
that
of
the
site
which
is
trying
to
access,
or
he
does
not
have
the
site
access
permission.
Some
of
you
might
think:
hey
what
happens
if
the
users
segment
changed
now.
If
the
user
segments
change
every
time
the
user
is
trying
to
access
a
site,
we
will
check
at
access
time
if
the
user
belongs
to
the
same
segment
as
that
of
the
site.
C
So,
for
example,
if
a
user
was
belonging
to
investment
banking
information
segment
and
was
accessing
a
site,
if
few
months
later,
they
user
changes
job
and
moves
to
corporate
advisory,
the
user
will
now
lose
access
to
all
the
previous
investment
banking
sites
because
add
access
time
when
we
match
the
segment,
the
user
no
longer
belongs
to
Investment
Banking.
He
has
actually
moved
to
corporate
advisory.
So
the
main
idea
here
is:
we
always
check
at
run
time
to
make
sure
that
the
right
user
is
accessing
a
SharePoint
site
which
is
protected
with
information
values.
C
Also,
sharing
is
another
way
of
allowing
users
access
to
your
site,
so
we
have
done
extensive
work
to
make
sure
that
the
site's
sharing
control
is
also
protected
with
information
barrier
policy.
It's
a
few
things
that
we
have
done
here.
I'll
start
with
the
leftmost
one.
Most
of
you
might
be
aware
of
anyone
with
link
sharing
option.
C
This
is
a
powerful
tool
which
you
can
you
know
once
you
share
a
site
or
a
content
with
anyone
willing,
then
the
user
does
not
need
to
sign
and
they
can
automatically
anonymously
access
the
content
so
for
information
values.
We
have
made
sure
that
anyone
with
link
option
is
disabled
because
the
site
is
protected
with
IB.
The
second
thing
that
we
have
done
is
the
centermost
one,
which
is
the
site,
and
its
content
can
only
be
shared
with
the
same
segment
users
as
that
of
the
site.
C
So
in
the
example
you
can
see
that
this
site
is
being
shared
with
user
Jeff,
but
cannot
be
shared
with
user
Nikita,
because
Nikita
does
not
belong
to
the
same
segment
as
that
of
the
site.
So
the
whole
idea
is
that
the
user
will
not
be
able
to
even
discover
somebody
who's
on
the
other
side
of
the
investor
of
the
information
barrier
wall,
and
the
third
thing
that
we
have
done
is
that
the
new
users
can
be
added
to
the
site
only
if
their
segment
matches
that
of
the
site.
C
Moving
from
sharepoint
to
onedrive,
as
you
have
understood
so
far,
that
with
information
barriers,
we
are
allowing
the
users
or
the
admins
to
segment
users,
which
means
you
are
classifying
your
user
as
an
investment
banker
user,
for
example,
or
a
corporate
advisor
user.
So
it's
basically,
the
user
also
has
an
information
segment.
Now,
if
the
user
has
an
information
segment,
what
we
are
doing
is
the
users
onedrive
will
automatically
get
associated
with
the
user
segment
for
their
policy.
C
So
if
a
user
belongs
to
Investment
Banking,
the
users
onedrive
site
will
automatically
get
associated
with
investment
banking,
as
well
as
other
segments
which
are
allowed
to
Investment
Banking
per
policy.
Also,
we
are
allowing
the
SPO
admin
to
manage
the
segment
association
on
a
onedrive
using
the
SPO
powershell.
So
similarly,
how
an
SPO
admin
can
add
segments
on
remove
segments
from
a
SharePoint
site.
We
are
also
allowing
them
to
manage
it
for
the
onedrive
sites.
C
Now,
once
the
I
once
the
onedrive
is
associated
with
segments,
the
access,
control
and
sharing
control
will
be
allowed
for
the
IB
segments
on
the
site.
So
it's
similar
to
how
the
access,
control
and
sharing
control
will
work
for
a
typical
SharePoint
site.
So
out
of
the
box
of
the
user,
has
a
segment
associated
the
users.
Onedrive
will
also
automatically
be
associated
with
the
segment.
C
C
For
that
particular
team
going
forward,
the
Microsoft
team's
files
experience
and
the
SharePoint
site
associated
to
it
will
also
be
honored
based
on
the
policies
of
the
members
of
that
team,
so
the
access
will
be
granted
based
on
the
segments
which
are
on
that
team,
as
well
as
the
sharing
control
will
be
based
on
the
segments
which
are
on
that
particular
team.
With
that,
let
me
quickly
give
you
a
demo
of
how
this
all
works.
C
So
here
is
M
365
security
and
compliance
center.
Like
we
mentioned
earlier,
information
values
is
a
unified
policy
across
an
365,
so
the
compliance
admin
will
have
to
go
to
your
M
365
security
and
compliance
center
to
define
segments
and
the
Associated
policy
today
that
can
be
achieved
using
a
CC
PowerShell
module
here,
I'm,
showing
you
a
mock-up
of
how
all
this
works
through.
So
this
is
an
example
where
the
compliance
admin
has
gone
ahead
and
created
two
segments
for
this
contoso
tenant.
The
segments
are
investment,
banking
and
advisory.
C
Today
we
allow
you
to
use
about
20
Azure,
Active,
Directory
properties
using
which
you
can
define
information
segments
here
is
an
example.
The
compliance
admin
has
defined
investment
banking
segments
using
the
fields,
location,
user,
principal
name.
You
can
use
other
fields
like
city
department,
so
on
and
so
forth.
So
here
is
the
definition
of
Investment
Banking.
C
Also,
there
is
another
segment
defined
which
is
advisory.
They
locate
the
attributes
that
have
been
picked,
our
location
and
user
principal
name
once
the
segments
are
defined.
The
next
step
is
defining
the
policy.
Typically,
the
customers
define
a
blog
policy.
The
whole
idea
is,
you
do
not
want
your
investment
bankers
to
communicate
and
collaborate
with
advisory.
So
here
you
can
see
that
I
have
set
up
a
policy
which
says
Investment.
C
C
Now,
once
the
policies
have
been
defined,
like
I
said,
if
the
user
is
associated
with
the
segment,
then
their
onedrive
will
automatically
get
associated
with
the
user
segment
and
any
other
poll
in
any
other
segment
that
is
allowed
to
the
user
segment
per
policy.
So
here
is
an
example
of
user.
If
you
remember
from
the
mock-up
users,
Asia
belong
to
investment
banking
segment,
so
here's
a
statius
onedrive
for
business.
This
has
automatically
got
associated
with
investment
banking
segment
same
as
Asia
segment.
C
Now,
access
to
this
particular
onedrive
will
be
granted
only
to
users
whose
segment
matches
that
of
the
investment
banking
segment,
which
is
on
the
onedrive
as
well
as
the
sharing
control,
will
honor
investment
banking
segment.
So
what
does
that
mean
is?
If
you
see
say
she
wants
to
share
a
particular
file
with
say
user
Jeff,
you
remember,
user
Jeff
is
an
investment
banker.
He
will
be
able
to
do
so
user
using
the
people
picker.
C
But
if
users
Asia
tries
to
look
up
or
even
share
the
site
or
its
content
with
user
Nikita,
he
would
not
be
able
to
do
so
because
Nikita
belong
to
corporate
advisory
and
/
investment.
Banking
policy
invest
and
/
IP
policy.
Investment
Banking
is
not
allowed
to
communicate
and
collaborate
with
advisory
and
because
Nikita
is
an
advisory.
Sasha
would
not
be
even
able
to
discover
her,
let
alone
be
able
to
share
the
content
with
her
through
people
picker.
C
So
this
is
how
we
make
sure
that
the
access
is
governed
by
the
segments
which
are
on
the
site,
as
well
as
the
sharing
is
purely
covered
by
the
segments
which
are
stamped
on
the
site.
Now,
switching
gears
to
a
SharePoint
site
here
is
a
SharePoint
site
which
is
Australian
banking
site
that
was
created.
The
SharePoint
administrator
has
gone
ahead
and
set
segment
Investment
Banking
on
this
particular
site,
using
PowerShell
module
as
the
site
owner
now.
I
can
go
to
the
site
information
panel
and
see
that
the
information
segment
of
the
site
is
Investment
Banking.
C
So
this
is
how
the
site
owner
would
know
that.
Okay,
my
site
is
now
protected
with
Investment
Banking
site
or
Investment
Banking
segment,
and
once
the
site
is
protected
by
segment,
the
access,
control
and
sharing
control
would
be
governed
by
the
segments
on
the
site.
Again,
if
user
is
trying
to
share
a
content
from
this
site
with
user
lakita,
he
would
not
be
able
to
do
so
because
Nikita
does
not
to
investment-banking
segments.
C
Now
you
might
think
okay,
this
is
all
good.
What
does
this
mean
in
terms
of
licensing?
Can
we
get
the
M
365
information
barrier
policy
for
any
license
or
not?
So
this
is
a
comprehensive
compliance
feature
and
it
would
be
available
with
all
re
5
licenses.
So
if
you
have
M
365,
P,
5
or
office,
365
P
5
or
a
5
compliance,
then
you
would
be
able
to
have
information
segment
information
barrier
feature
in
your
tenant.
C
B
And
thanks
Nikita,
as
well
so
I'm,
going
to
go
ahead
and
share
my
screen
where
you
can
take
the
next
step
or
the
link
where
you
can
learn
more
about
this
feature:
akms
slash,
SPO
info
barriers.
That
will
give
you
a
link
to
information
about
all
SharePoint,
related
information
and
then
slash
onedrive
info
barriers
is
also
available,
and
then
there
was
a
question
about
its
g8.
Where
is
it
it's
a
preview
and
so
on?
So
this
information
barriers,
as
we
discussed
as
we
showed
you
is
actually
available
as
a
general
availability
for
June
20th.
B
A
Just
a
quick
note
before
shots,
not
that
I
can
say
a
few
hands
on
the
on
the
session,
but
let's
use
to
chat,
win
chat
in
this
time
because
there's
more
than
240
people
in
this
call,
so
we
can't
really
go
to
audio
it.
Doesn't
it
doesn't
work
like
that?
That's
well
within
this
amount
of
people.
So
let's
use
the
chat
for
questions.
If
you
don't
mind
so
Asia
feel
free.
Yes,.
B
Thanks
Teresa,
so
users
should
be
added
on
SharePoint
group
and
AD
group.
In
order
to
get
this
working
though
the
need
here
is,
the
user
needs
to
be
in
your
Azure
Active
Directory
and
either
you
can
use
a
property
on
the
user
object,
such
as
department,
property
or
location
property,
and
so
on,
to
create
these
segments
that
Nikita
was
showing
or
you
can
use
a
security
group
that
you
have
defined
in
as
your
Active
Directory
to
use
that
to
define
a
segment.
B
So
it
has
to
be
some
security
principles
in
Azure,
Active,
Directory
and
just
to
double
click
on
that
there
was
a
question
about:
can
a
dynamic
security
group
in
Azure
Active
Directory
be
used
in
order
to
define
your
segments,
and
the
answer
is
yes.
As
long
as
it's
a
Azure
Active
Directory
security
group
doesn't
matter
whether
it
is
a
static
or
dynamic
one,
then
you
can
use
that
for
segment
creation.
Now
I
do
want
to
emphasize
that
these
segments
Association
are
very
strictly
compliance
and
regulatory
driven.
B
Go
up
is
email,
communication
blocked
by
exchange,
so
the
info
barrier,
information
barrier
policy
that
you
are
creating
as
the
Nikita
showed,
is
actually
you're,
creating
it
in
the
Microsoft
365
security
and
compliance
compliance
Center,
and
that,
once
it's
created
for
communication
in
teams,
as
well
as
in
email
communication,
those
will
get
honored
and
then,
in
the
context
of
collaboration
in
SharePoint
and
onedrive.
These
will
get
honored
in
that
aspect
as
well,
and
there
is
more
work.
B
We
are
planning
to
do
for
exchange
specific
information
barriers
and
stay
tuned
for
more
updates
on
that
later,
this
country,
so
ok,
this
be
available
for
guest
user
accounts
in
your
tenancy.
As
long
as
there
is
an
user
account
in
your
as
your
Active
Directory
and
you
have
the
appropriate
licenses
assigned
to
them
in
this
case.
This
feature
does
require
a
five
to
be
assigned.
B
When
will
this
be
made
available?
Will
it
be
for
office
t5
or
just
M,
365
I,
think
this
is
for
office.
365
services
like
SharePoint,
onedrive
teams
and
exchange
itself.
It's
the
I
would
say
the
branding
wise.
We
are
all
using
now
Microsoft
Excel.
That's
reason
why
it
is
called
as
Microsoft
least,
five
information
barriers.
C
There
is
a
question
the
limit:
what's
the
limit
on
how
many
segments
can
we
create?
So
today
you
can
create
up
to
hundred
segments
in
your
tenant,
but
on
a
SharePoint
site
you
can
set
only
up
to
10
compatible
segments
on
a
site,
so
in
a
tenant
they
can
be
up
to
hundred
segments
but
on
a
site
collection.
Today
you
can
set
up
to
ten
segments
only.
B
Perfect
there's
another
question:
by
default,
what
segments
a
user
will
be
associated
with,
and
the
answer
is
no
segments
by
default?
If
you
just
create
a
user
object
in
Azure,
Active
Directory
no
segments
the
user
is
associated
with,
so
it's
an
explicit
choice
or
action
that
the
admin
has
to
take
in
order
to
make
a
user
part
of
a
segment
and
imagine
you
create
a
user
object
and
you
have
a
department
code
and
you
said
that
to
investment
bankers,
and
only
then
he
becomes
part
of
that
investment
bankers
segment,
but
by
default.
B
If
you
do
nothing,
that
user
is
no
longer
it's
not
associated
with
any
sickness
whatsoever.
I
think
the
search
results
I
already
conformed
it,
which
is
search
results,
will
be
security,
trimmed
based
on
this
information
barrier
policy.
And
yes,
if
you
changing
your
segment
and
it
will
have
impacts
across
your
segmented
sites
and
the
corresponding
search
as
well.
So
changing
a
segment
of
a
user
is
a
very
big
deal
like
as
I
said.
Typically,
when
you
change
the
role
from
investment
bankers
to
carpet
advisors,
it's
not
a
you
know
everyday
kind
of
activity.
B
You
do
it.
Maybe
once
in
multiple
years
that
you
change
the
role
in
your
organization,
so
that's
a
very
typically
seldom
running
activity
and
what
scope
this
IP
policy
is
enforced.
You
as
I
explained
this
is
a
test
site
collection,
scope.
That's
the
level
that
you
associate
a
given
information
barrier
and
that's
where
the
information
barrier
policy
is
also
enforced.
B
Okay,
I
think
I
covered
most
of
the
questions.
Let
me
build
segments
be
defaulted
for
site
memberships
that
get
auto
created
from
Project
online
site
creation
using
PW
a
permissions
not
necessarily
like
segment
Association
to
a
given
site
collection.
Be
it
whether
it
is
created
from
project
online
or
you
are
creating
using
a
custom
site
provisioning
script.
You
would
have
to
take
an
explicit
step
to
associate
a
segment
to
a
site
collection.
Again,
it's
a
compliance
regulatory
feature.
B
So
you
need
to
be
aware
and
be
very
thoughtful
and
mindful,
then,
you
are
actually
associated
to
a
site
collection.
It's
also
getting
an
IP
segment
to
a
site
collections.
That's
why
it's
an
explicit
step!
There's
no
automatic
association
happens
whatsoever
in
the
SharePoint
sites,
so
you
do
have
to
take
explicit
step
to
associate
an
IB
segment
to
a
SharePoint
site
collection.
Okay,
there
was
a
question
about
the
difference
between
sensitivity,
labels
and
the
information
barrier
policy.
That's
a
really
good
question.
B
Let
me
give
a
meta
clarification
there.
So
sensitivity.
Labels,
as
you
know,
is
meant
for
securing
all
your
policies
into
a
single
label,
let's
say
creating
a
top-secret
label
and
if
you
have
associate
different
policies
to
it,
like
your
privacy
policy
or
unmanaged
device
policy,
and
so
on.
Typically,
that
is
meant
for
holistic
security
control
of
your
organization
and
of
your
site
collection,
whereas
this
info
barrier
that
we
just
shared
with
you
is
primarily
compliance
and
regulation.
B
B
So
that's
how
you
should
that's
how
internalize
these
two
models
now
in
the
future,
as
we
think
further
ahead
in
the
future,
would
we
look
at
bringing
them
together
in
some
fashion
or
so
that's
definitely,
you
know
we're
thinking
about
it
and
we
will
see
if
there
is
a
natural
fit,
then
we
will
definitely
try
to
look
into
it
further,
but
for
now
you
should
think
of
them
as
a
independent
concepts.
One
is
sensitive.
B
Labels
meant
for
orchestrating
many
policies
and
is
meant
for
protecting
your
content,
whereas
info
barrier
is
all
about
compliance
and
regulatory
needs.
That's
why
the
segment's
associating
me
to
a
site
and
a
user
is
super
critical.
Okay,
I'm
going
to
take
one
last
question:
we
see
whether
any
new
message
isn't
so
the
question
was
any
plans
to
mirror
this
functionality
in
M
Cass.
B
B
He
will
no
longer
be
able
to
access
the
investment
banking
related
sites
that
he
used
to
be
able
to
access
in
the
past,
and
this
is
where
the
2
layer,
authorization
that
I
explained,
really
comes
into
play,
and
it's
a
very
powerful
feature
in
that
regard.
Okay,
I
think
I've
captured
all
the
questions
the
visa,
so
I'll
turn
it
back
to
you.
Thank.
A
B
Yes,
definitely
it's
the
Microsoft
cloud,
app
security.
It's
a
one
of
the
security
broker
product
Caspi
product.
We
call
it
cloud
access
security
broker,
product
that
Microsoft
sales.
Typically,
it's
used
for
all
the
applications
in
your
enterprise,
not
only
just
office
65,
but
all
the
applications.
If
you
want
to
secure
them,
then
MCAS
is
our
product
suite
that
helps
you
to
achieve
that
excellent.
A
A
What
I
thought
cute
cute,
but
thank
you
Thank
You
session
Thank
You
Nikita
for
this
one,
a
really
great
stuff
and
great
capability,
as
mentioned
already
numerous
times
on
discussions,
it
is
an
e5
capability,
so
it's
an
advanced
capability,
but
I
think
there
will
be
a
lot
of
customers
who
are
interested
on
this
kind
of
a
security
and
compliance
e
features.
So
it's
really
great
to
see
and
these
kind
of
things
being
available
in
the
myself
365
flavor.
Now,
let's
just
recap
the
recording
and
will
be
available
within
24
hours
in
no
moisture
freezes.
A
The
first
shipment
community
YouTube
channel.
So
this
is
a
game
as
interest
is
to
rtmp
videos
from
there.
You'll
find
actually
the
latest
the
14
virtual
conference
sessions
as
well,
which
was
the
new
videos
related
on
many
of
these
things
actually
session,
has
a
video
there
as
well
related
on
security
and
compliance
topics.
A
If
you're
interested
in
following
up
on
the
extensibility
side
of
the
house,
it
is
introduced
five
trees
in
treat
Mike's
a
365
day
for
entries
in
house
increases
to
about
BMD
on
the
accounts
and
obviously
interested
on
SharePoint.
It
is
an
ADD
SharePoint
is
the
account
in
Twitter
the
next
shape.
One
framework
community
call
is
in
July
16th,
so
on
Thursday
this
week
we
have
three
community
demos
queued
up
from
that
one,
and
that
starts
at
7:00
a.m.
Pacific
time.
A
The
next
monthly
community
call
is
August
14th
and
we
have
checks
joining
us
on
on
explaining
what
is
the
latest
and
greatest
related
on
Power,
Platform
and
SharePoint,
and
and
files
really
cool
setup
coming
on
the
August
as
well,
and
so,
but
thank
you,
everybody
for
joining
and
thank
you
once
again
session
together
for
the
great
presentation
and
and
really
nice
to
see
the
the
interest
and
the
questions.
So
there
was
a
lot
of
again
activity
is
happening
in
the
chat.
So
thank
you
for
that,
but
that's
it
from
our
side.