►
From YouTube: AppSource Office add-in Validation Improvements
Description
In this 10-minute Developer-focused demo, Juan Balmori delivers the news - effective immediately, we (AppSource) no longer require IE (Trident) support. If your add-in fails to load in Trident, we’ll soft-fail it. Top failures when validating add-ins include: no testing instructions, poor first run and external service experiences, missing additional charges disclosures, and more. Now you can engage directly with the Add-ins Validation Team in response to a validation report from team. This PnP Community demo is taken from the Office Add-ins community call – May 2022, recorded on May 11, 2022.
Demo Presenter
• Juan Balmori - Principal Product Manager (Microsoft) | @juaneloBalmor
Supporting documents
• Documentation - App validation documentation | https://docs.microsoft.com/office/dev/store/
• Documentation - Microsoft AppSource submission FAQ | https://docs.microsoft.com/office/dev/store/appsource-submission-faq
• Article – Announcing WebView2 for Office Add-ins Platform – Preview | https://devblogs.microsoft.com/microsoft365dev/announcing-webview2-for-office-add-ins-platform/
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community
A
So
this
is
juan
valmoria
here
I
have
an
update
for
you
with
appsource
app
source
validation
just
to
set
up
some
context
here.
If
you
want
to
deploy
your
admin
using
appsource,
basically,
our
store,
there's
a
validation
process
that
is
going
on.
We
have
a
team
of
people
who
are
validating
that
add-ins
meet
certain
policies
and
we
have
been
making
some
improvements
here.
You
know
these
processes
around
taking.
A
I
don't
know,
depending
on
the
type
of
file
that
you
submit
between
three
and
two
weeks,
and
basically
we
work
to
try
to
validate
your
audience
as
soon
as
we
can
right.
So
in
order.
I
have
a
few
updates
here.
Just
take
a
couple
of
minutes
so
yeah
I
will
cover
three
topics.
Basically,
first
of
all,
the
most
important
update
is
that
we
have
a
browser,
support,
update.
A
So
in
a
nutshell,
we
will
no
longer
reject
add-ins
that
are
not
supporting
trident
or
basically
internet
explorer,
and
that's
huge
news
here
and
then
I'm
going
to
talk
a
little
bit
also
about
validation
failures.
You
know
what
are
our
top
issues
that
the
team
is
finding
so
that
when
you
submit
an
add-in,
you
kind
of
pay
special
attention
to
these
issues
so
that
you're
pure
adding
I
mean,
if
you
help
us
your
adding,
will
be
validated
way
faster.
A
A
That
didn't
mean
that
addings
were
not
supported
in
ie.
It
basically
meant
that
the
web
apps,
so
if
you
were,
if
you
went
to
office
for
the
web,
you
know
basically
word
will
not
be
supported
anymore
in
internet
explorer
right
and
many
people
assumed
that
that
was
the
same
for
office
islands
and
that's
not
the
case.
So
we
we
continue.
A
In
fact
today
we
continue
to
support
ie
in
guevara's
and
we
need
to
support
it.
Believe
me,
if
it
was
a
choice
of
my
team,
we
will
say
I
is
no
longer
supported.
Everything
is
in
webview
too,
but,
however,
that's
not
possible
because
we
have
office
2013
office,
2016,
2019,
msi
that
they
still
we
are
still
supporting
these
products
until,
as
you
can
see
on
this
slide
office,
2013
it's
going
to
be
supported
until
april.
11,
2023,
2016
and
2019
are
going
to
be
supported
until
2025..
A
So
basically
there's
still
an
universe
of
users
that
are
on
these
products
and
they
they
don't
have
other
browser
options
but
tried
it.
So
that's
why
we
were
still
requiring
it
now.
The
good
news
here
is
that
you
know
well,
if
you're
in
network
365
subscription,
if
you
have
a
subscription
for
365,
whether
that
subscription
is
a
monthly
subscription
or
a
semi-annual
subscription
or
a
mech
subscription.
A
Most
of
you
folks,
and
by
most
I
mean
more
than
95
percent,
are
now
running
in
webv2.
So
basically
we
were
monitoring
how
you
know
how
active
was
the
the
activations
going
on
in
webview
two
versus
all
the
other
engines,
and
we
finally
are
happy
to
announce
that
you
know
webv2
has
become
the
mainstream
in
the
office
adding
world.
So
a
very,
very
significant
percentage
of
office.
Add-Ins
are
activated
in
webview
2.
A
and
then,
as
a
result
of
this,
what
we
are
deciding
in
the
store
is
that
we
are
not.
Basically
now
we
are
recommending
you
to
support
trident.
We
are
not
enforcing
it.
So
basically,
if
you
submit,
are
not
into
the
store
and
it
fails
loading
in
trident,
we
are
not
going
to
reject
your
add-in,
but
we
are
going
to
basically
what
we
call
soft
fail-it,
which
means
it's
going
to
be
approved,
you're
going
to
be
in
the
store,
and
we
will
recommend
you.
A
You
know
to
support
trident,
because
you
know
your
adding
is
not
working
in
trident
and
maybe
you
will
have
a
customer
that
is
in
2016
or
2019
that
they
want
to
use
your
rating.
That
is
the
this
decision
is
made
effective
immediately.
So
if
any
add-ins,
you
saw
me
today
to
the
store
will
no
longer
be
rejected,
based
on
lack
of
support
for
trident.
A
A
A
So
that's
the
news
number
one.
By
the
way
we
already
updated
our
documentation.
If
you
go
to
our
website
and
ricky,
just
yesterday
changed
this
paragraph.
That
is
basically
summarizing.
What
I
just
said
here,
so
it's
now
public
policy
is
updated.
It's
all
done
so
moving
on.
I
just
want
to
talk
to
you
about
two
topics
here
number
one
top
failures
were
about
when
validating
addeds,
so
the
top
failure
up
to
recently
was
lack
of
lack
of
support
of
trident.
A
A
So
if
and
by
the
way,
this
is,
if
you
want
to
help
us
help
you,
this
is
basically
what
you
need
to
do.
Put
special
focus
on
number
one.
The
number
one
reason
of
failing
an
add-in
is
the
testing
notes
right.
So
basically
people
submit
add-ins
and
they
don't
include
how
we
can
test
them.
So
we
don't
have
a
test
account
that
we
can
log
into
the
add-in.
A
So
we
don't
know
we
don't
have
a
very
good
idea
of
how
to
try
your
ad
in
the
different
environments
right
and
if
we
don't
have
this
information,
evidently,
because
we
cannot
continue
the
validation
right.
So
please
be
as
detailed
as
as
you
can,
sharing
the
details
on
how
we
should
test
your
add-ins
give
us
the
accounts,
the
users
and
passwords
we
need,
you
know
to
test
it
or
how
can
we
create
a
test
account
for
it?
Simplify
our
lives
in
this
sense,
and
basically
you
should
be
fine.
A
There
is
a
very
large
volume
of
offers
that
have
this
issue
and
it's
basically
I
mean.
Maybe
your
rating
is
working
perfectly,
but
just
because
our
team
is
not
able
to
load
it,
but
we
need
to
reject
it
right,
and
I
have
seen
you
know
many
times
that
we
reject
many
times
an
alien
that
doesn't
have
clear
testing
notes
the
second
top
failure,
which
is
very
related
to
the
first
one,
is
the
first
run
experience,
so
many
admins
don't
have
a
clear.
A
This
is
a
bit
subjective.
I
would
I
would
admit,
but
you
know
many
times
we
we
don't
know
how
to
use
an
add-in.
I
mean
it's
like
the
ux,
the
experience.
There
are
no
enough
instructions
on
how
to
use
it.
There
are
some
add-ins
that
are
really
beautiful
and
the
design
is
kind
of
it's
very
intuitive
and
it's
kind
of
obvious
what
you
need
to
do,
and
there
are
other
cases
where
we
will
have.
We
don't
know
what
to
do.
A
First,
you
know
so
providing
a
good
instructions
on
the
first
run
experience
it's
going
to
help
a
lot,
your
validation
right.
If
you
are
using
an
external
service,
many
people
forget
to
other
way
to
sign
in
sign
out
of
that
service
or
to
sign
up.
You
know,
if
you
don't
have
an
account
on
that
service.
You
know
way
to
kind
of
start
an
account.
It's
not
exposed
you
know,
and
then
the
one
that
I
want
to
also
chat
more
here
is
the
additional
charges.
So
there
are
many
offers
in
the
store
that
require.
A
You
know
they
have
like
a
free
experience,
but
then
require
users
to
buy
a
subscription
to
a
service
or
stuff
like
that,
and
you
don't
disclose
that
you
know
in
your
in
your
submission.
So
every
time
you
submit
your
ad
into
appsource
and
you're
charging
at
some
point
for
additional
services.
You
need
to
tell
us.
I
mean
this
is
kind
of
a
legal
thing
we
need
to.
We
need
to
support
so
so
we
appreciate
that
you
you,
you
help
us
with
this.
A
If
you
hold
on
to
those
two
four
issues,
I
am
pretty
sure
that
your
ad
is
going
to
be
validated
in
less
than
one
or
two
days:
okay,
okay,
so
and
the
third
thing
that
I
thought
that
was
the
second
topic.
The
third
thing
that
I
want
to
talk
to
you
about
is
that
now
we
have
like
a
direct
engagement
with
the
validation
team
mechanism
in
place.
A
A
What
used
to
happen
is
that
we
were
creating
a
support
ticket
in
css,
so
we
so
we
were
involving
our
support
organization
here
and
evidently
that
came
with
a
little
bit
of
you
know
that
our
response
time
was
increased
significantly
just
by
involving
the
support
organization,
but
now
there's
a
way
that
you
can
actually
contact
us
directly
right.
So
the
way
this
works
is
that
every
time
that
we
send
you
an
email
after
your
certification
or
your
validation,
we
send
your
report
know
that
what
happened
why
we
rejected
your
add-in?