►
From YouTube: Office Add-ins community call – December 2022
Description
This month's community call topics include
• Marketplace leads for Office plugins are now becoming available in the Referrals Workspace (consent to access valuable leads and metrics) - Sudha Padmanabhan, Senior Product Manager (Microsoft)
• Add-in Auto Open for Word and Excel (requirements gathering for additional auto launch/open capabilities) - Yun Wang, Principal Product Manager (Microsoft)
• Top 5 AppSource Validation Errors hit by Office Add-ins' submissions (Tips to expedite marketplace certification) - Elizabeth Samuel, Senior Technical Writer (Microsoft)
• Q&A – formal and addressed as well in chat throughout the call.
The call was hosted by Preethika Kiruveedula (Microsoft). Recorded on December 14, 2022.
Agenda
• 00:41 - Marketplace leads for Office plugins are now becoming available in the Referrals Workspace - Sudha Padmanabhan, Senior Product Manager (Microsoft)
• 05:02 - Add-in Auto Open for Word and Excel - Yun Wang, Principal Product Manager (Microsoft)
• 17:44 - Top 5 AppSource Validation Errors hit by Office Add-ins' submissions - Elizabeth Samuel, Senior Technical Writer (Microsoft)
• 28:00 - Q&A – Preethika Kiruveedula, Product Manager (Microsoft)
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 – January 11th at 08:00am PT - https://aka.ms/officeaddinscommunitycall
A
A
Good
morning
or
good
evening,
everyone,
depending
on
your
time
zone,
welcome
to
the
December
office,
add-ins
Community
call.
We
have
three
things
on
our
agenda
today
that
we'll
be
going
over.
Firstly,
Marketplace
leads
for
office.
Plugins
are
now
becoming
available
in
the
referrals
workspace.
We
also
are
going
to
go
over,
add
an
auto
open
for
Word
and
Excel,
and
the
top
five
appsource
validation
errors.
A
B
Sure,
thanks
for
that,
quick,
intro,
kritika,
hey
everyone,
I'm
I
work
as
a
senior
product
manager
in
the
Microsoft
partner
center
team,
mainly
dealing
with
the
referrals
workspace
I
just
wanted
to
take
a
quick
poll
of
the
audience
here.
How
many
of
you
are
just
office
enrolled
in
the
office,
plugin
developer
program
versus
commercial
Marketplace
or
the
mCP
program?
B
You
might
have
seen
that
and
additionally,
we've
basically
tried
to
make
partner-center
reference
workspace
sort
of
like
your
CRM,
to
manage
all
your
leads
and
opportunities,
and
we
we
wanted
to
be
that
One-Stop
shop
right
that
one
place
that
you'd
go
to
where
you
know
where
also
investing
in
lead
enrichment
for
your
success.
So
in
August
we
actually
shipped
these
indicators
that
validate
whether
the
email
address
is.
B
Actually
you
know
whether
the
email
address
is
valid
in
that
that,
if
you
sent
out
like
an
email
nurture
campaign,
you
would
know
that
there,
the
email
address
would
be
would
be
delivered
in
the
Inbox
and
similarly,
you
know
the
validity
of
the
phone
number
as
well.
So
these
are
available
not
only
in
the
interface
but
also
as
filters.
So
you
can
prioritize
leads
if
you're
getting
a
lot
of
them.
I
do
know
a
lot
of
office.
Plugins
do
generate
a
large
volume
of
leads.
B
So
you
know
those
are
just
handy
tools
that
you
can
use
inside
of
partner
Center
reference
workspace,
we're
also
looking
at
investing
in
lead
enrichment.
If
you
can
see
here
we're
looking
at
sort
of
pulling
in
maybe
the
LinkedIn
profile,
their
location,
We've
added
a
lead
rating,
a
number
of
interactions
with
Microsoft
events
that
they've
attended.
These
signals
to
help
you
sort
of
have
better
conversations
with
with
your
leads
and
prioritize
them
as
well
and
so
and
product
usage.
B
This
is
another
one
that
we
think
will
be
valuable
where
you'll
know
how
engaged
they
are
with
certain
certain
of
the
Microsoft
products.
So
I
wanted
to
leave
everyone
here
with
with
sort
of
a
call
to
action,
so
we're
doing
this
back-end
linking
process
just
to
make
sure
that
you
know
we
have
a
legacy
sort
of
tech
stack
for
the
office
developer
program
and
so
we're
looking
to
sort
of
link
up
the
office
developer
account
with
your
partner
Center
account,
which
is
tied
up
with
your
MPN
or
MCPE
partner
ID.
B
So
this
consent
form
will
basically
help
us
do
that
and
then
you
can
access
the
referrals
workspace
and
and
see
your
leads
in
there.
So
go
ahead.
If
you
need
to,
you
know,
sign
up
for
that
and
then
we'll
Reach
Out
offline
and
help
you
through
that
process
of
getting
onboarded
into
partner
Center
reference
workspace
all
right,
great.
C
Recently
we
received
a
different
request
from
the
partners
that
they
would
like
to
have
the
auto,
open
or
Auto
installation
capabilities
for
the
add-ins.
We
already
have
different
functions,
enabled
to
help
our
customers
do
the
the
auto,
open
or
Auto
launch.
If
you
want
to
call
it
so
before
going
into
some
questions
or
some
you
know,
use
cases,
reviews
for
the
new
requirements,
I
would
like
to
do
a
recap
of
the
current
behavior
for
auto
opens
so
for
auto
open.
C
There
are
different
understandings
from
Partners
some
of
the
partners
they
would
like
to
have.
They
add
in
to
be
automatically
installed
and
opened
when
a
specific
document
has
been
opened.
So
when
you
open
up
a
Word
document,
then
you're
adding
but-
and
that
is
the
document
that
created
with
the
idea
and
so
that
they
want
to
have
the
add-in
to
be
able
automatically
and
some
of
the
partners
they
would
like
to
have
any
of
their
document
to
open
the
add-in
automatically
automatically.
C
So
first
one
is
that
you
could
automatically
open
the
task
pane
when
an
add-in
is
installed.
So
we
have
a
documentation
here,
I
put
here,
so
that
you
can
take
a
look
from
there.
You
could
config,
which
page
or
which
task
pin
you're
adding
you
want
to
Auto
open
during
the
after
the
installation,
and
another
way
is
that
you
could
embed
and
add
in
into
a
document.
C
So
you
could
do
some
XML
changes
to
insert
or
embed
and
add-in
into
a
specific,
the
Excel,
spreadsheet
or
Word
document
Etc,
so
that
whenever
this
document
gets
opened,
the
add-in
will
be
automatically
installed
and
opened
for
that
user.
The
the
problem
with
this
is
that
you
know
the
add-in
will
be.
We
persist
into
the
document
all
the
time.
So
unless
the
the
user
knows
how
to
change
the
underneath
XML,
the
normally
the
user,
cannot
change.
C
Turn
off
that
auto
open
feature
themselves
through
this
embedded
way,
and
we
also
have
a
auto
open
feature
for
a
specific
document
that
you
could.
The
add-in
can
control
whether
to
persist
the
add-in
to
be
able
to
automatically
opened
or
not
so.
In
this
way
we
could
control
we.
We
can
control
that
behavior
through
either
XML
settings
or
the
underneath,
adding
code
so
that
the
user
can
choose.
C
C
I
also
put
a
link
here,
but
before,
besides
these
options,
we
still
received
different
Auto,
open
requirements.
I
have
put
a
survey,
link
a
forms
link
here
and
I
hope
that
you
could
help
us
to
understand
your
scenarios
as
well
to
give
us
the
feedback
for
your
auto
open
requirements.
So
there
are
a
couple
of
requirements
that
we
are
gathering
now,
so
the
first
of
all
the
the
document
automation.
C
So
many
of
our
customers,
for
example.
They
would
like
to
do
the
data
classification
document
classification,
check-in
or
encryption
of
the
document
or
setting
the
labels
data
Integrity,
checkings
Etc,
so
so,
for
these
purposes
they
would
like
to
have
the
auto
add-in
to
be
automatically
launched
in
the
background,
so
that
whenever
a
user
tries
to
change
the
document
or
upload
the
document
or
even
share
the
document,
the
add-in
underneath
can
check
the
Integrity
of
the
data
or
check
the
the
whether
the
the
data
has
been
encrypted
or
not
Etc.
C
So
many
companies
require
this
capability,
and
also
this
is
not
for
just
the
one
specific
document.
This
is
actually
from,
for
example,
for
a
company-wide
that
they
would
like
to
have
all
the
word
document
or
the
Excel
document
to
automatically
launch
some
specific,
like
security
related
or
data
classification
related
add-ins
and
their
needs
to
to
check
all
the
documents,
and
also
we
have
another
use
case
that
people
want
to
to
say:
hey.
C
If
I
share
a
document
to
others,
you
know
I
want
to
I
want
others
to
open
that
add-in
automatically
with
the
document
as
well.
So
currently
you
you
can
partially
do
it
with
the
embedded
add-in
which
that
currently
our
customers
or
Partners,
if
they
have
a
system,
they
can
have
that
system
to
create
to
create
a
document
embedded
with
some
specific
add-ins.
However,
you
know
this
requirement
is
more
broad
that
they
don't
require
a
system
to
create
that
document.
This
is
to
say
anyone.
C
In
another
case,
the
third
one
is
the
ancient
scheme,
one
especially
in
edu
education
field
that,
for
example,
many
teachers.
They
reviewed
different
documentation
from
the
students
in
this
way
that
the
teachers
always
received
a
different
homeworks
different
papers
from
students,
so
that
they
would
like
to
have
every
document
to
how
to
launch
their
add-in
to
give
feedbacks.
C
So
this
is
very
important
for
them
because
they
don't
like
to
open
the
add-in
for
each
document,
one
by
one,
because
every
time
they
will
open
up
like
20
30
50
documents
at
the
same
time.
So
they
they
do.
They
don't
want
to
do
the
to
waste
the
clicks
or
to
open
the
add-ins.
So
the
proposal
here
is
that
they
just
would
like
the
office
to
remember
the
last
status
of
the
the
launching
add-in.
C
So
all
these
settings
could
be
set
by
the
advance
themselves.
So
many
of
the
the
the
settings
here
should
be
controlled
by
the
administrators
for
the
office.
So
again,
I
put
a
link
here
so
that,
hopefully
you
can
put
some
of
your
ideas
for
these
scenarios
and
give
your
feedbacks
as
well
as
I
said
at
the
beginning.
So
different
people
has
different
understandings
for
auto
launch,
so
many
partners
when
they
say
Auto
launch
they
actually
mean
that
auto
install
with
auto
open
of
netting.
So
we
also
have
different
Auto
install
requirements.
C
Leslie
here,
which
are
sort
of
interesting
and
I,
would
like
also
take
advantage
of
this
opportunity
to
have
your
opinions
in
the
survey
here
and
the
first
one
is
that
if
I
have
both
come
and
calm
and
GS
add-ins,
so
this
is
very
common
that
many
of
our
partners
started
their
migration
from
commentings
to
the
GS
add-ins,
but
they're.
Normally,
there
will
be
a
due
duration
of
time
that
people
it
takes
time
to
fully
migrate
from
com
to
GS.
So
in
this
way
people
want
to
say
hey.
C
If
on
my
windows,
client,
if
a
customer
has
the
commenting
installed,
could
you
please
also
do
the
auto
install
for
the
other
devices?
For
example,
if
a
user
now
opened
up
a
a
word
online
or
Excel
online,
or
they
just
open
up
a
new
Mac
word
Etc,
so
those
clients
will
open
the
the
same
add-in
from
the
same
brand
automatically.
C
C
So
so
this
will
also
help
some
of
our
clients
to
say
you
know
during
my
migration
process
from
com
to
GS.
I
would
like
to
take
advantage
of
this
way
to
replace
my
calm
add-in
with
the
gsetting
on
some
of
our
clients
system,
and
also
we
have
the
adding,
should
be
installed
and
launched
automatically
for
the
company's
standards
templates,
which
means
that
for
particular,
so
many
companies
or
Enterprises.
They
would
like
to
create
something
based
on
the
the
company
standards
templates.
So
they
would
like
to
say
if
a
user
choose
a
template.
C
That
is
created
by
the
company,
then
you
know
the
the
the
the
embedded
add-ins
should
be
automatically
installed
and
launched
for
the
user
within
in
the
company
and
also
in
the
share
a
share
mode.
When
a
user
tries
to
share
a
file
to
others,
sometimes
they
would
like
to
have
the
the
ideas
to
be
automatically
installed
and
opened
so
that
the
others
can
continue
working
basing
on
this
file.
A
D
Yes,
I
am
oh,
so
good
day,
good
night,
everyone
I
am
here
to
talk
about
the
top
five
appsource
validation
errors
that
office
addends
can
face
when
they're
submitted.
So
we
thought
that
this
would
be
really
helpful,
we're
doing
a
blog
post
on
this,
and
we
share
that
link
out,
probably
with
the
when
we
update
the
page
that
includes
the
information
about
this
community
call.
D
We
make
sure
that
the
blog
link
is
there
too
so
I,
don't
know
how
many
of
you
actually
submit
to
appsource,
and
so
we
hope
that
this
is
really
useful
information
to
the
community.
The
five
top
errors
are
usually
these.
Five
additional
charges
are
not
disclosed
to
users.
The
first
run
experiences
on
clear.
Sometimes
we've
seen
things
where
it
just
says
sign
it.
It
doesn't
say
what
the
add-in
does
anything
like
that
there
are
no
links
for
sign
in
sign
out
or
sign
up.
D
You
provider
name
doesn't
match
the
publisher
name
and
the
testing
instructions
are
missing
or
inadequate
for
the
reviewers
to
go
through.
So
let's
dig
into
them
a
little
more.
First
up
additional
charges
are
not
disclosed
some
things.
You
need
to
ask
yourself:
does
your
add-in
have
any
dependencies
on
additional
accounts
and
services,
and
particularly
do
they
require
purchase?
D
So
if
the
user
needs
to
pay
for
any
of
these
accounts,
any
of
these
Services,
the
add-ins
are
usually
free,
but
if
they're
connected
to
SAS
offers
or
anything
like
that
that
require
them
to
spend
money,
you
definitely
need
to
let
them
know.
Next
up.
We
have
that
the
first
one
experiences
on
clear
so
to
continue
from
the
first
point,
if
one
of
the
key
things
we
have
in
the
policies
is
that
the
adder
needs
to
have
a
clear
value
proposition,
why
should
I
get
this
added?
What's
really
so
awesome
about
it?
D
What
are
the
benefits?
So
you
want
to
make
sure
and
have
that
description
like
even
on
the
add-in
itself
in
the
start
screen,
so
that
they
have
installed
the
add-in,
and
maybe
it
was
a
while
ago.
Why
do
I
have
this
add-in?
What's
the
point,
and
you
want
to
make
sure
that
you
have
at
least
a
couple
lines
that
explain
this
is
what
the
add-in
is
for.
This
is
what
it
can
do
for
you
and
that
should
be
on
the
start
screen
of
the
add-in.
D
It's
the
first
round
experience
seamless
so,
first
time
they
come
in
they're
not
familiar
with
it,
make
sure
that
they
can
go
through
it's
seamless,
it
makes
sense
and
they
can
do
what
they're
trying
to
do
if
it
needs
to
have
sign
up
or
sign
in
there's
an
another
thing
error.
That's
related
to
that
too.
I'll
go
into
a
bit
more
about
that,
but
if
they
need
to
sign
up
for
some
with
some
account,
you
want
to
make
sure
that
that's
clear
to
them
in
the
UI
before
they
sign
up
for
something.
D
If,
however,
it's
targeting
Enterprise
like
larger
organizations,
then
you
don't
necessarily
need
to
explain
about
a
value
proposition,
because
your
assumption
is
that
the
company
installed
the
true
Central
centralized
deployment
or
something
like
that.
But
you
still
want
to
make
sure
that
there
is
information
on
there,
a
link
to
a
site
or
an
email
contact
so
that
the
users
in
that
Enterprise
can
contact
you
and
say:
hey
I,
want
to
know
more
about
this
or
send
them
to
a
link
so
that
they
can
read
for
themselves.
D
Next
up,
no
links
for
sign
and
sign
Auto
sign
up.
So
it's
like
hey,
there's
a
sign-in
screen.
It
doesn't
say
what
they're
signing
in
with
anything
like
that,
and
so
you
want
to
make
sure
that
that
information
is
very
clear
on
the
add-in
sign-in
screen.
If
they
need
to
sign
up,
you
want
to
make
sure
that
all
those
links
are
really
clear.
They
know
exactly
what
they
need
to
do
as
they
go
to
the
add-in
experience
is
then
Easy
Link
to
sign
out
once
they're
in
those
kind
of
things
again.
D
If
it's
targeting
Enterprises,
then
you
don't
need
to
have
it
if,
if
the
Enterprise
itself
controls
that,
in
that
you
know,
login
situation,
and
so
as
long
as
the
individual
user
doesn't
need
to
go
and
figure
out
what
accounts
I
need
and
those
kind
of
things-
and
this
is
maybe
something
that
uses
single
sign-on
with
the
Enterprise
work
account.
Then
it's
managed
by
the
Enterprise
and
you
don't
necessarily
need
to
have
all
of
this
information
on
the
island
itself.
Okay,
fourth,
one
is
the
provider
name
doesn't
match
the
publisher
name.
D
So
they
need
to
match
up
and
we
want
to
make
sure
that
when
the
person
goes
under
appsource
and
they
see,
this
is
the
publisher
that
when
they
actually
use
the
admin
and
look
at
the
add-in
metadata,
for
example,
that
they
are
in
sync-
and
that's
of
course,
confusion
and
last
up.
This
one
is
the
testing
instructions.
This
one
is
really
important
for
particularly
going
through
the
app
Source
validation
and
verification
process,
and
so
we
have.
D
The
certification
process
means
that
the
reviewers,
especially
depending
on
how
much
volume
they
have
they
really
don't,
have
the
time
to
come
back
to
each
person
and
say
hey.
We
need
this
piece
of
information
from
you
or
we
need
clarification
on
that.
So
we
need
the
test
account,
so
we
need
keys,
so
all
those
kind
of
information.
D
So
there
are
some
other
things
like
if
it
has
custom
functions
which
some
of
the
office
add-ins
can
support
in
Excel,
then
you
want
to
make
sure
that
at
least
one
of
the
custom
functions
you're
very
clear
about
how
the
tester,
what
if
the
certifier
needs
to
go
through
and
use
the
custom
function
so
that
they
can
try
all
the
others.
You
don't
necessarily
need
to
explain
how
all
of
them
work,
but
you
at
least
need
to
get
an
example.
So
they
have
an
idea
how
to
do
the
others.
D
We
really
suggest
that
if
you
have
super
complex
add-in
scenarios-
or
it
would
just
be
really
helpful-
to
have
screenshots
going
through
the
flows
so
that
the
reviewer
knows
what
to
expect.
So
there
is
an
option
that,
instead
of
using
the
notes
for
certification
box,
which
gets
refreshed
every
time
you
submit,
then
you
need
to
you.
Can
you
have
the
option
to
upload
a
PDF
version
of
it
and
that
actually
gets
kept
throughout
submissions?
D
And
so
you
don't
need
to
re-upload
it
every
time
which
has
really
helpful,
especially
if
you
end
up
having
to
resubmit
a
couple
times
and
the
testing
instructions
are
comprehensive
enough,
that
they
don't
need
to
come
back
to
you
and
go
back
and
forth
with
it.
So
Juan
is
on
here
as
well.
He
is
our
key
point
of
contact
working
on
the
validation
flow,
so
I
appreciate
them
going
through
and
looking
at
the
questions.
I'll
do
so
once
I'm
done
here.
So
those
are
the
top
five
things.
We
also
included
some
resources
here.
D
D
There
are
also
a
couple
of
document
pages
that
are
like
the
checklist,
the
submission
guide,
those
have
like
screenshots
and
steps
to
help
guide
you
through
the
process.
So
that's
basically
all
I
had
once
we
had
like
I
said
once
we
have
the
blog
published,
we
will
make
sure
that
we
have
that
information
posted
with
the
recording
of
this
online
so
that
you
have
that
information
when
that
goes
up
so
I
think
that's
it
for
me.
Thank
you
very
much
for
your
attention.
D
A
Great
thanks,
Elizabeth,
that
was
super
awesome.
We
now
have
a
few
q,
a
questions
that
were
submitted
pre,
the
community
call
that
we
will
be
going
over
starting
off.
The
first
question
was
when
using
SSO
the
samples
use
a
DOT
EnV
file
to
contain
the
secret.
Are
there
any
links
on
where
to
put
the
secret
when
you
release
to
production?
So
the
answer
is
we
recommend
you
use
something
like
Azure
key
Vault
for
securely,
storing
and
assessing
accessing
secrets
on
your
production,
app
service.
There's
a
link
here
that
you
can
follow.
A
A
So
there
was
an
Outlook
add-in
developed
with
event-based
integration
to
insert
the
signature
on
the
specific
event,
but
they
would
like
users
that
have
aliases
and
when
they
change
the
from
address,
they'd
be
like
to
re-trigger
their
add-in
script,
to
insert
their
signature
and
they're
just
wondering
if
there's
a
way
to
do
that,
so
there
actually
is
a
feature
that
will
be
delivered
in
the
near
future.
We
don't
have
an
exact
date
or
the
exact
road
map.
We
can
provide
you
yet,
but
we
will
update
you
on
that.
So
stay
tuned.
E
A
So
the
note
is
for
node.js
support
and
the
browser
is
for
clients
running
in
the
browser
similar
to
Spa.
There
are
a
few
documentations
that
we
shared
here
that
may
come
in
handy
to
help.
You
further
understand
the
difference,
so
the
top
outlines
all
the
complete
list
of
platforms
supported
by
msel,
so
feel
free
to
use
this
link,
and
then
this
GitHub
link
below
that
provides
a
lot
more
in-depth
information
for
M
cell
node.
A
A
F
Thank
you
thanks
yeah,
so
I
just
wanted
to
follow
up
on
a
question
that
was
asked
a
couple
months
ago,
someone
was
asking
for
us
to
add
some
a
Snippets
to
script
lab
for
PowerPoint
there's
some
preview
apis
that
were
demoed
back
in
I,
think
it
was
like
March
or
April.
So
somebody's
saying:
hey,
could
you
add
those
to
PowerPoint
so
I?
Just
let
folks
know
that's
there.
I
can
just
show
you
real,
quick
where
they're
at.
Let
me
just
share
the
screen
here.
F
So
if
you
open
up
PowerPoint
open
up
script
lab
go
to
the
samples,
there
is
a
shapes
section
so,
like
all
the
apis
for
getting
setting
and
loading
and
saving
shapes,
are
here,
and
you
can
run
those
you
can
create
shapes.
You
can
go
ahead
and
select
some.
You
can
change
the
colors
stuff
like
this.
So
anyway,
there's
all
those
samples
if
you
want
to
take
a
look
at
those
apis
by
the
way
these
apis
are
in
GA.
Now,
there's
also
some
slide
management
ones.
There's
these
get
set
load
and
save
slides.
F
F
A
Go
thanks.
David,
that's
awesome.
I
know
that
this
has
been
asked
for
a
while
all
right,
so
that
was
the
end
of
our
q,
a
section,
but
if
you
are
new
to
the
office,
add-ins
Community
here
are
a
few
resources
here
that
you
can
always
use
so
there's
our
documentation
link
a
few
quick
starts
script,
blob
our
samples,
repo,
the
M365
developer
program
and
a
link
to
The
Office
script,
documentation
that
you
can
follow
here.
A
If
you'd
like
to
engage
with
the
team,
we
have
a
few
places
that
you
can
go
to.
If
you
have
technical
questions
about
office
add-in,
specifically,
you
can
go
to
this
aka.ms
link
right
here
or
stack
Overflow.
If
you
have
product
bugs
feel
free
to
submit
an
issue
in
our
office.js
repo
and
for
any
feature,
requester
ideas,
we
have
an
M365
Dev
suggestions.
Page
it'd
always
be
great
to
hear
new
feature
ideas
from
you
all
and
feel
free
to
send
a
smile
or
frown
if
you
like
our
products
and
features
at
inside
office.
A
So
we
also
do
have
a
few
different
calls
that
you
could
attend
they're
all
listed
here.
This
PowerPoint
will
also
be
on
the
blog
post,
so
you
can
reference
them
at
any
time.
So,
if
you'd
also
like
to
attend
other
community
calls
about
different
things
across
Microsoft
feel
free
to
attend
these
as
well
and
all
right.
So
that
is
all
for
this
community
call.
This
is
the
last
one
of
this
calendar
year.
Thank
you
all
for
attending.
We
will
be
having
another
one
in
2023
on
January
11th
at
8,
A.M
Pacific
time.