►
From YouTube: Office Add-ins developer community call-January 2020
Description
January’s call, hosted by Kim Brandl, featured the following presenters and topics:
-Alex Jerabek, Dev Writer, provided a general overview of Office Add-ins.
-Raymond Lu, Senior Program Manager, shared information about Excel preview (beta) APIs in requirement set 1.11.
-Vesa Juvonen, Principal Program Manager, presented about building Office Add-ins using the SharePoint Framework.
-Kim Brandl, Senior Dev Writer, shared that the Yeoman generator for Office Add-ins will soon support creating SSO-enabled Office Add-ins.
For more information, visit https://developer.microsoft.com/office
A
All
right,
good
morning,
everyone
welcome
to
the
office
Adams
developer
community
called
today's
January
8
2020
and
really
happy
everyone
could
join
us
for
the
first
call
of
the
new
year.
Just
a
few
notes
about
the
call
before
we
get
started
here
for
anybody
who's
new.
If
you
don't
already
have
the
recurring,
invite
you
can
download
it
using
the
AKMs
link
on
this
slide.
This
call
happens
the
second
Wednesday
of
every
month,
so
next
month's
call
will
be
on
Wednesday,
February
12th.
A
This
is
a
chance
for
everyone
to
meet
the
folks
on
the
product
teams
that
are
building
the
office.
Javascript
API
is
in
the
office
Adams
platform.
We
talk
a
lot
about
what's
new
and
what's
coming
soon,
so
this
is
a
great
way
to
kind
of
be
on
the
leading
edge
of
what's
happening
in
the
office
Adams
platform.
You
also
get
to
witness
some
technical,
deep,
dives
and
learn
in
depth
about
certain
subjects
and
occasionally
we'll
have
a
customer
presentation
where
you
get
to
learn
from
other
folks
that
are
building
on
the
office
at
its
platform.
B
A
D
Right,
Thank,
You
Kim,
so
yeah,
like
you
mentioned,
we
like
to
start
up
this
call
of
a
brief
overview
of
office
add-ins
to
make
sure
everyone's
on
the
same
page.
So
what
is
an
office
add-in
on
Adhan
is
a
web
service
that
you
interact
with
through
your
office
client.
So
you
have
your
web
service
that
you
can
access
through
Excel
or
PowerPoint
right
within
the
workbook
or
presentation
and
add-in
consists
of
two
parts.
D
One
is
the
web
service
itself
and
that
is
written
with
familiar
web
technologies,
HTML
or
CSS,
and
then
there
is
a
second
part,
the
manifest
file,
and
that
is
what
configures
your
office
host
to
be
able
to
find
the
web
service
out
there.
The
manifest
file
is
what's
shared
across
platforms
into
your
customers,
either
it's
uploaded
the
office
Store
for
people
to
download
or
its
side
loaded
for
testing
or
it's
deployed
through
your
admin
Center,
and
that
allows
your
added
to
be
hosted
on
desktop
on
Mac
online
and
all
these
different
clients.
D
D
We
have
a
series
of
five-minute
quick
starts
that
will
get
you
up
and
running
with
a
working
add-in.
You
can
also
take
our
full
fledge
tutorials
and
start
playing
around
the
api's
in
script
lab.
So
you
can
see
how
those
office
JavaScript
API,
is
actually
interact
with
your
workbook
or
Word
document
under
that
I
think
I'll
turn
it
back
over
to
Kim
Thank,
You
Kim,
awesome.
B
Thankthank
scheme
thanks:
everyone
Happy
New,
Year
everybody.
My
name
is
Raymond
I'm,
a
program
manager
in
Excel,
JavaScript
API,
our
team
located
in
Beijing,
and
today
I
would
like
to
talk
about
the
three
topic.
One
is
one
point
xi
j
time.
A
second
is
one
point:
eleven,
a
beta
api
candidates
and
the
third
one
I
will
share
you
how
to
try
a
beta,
API
and
I'll.
Give
you
ten
more
at
the
end,
so
the
first
one
is
the
the
time
when
we
get.
B
C
B
B
A
B
Okay,
oh
yeah,
by
the
way
this
is
all
the
candidate
API.
It
doesn't
mean
that
we
has
to
release
those
API,
because
now
we
want
to
hear
your
feedback
and
if
there's
anything
we
need
to
change
or
any
feedback
is
really
welcome
and
we
we
may
women
do
some
modification
if,
if
there's
needed,
so
your
feedback
is
really
important
to
to
our
1.11.
If
yeah,
I'll,
better
ABI,
okay,
so
for
range
range
area,
we
we
bringe
object.
We
have
a
new
api,
which
is
very
useful.
I
said
we
know
that
we
have.
B
We
have
copy
and
paste,
but
we
don't
have
to
copy
the
paste.
So
we've
received
a
lot
of
feedback
from
a
lot
of
requests
from
other
from
a
customer,
so
we
release
this
API,
so
you
can
use
to
move
to
and
can
realize
your
copy
cut
and
copy
future.
Okay
and
the
range
format
we
we
enabled
an
indent.
You
can
use
this
API
to
adjust
intent,
increase,
indent
or
decrease
indent
and
slicer.
We
enable
the
name
in
formula
okay
and
we
have
released
15
more
about
the
comments
API
previously.
B
You
know
in
one
point
one
point:
n:
we
release
about
30
API
for
comments,
and
then
we
get
15
more.
These
may
give
you
a
possibility
to
access
the
comments,
reply,
comments
and
mention
all
these
kind
of
information
which
is
really
useful
and
for
what
pool
level
and
work
she
level
we
a
few
more
capability
and
for
workbook
you
can
use
the
what
boot
are
closed.
They
can.
Let
you
close
the
hole
the
workbook
and
save
can
enable
you
to
save
the
document
and
as
well
as
the
get
file
a
a
sink.
B
We
now
we
support
PDF
format
for
the
worksheets.
We
support
the
calc
events.
Then
then
you
can
use
these
two
to
listen,
whether
there's
a
cow
triggered.
So
the
last
is
the
row
hidden
events,
so
you
can
use
the
low
heat
and
events
to
to
monitor
whether
whether
the
the
customers
heat
in
the
row
or
unheeded
row
yeah,
and
that
can
give
you
the
information,
whereas
her
dress
wasn't
was
the
type
and
what
which
seed
our
user
are
doing
that.
Okay.
B
So
all
these
API
beta
right
here,
how
do
you
do
it
actually
very
simple
I?
You
could
use
you
can
change
your
reference
to
beta
CDN
then
like
in
github.
You
could
choose
to
change
the
as
one
to
beta
and
then
you
can
have
the
capability
to
use
that
law
cell
near
me.
Let
me
share
my
screen.
I
will
give
you
a
demo
how
to
how
to
use
that
okay,
so
let
me
do
is
some
from
very
beginning.
Okay.
B
This
is
a
a
blank
snap,
okay,
so
if
we
run
it
and
and
just
just
nothing,
this
is
a
discipline
and
if
I
want
to,
for
example,
I
want
to
use
the
cultural
info
API,
so
I
gonna
do
this.
B
The
cultural
info
is
actually
as
I
show.
You
previously
is
under
the
application.
So
I
can
do.
Is
I
load
these
API,
though
these
property
and
then
I
just
eat
very
easy.
Just
show
that
what
a
cultural
name
for
and
then
I
just
want
to
know
that
was
the
since
this
ammo
separator.
So
that's
very
simple.
Okay,
so
when
I
do
run
run
okay,
you
got
the
arrow.
The
reason
is
that
we
are
not.
This
is
reference
to
product
CDN.
B
So
if
I
go
to
the
library
here,
if
I
change
it
to
from
1
to
beta,
then
I,
do
it
run
it
again
here?
Okay,
then
then
the
beta
beta
API
is
it
be
able
to
to
access.
Now
you
can
see
that
your
system,
cultural
name,
is
I'm
located
in
China,
so
this
is
HTM.
My
assistant
setting
and
my
decimal
separator
is.
Is
this
this
one
yeah?
B
So
that's
it's
the
end
of
my
demo.
So
please
try
it
out
the
oldest
beta
beta
API
and
your
feedback
is
really
are
very
helpful
for
us
see
whether
you
have
advice
and
suggestion
how
we
can
make
it
better
and
if
it
is
necessary
we
need
to
do
some
changes
for
these
API.
So
before
before
may,
before
the
beaut
May
Day
May
19,
we
still
have
chance
to
do
some
modification
for
those
API.
B
If
you
have
some
requirement
or
special,
as
for
these
okay
and
beside
beside
all
this
API,
we
still
our
team
still
working
on
the
1.12
api.
One
point
l
might
include
some
api
like
president's,
like
custom
properties
like
the
the
the
commons
events,
something
like
that
and
we
will
share
more
details
in
the
future
community
call,
that's
all
for
my
site.
Thank
you
very
much
and
yeah
and
I
return.
My
control
back
to
Kim.
A
A
At
the
end
of
this
decade,
one
there's
a
there's:
gonna
be
a
slide
with
some
learn
and
engage
resources,
and
one
of
the
links
on
there
is
going
to
be
the
github
repo.
It's
just
an
it's
in
the
office,
dev,
org
and
github,
and
it's
called
office
J
s
office
JSF.
So
if
you
do
have
feedback
about
any
of
the
beta
api's
or
anything
that
Raymond
showed
today
feel
free
to
provide
feedback
to
us.
A
That
way,
that
would
be
great
and
likewise
there'll
be
a
link
also
to
user
voice,
which
is
how
we
collect
feature
requests.
So
if
there's
AP
is
that
you
haven't
heard
of
being
already
under
development
that
you
think
would
be
really
useful
for
you
I'm,
you
can
submit
them
to
us
via
a
user
voice.
There'll
be
a
link
to
that
as
well.
So
thanks
Ranger,
that's
really
great.
It's
really
great
to
see
the
velocity
with
which
we
continue
to
add
api's
to
excel
it's,
it's
really
a
very
robust
set
of
api's
now.
B
A
And
folks,
if
you
have
any
other
questions
about
the
Excel
API
is
feel
free
to
post
them
to
the
chat
window
and
Raymond.
If
you
can
keep
an
eye
on
the
chat
window
there
and
just
kind
of
correspond
with
people
that
way,
that
would
be
great.
Okay.
Great!
Thank
you
awesome.
So
next
up
we
have
a
so
here
with
us
from
the
SharePoint
team.
He's
gonna
talk
about
building
office
add-ins
using
the
SharePoint
framework.
C
Excellent
Thank,
You
Kim
so
before
I
actually
start
so
my
name
is
Osso.
You
want
to
know
I'm
principal
program
manager
in
the
one
try
SharePoint
team,
which
is
a
joint
engineering
effort
and
I'm,
also
responsible
of
our
open
source
and
community
engagement,
so
making
sure
that
their
customers
and
partners
understand
how
to
do
extensibility
in
Microsoft
365
in
general
or
in
the
SharePoint
and
onedrive
area,
and
all
of
us
that
includes
crafts
and
everything
else.
What
we're
doing
this
side
now
in
shape?
C
One
side
of
the
house
we've
been
using
the
our
latest
extensibility
model,
which
is
SharePoint
framework
for
a
while
and
SharePoint
framework,
was
released
almost
three
years
ago,
and
it
has
been
a
widely
successful
in
the
cloud
and
it's
designed
for
a
UX
layer
extensibility.
So,
basically,
if
you
want
to
modify
and
create
an
widget
on
a
SharePoint,
I
want
to
create
a
widget
in
Microsoft
teams
or
nowadays,
if
you
want
to
create
a
widget
or
functionality
or
a
solution
also
in
office
settings,
you
can
actually
take
advantage
of
SharePoint
framework.
C
Now
why
on
earth,
where
I
would
actually
do?
That
would
be
to
probably
the
first
question:
if
you're
not
familiar,
we
share
one
framework,
so
let's
actually
start
with
that
one
and
quickly.
So,
first
of
all,
if
you're
not
familiar
what
is
a
SharePoint
framework
and
how
these
things
work,
obviously
I
will
show
you
some
resources
and
a
live
demo
in
a
second.
C
But
the
beauty
of
SharePoint
framework
is
that
we
take
care
of
the
hosting
so
number
one
challenge:
what
office
add-ins
developers
kept
on
saying
and
enterprise
developers
who
were
planning
to
do
an
enterprise
extensibility
for
their
customers
were
saying
that
well,
it
always
gets
complicated
because
somebody
needs
to
host
my
extensibility.
My
web
application
I
need
to
create
an
azure
application
and
I
when
I
go
and
request
an
azure
application
for
my
customer
enterprise
customer.
C
It
takes
a
cheers
to
get
that
and
all
those
permissions
and
everything
else,
it's
really
really
difficult,
which
open
framework
and
officer
dense
development.
All
of
this
is
automatic.
You
don't
actually
have
to
worry
about
hosting,
because
everything
is
hosted
for
you
automatically,
so
your
code
is
being
hosted
by
us,
which
is
a
great
thing,
because
you
can
save
money.
Now
the
second
really
good
thing
is
that
authentication
so
authentication
and
which
open
framework
and
of
assonance
it
just
works.
You
don't
need
to
do
anything
related
on
your
code
and
the
authentication
just
works
automatically.
C
C
You
don't
have
to
do
any
changes
within
your
code,
except
unless
you
want
to
access
something
a
service
or
application
specific,
for
example,
using
the
office
Java
JavaScript
SDK,
then
you
obviously
use
the
office
JavaScript
SDK,
which
is
given
to
you
easily
within
the
code
as
well
and
I'll
show
you
that
one
in
a
second
as
well,
but
you
can
basically
the
baseline
component
and
based
on
implementation
and
solution.
It's
exactly
the
same.
So
you
can
reuse
the
same
piece
of
code,
which
is
super
super
important.
The
skills
reuse
super
important
thing.
C
You
don't
actually
have
to
learn
at
anything
specific
if
you're
developing
anything
for
these
three
different
applications.
So
it's
the
same
tool
set
it's
the
same,
yeoman
generator,
it's
the
same,
API,
it's
the
same
same
type,
script
version,
it's
the
same
extensibility
model
which
we
are
taking
advantage,
so
you
can
actually
build
on
top
of
your
existing
skill
set
and
the
deployment
is
super
easy
and
you
basically
have
automatic
hosting,
and
you
can
want
this
one
way
of
deploying
office
settings
much
the
same
steps
or
SharePoint
framework
with
parts
as
well.
C
Now
we're
also
looking
into
having
a
more
consistent
and,
let's
say,
more
wider
Microsoft
resist
if
I'm
developer
story-
and
this
is
something
which
is
coming
slightly
later
so
sooner
or
later
you
don't
actually
use
SharePoint
framework
to
create
of
a
sentence
you
use,
Microsoft,
365
framework
or
whatever
it
will
be
called
and
even
in
ignite,
we
kind
of
a
set.
We
didn't
say
out
loud
what
it
will
be
called
because
it's
marketing
decision,
but
there
will
be
a
one,
unified,
Microsoft
365.
Is
it
a
component
or
an
application
platform?
C
We
can
actually
then
say
that
hey
I
want
to
have
a
component,
and
with
that
component
you
can
define
where
it's
going
to
be
hosted.
It's
going
to
be
hosted
in
office,
add
as
an
office
settings
or
as
a
Microsoft
themes
term
or
as
a
SharePoint
framework
board
the
covenants.
So
you
can
have
a
one
centralized,
centralized
management
of
the
the
covenants
as
well,
so
managing
all
of
your
applications
in
a
single
location.
C
This
comes
with
a
unified,
app
catalog,
which
is
in
development
and
not
yet
available,
and
then
cross-platform
support
in
the
office
are
using
the
same
chiffon
framework
web
part
or
your
office
settings
across
the
windows,
Excel
PowerPoint
and
office
across
all
of
the
different
platforms
as
well
again
same
piece
of
code,
which
is
a
superset
very
important
thing.
So
those
three
things
are
coming:
they're
not
yet
available.
Technically,
the
whole
implementing
of
a
sudden
surge
in
SharePoint
framework
is
in
preview,
so
we
released
it
actually
to
preview
yesterday.
C
So
this
is
super
super
new
stuff
for
you
to
take
advantage.
We
did
show
it
in
the
night
already,
so
my
actually
seen
some
of
the
videos
now
the
longer-term
vision.
What
we
want
to
do
with
my
accessories
is
device
platform
is
really
to
come
up
with
a
one
unified
way
of
doing
extensibility,
obviously,
and
it's
a
complex
platform
and
Obrestad
behind
the
scenes-
videos
max
of
craft
api's,
because
that
gives
you
the
contextual,
personalized,
access
to
the
relevant
information,
and
then
you
can
use
the
specific
KPIs
and
SDKs
for
the
service.
C
What
you're
using,
but
the
whole
idea
of
this
longer-term
vision
is
to
have
a
one
yo
at
Microsoft
365,
where
you
can
actually
then
create
your
application
or
your
widget
or
a
solution
which
then
you
can
define
where
it's
going
to
be
hosted
when
it
kind
of
space
surfaced.
So
you
don't
actually
again
need
to
have
specific
knowledge
of
a
specific
application,
not
sure.
If
you're
implementing
an
excel-based
extensibility,
you
will
take
advantage
of
excel
JavaScript
SDK
and
it
has
its
own
specific
things
to
make
happen.
C
But
the
actual
widget,
the
implementation
of
the
style,
is
the
same
cross
to
Microsoft
reassessed,
environment.
That's
the
vision
where
we're
heading
gradually.
This
will
take
a
while
still
and
to
get
there,
but
this
was
already
presented
in
the
ignite
ignite.
2019
in
November
in
Orlando
three
months
ago,
but
that
gives
you
a
scene
where
we
are
hitting
now
like
I
said
yesterday,
and
we
released
the
preview
version
of
office
add-ins
built
with
SharePoint
framework,
and
even
that
sounds
really
weird.
C
By
the
way,
creating
office
items
using
SharePoint
framework,
why
would
you
use
shape
and
frame
were
too
great
of
a
sentence?
Well,
that's
precisely
the
reason
why
we're
renaming
all
of
this
stuff
as
a
unified
platform
0
later,
but
for
now
what
we're
actually
doing
is
that
we
are
building
a
ship
on
framework
report
during
the
preview
timeframe.
C
We
have
a
shipment
framework
web
part
to
kill
a
bit
of
this
context
and
we
have
the
office
manifest
and
we
are
using
site
loading
during
preview
for
time
frame
and
that
actually
is
the
Outlook
Web
Access
application,
so
Outlook
Web
Access,
adding
which
you
can
then
take
advantage
with
in
your
Outlook
Web
Access.
This
is
the
preview
time
frame
and
we're
looking
into
extending
this,
then
to
cross
all
of
the
other
applications
as
well.
So
word
PowerPoint
Excel
and
all
of
that
work
is
being
done
already
or
being
actively
worked
on.
C
So
let's
have
a
look
on
this
one
in
practice.
So
what
does
it
actually
mean
that
you
built
using
a
one
specific
tooling
and
it
targets
either
webpart
or
a
sharepoint
or
a
teams
or
an
office
settings?
And
what
does
it
mean
that
I
can
access
to
office
JavaScript
SDK
within
my
code?
They
jump
first
on
the
commander.
So
let's
actually
have
a
look
on.
How
do
we
create
this?
C
So
if
you
are
familiar
with
SharePoint
framework
and
then
it
might
be
super
familiar
what
I'm
doing
here,
but
let's
actually
have
a
look
on
what
we
are
doing
so,
first
of
all,
we
are
using
the
SharePoint
framework,
yeoman
generator
like
set
for
now,
sooner
or
later,
there's
going
to
be
Microsoft,
365,
yeoman
generator,
which
you
use
for
generating
the
UX
layer
for
extensibility
and
because
this
is
a
preview
bility
and
we're
gonna
do
before
I
go
to
the
comment
line.
Let
me
recap
slightly
and
you
can
find
the
documentation
in
akms.
C
Spf
X
is
actually
the
URL
AKMs
SPF
X
is
the
easiest
way
to
find
the
relevant
documentation
and
that's
a
really
easy
thing
to
remember
as
well.
Spf
X,
meaning
SharePoint
framework
from
here
I
can
search
for
office
office,
adding
or
office,
and
we
can
actually
find
the
building
of
a
Saturday
institution
a
sharepoint
framework
and
that's
basically,
then
the
tutorial
which
we
kind
of
a
take
advantage
in
this.
You
end
this
quick
demo
as
well,
so
we
can
I
use
the
OMA
generator
and
we're
gonna
use
the
past
beta
command
behind
it.
C
So
let
me
actually
get
back
on
the
comment
line.
Do
the
plus
beta
and
I'll
do
skip
install
here,
which
basically
means
that
I'm
not
going
to
run
the
yeoman?
Sorry,
the
npm
install,
which
will
save
some
time
for
showing
you
what
we
actually
can't
for
executing
the
yeoman
generator
so
ano
my
generator,
and
if
you
open
framework
its
first
gonna
ask
what's
the
solution
name
so
outlook
demo
is
fine.
We're
gonna
talk
a
SharePoint
Online
for
now,
like
I
said
for
now.
C
This
is
quite
SharePoint,
specific
questions,
but
all
of
this
is
going
to
be
changed
in
the
future
use
the
current
folder.
Do
we
want
to
allow
to
not
admin
to
deploy
stuff
immediate
across
the
tenant?
Yes,
we
want
to
have
a
specific
permissions.
No
we're
going
to
target
a
web
part
for
now
and
we're
gonna
call
it
outlook.
Demo
and
description
is
fine.
I
do
want
to
use
react,
knockout
well,
for
now,
let's
not
use
in
a
JavaScript
framework,
and
there
we
go.
C
The
yeoman
generator
has
created
us
the
solution,
without
node
modules
folder
so
quickly
having
a
look
on
what
actually
happens
here
is
that
we
give
you
a
webparts
solution
and
with
part
baseline
solution,
and
we
also
give
you
it's
basically
ready
to
go
as
a
starting
point,
and
we
also
give
you
a
manifest
file
which
is
ready
to
go
to
get
hosted
into
Outlook
Web
Access.
So
you
can
easily
get
started
on
testing
things
because
everything
what
you
need
is
available
in
here,
so
I'm
not
gonna,
actually
kept
in
a
package.
C
This
one
I'm
gonna
close
this
one
I'm
gonna,
use
another
solution
which
I
created
earlier,
because
I
wanted
to
save
some
time
for
not
actually
installing
the
node
modules
and
that's
the
one,
if
I'm
not
mistaken.
Yes,
that
is
the
one.
So
this
is
a
solution
which
I
created
earlier,
where
we
actually
have
an
access
already
to
the
office
office
context
and
accessing
the
office
context
is
nothing
more
then
in
the
web
part
or
in
the
panel
implementation.
I.
C
Do
this
context
the
test
a
case
and
from
here
again
depending
where
the
panel
or
an
widget
or
an
application
whatever?
We
want
to
call
this
in
the
future
if
it's
actually
hosted
in
office
and
that
office
context
is
then
available
and
from
the
office
context,
I
can
actually
access
something
like
mailbox
and
Mail's
and
messages,
and
all
of
that,
whatever
is
the
API.
What
you
need
to
access
on
now
I
can
then
use
this
context.
To
figure
out
am
I
actually
in
office
or
am
I
in
SharePoint.
C
So
I
can
use
exactly
the
same
piece
of
code
as
an
officer
in
or
as
a
SharePoint
framework
or
as
a
team
stamp
as
well.
If
you
prefer
to
do
that,
so
in
this
case
we're
just
going
to
basically
output
the
message
and,
depending
on
the
fact
that
are
we
in
SharePoint
are
we
in
the
office
so
quick?
Let's
quickly,
actually
walk
this
through,
because
this
is
super
super
cool
because
all
of
the
hosting
deployment
everything
else
super
streamlined
or
you.
C
C
Json
files,
you
can
even
ask
my
craft
permissions,
so
nobody
needs
to
go
to
as
your
ad
and
create
an
application
or
grant
permissions
then
go
through
all
of
that
burden
in
the
enterprise
development
process
to
get
those
permission
ekran'
debts.
Now
you
don't
actually
need
to
go
through
ad
at
all.
You
just
request
the
permissions
and
the
tenant
administrator
of
the
office
tenant
can
grant
the
permissions
and
this
for
your
application,
quite
streamlined
experience.
Now
let
me
actually
do
a
cop
package
solution
as
well,
so
I'm
going
to
actually
package
the
solution.
C
It's
going
to
not
kind
of
take
too
long
and
that
we
actually
get
stuff
created
and
let
me
actually
open
up
and
that
solution.
So
here's
my
solution.
We
can
actually
see
I'm
located
in
Finland,
it's
631
right
now
in
Finnish
timeframe.
So
let
me
actually
go
to
my
tenants.
What
are
we
going
to
how
we're
going
to
install
this
to
my
tenant
right
now?
It
is
still
using
the
SharePoint
app
catalog
again
we're
working
on
a
unified,
Epcot
experience
in
a
tenant
level.
C
That's
coming
sooner
or
later
this
year,
as
well
now
I'm
installing
the
solution
to
my
tenant
and
it's
gonna
actually
ask
some
permissions.
Just
gonna
ask
them:
do
some
nodes
related
in
minecraft
permissions
which
which
the
solution
is
requesting
to
get
up
their
missions
as
well
I'm,
not
actually
using
those
in
the
sample,
so
I
don't
need
to
grant
us
that
the
permissions
as
such,
but
now
there
we
go.
Our
solution
is
being
hosted.
C
What's
really
cool
about
this
model
again,
if
you're
not
familiar
with
SharePoint
framework,
is
the
fact
that
this
file,
this
SP
PKG
file,
actually
contains
all
of
the
assets
it
contains.
All
of
the
JavaScript
files,
it's
going
to
condense,
all
of
the
manifest
files
and
all
of
those
stuff,
so
everything
is
automatic.
I
can
send
that
file
to
any
of
my
customers
and
say
instead
that
your
and
you're
good
to
go
super
easy
super
convenient
experience
as
well.
C
C
Let
me
actually
get
the
path
to
the
folder.
Let
me
actually
open
up
a
folder
one
more
time,
so
I'm
actually
get
the
manifest
location.
That's
my
manifest
location
for
this
file,
which
we,
by
the
way,
create
automatically
for
you
as
well.
So
I
don't
have
to
worry
about
how
do
I
create
the
manifest
we
create
it
for
you
with
the
default
settings.
So
now,
if
I
go
to
the
outlook
settings
in
my
tenant,
my
applications
at
a
head
from
file
I
can
upload
my
application.
C
Manifest
file
install
that
as
it
using
the
site
loading
during
the
preview
time
frame
and
then
then
means
that
I
can
actually
start
my
application,
which
is
actually
automatically
hosted
from
the
SharePoint
and
super
easy
super
convenient
way
of
implementing
add-ins,
oh
and
that
worked
really
well
and
then
I
did
a
mistake:
I'm
not
going
to
spend
too
much
time
on
investigating
and
we
are
in
a
preview
timeframe.
I
will
need
to
double
check.
What
did
I
actually
do
wrong
and
I
know
what
I
did
wrong
so
I
actually
use
the
wrong
manifest
file.
C
Let
me
actually
fix
that.
So
I
will
prove
you
that
the
things
are
working.
Probably
so,
let's
do
that
one
more
time
it's
not
going
to
take
too
long,
but
I
don't
have
too
much
time
on
my
built
anymore,
because
I
promise
to
do
stuff
in
15
minutes
there
we
go.
Let's
cloak
that
wasn't
necessary,
but
let's
get
the
application
manifest
one
more
time
in
and
uploading
from
a
file
and
I
uploaded
the
wrong
file.
That
was
the
problem.
C
It's
installed
that
there
we
go
and
let's
get
my
application
available
and
now
it's
getting
hosted
and
there
we
go.
Welcome
to
office,
extended
Norfolk,
Swiss,
custom,
business,
extensibility,
there's
the
context
I'm
accessing
the
email
address
where
I'm.
Actually
there
you
can
do
some
level
of
a
configuration
as
well
and
everything
will
be
available
for
you
again
super
convenient
automatic.
C
We
host
that
you
can
take
advantage
of
things
you
can
get
access
on
the
office
chairs,
so
the
the
JavaScript
SDK
from
the
implementation
really
easily
as
well,
but
I
think
that's
pretty
much
from
my
side
like
sides,
we
do
have
a
tutorial.
We
are
more
than
willing
to
get
your
feedback
on
this
one.
There's
multiple
people
into
office,
add-ins
engineering.
It
would
be
highly
interested
in
getting
your
feedback
on
this
one
as
well,
because
this
definitely
is
not
a
SharePoint
specific
thing.
C
This
is
an
Outlook
and
an
office
add-ins
engineering
investments
mainly
and
and
for
SharePoint
specific
stuff.
We
do
have
an
issue
list
in
the
SPD
Docs
issues
where
we
would
love
to
have
your
input
as
okay
tablet.
Comm
SharePoint
SP
develops
issues
where
we
would
love
to
have
your
feedback.
Your
input,
your
suggestions
related
on
things
which
you
might
be
finding
from
the
solution,
but
that's
it
from
my
side
for
now.
So
hopefully
you
find
that
interesting
and
it's
a
useful
thing
for
you
as
well.
Thank
you.
C
Oh
maybe
before
we
move
the
Kim
just
a
pinpoint
of
fact,
this
is
not
going
to
replace
and
the
sauce
level
implementations
of
add-ins.
This
is
definitely
in
an
add-on
tool
for
your
tool
belt
as
a
basically
designed
for
enterprise
developers
and
and
let's
say,
system
integrators
who
implement
Enterprise
extensibility
for
Outlook
and
an
office
as
well.
So
you
easy
getting
dengue
techs
deployed
your
stuff,
but
there's
obviously
still
will
be
applications
which
are
web
hosted.
C
Applications
like
let's
say
key
top
or
let's
say
Trello,
and
if
you
want
to
extend
any
of
those,
is
be
solutions
within
your
within
your
office
add-ins
or
in
your
Outlook.
The
model
still
remains
exactly
the
same
as
in
the
past,
but
I
think
that's
it.
For
now,
please
give
us
feedback
and
let's
jump
back
on
Kim's
screen
great.
A
C
A
Really
cool
to
see
the
init,
this
integration
with
the
SharePoint
framework
and
office
add-ins,
like
Lisa,
said
just
an
yet
another
way
that
you
can
build
office
add-ins
and
additions.
In
addition
to
the
ways
you've
already
been
able
to
build
them
previously,
also
really
cool
to
see
the
direction
that
things
are
with
the
M
365
developer
experience
in
this
greater
effort
on
our
part
to
make
developing
across
the
various
Microsoft
workloads,
a
seamless
experience
versus
feeling,
like
everything,
is
a
little
bit
different,
so
really
cool
to
see
where
things
are
headed
there.
A
All
right
so
I'm
going
to
talk
to
us
for
a
minute
about
the
process
of
creating
SSO
enabled
office
Adams.
So
until
now,
if
you
wanted
to
create
a
an
office
add-in
that
uses
single
sign-on,
it's
been
it's
been
possible,
but
it's
been
a
little
bit
of
a
journey.
There's
we
have
quicksort
tutorials
I'll
call
them
in
the
documentation
that
walk
you
through
all
the
various
steps
required
to
establish
the
necessary
configuration
settings
in
Azure
and
then
to
create
the
code,
that's
necessary
to
enable
SSO
within
an
office
add-in.
A
Well,
that's
been
possible,
it's
been
tedious
and
there's
a
lot
of
manual
steps.
They
have
to
be
done
there
so
I'm
happy
to
announce
today
that
very
soon
you'll
be
able
to
use
the
yeoman
generator
for
office
add-ins
to
create
SSO
enabled
office
add-ins.
So
this
isn't
available
quite
yet
we're
putting
the
finishing
touches
on
it.
Now,
as
we
speak,
should
be
available
very
soon.
Keep
an
eye
out
on
the
office.
Developer.
A
Blog
I
put
the
link
here
at
the
bottom
of
the
page
for
an
announcement
when
this
is
available,
but
essentially
the
next
version
of
the
yeoman
generator
that
we
published
that
we
release
will
give
you
the
ability
to
use
yeoman
generator
to
create
an
office
add-in
for
Word,
Excel
or
PowerPoint
that
uses
SSO.
So
what
does
that
mean?
A
It
means
the
yeoman
generator
is
going
to
automatically
take
care
of
for
you
all
of
the
manual
steps
you
used
to
have
to
perform
in
terms
of
you
know,
creating
the
application
as
you're
getting
the
client,
secret,
etc
and
then
plugging
that
into
the
code
within
the
office
at
in
project.
All
of
that
will
happen
for
you
seamlessly
automatically.
Just
as
part
of
creating
the
project
with
the
yeoman
generator,
so
it's
a
really
cool,
really
quick
way
to
get
up
and
running
with
single
sign-on
in
office.
Attends
and
I
will
point
out.
A
Here
too,
we
had
a
question
earlier
in
the
chat
window
about
the
status
of
SSO
as
a
feature
with
an
office
add-ins,
it's
still
in
preview.
As
we
speak
today,
I
don't
believe
we
would
get
announced
a
timeline
for
GA,
but
I'll
follow
up
with
the
PM
who
owns
SSO
offline
and
we'll
post.
If
we
have
any
information
to
share
about
potential
GA
timelines,
I'll
post,
that
to
the
blog
post
that
we
published
following
this
call,
to
recap
the
call
so
keep
an
eye
on
that
office:
developer
blog
for
that
as
well.
A
So
next,
just
an
invitation
to
engage
with
us,
we'd
really
love
to
hear
from
you.
I
know.
Last
year
on
the
call
several
times
several
different
calls
we
had.
Customers
presents
about
the
solutions
that
they're
building
on
the
office
add-ins
platform
and
share
some
really
useful
information.
It
was
really
beneficial
to
the
broader
audience
here
on
this
call.
A
So,
if
you're
building
something
on
the
office
at
his
platform
or
maybe
you've
built
something
previously-
and
you
you
know,
learn
some
lessons
along
the
way
or
you
think
it's
you
know-
maybe
a
really
cool
application
of
office,
add-ins
we'd
love
for
you
to
reach
out
to
us
and
chat
about
potentially
sharing
that
with
others
on
a
future
call.
You
can
do
that
via
this
form.
A
Here,
it's
aka,
MS,
Office,
Eddins,
engage
and,
if
you
reach
out
to
us
that
way,
we'll
be
in
touch
and
we'll
we'll
connect
and
see
if
we
can
get
you
scheduled
for
an
upcoming
call.
We're
also
really
interested
in
hearing
feedback
about
developer
experience
in
general,
but
specifically
the
documentation.
A
So
if
you
have
any
feedback
to
share
about
the
docs
you're
welcome
to
reach
out
through
this
us
this
way
as
well
we'd
love
to
connect
with
you
and
hear
how
we
can
improve
that
experience,
for
you,
I
think
we're
doing
pretty
good
on
the
QA
I'm
going
to
skip
past.
This
I
think
we've
addressed
a
lot
of
the
questions
in
the
chat
window,
but
just
a
quick
call
out.
A
If
there's
any
questions
that
we
weren't
able
to
answer
in
the
chat
window
today,
we
will
be
posting
a
list
of
those
questions
with
answers
to
the
blog
posts
that
we
published.
To
recap.
This
call
so
we'll
be
publishing
that
blog
post
sometime
in
the
next
few
days.
It
takes
us
a
little
bit
of
time,
sometimes
to
track
down
the
right
people
to
answer
the
questions,
but
keep
an
eye
out
on
the
office
developer
blog
for
the
blog
post
and
we'll
answer
your
question
there.
We
weren't
able
to
get
to
it
today.
A
So
just
some
developer
resources
here,
as
I
said,
we'll
be
sharing
this
deck
on
the
blog
post
as
well.
So
you'll
have
access
to
all
of
these
links
when
we
do
that,
publish
that
deck,
so
lots
of
resources
for
learning
about
the
office,
add-ins,
JavaScript,
API
and
platform,
as
well
as
resources
for
engaging
with
us.
So
earlier,
Raymond
presented
about
the
excel
JavaScript
API
and
mentioned
that
we'd
love
to
hear
your
feedback
about
the
beta
API
is
that
he
shared
with
us
today
in
requirements
at
1.11.
A
You
can
do
that
via
the
github
link
down
in
the
engage
section
of
this
slide,
so
it's
just
office
dev
/
office
Jas
in
github,
so
that's
it
we're
finishing
a
little
early
today.
Thank
you,
everyone
for
joining
us.
We
really
appreciate
your
time
today
we'll
be
publishing
this.
According
of
the
call
very
soon
to
the
office
developer,
YouTube
channel
and
as
previously
mentioned,
this
calls
the
second
Wednesday
of
every
month,
which
means
next
month's
call
will
be
on
Wednesday
February
12th.
A
If
you
have
questions
that
you
want
to
submit
ahead
of
time,
feel
free
to
do
so
via
the
second
AKMs
link
office.
Add-Ins
form
on
this
slide.
And
finally,
if
you
don't
already
have
the
recurring
series,
you
can
add
it
to
your
calendar
by
downloading
it
for
the
last
link
in
this
slide.
So
thanks
everyone
for
joining.
You
really
appreciate
it,
and
we
look
forward
to
seeing
you
on
next
month's
call.