►
From YouTube: Office Add-ins community call – January 2023
Description
This month's community call topics include: Deploy Office Add-in that uses SSO to Azure App Service (demo steps through recent article on topic) - David Chesnut (Microsoft) | @davidchesnut, Feedback for WXP (Word, Excel or PowerPoint) add-ins (request to complete add-ins user scenarios survey) - Yun Wang, Principal Product Manager (Microsoft), and Outlook add-in preview API - prependOnSendAsync (demo on preview release of Prepend onSend API) - Yashvardhan Joshi, Senior Product Manager (Microsoft). 4 topics formally addressed in this month’s Q&A, other topics addressed in chat throughout the call. The call was hosted by Preethika Kiruveedula (Microsoft). Recorded on January 11, 2023.
Agenda
00:00 – Intro
00:40 – Demo - Deploy Office Add-in that uses SSO to Azure App Service - David Chesnut (Microsoft) | @davidchesnut
17:35 – Feedback - Feedback for WXP (Word, Excel or PowerPoint) add-ins - Yun Wang, Principal Product Manager (Microsoft)
20:10 – Demo - Outlook add-in preview API - prependOnSendAsync - Yashvardhan Joshi, Senior Product Manager (Microsoft)
26:38 – Q&A – Preethika Kiruveedula, Product Manager (Microsoft)
29:38 – Resources
30:24 – Closing
Stay connected
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Twitter - https://twitter.com/microsoft365dev
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Link to all Microsoft Developer Community calls - https://aka.ms/M365DevCalls
• Submit questions for next community call - https://aka.ms/officeaddinsform
• Next community call – February 8th at 08:00am PT - https://aka.ms/officeaddinscommunitycall
A
A
We
have
a
demo
for
deploying
an
office
add-in
using
SSO
ask
for
feedback
for
wxp,
so
word
excel
and
PowerPoint,
and
a
presentation
on
prepend
Onsen
for
Outlook,
so
on
the
agenda
today
for
our
presenters
will
be
David,
Chestnut
who's,
a
senior
technical
writer
at
Microsoft,
Yoon,
Wang,
who's,
a
principal
product
manager
at
Microsoft
and
yashbar,
then
Joshi
who's
also
a
senior
product
manager
at
Microsoft
David.
If
you
wanted
to
take
over.
B
Thanks
preethica
hi
everyone,
my
name
is
David
Chestnut
I'm,
a
senior
technical
writer
on
the
office
platform
team.
Today,
I'm
going
to
do
a
demo
of
how
you
can
deploy
an
office
add-in
that
uses
SSO
to
Azure.
This
is
a
question.
That's
come
up
a
few
times
like
on
the
GitHub
issues,
I've
seen
folks
struggling
with
it,
and
so
last
month
in
December,
I
decided
to
write
an
article
to
tackle
this
subject
that,
hopefully,
is
going
to
help
people
so
I'm
just
going
to
do
a
demo.
B
B
So
this
is
gonna,
be
one
of
those
fun
demos
where
I'm
really
hoping
it
works
when
I
get
to
the
end
of
these
steps,
I'm
basically
going
to
walk
through
this
article
and
talk
about
what
you
need
to
do
and
just
to
be
clear.
The
focus
of
this
article
is
really
on
what
you
need
to
do
to
the
office
add-in
to
deploy
it.
B
It's
not
so
much
about
how
do
you
deploy
in
Azure,
because
there's
tons
of
resources
out
there
in
Azure
and
there's
tons
of
ways
to
deploy,
there's
continuous
integration
either
through
Azure
devops
or
GitHub
actions?
You
can
set
up
deployment
slots
for
staging
and
live
so
this
article
is
really
about
what's
just
a
simple
path
to
deploy
it.
So
you
can
understand,
like
what
parts
of
your
office
add
and
need
to
be
adjusted
if
you're
going
to
an
Azure
app
service.
B
And
the
first
thing
to
point
point
out
here
is
that
we
do
have
an
existing
article
on
how
to
deploy
a
static
HTML
to
a
storage
account
on
Azure.
This
works
or
I
believe
all
of
the
oauthis
templates.
It
doesn't
work
with
SSO
and
the
reason
for
that
is
because
SSO
requires
you
to
run
server-side
code.
So
for
that
you
have
to
use
an
Azure
app
service
and
that's
why
this
is
a
little
different.
B
So,
let's
go
in
through
this
now
as
a
prerequisite.
This
is
based
on
the
oauthis
template,
so
we'll
get
started
with
running
yo
office
and
we're
going
to
build
just
a
simple
little
SSO
add-in
and
the
thing
you
want
to
be
sure
at
first.
If
that's
working
on
localhost
before
you
deploy
it,
because
you
don't
want
to
deal
with
both
deployment
and
try
to
debug
stuff
at
the
same
time.
B
A
B
Half
of
this
article
is
about
how
you
modify
the
project
itself
and
some
of
these
changes
I'm
going
to
be
looking
at
putting
a
PR
to
the
template
itself,
because
I
think
we
can
simplify
some
of
this
and
then
hopefully,
that'll
remove
some
of
these
steps.
So
you
don't
have
to
do
quite
so
much
to
update
your
pack
your
project
and
deploy
it.
B
B
Do
you
want
to
run
npm
install
in
the
Azure
app
service?
Or
do
you
want
to
just
upload
the
node
modules,
folder
Trump
local
housed,
I'm,
not
sure
if
anyone
has
a
preference
on
that
I
do
know
that
if
you
go
and
set
up
continuous
integration
in
various
paths,
there
are
mechanisms
to
deal
with
that
in
this
article,
I
just
run
the
npm
install
on
the
server,
but
you
can
always
change
that.
So,
let's
open
up
our
project.
B
B
B
And
so
actually,
while
it's
doing
this,
we
can
jump
ahead.
You're
going
to
need
this
Azure
extension
installed
into
Visual
Studio
code,
and
then
you
can
connect
your
tenant.
I,
have
a
visual
studio,
msdn
subscription
and
I'm
going
to
connect,
and
then
you
have
app
Services
up
there
and
I
already
have
a
few,
because
I've
been
testing.
So
what
I'm
going
to
do
is
create
a
new
app
service,
and
these
are
the
steps
over
here.
By
the
way
you
can
do
other
steps.
B
Call
this
one
web
just
so
I
can
remember
this.
Is
the
web
server
part
of
it?
You
need
to
pick
a
resource.
You
can
create
a
new
one.
If
you
don't
have
one
I've
got
one
set
up
here:
I
right
now,
the
SSO
template
is
using
node
16,
so
I'm
going
to
node
18.
Just
yet
it
lags
behind
I,
don't
know
maybe
a
month
or
two,
and
then
you
know
it's
testing
down
into
updates.
B
So
I'm
going
to
pick
16
I'm
going
to
pick
Windows
as
my
OS
and
then
I'm
going
to
pick
my
region
I'm
on
the
west,
us
so
we'll
do
that
and
then
pick
one
of
your
service
plans.
I'm
gonna
go
ahead
and
use
this
paid
service
plan.
I
have
you
can
also
use
like
a
free
one?
If
you
want
or
you
can
create
one
here.
B
Paid
one
tends
to
be
a
little
more
performant
all
right,
so
it's
off
creating
the
web
app!
Let's
go
back
to
here.
Okay,
we've
got
our
project
configured,
so
the
next
step
is
to
start
configuring.
Our
project
I
believe
so
we're
going
to
want
to
update
the
Manifest.
So
if
you
open
up
your
manifest
and
take
a
look
like
this
is
right,
everything
in
here
is
going
to
be
localhost
and
we
need
to
change
that
to
our
actual
server
URL.
So
let's
go
get
that
LL
still
creating
it.
B
I'll
give
it
a
sec
just
to
finish
that,
but
the
easy
way
to
update
that
you
can
set
up
a
deployment
option
and
the
webpack
config
that
comes
with
this
template.
It
will
look
for
localhost
and
replace
it
for
you,
but
you
do
need
to
change
it
a
little
bit
it
just
once
you
just
want
the
domain
I'll
go
put.
The
website
URL
here
should
be
done
by
now.
Yep
there
it
is
so
I'm
going
to
open
it
right,
click
on
it
and
open
it
in
the
portal.
B
B
B
Okay,
so
let's
make
sure
we
did
this
handing
so
that
should
take
care
of
our
manifest.
Then
we
also
need
to
take
care
of
our
package.
Json
there's
a
couple
of
changes.
We
need
to
make.
There's
some
helper
commands
I
put
in
here
that
you
can
run
the
command
line
to
update
the
start,
and
you
also
want
to
delete
this
pre-start
script,
because
it'll
be
deploy
to
Azure
will
run
that
pre-start
and
it's
well.
Actually,
let
me
show
you
why
I
should
point
this
out.
B
If
you
go
to
the
package
Json,
this
start
is
trying
to
run
this
office
add-in
debugging
package
and
that's
basically
attempts
to
launch
Excel
which
isn't
going
to
work
with
your
server.
So
instead
this
has
to
become
node
middle
tier.js,
so
we
can
just
start
the
node
server
and
then
the
other
thing
is
you
want
to
get
rid
of
this
pre-start,
because
it'll
try
to
run
a
build
and
we're
going
to
have
the
build
already
done,
so
we
don't
need
to
run
a
build.
So
we
take
that
out.
B
That's
what
those
two
commands
do
and
then,
let's
make
sure
we
save
these
changes,
we
need
one
more
update
to
webpack,
which
is
we
want
to
make
sure
we
copy
our
package
Json
over
to
our
distribution,
so
that
when
we
deploy
it'll
run
the
npm
install
on
the
server
side.
So
I'm
going
to
put
that
in
down
here
near
the
bottom.
B
B
B
It
will
want
to
use
this
office
ad
in
Dev
search
to
create
an
SSL
self-science
certificate,
but
you
don't
want
to
do
that
on
the
server
side
here
or
on
Azure
you'll
have
one
already,
and
this
will
fail
if
it
tries
to
run
because
it
tries
to
look
for
a
Windows
I
forget
what
it's
called.
It's
like
a
Windows
storage
for
certificates
or
something
so
to
make
it
easy,
I
just
copy
paste
and
replace
it.
B
B
B
Now,
while
that's
going
to
open
up
another
portal
to
Azure
now
this
is
the
tenant
that's
going
to
consume
and
it
has
my
app
registration
at
the
moment
because
I
need
to
update
this
as
well.
So
if
I
go
to
my
app
registrations
and
sort
by
date,
because
I
have
way
too
many
of
these
there's
my
contoso
SSO
tests.
This
is
the
one
that
the
npm
configure
command
ran
and
it
created
this
for
me.
But
if
you
look
at
like
you
redirect
your
eyes,
you'll
see
these
still
say
localhost
3000.
B
So
these
need
to
be
updated
as
well.
You
might
want
to
create
multiple
app
registrations
like
when
you're
testing
locally.
You
might
want
this
one
and
you
could
create
a
copy
of
this
and
then
have
another
one:
that's
using
your
server
or
a
staging
server
or
whatever
for
Simplicity
I'm
just
going
to
edit
this
one.
B
Copy
that
now
this
builds
done.
So
let's
get
this
going
because
this
might
take
a
moment
so
I'm
going
to
right
click.
My
dist
folder,
because
I
want
to
deploy
it
I'm
going
to
say,
deploy
to
web
map
I'm
going
to
pick
the
one
that
we
just
created,
ketoso,
test,
SSO
web,
say:
yep,
go
ahead
and
deploy
it
because
it's
I
can
overwrite.
What's
up
there
and
I'm
going
to
say
yeah
we
can
default
to
that
in
the
future.
So,
if
I
keep
deploying
if
I
make
updates
to
this
folder
I
can
keep
uploading
it.
B
So
here
we
can
see
it's
doing
its
deployment,
so
it's
packaging
everything
up
and
setting
up
the
server
and
then
it'll
start
node
for
us.
Whilst
doing
that,
it's
going
to
go
back
to
the
app
registration
it's
over
here,
so
we
can
make
sure
we
update
this,
save
it,
and
you
don't
need
to
update
this
task
paid
what
I'm
not
sure
why
the
template
creates.
It
I
think
it's
that
used
to
be
the
name
or
something
so
I
mean
change
it.
B
B
I'm
gonna
go
ahead
and
just
side
load
this,
so
I'm
going
to
go
just
upload
the
Manifest
from
just
from
locally-
and
let's
see
here,
let's
go
to
the
demo.
Folder
I
need
SSO
test
I'm
not
going
to
use
this
manifest.
That's
the
localhost
one
in
the
dist
folder
is
the
one
that
got
built.
That's
switched
out
with
the
correct
domains,
so
I'm
going
to
open
that
one
upload.
It
show
taskbase
SSO
test,
yep,
okay,
see
if
it
works.
B
B
So
next
steps
I
will
update
the
article
so
that
for
sure
it
works
correctly.
I'll
figure
out
why
this
is
failing
in
some
cases
and
hopefully
get
that
polish
by
the
end
of
this
week
and
then
after
that,
I'll
be
following
up
with
the
folks
on
the
template
to
submit
a
PR
and
see
if
we
can
makes
fewer
steps
for
deployment.
C
D
Yeah
all
right
so
hello,
everyone,
my
name,
is
Wang
yin
and
I
am
the
product
manager
for
the
office,
especially
word
and
pop
round.
Today,
I
will
get
more
feedback
from
you
through
several
surveys
we
have
so
we
we
already
posted
two
surveys
previously
in
previous
Community
called
P
calls.
So
your
inputs
are
very
valuable
for
us
to
determine
the
future
investment
as
well
as
to
do
better
job
on
prioritize
our
work.
D
So
we
do
expect
that
we
we
can
get
more
feedbacks
from
you
on
these
topics.
So
first
one
is
the
auto,
install
and
launch
add-ins
for
word
excel
and
PowerPoint.
So
in
this
way
we
are
asking
questions
about
this
scenario.
User
scenarios
as
well
as
you
know
how?
How
do
you
think
about
the
auto,
open
and
auto
launch
capability?
It
is
that
can
benefit
your
aliens
for
wxp
and
also
earlier
last
year.
We
also
had
a
survey
for
structured
document,
content
usage,
import
settings.
It
actually
talked
about.
D
How
do
you
want
to
leverage
content,
controls
and
Fields
to
accomplish
your
add-in
work
for
structured
document
and
actually
the
previous
survey
results?
Helped
us
a
lot
to
invest
in
the
content,
control
and
refuse
related
features,
and
some
of
those
will
will
come
up
pretty
soon
as
preview
in
the
first
half
of
this
year
and
when
we
continue
looking
forward
to
more
feedbacks
from
you,
so
that
we
can
continue
investing
in
these
areas,
and
today
we
have
a
new
survey.
D
We
want
to
learn
about
your
scenarios,
your
use
cases
about
word
excel
PowerPoint
and
that
will
also
benefit
our
future
investment
strategy
shaping
Etc.
So
please
go
into
this
link
or
just
scan
the
QR
code
on
the
page
so
that
you
can
get
more
details
for
the
survey
content.
So
that's
all
for
my
content
today,
thanks.
E
Look
as
a
product
manager
in
the
Outlook
extensibility
team
and
we
recently
have
been
trying
to
roll
out
a
new
JS
API.
Let
me
talk
about
the
future
prependers
and
late.
Last
year
we
launched
a
set
of
apis
called
abandon,
send
and
essentially
what
they
let
you
do
on
Outlook,
who
is
ADD
content
to
the
end
of
the
email
or
event.
E
E
E
This
is
what
the
API
looks
like
you
can
find
it
at
office,
contextmailbox,
dot,
item
dot,
body
prepend
on
send
async.
If
you
want
to
use
HTML,
then
the
quotient
type
can
be
context,
question
type,
dot,
HTML
or,
as
the
example
shows
below.
If
you
want
to
use
plain
text,
then
the
question
type
can
be
text.
E
E
This
is
a
tough
call,
but
essentially
what
we
are
going
to
do
is
the
extended
permissions
that
were
used
for
append
on
send
will
also
turn
up
for
prepend
on
sign.
So
in
the
extent
extended
permissions
section,
you'd
have
to
mention
append
on
sending
or
manifest,
and
that
should
get
a
banned
on,
send
and
depend
on
send
working
for
both
the
Manifest
changes.
E
Maybe
I'll
show
you
how
quickly
looks
like
this
is
how
the
end
product
would
look
like.
I
could
run
a
demo
video
for
you,
so
here's
the
Manifest
and
as
I
had
earlier
mentioned,
I'm
not
sure
if
it's
visible
or
not,
but
the
extended
permissions
section
now
has
a
bend
on
send
and
that's
enough
for
the
dependence
and
to
work
as
well.
E
Okay.
So
here
what
we're
essentially
trying
to
do
is
on
the
console.
We
will
paste
the
messages,
the
the
code
that
I
had
actually
shown
in
an
earlier
site.
This
is
for
HTML
and
what
happens
here
is
yeah,
as
it
shows
its
clearly
mentioned.
Question
type
is
HTML,
and
once
we
run
this,
the
console
says
the
text
has
been
prepended
and
now
when
we
send
the
email,
you
should
be
able
to
see
the
appended
text.
E
A
A
And
our
answer
to
this
is
we
currently
do
not
have
an
exact
roadmap
for
this
feature,
but
it'd
be
great
to
get
a
few
more
details
on
your
add-in
and
your
exact
Necessities
for
it
for
compose,
so
we
could
learn
more
about
it.
So
here's
this
link
right
here
feel
free
to
follow
that
and
submit
another
feature
request
and
then
our
second
question
was
a
two-part
question.
A
First,
we
would
like
to
enter
Outlook
adding
into
app
Source,
but
it
is
blocked
because
it
is
an
onsend
add-in
when
will
appsource
accept
onsend
add-ins
and
then
the
second
part
of
the
question
is:
what
is
a
roadmap
regarding
sent,
adding
Onsen
functionality
to
phones,
both
iPhone
and
Android?
The
answer
to
this
question
is
this
is
unfortunately,
still
not
allowed
we've
recently
shipped
smart
alerts
is
the
relatively
same
functionality
and
is
allowed
in
the
store,
so
that
might
be
a
good
alternative
to
look
into
this
link
to
the
documentation.
A
Third
question:
what
is
the
timeline
for
upcoming
features
in
PowerPoint?
There's
a
lot
in
Excel
that
can't
be
done
in
word
or
PowerPoint.
The
developer
feedback
and
ideas
Forum
doesn't
get
much
attention.
Could
there
be
more
effort
in
this
review?
This
is
good
feedback
to
receive
we'll
answer
this
more
thoroughly
in
the
blog
post,
but
it'll
be
definitely
something
to
consider
moving
forward
for
PowerPoint
and
word.
A
Lastly,
is
there
a
timeline
for
one
Outlook
mobile
on
IOS
and
Android?
Will
support
compose
mode
for
office
add-ins
and
further,
when
the
onsend
event
will
be
supported?
Currently,
only
read
mode
is
supported
for
Outlook
add-ins,
and
this
has
been
a
state
for
many
years,
but
our
add-on
is
essentially
for
compliance
measures
to
ensure
all
sent
messages
include
some
extra
input,
slash
metadata
from
the
sender.
A
This
is
similar
to
the
first
question,
and
our
answer
to
this
is
we've
been
getting
questions
on
onset
report
for
mobile
quite
frequently
now,
and
this
feature
will
be
looked
into
once
we're
able
to
finish
delivering
on
other
features
that
onset
would
build
upon
so
stay
tuned
for
more
information
about
this,
and,
lastly,
is
there
an
APR
access
point
where
we
can
call
how
many
seats
have
been
provisioned
for
an
office
add-in
by
the
365
administrator?
For
example,
their
company
has
25
seats,
but
only
authorizes
five
for
their
add-in.
A
Is
there
a
way
for
the
added
developer
to
know
that
please
note
that
we
do
not
have
an
sas
application,
just
an
office
store
admin.
This
will
also
be
answered
in
the
blog
post.
Stay
tuned
for
that
as
well,
and
if
you
are
new
to
office
add-ins
here
are
a
few
links
to
get
started
in
terms
of
our
documentation.
A
few
quick
starts
script
lab
where
samples
repo
lives,
the
M365
developer
program
and
a
link
to
the
office
scripts
documentation
to
further
engage
with
our
team.
There's
a
few
links
here
so
for
technical
questions.
A
We
have
the
office
add-ins
Dev
questions,
and
then
we
also
have
stack
Overflow
and
we
monitor
both
of
those
and
if
you
find
a
bug
in
one
of
our
features
feel
free
to
put
in
an
issue
on
our
GitHub
repo
under
office.office.js
and
for
any
feature,
requests
and
ideas
feel
free
to
go
to
our
M365
Dev
suggestions.
Page.
You
can
also
always
send
us
a
smile
or
a
frown
at
inside
office,
and
we
have
a
few
other
developer.
A
Community
calls
that
you
can
also
take
a
part
of
so
if
any
of
these
look
interesting
to
you
feel
free
to
also
join
these,
they
will
be
at
a
different
time
than
the
office
items.
Community
call
so
you
can
always
look
into
these
as
well,
and
that
being
said,
thank
you
for
joining
today.
The
recording
will
be
available
in
about
24
hours
on
our
YouTube
channel.
You
can
follow
us
on
Twitter
at
Microsoft,
365
Dev,
and
our
next
call
will
be
February
8th
at
8am.
Pacific
Time
there'll
also
be
a
blog
post.