►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 27th of September. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
Cool demos:
- Franck Cornu - React adal bot with SPFx to modern sites
- Luca, Pat, Vesa - SPFx 1.7 update: what's coming with fresh demos from Ignite
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
sync
is
a
special
ignite
edition
as
September
27th
2018
and
we've
got
a
great
meeting
here,
including
some
updates
from
live
from
ignite,
but
first
we
always
like
to
go
over
for
folks.
That
might
be
new
to
this
call
or
listening
to
the
recordings
for
the
first
time,
why
we
have
these
SIG's
and
what
they're
all
about
these
special
interest
groups
give
us
a
platform
to
really
dive
deep
into
specific
topic
areas.
A
This
one
is
about
client-side
development,
so
everything
around
SharePoint
framework
and
the
associated
development
patterns
they're
the
PNP
jeaious
libraries,
as
well
as
the
office
365
CLI
and
SP
effects,
reusable
controls.
So
all
of
those
are
client-side
related
technologies,
and
then
we
have
a
second
cig
special
interest
group
around
the
powershell
and
see
some
development
that
we
will,
that
is
on
alternating
week.
So
that
would
be
next
Thursday
we'd
have
that
sig?
A
So
welcome
you,
of
course,
to
join
either
or
both
of
the
SIG's
love
to
have
you
on
the
calls
and
let
you
tailor
it
a
little
bit
to
the
kind
of
content
you're.
Most
interested
in
to
links
down
there
at
the
bottom,
aka
MSS,
P,
P
and
P
dash
community
takes
you
to
the
Microsoft
tech
community,
specifically
the
SharePoint
area
of
the
Microsoft
tech
community.
That
is
a
great
location
to
ask
your
general
kind
of
questions
that
aren't
really
about
a
specific
library
or
a
specific
technology
that
are
more
like.
A
How
would
I
architect
my
solution
or
how
might
I
go
about
debugging,
a
certain
problem
stuff,
like
that
great
forum,
great
participation
there
so
do
check
that
out.
If
you
have
those
general
kind
of
questions
and
if
you
have
very
specific
SharePoint
development
questions,
the
second
link
there
aka
MSSP,
dev
Doc's,
will
take
you
to
all
of
the
SharePoint
developer
documentation,
so
whether
you're
new
to
and
getting
started
with,
SharePoint
framework
or
working
with
add-ins
or
even
the
the
seesaw
model,
so
on-premises
the
WSP
package
model.
A
A
So
today
our
agenda
is:
we've
got
an
engineering
update
on
SharePoint
framework,
quick
updates
on
the
PN
pjs
of
office,
365
CLI
and
the
reusable
controls
and
then
as
well.
We've
got
some
great
demos.
The
first
from
Frank
he's
got
a
bot
with
SPF,
X
and
modern
sites,
very
cool
demo,
and
then
we've
got
special
guests
here
today.
We've
got
luke,
abandon
Ellie,
Pat,
Miller
and
then
well
face
is
not
a
special
guest
he's
here
every
week,
but
we're
gonna
get
some
great
updates
on
SPF
X
1.7.
A
What's
coming
with
that
straight
from
the
floor
on
ignite,
so
very
excited
to
see
that
stuff.
If
you
haven't
gotten
to
watch
the
sessions
online,
this
will
be
a
nice
sort
of
quick
overview
not
as
in
depth
as
the
sessions
and
then
the
session
recordings
will
be
coming
available
in
the
coming
I'm,
not
sure
what
the
timeline
is
for
that
cup
of
coming
days
and
I
would
think
definitely
by
next
week
and
then
maybe
at
the
end,
we'll
have
a
little
bit
of
time
for
Q&A.
A
But
as
always,
you
can
use
the
chat
window
for
questions
and
we'll
do
our
best
to
keep
up
and
answer
those
before
we
get
started
want
to
mention
opportunities
to
participate
in
the
PNP,
SP
FX
and
JavaScript
special
interest
group.
So,
as
always,
we
really
really
really
welcome
and
encourage
the
community
demos.
So
if
you've
got
some
cool
code,
you're
working
on
that
involves
either
SP
FX
or
any
of
the
at
PNP
solutions.
A
So
whether
that's
the
CLI,
the
PJs
or
the
reusable
controls
would
love
to
see
demos
on
any
of
those
things
and
then
as
well.
Demos
related
just
to
client-side
development
on
SharePoint,
even
if
it's
outside
SharePoint
framework
I'd
love
to
have
those
as
well
so
just
reach
out
to
us
myself
or
vaisya,
and
we'll
get
you
on
the
schedule
just
as
soon
as
we
can.
We
are
booked
out
I.
A
A
I
do
think
that's
one
of
the
the
best
of
the
most
valuable
parts
of
these
calls
has
seen
all
the
great
stuff
all
of
you
out
there
in
the
community
are
working
on
and
building
so
really
excited,
for
example,
to
see
what
Frank's
got
for
us
today
and
then
what
you
all
might
offer
up
and
want
to
show
in
the
future.
So
please
just
reach
out
love
to
have
those
demos
as
well.
You
can
contribute
on
github,
so
that
can
take
the
form
of
reporting
issues.
We
always
appreciate
those
issues,
feedback
and
ideas
as
well.
A
We
welcome
your
pull
requests,
so
if
you
have
the
time
and
want
to
put
in
a
pull
request
around
fixing
an
issue
or
adding
an
enhancement,
adding
some
capabilities-
and
that
goes
across
p.m.
PJs,
the
CLI
and
the
reusable
controls
are
all
absolutely
welcoming
of
your
contributions.
So
if
you
have
ideas,
please
contribute
those.
A
If
it's
a
bigger
idea,
don't
be
scared
to
reach
out
and
talk
to
us
about
it
first
and
make
sure
it's
gonna
be
a
good
fit
before
you
invest
a
ton
of
time,
but
I'm
almost
certain
it'll
be
just
fine
and
we'd
love
to
have
your
contributions
and
then,
finally,
you
can
always
provide
feedback
on
everything
we
do
so.
The
feedback
on
these
calls
feedback
on
the
samples,
the
documentation,
the
demos,
what
demos
you'd
like
to
see
things
like
that.
A
So
we
definitely
welcome
that
feedback,
and
while
we
can't
always
act
on
every
piece
of
feedback
immediately,
we
do
take
them
to
heart,
discuss
them
and
do
our
best
to
adjust
what
we're
doing
based
on
what
you
all
are
telling
us.
You
want
to
see
and
hear
so
step
you
to
now
hand
things
over
to
visa
for
the
SharePoint
framework
latest
SharePoint
engineering
update.
B
Sure
these
sections
can
be
relatively
whoo,
and
then
we
let
Frank
to
do
the
demo
and
then
we'll
get
back
on
the
funny
SharePoint
framework
announcements.
But
what
I
wanted
to
do
is
quickly
progress,
the
two
specific
slides
which
always
stop
here.
First
of
all,
the
documentation,
quite
a
sec,
MSSP
div
Docs,
just
to
remind
everybody
ship
on
framework,
modernization,
documentation
and
all
of
that
has
been
updated.
So
it's
up
to
date,
there's
Chapman
framework,
1.6
documentation
out
there,
tutorials,
updated
videos,
updated
and
all
of
everything
is
up
to
date.
B
Now,
once
again,
one
centralized
location
for
all
of
the
documentation
for
SharePoint.
The
second
thing:
what
I
wanted
to
remind
at
the
same
time
is
a
reminder
for
ourselves.
After
ignite,
we
promise
to
catch
up
on
the
issue
list.
We
can
really
falling
behind
on
following
up
on
the
Devi
issues
on
the
base,
PDF
Docs,
and
we
will
absolutely
work
on
this
to
get
clear.
He
needs
to
get
it
claimed
a
fake
night
and
keep
up
to
date
on
what
you're
submitting
so
great
way.
Anyway.
B
The
intention
of
this
location
is
that
you
can
report
any
developer
topics
or
API
issues
directly
to
the
engineering
and
we'll
start
working
on
them,
obviously,
depending
on
the
priority
or
criticalness
of
the
issue,
what
you
encounter
now
unique
nights.
Well,
obviously,
we
we
talked
about
the
future
before
we
go
there
and
just
to
quickly
update
you
on
the
usage
as
well
as
you
can
see,
the
SharePoint
framework
usage
is
actually
rapidly
growing.
I,
there's
an
interesting
optic,
which
we
can
see
already
this
autumn
and
it
seems
to
be,
let's
say,
exponentially
growing
the
adoption.
B
So
if
you're
kind
of
a
wondering
is
worthwhile
to
start
learning
this,
the
answer
is
yes
now,
and
you
should
be
remembering
that
we
are
some
engineering.
We
actually
build
all
of
our
stuff
using
SharePoint
framework
as
well.
So
this
is
the
same
tooling
same
code,
same
platform,
saying
Moodle
what
were
used
in
generally
as
well,
so
that
should
keep
you
confident
enough
to
actually
adapting
to
SharePoint
framework
and
and
it's
great
to
save
that
option.
It
is
absolutely
fabulous
to
say
that
people
are
using
more
and
more
I
share.
B
One
framework
now
on
one
point:
seven:
this
is
what
we
actually
showed
yesterday
in
our
SharePoint
frame
obsession.
So
what
is
the
main
coming
by
end
of
this
year,
hopefully
before
Christmas
and
hopefully
before
December,
and
all
of
that?
What's
with
the
promises
planned
of
this
year,
we
in
the
past
between
talking
about
the
end
of
October.
It
might
be.
It
goes
to
November
sign,
but
in
here
the
big
things
are
a
domain
isolated
web
parts.
B
So
you
can
live
getting
notifications
on
your
components
when
somebody's
selling
items
to
the
list
or
documents
or
lists
so
everything's
going
up
today,
automatically
SPF
X
component
in
steams,
we'll
go
to
preview
in
1.7,
so
you're
able
to
build
up
one
piece
of
code,
which
then
works,
seamlessly
Impulse,
SharePoint
and
also
in
my
stuff
themes-
and
that's
should
be
honest.
That's
only
a
starts
over
looking
into
using
SharePoint
framework,
also
in
other
services,
some
products
as
well
most
likely
it's
going
to
be
done
renamed
just
something
else.
Maybe
that
framework
or
Luca
framework.
B
Seven
supporting
for
what
a
hosted
solutions
and
that's
pretty
high-level
statement.
What
it
means
is
that
you
can
take
the
Microsoft
team
solutions
and
actually
run
them
in
the
SharePoint
site.
So
basically
the
way
how
you
can
build
external
solutions
in
my
stuff
themes,
those
same
solutions
actually
will
work
on
the
SharePoint
site
as
well,
so
really
kind
of
an
aligning
on
the
side-by-side
with
teams
and
SharePoint
on
the
development
experience.
B
And
then
the
last
piece
is
app
pages:
I'm
going
to
do
a
live
demo,
hopefully
on
that
one
as
well
today,
and
so
you
can
build
actually
app
pages,
not
assimilates
applications
as
such,
but
app
pages
inside
of
SharePoint,
so
we're
gonna
stay
alive.
The
amount
that
one
as
well
now
there
was
few
questions
which
I
want
to
actually
ask
from
that
directly
with
by
the
sitting
here,
and
that
is
our
engineering
manager
responsible
of
actually
implementing
stuff.
So
will
we
get
an
update,
update
to
call
up
technically
I'm,
not
really
sure
what
that
means?
B
C
B
In
fact
that
if
you
have
builders
web
parts
using,
we
have
15,
you
don't
have
to
upgrade
them
at
that
moment.
So
we
need
that's
kind
of
delaying
darkride
or
just
padding
the
supporter
for
your
60
and
because
we
need
to
support
site
by
site
so
that
your
old
webparts
will
not
get
broken
and
you
don't
have
to
recompile
them
or
retrenched,
compile
them.
B
Say
well,
there's
a
question
surround
types
of
tree
will
see
what
will
width
version
will
be
aligning
first
and
obviously,
whenever
there's
a
newer
versions,
it
will
take
a
while
for
us
to
catch
on
down.
We
can't
always
go
and
push
just
update
on
the
latest
and
greatest
technology
version,
because
that
might
actually
cause
issues
from
the
existing
code.
So
that's
kind
of
a
slowing
slightly
down
to
adoption
and.
C
B
Now,
there's
a
quick
question
from
Ross
cell
before
we
go
to
the
French
stem
on.
Let's
get
back
on
the
discussion,
but
there's
a
Russell
had
a
quick
question
as
well.
So
can
we
use
SharePoint
framework
with
parts
in
the
SharePoint
mobile
app
as
an
alternative
to
power?
Half
so
bad
we'll
do
the
SharePoint
mobile
app
support,
SPF,
X,
probably
sooner
or
later,
I-
think
that's
in
the
progress
the
the
mobile
app.
C
C
B
C
And
turn
that
all
the
support
already
exists,
yeah,
what
we're
doing
is
were
updating
the
human
generator
in
1.7
and
it'll.
Ask
do
you
want
2016
or
2019
Iran
crammed
for
now
for
2019,
just
install
version,
one
four
zero
of
the
yeoman
generator
and
the
packages
that
that
crates
will
be
compatible
with
ninety.
B
Or
one
point
four
one:
without
the
crap
API
so
good.
Now
we
can
keep
on
and
cling
on
the
questions.
Well,
let's
get
back
on
the
questions
after
Frank's
dimmer
and
we'll
do
live
demos
or
some
of
this
stuff
out
then
ask
the
questions
as
they're
coming,
but
Frank
has
a
really
cool
demo
also
coming
up.
So
let's
get
back
on
the
SPX
topic
and
each
night
updates
after
that
one
so
I
think
that
was
a
black
one
on
that
one
so
Patrick
on
the
PM
BJ's
and
then
let's
go
to
Frank.
A
Excuse
me
quick
updates
on
our
normal
topics
here.
So
next
release
for
peen
PJs
is
going
to
be
October
5th.
We
got
the
changelog
updated
to
see
what's
coming
mention
this
last
time,
but
wanted
to
mention
it
again.
Great
new
documentation
for
nodding
thanks
to
Chris
Kent,
did
some
great
work
to
get
us
onto
MK
docks.
So
that's
hopefully
addressed.
We
had
a
lot
of
feedback
that
they
were
hard
to
navigate.
It
was
hard
to
find
things.
I
think
that's
much
improved.
A
So
thanks
to
Chris
for
that,
if
you
haven't
looked
at
the
docs
in
a
while,
do
please
check
those
out
and
I
did
want
to
mention
briefly
on
browser
support.
We
are
in
PNP
jeaious
drifting
away
from
ie
11
we've
updated
the
polyfill
article,
we're
not
aiming
to
break
functionality
in
IE
11,
but
we
are
not
working
quite
as
hard
to
explicitly
support
it.
Now,
we've
heard
feedback
on
that,
so
we
and
that
can
cause
folks
some
pain.
A
So
we're
not
not
gonna
break
ie
11,
but
we
are
gonna
start
to
use
a
few
of
the
new
features,
for
example
map.
So
we're
not
using
anything
crazy,
but
I.
11
at
this
point
is
five
years
old.
So
it's
it's
I!
Think
time
for
us
to
start
getting
to
you
some
of
the
new
stuff
and
for
all
of
you
to
get
to
do
that.
So
I've
got
like
I
said
updated.
The
polyfill
article
would
encourage
everybody
to
I
know.
We've
got
a
lot
of
customers
that
say
they
can't
move
off.
A
Ie
11
be
an
advocate
for
moving
off
of
il
Evan.
That's
a
big
push
from
a
lot
of
areas
inside
Microsoft
is
to
get
onto
modern
desktop,
so
be
a
be
an
advocate
to
move
away
from
ie
11
as
much
as
possible.
I
know,
there's
scenarios
that
you
need
I
11
for
legacy,
software
legacy,
functionality
etc,
but
do
do
be
an
advocate
for
moving,
because
there's
gonna
be
come
a
day.
This
is
not
an
announcement.
I
don't
have
any
special
knowledge
where
I
eleven
is
just
no
longer
support
it
for
SharePoint
Online,
for
example.
A
B
A
A
Sorry
to
take
you
on
office,
365
CLI
updates.
We've
got
a
new
beta
out
1.70
with
support
for
managing
or
retrieving
in
this
case.
Taxonomy
term
groups
retrieving
web
hooks
exporting
flows,
adding
sections
to
modern
pages
and
improving
the
upgrade
experience
for
SP
FX
projects.
So
that's
really
a
great
great
feature.
A
If
you
haven't
tried
that
out,
the
CLI
now
helps
you
update
or
upgrade
your
SP
FX
projects
from
excuse
me,
older
versions
to
newer
versions,
so
a
great
feature
and
very
much
worth
checking
out
the
CLI
almost
for
that
alone,
so
definitely
check
that
out
and
then
in
progress,
claw
across
platform,
PNP,
starter
kit,
setup
script
and
then
more
commands
and
then,
as
always,
wall
decks.
Looking
for,
if
you
have
additional
ideas
of
commands,
you'd
like
to
see
added,
certainly
would
love
to
hear
those.
A
And
of
course,
if
you'd
like
to
help
out
with
the
CLI,
that's
a
pull
request.
They're
absolutely
welcome
as
well.
You
can
always
install
the
latest
version
and
then
you
can
get
more
information
from
AKMs.
Oh
three,
sixty
five
CLI
so
do
check
that
out.
It's
a
great
great
capability,
especially
if
you're
unable
to
use
PowerShell.
A
So
if
you're
on
a
Mac
or
other
environment
where
PowerShell
is
not
an
option
for
you,
so
big
updates
on
the
reusable
SP
FX
controls,
so
big
I
had
to
make
the
font
small
I'm
not
actually
gonna,
read
through
all
of
these,
but
some
great
enhancements
in
both
the
1/8
and
1/9
versions.
And
if
you
haven't
tried
out
the
controls.
These
are
reusable
controls
to
use
in
the
body
of
your
sharepoint,
Framework
web
parts
or
I.
Guess
application
customizers
as
well,
but
really
saves
you
a
lot
of
time
and
they're.
A
Just
really
great
drop-in
react
components:
they're
styled
with
the
office
UI
fabric,
so
they're
gonna,
give
you
the
out-of-the-box,
look
and
feel
without
you
having
to
really
do
all
work
and
build
that
functionality
yourself.
So
things
like
the
people,
picker
a
listview
part,
a
fieldname,
renderer
renderer
and
a
taxonomy
picker
are
all
great
capabilities
and
there's
even
more
so
definitely
check
those
out.
If
you
haven't
for
your
projects,
you
can
save
yourself
a
whole
lot
of
development,
time
there
and
then
as
well.
This
is
another
place
if
you're
looking
to
get
involved
or
provide
feedback.
A
Certainly
you
know
this
is
welcome
for
the
property
controls
as
well,
and
so
the
property
controls
are
for
the
SharePoint
or
SharePoint
framework,
webpart
property
panes,
so
like
when
you
edit,
the
web
part,
you
get
the
little
property
pane.
These
are
again
dropping
controls.
You
can
use
to
customize
that
editing
experience
and
they're
designed
to
work
seamlessly
there
and
again
styled
with
office
UI
fabrics,
so
you're
going
to
maintain
that
out-of-the-box.
Look
and
styling
with
you
know
these
custom
controls
and
again
saving
yourself
a
whole
ton
of
work.
A
You
know
with
you
know,
having
to
build
these
editing
experiences
in
your
webparts
and
controls.
Excuse
me
so
do
check
that
stuff
out,
and
you
know
absolutely
on
all
of
these
things
p.m.
PJs,
the
CLI
or
these
reasonable
controls
definitely
welcome
your
feedback
and
welcome
your
contributions.
If
you're
looking
to
get
more
involved
in
P&P,
so
I
talked
very
quickly,
so
we
can
get
right
to
Frank
hi.
Everyone.
D
Consultant
attic
was
in
Montreal
Canada
today,
I
will
show
you
a
quick
sample
that
I've
made
a
couple
of
weeks
ago
about
a
bird's
integration
within
a
shopping
sites.
So
before
beginning
a
couple
of
slides
just
to
introduce
the
use
case
and
so
on.
So
basically
the
use
case
for
this
sample
is:
let's
say
you
want
to
build
a
but
assistant
for
your
Sappington
intranets,
for
instance,
to
answer
some
basic
questions
like
it's
a
gift.
We
event
information
about
the
equipment,
users
like
meetings
browsers
from
software
or
even
automate
actions.
D
So
this
is
really
the
use
case,
so
build
an
assistant
for
from
certain
internets.
Technically
speaking,
the
debug
needs
to
access
predicted
resources.
In
our
case
it
will
be
already
resources,
so
the
god
needs
to
access
these
resources
authenticated
as
the
user
to
which
we
will
events
information
because
to
be
truly
an
efficient
and
about
us
to
know
you,
because
by
default,
but
when
I
say
but
I
mean
the
botfly
mark
from
for
Mikasa
by
default,
the
bird
doesn't
know
you.
It
means
there
is
no
single
silent
depending
the
channel
you
use.
D
D
Teams
get
this
education
so
to
access
this
paretic
businesses
from
a
shop
inside
there
are
multiple
options,
and
so
the
first
one
is
the
upon
me
permissions.
But
in
all
cases
it
is
not
really
the
best
option,
because
what
she
wants
is
to
act
as
the
user,
so
you
can
really
grants
the
permissions
which
one
up.
So
this
is
not
reasonable
case.
I'm
not
showing
would
be
to
use
the
implicit
one
flew
with
my
certification
library,
using
the
edge
of
the
v2
endpoints.
This
is
the
purpose
of
the
previous
central,
the
NSL
box
extension.
D
So
basically
the
idea
is
to
handle
the
bottom
situation,
part
within
an
SPCC
extension
and
then
send
the
token
to
the
bottle
object.
So
it
could
access
the
political
resources.
So
we
were
using
the
back
channel
to
communicate
between
yes
prefix
extension,
and
it
is
basically
the
ID
and
there
is
already
a
sample
for
this.
The
other
way
is
to
use
the
optimization
run
flow
with
and
LGS
with
the
other
V
one
endpoint.
This
is
the
proposal
this
demo,
so
we
end
the
scene.
D
D
This
I
have
a
modern
site
here.
This
is
your
intranet
and
I've
created
a
specific
extension
in
my
infinite
resistance.
So
when
you
click
here
you're
in
a
conversation
window
and
when
you
engage
the
communication
with
the
Box
first
of
all,
you
have
to
sign
in
to
access
to
access
resources.
In
this
case,
it
will
be
the
graph
endpoint
to
forget
some
relevant
information
about
this
user.
So
I,
just
click
to
sign
em
up
I'm
setting
in
the
web
and
I
can
access
resources.
So
that's
the
risk
manager
and
beyond
the
sea.
D
The
God
caused
the
graph
end
point
to
get
this
information,
so
I'm
logged
in
and
I
can
get
this
information.
So
pretty
simple
example,
but
in
real
cases
you
want
to
use
other
empires
and
more
complex
scenarios,
but
this
is
the
point.
So
if
I
go
back
here
and
return
to
my
god,
the
conversation
is
saved,
so
I
can
follow
the
conversation.
I
am
I'm,
not
I,
don't
have
to
log
again
within
the
sites,
so
the
technical
part
of
it
to
get
this
conversation
just
stored
in
the
local
storage.
D
To
get
back
to
the
conversation
to
the
bus,
so
how
does
it
work
technically
speaking?
The
first
thing
you
have
to
do
is
stay
fixed
extension,
so
nothing
really
complex.
It's
just
an
extension.
The
main
point:
it's
a
custom,
react
control.
So
this
is
the
bot
framework
we
have
control.
You
can
get
this
control
through
an
NPM
package,
so
you
have
a
github
page
explaining
how
to
use
this
console
behind
the
scenes.
D
This
control
uses
the
type
J
recline
channel
from
the
bus
service,
so
I
will
show
you
the
reserve
that
you
have
to
store
this
information,
the
direct
dying
secrets
within
your
application.
In
this
case,
this
information
is
stored
in
the
story
in
the
local
tenant
flow.
Very
so
this
is
the
way
I
just
store.
This
information
and
the
bird
shows
this
control
to
communicate
with
the,
but
one
important
thing
is
to
transmit
to
the
bot.
D
The
user
identity
when
I
mean
left
is
just
the
unique
ID
for
the
user
and
the
name
to
be
able
to
reach
with
specific
information
about
these
users.
So
there
is
notification
part
on
the
SPF.
It's
extension.
The
most
interesting
part
is
in
the
box
so
to
create
a
virtual
method
options
in
a
juror.
You
have
a
block
here,
so
you
can
create
about
using
another
function
on
the
way
up.
This
is
a
web
app
in
this
case,
I
will
explain.
D
D
About
the
integral
it
was
for
the
service
that
you
can
setup
to
configure
to
keep
your
certification
that
it's
not
part
of
this
demo,
but
it
exists.
So
you
can
take
a
look
at
this
option.
You
can.
It
works
with
multiple
identity
providers
already,
of
course,
but
Facebook
and
so
on.
So
you
can
you
can
trade
it.
So,
let's
go
back
to
the
Box
cut
itself.
D
Yes,
but
so
this
picture
is
very
basic.
We
have
some
routes
here
for
but
diamonds,
we
have
also
groups
to
call
backs
from
the
OAuth
flow
and
to
get
messages
so
to
communicate
with
quality
protected
resources.
We
will
need
to
create
an
application,
as
naturally
application
within
your
talent.
So
let's
say
I'm
on
this
talents:
I
have
to
go
to
the
azure
chance
for
from
this
domain
time,
I
will
create
an
application,
and
this
application
I
would
give
the
deformation
I
want.
D
So
in
this
case,
this
is
the
graph
permission
very
basic,
so
we
use
the
delegated
from
permission
to
two
seems
to
sing
as
the
user.
When
you
can
configure
your
own
here
and
a
really
important
thing
is:
if
they
reply
you
are
now,
so
they
will
tell
you
about.
The
callback
will
be
called
when
the
user
is
long.
So
that's
really
well.
D
You
have
to
use
a
web
app,
but
instead
and
has
no
function,
but
because
you
are
the
supporting
points
that
you
will
use
so
the
callback
to
get
the
token
leave
the
relation
code
that
you
have
to
under
messages
with
another
function.
You
have
only
one
endpoint,
so
it's
difficult
to
get
to
endure
this
dissing.
Also,
you
configure
this
callback
here
and
that's
that's
it
for
the
for
the
user
application.
D
So
if
I
go
back
to
my
about
dialogue,
so
every
time
a
user
send
a
message,
it's
the
root
dialogue.
So,
in
this
wood
dialogue,
I
have
a
meter
the
get
authorization
when
I
will
check
if
the
user
is
already
authenticated
for
this
I
have
some
snow
meetups
options
within
the
bot
framework
to
store
this
information.
In
this
case
it
will
be
the
access
token
in
the
pod
frame
of
like
I,
said
multiple
option
to
store
information
for
a
demo
purpose.
I
used
the
memory
the
in.
D
You
can't
use
this
in
Yukon,
so
get
back
to
my
well,
so
I
just
check.
If,
for
this
user,
this
particular
user,
there
is
an
access
token,
if
not
I've,
generated
signing
car
as
I.
Think
I,
guess,
if
you
just
the
link
sent
to
the
users
with
a
with
a
pretty
funny
Avella
in
this
scaled
URL
will
be,
will
be
built
to
initiate
the
reasoning
flow.
So
this
is
a
three
parameter
URL,
with
the
resource
I
can
access
and
so
on.
The
video
aqy
and
the
way
I
want
to
longer.
D
There
is
a
so
special
parameter.
The
state
parameter
is
really
important
in
this
case,
because
this
parameter
will
give
you
the
opportunity
to
store
information,
personal
information
and
useful
information,
and
this
information
will
be
would
be
back
to
you
after
the
user
logged
in
so
in
this
case,
I
stopped
the
address
of
the
bots.
The
addresses
like
the
way,
the
information
that
allow
you
to
to
start
a
conversation
to
to
I
can
I
can
say
that
to
continue
a.
D
So
then,
if
a
user
is
since
Kerry,
I
can
make
call
to
my
graph
resources
so
in
this
guy
I
used
Louis
to
detect
the
intention
and
associate
a
particular
call
from
the
graph
that
would
be.
You
can
use
anything
you
want,
it
doesn't
really
matter.
The
point
is
really
about
the
the
authentication,
so
all
the
flow,
the
authentication
flow
reason,
though,
to
add
a
yes,
so
this
is
back
in
show
I
control,
the
URL
and
the
way
the
authentication
is
performed.
So
this
is
you
to
tell
flexibility
about
about
this.
D
D
A
Great
stuff
Frank,
thank
you
very
much
that
awesome
stuff
and,
as
you
saw
a
lot
of
possibilities
for
bots,
so
definitely
check
those
out
and
there's
a
great
question:
can
one
bot
connect
to
lots
of
things
and
the
answer
is
yes,
so
you
can
set
up
those
different
channels
as
Frank
was
showing
and
you
can
connect
to
teams
you
can
connect
to
you
know
various
you
know
chat
like
I.
Am
you
can
connect
to
other
surfaces,
so
really
cool
stuff?
A
C
Step
is
less
code
and
more
showing
some
new
capabilities
that
were
going
to
be
rolling
out
in
preview
for
with
1.7
release,
and
so
what
we've
got
here
is
a
page
where
we
grab
the
personal
email
web
part
from
the
SP
starter
kit
and
put
it
on
our
page
when
I
first
rendered.
This
page
I
didn't
have
bumps
or
everything
sound
so
to
standard
I
whip
hurt
in
the
page
and.
C
B
B
C
A
C
B
B
C
And
here's
the
app
that's
running
in
that
app
or
here's
the
permissions
of
the
app
itself
has
provisions
to
the
graph
saying
read
you
read:
user
email,
the
this
isolated
personal
email
app
has
been
configured
to
have
all
of
the
reply.
Urls
to
this
other
app
domain,
which
was
created
per
component
and
so
we've
basically
taken
the
exact
same
web
part
dropped
it
on
the
page.
But
it's
now
wrapped
in
a
separate
application
that
makes
that
has
a
different
URL
that
has
its
own
unique
permissions,
but
still
interacts
nicely
with
the
page.
We're.
C
C
Jason
that
says,
I
would
like
this
solution
to
be
domain
isolated
and
at
that
point
in
time,
all
the
webparts
running
from
this
package
will
be
isolated
in
their
own
iframe,
which
will
communicate
back
and
forth
with
the
host
page.
There's
a
slight
hiccup
right
now
in
the
code
where
the
so
basically.
B
The
this
answers
the
concern
of
some
customers
saying
that
well,
if
I
put
many
of
the
webparts
on
a
page
with
from
a
multiple
vendors,
they
can
access
to
access
tokens
and
taking
kind
of
a
leak,
theoretically,
some
data.
So
if
that
is
a
concern
for
you
or
the
administrator
or
for
your
customers,
you
can
isolate
that
part
running
in
a
different
domain,
which
adds
additional
security
yeah.
The
other
scenario
that
these
feature
covers
is
you,
as
an
ISV
was
the
protector
ID.
Neither
one
are
the
components
for
your
API.
B
C
B
D
B
C
The
code
running
has
full
access
to
the
same
DPI's.
It
has
the
full
page
context
for
the
current
page
that
have
toasted
on
the
user
information,
the
theming
information
that
will
tell
the
regional
setting
my
pod
for
responsiveness.
It's
an
aggregate,
so
it'll
be
slightly
less
responsive.
Sorry,
it'll
be
slightly
less
fast
than
the
main
page.
Our
goal
is
that
it'll
be
the
same
responsiveness,
so,
like
I
said,
the
slight
hiccup
right
have
right
now
is
that
we're
yeah
like
an
off
by
one
or
off
by
two
pixel
there?
C
B
C
B
These
page
will
basically
one
form
factor
or
another
we're
still
debating.
What
is
the
right
works?
It
will
show
all
the
permission
that
has
been
requested,
and/or
approved
for
the
tenon,
which
is
what
you
have
in
1.6,
as
well
as
all
the
permissions
that
have
been
or
requested
for
a
specific
component,
and
we
were
doing
work
to
be
sure
that
these
information
and
thought
together,
clearly
yeah
and
just
to
be
super
clear.
This
is
super
early.
C
C
B
B
B
C
C
B
B
Which
is
launched
for
you,
you
want
to
basically
readable
application
without
requiring
an
alpha
to
compose
your
application,
and
you
want
also
to
lock
the
experience
so
that
accidentally
or
on
purpose
the
applications
get
removed
by
division
so
into
users
can't
accidentally
delete
all
right
or
correct,
which
makes
lot
of
sense.
That's
obviously,
because.
B
D
B
C
Part,
so
we
really
think
there's
basically
two
models
of
app
pages.
One
of
them
is
I,
have
one
control,
and
in
that
case
the
control
is
the
full
size
and
if
there's
any
scrolling,
it
happens
within
the
control,
yeah
and
then
there's
an
alternate
one,
which
is
I,
basically
got
a
page
that
I've
configured.
Maybe
it's
using
part
two
part
communication,
a
bunch
of
text
and
I
can
create
that
into
an
app
page,
and
in
that
case
it
will
act
like
a
normal
page,
but
it
won't
have
the
generous
header
at
the
top.
C
B
C
C
Which
was
your
real-time
news
beam?
What
girl
this
video
exactly,
but
it
was
it
was.
It
was
great,
particularly
because
you
had
this
long
description
of
how
to
actually
get
socket
IO
to
get
live,
updates
which
sort
of
went
on
and
on
and
on
about
all
the
work
had
to
do
with
Azure
and
creating
message,
pumps
and
all
this
stuff,
and
so
for
1.7.
What
we're
gonna
release
is
a
preview
close
make
sure
this
is
the
rates.
C
C
C
C
B
C
List
isn't
in
the
current
site
in
the
current
web.
You
can
pass
those
parameters
in
as
well
come
if
you're
doing
from
a
my
a
regular
one
or
the
opposite,
you
can
pass
it.
You
need
to
pass
in
the
target
domain.
Oh
and
then
all
you
do
is
you
say:
I
want
to
call
this
function
when
the
notification
happens
and
this
function
when
we're
connected
yeah.
D
B
D
B
C
C
B
B
B
C
B
B
You
Frank
did
a
great
job
on
the
anti
example
on
pants
already,
but
it's
it's
now.
This
is
really
doesn't
require
that
much
code
and
it's
really
easy
to
do
well.
Did
we
have
anything
else
to
still
are
I
think
that's
it
for
this
one
we're
running
out
of
time
anyway.
The
dynamic
dude
is
that
the
best
time.
B
B
And
so
I
think
this
is
fun,
if
not
like
said,
will,
will
absolutely
cover
all
of
the
other
announcements,
branding
announcements,
I
designs
of
that
stuff
in
our
chemicals,
absolutely
the
next
sorry
Patrick,
the
next
SPF
x
call
is
an
october
11th
and
then
the
next
general
shape
on
dev,
where
we're
gonna
cover
branding
stuff
site
designs.
All
of
those
this
is
from
next
Thursday
doper.
C
I'm
not
sure
if
it
requires
us
to
do
internal
work
or
if
it's
ever
be
do,
but
community
is
an
easy
way
to
convert
existing
SharePoint
add-ins
replace
the
off
module,
which
is
effectively
the
token
helper.
The
bulky
to
use
something
compatible
with
themes
on
all
the
new
team
in
model
yeah,
because
it'd
be
great.
If
we
could
just
say
here's
the
drop-in
replacements
and
you're
good
to
go,
and
now
you
get
access
to
the
rest
of
office
365.
So.
B
B
B
Capabilities
introduced
and
arab
making
sure
that
you
can
achieve
same
stuff
lesson
adding
some
more
on
that
model
as
well.
So
but-
and
this
is
propelling
it's-
the
code
is
not
available.
Teams
integration
not
yet
available,
though
it's
coming
at
1.7,
and
they
will
get
additional
guidance
out
immediately
when
we
can
so
you'll
be
up-to-date
on
anything
but
I
think
that's
it
Patrick
any
last
words
from
your
sign
not.