►
From YouTube: Publish your app in the Microsoft Teams App Store
Description
#MicrosoftTeams #AppDevelopment #Microsoft365
The Microsoft Teams App Store gives you access to millions of Microsoft Teams customers around the world! Your apps can be monetized through the Microsoft Commercial Marketplace (https://aka.ms/monetize-your-app) to generate revenue.
While there are a lot of videos showing how to build a Teams app (like this one: https://aka.ms/Get-Started-Teams-Apps), there aren’t many about publishing an app in the Teams app store. In this video, Cloud Solutions Architect Natalia Kats walks you through every step of app publication.
You'll learn about the Partner Center signup and app submission process as well as how buyers will see your application in the Teams Store and in Microsoft App Source. Natalia also shares advice on how design your app so it can pass validation and how to make the validation process faster and easier.
00:00 Introduction
1:15 Steps to publish an app in the Teams store
5:04 Store validation guidelines
12:55 Check validation in the Teams Developer Portal
14:26 Create a Partner Center account
17:29 Submit your application
24:48 App compliance programs
27:36 Review and publish your application
28:40 Validation process
32:10 Update your app after publication
A
Hello:
everyone,
my
name
is
natalia
katz
and
I'm
cloud
solution
architect
for
microsoft.
I
work
with
the
partners
to
help
them
to
build
applications
for
the
teams,
and
today
I
want
to
tell
you
how
to
prepare
and
publish
your
application
to
the
team
store.
So,
let's
start
from
the
beginning
here
you
see
the
steps
which
will
help
you
to
build
your
application.
So
the
first
step
is
planning
your
app
here.
You
identify
the
user
scenarios.
A
You
select,
which
components
you
will
use
for
your
application,
for
example,
vote
tab
messaging
extension,
media
extension,
how
you
will
use
adaptive
cards
after
that?
You
start
to
design
your
application
using
our
guidelines.
After
that,
you
start,
you
start
to
code
and
you
may
use
the
microsoft
graph
if
you
want
to
work
with
microsoft,
365
data
from
your
application
and
when
your
application
is
ready,
you
may
consider
what
to
do
next,
so
it
can
be
two
options.
So
the
first
you
can
install
application
to
the
organizational
catalog.
A
For
example,
it
can
be
your
organization,
a
catalog.
If
your
organization
want
to
use
this
application-
or
it
can
be
customer
organization
catalog,
so
you
create
the
application
for
specific
customer
and
after
that,
when
application
is
ready,
you
just
send
at
manifest
to
him
and
another
option.
It's
public
key
application
to
the
team
store.
So
with
the
publishing
application
to
this
team
store,
you
make
it
discoverable
for
all
users
of
microsoft
teams
across
the
globe.
So
that's
a
great
opportunity
for
you
to
engage
new
new
customers
to
make
them
familiar
with
your
applications.
A
And
now
we
have
monetization
in
team
store
and
to
have
money
to
make
money
as
well.
So
today,
we'll
focus
on
this
part
in
publishing
your
application.
Here
in
this
article,
you
see
that
for
each
step
you
have
the
links
get
started
so
where
you
can
read
a
lot
of
documentation
regarding
each
step
and
let's
go
to
the
publish
your
application
on
this
page,
you
see
steps
which
are
required
to
submit
the
application
to
the
store,
and
I
will
describe
in
more
details
about
each
of
them.
A
A
That's
the
first
place
in
teams,
client
and
the
second
place
where
the
app
will
appear
after
publication.
That's
the
apps
source,
it's
our
commercial
marketplace
where
all
applications
for
m365
power
platform,
dynamic
and
our
commercial
offers
will
appear.
For
example,
I
will
show
you
application
from
one
of
our
partner
gigbot,
there's
application
for
teams,
as
you
can
see,
and
the
same
the
same
app
description
and
screenshots
from
here.
You
can
see
that
gigbot
application
will
help
developers
with
the
standups
meeting
and
to
work
with
the
geographically
distributed
teams.
A
So,
let's
go
back
to
the
recommendation
and
let's
go
step
by
step
with
the
all
of
the
process,
so
the
first
review
the
store
guidelines,
in
my
point
of
view,
the
most
important
part
of
building
application.
You
need
to
review
the
store
guidelines,
not
when
your
app
is
ready
and
you
you
want
to
submit
it
for
the
publication,
but
in
the
beginning,
because
our
store
guidelines
fully
impact
on
app
functionality
and
if
your
app
doesn't
fit
them.
A
Your
application
may
not
pass
the
validation,
and
I
really
recommend
you
to
start
building
your
process
from
reviewing
these
store
guidelines,
because
if
you
start
to
build
the
application
within
these
rules,
it
will
help
you
to
don't
change
your
code.
Don't
change
a
lot
in
user
experience
of
your
application
during
the
up
validation
process.
So
let's
see
what
it's
this
guideline
about
and
here
that's
a
part,
distribute
your
application
and
publish
to
the
team
store.
A
So
that's
the
main
articles
which
will
help
you
to
do
the
publication
will
which
will
help
you
to
prepare
your
application
in
the
best
way.
If
we
go
we'll
be
back
to
the
overview
page,
you
will
see
absolutely
the
same
process.
Publication
process
can
contains
of
several
steps
so
the
first
it's
review,
the
team
store
guidelines.
The
second,
you
need
to
prepare
your
partner
account
if
you
don't
have
it
third
step.
A
Let's
prepare
your
store,
submission
after
the
submission
process
and
resolve
issues
during
the
validation
process,
and
after
that,
when
application
is
published,
you
know
you
can
update
this.
We
will
also
cover
this
topic,
so
let's
go
back
to
the
store,
validation
guidelines
and
what
is
what
it's
about
so
you
see
that
it's
very
big
article.
So
let's
go
through
these
rules
and
I
will
try
to
focus
on
the
rules
which
are
very
popular
based
on
my
experience,
and
you
will
see
how
this
article
can
help
you.
A
So,
first
of
all,
there
are
two
type
of
rules.
It's
mandatory
fix
and
suggested
fix,
so
the
first
mandatory
fixed
means,
but
you
need
to
fix
issue
if
your
application
doesn't
follow
these
rules,
this
mandatory
rule,
in
this
case
the
affiliation
process,
will
be
blocked
and
the
second
one
is
suggested
fix.
It
mean
that
the
rules
recommended
for
for
better
user
experience,
but
it's
not
mandatory,
so
it
will
not
block
you
from
publication
in
team
store.
A
So,
let's
see
which
rules
are
for
different
parts
of
your
application,
so
the
first
it's
we
can
start
from
up
name.
For
example,
app
name
shouldn't
contain
specific
words.
It
shouldn't
contain
the
names
of
our
products,
and
so
here
you
can
see
that,
of
course,
we
will
not
read
all
of
these,
so
the
next,
for
example,
general
functionality
and
performance.
A
So,
first
of
all
your
application,
you
could
go
to
this
section
compatibility,
it
should
work
on
different
devices.
It
means
that
your
application
should
works
on
the
desktop
client
on
the
web,
client
and
in
teams,
mobile
client
and
especially
it's
relevant
for
taps.
So
if
your
tab,
it's
not
adopted
or
it's
not
supported
on
the
mobile
version
of
teams,
client
can
be
blocker
for
the
app
validation.
The
next
important
part
is
launching
external
functionality.
That's
one
of
the
main
issues
during
the
validation
process.
A
It's
when
application
forwards,
user
to
external
site,
for
example
your
bots
and
message,
and
here's
only
one
button.
You
see
detailed
information
and
after
user
clicks
button,
he
will
be
forwarded
to
the
external
site
and
see
detailed
information
about
any
items.
One
of
the
core
scenario
of
the
application
and
after
clicking
the
button
it
will
forward
user
to
external
resource
and
all
main
activity
will
will
happen
outside
of
the
teams
it
won't.
It
won't
be
good,
so
it
won't
be
good
for
the
user
interface
and
it
will.
A
It
can
be
blocker
for
the
a
validation.
So
you
see
that's
a
mandatory
fix
as
well
and,
of
course,
if
some
configuration
of
your
app
should
be
done
externally
initial
configuration
it
shouldn't,
be
blocker,
but
it
for
main
scenario.
You
forward
users
outside
it's
better
to
use,
for
example,
a
task
module
and
show
the
external
page
in
pop-up
window.
A
How
app
description
should
be,
and
here
you
see
advices
what
do
what
doesn't
do?
Screenshots
for
your
applications,
because
I
see
application
will
be
added
for
the
public
marketplace.
Of
course,
there
should
be
screenshots.
This
will
will
show
the
main
functionality
of
the
application
if
you
want
to
build
transactable
offer,
so
you
want
to
monetize
your
application
to
the
team
store.
A
There
also
requirements
for
this
kind
of
applications
and
let's
go
a
little
bit
through
the
app
components,
for
example
tabs,
so
for
each
when,
when
you
open
each
section
tabs
both
here,
you
see
the
information
with
the
green
color
with
the
link
to
design
guidelines.
If
I
click
on
this,
you
can
see
our
recommendation
how
to
build
application,
how
the
user
interface
should
looks
like
so
before.
Building
up,
please
review
this
as
well,
and
we
have
a
toolkit
for
designers
to
make
the
application
more
within
teams
user
experience.
A
Just
imagine
that
your
application
is
published
to
the
team
store
a
lot
of
users,
some
millions
of
teams.
Users
will
be
able
to
find
it,
and
they
may
not
be
aware
about
your
application
and
how
to
register
in
the
application
how
to
become
a
customer.
So
for
these
users
you
need
to
provide
guideline,
or
maybe
it
will
be
linked
to
create
a
new
account
or
maybe,
if
they
need
to
call
you.
Maybe
the
registration
process
is
more
complicated.
It
should
be
clear
from
the
first
run
user
experience.
A
So
that's
why
I
really
recommend
you
to
think
about
app
experience
for
users
who
are
not
aware
about
the
application,
take
a
time
and
think.
Okay.
Today
I
will
be
the
user.
Who
is
not
aware
about
what
this
app
is
about.
I
will
check
if
I
can
go
through
all
process,
if
I
can,
if
it's
clear
for
me
how
to
register
in
the
application
how
to
configure
it,
how
to
use
it
at
the
first
run.
Experience
it's
highly
important,
so
the
next
part
is
navigation
in
your
top.
Navigation
should
not
be
like.
A
We
have
in
teams
client,
as
you
can
see,
on
the
screenshots.
What
is
what
is
allowed?
What
is
not
allowed,
so
please
review
this,
because
this
screenshot
really
helps
a
lot
so
a
little
bit
about
the
usability.
So
what
is
happening
really
very
often
that
partners
can
just
embed
the
total
website
in
teams
and,
of
course
it
will
be
header,
footer,
complicated
menu,
navigation
and
so
on.
A
In
this
case,
we
recommend
to
show
only
focused
content
to
remove
header
footer,
to
don't
embed
the
full
site
experience
or
if
you
have
your
own
sauce
and
there's
a
lot
of
navigation
to
don't
embed
the
full
experience
it
should
be.
Some
parts
of
the
interface
should
be
removed.
Here
you
can
see
from
usability
a
part
of
the
documentation.
A
You
can
see
that
there's
a
welcome
message
and
the
screenshot
without
a
welcome
message
and
user
won't
be
aware
of
what
we'll
do
what
is
also
important
for
bots.
It's
what's
massive
spamming.
So
please
avoid
both
to
send
a
lot
of
notifications
to
the
users
and
if
what
do
it
were
frequently,
maybe
it's
better
to
send
notification
one
digest
per
day
or
per
week.
So
please
consider
this,
because
if
your
bot
will
spam
user,
of
course
it
will
be
the
blocker
for
the
validation
as
well.
A
So
the
other
parts
you
see
the
messaging
extension
so
for
each
component
there
are
specific
rules,
so
it
depends
on
what
is
in
your
application.
You
can
read
this
part
if
your
application
makes
microsoft
rough
calls,
you
need
to
mark
it
as
a
publisher
verified
here.
There's
instruction
how
to
do
this,
and
after
that,
on
the
app
content
screen,
it
will
be
blue
sign
that
publisher
is
verified
to
make
publishing
verification.
A
You
need
to
go
to
the
app
registration
and
add
this
information
to
their
specific
section,
publisher,
verification-
and
here
you
need
to
add
your
mpan
id
everything
will
be
described
in
this
article.
Please
don't
forget
about
this
if
you
make
calls
to
with
microsoft
graph,
so
the
second
step
is
published
attestation.
I
will
take
about
this
little
bit
later
after
your
review.
All
of
these
validation
guidelines
and
you
check
that
your
application
follow
our
guidelines.
A
You
can
go
to
the
next
step
and,
of
course,
as
you
can
see
a
lot
of
these
guidelines,
only
you
can
check
them
because
it's
fully
related
to
your
application
functionality,
but
some
of
these
rules,
you
can
check
with
our
tools.
Let
me
show
you.
I
hope
that
you're
familiar
with
the
developer
portal,
which
will
help
you
to
create
the
app
manifest,
and
here,
if
you
go
to
the
publish
section,
publish
to
the
store,
you
will
see
warnings,
errors
and
what
you
need
to
fix.
A
A
If
I
go
to
the
basic
information
about
my
application,
I
see
that
the
name
contains
teams,
so
I
need
to
delete
this
and
after
and
I
save
it
and
after
that,
this
will
disappear.
Also
because
we
are
editing
app
manifest.
Please
don't
forget
to
add
the
microsoft
partner
network
id
mp
and
id
to
your
app
manifest.
We
will
create
the
account
in
microsoft,
partner
network
on
the
next
step,
but
after
that
it
should
be
added
to
the
app
manifest.
So
here
that's
the
tool
how
you
can
check
the
application.
A
So
you
see
that
this
warning
disappeared
because
we
changed
the
title
of
our
application.
The
next
step
is
create
the
partner
center
account.
So
here
you
so
you
just
easily
in
the
documentation,
go
step
by
step.
So
let's
click
on
this
create
a
partner
center
developer
account.
If
you
already
are
registered
in
microsoft,
partner
network,
you
only
should
activate
the
program.
I
will
show
you
how
to
do
this.
If
you're
not
registered,
you
can
just
go
through
our
documentation.
A
How
do
I
create
a
partner
center
account
and
if
you
are
new
to
partner
center
and
don't
have
the
microsoft
network
account
create
the
account
using
the
partner
center
enrollment
page?
Let's
do
this.
We
opened
another
article,
create
an
account
using
the
partner
central
announcement
page
and
there's
links
to
partner
central
enrollment
page.
A
A
So
there's
experience
of
partner
center
and
to
be
able
to
submit
the
application
to
the
store
here
in
marketplace
offers
you
should
have
part
office
store
and
you
should
be
able
to
create
the
new
teams
app.
That's
a
new
experience
of
partner
center
and
with
old
experience
you
will
have
instead
of
marketplace,
you
will
have
office
store
on
the
left
side
and
if
you
click
overview
from
here,
you
will
be
able
to
create
the
teams
app.
So
what
to
do?
A
A
Go
to
the
programs
in
programs.
You
need
to
check
that
office.
Store
program
is
enabled
so
you
you're
registering
so
after
you
register,
the
office
store
will
be
added
in
your
menu
and
you
will
be
added
to
create
the
new
teams
application.
So
please
don't
forget
about
this
because
for
some
partners
who
usually
create
application
for
azure
and
that's
a
first
teams
application
for
them.
Please
check
this.
So
what?
Next?
So,
let's
go
back
to
the
documentation.
Let's
go
to
the
steps
we
reviewed
the
team's
store
guidelines.
A
A
So
after
that
you
need
to
prepare
the
document
for
the
validation
team,
because
when
you
submit
the
application
to
the
partner
center,
the
validation
team
will
review
your
application.
They
will
test
your
application.
That's
why
you
need
to
provide
for
them
credentials
if
there's
a
different
experience
for
admin
and
for
regular
user.
A
You
can
provide
both
credentials
and
it's
really
better
to
create
a
good
document
for
them,
because
the
validation
process
can
take
time
and
then
you
should
be
able
to
read
your
documentation
and
understand
your
scenario
and
don't
ask
you
again
so
what
the
scenario
how
it
should
work?
So
everything
should
be
explained,
so
they
will
be
the
testers
of
your
application.
So
please
make
the
instruction
for
them
as
clear
as
possible
and
describe
all
possible
scenarios
of
your
application,
because
it
will
help
a
lot
in
the
to
decrease
the
duration
of
the
validation
process.
A
If
you
have
a
video
instruction,
it
will
be
also
great,
if
you
add
this
and
as
I
told
you
in
the
beginning,
that
your
application
will
appear
in
two
places
in
team
store
and
in
appsource
in
appsource,
and
it's
like
two
separate
pages:
you
need
to
prepare
information
but
usually
copy
paste.
A
title
up
description
should
be
the
same,
and
you
need
to
provide
screenshots.
So
everything
is
described
here.
A
A
A
So,
let's
do
it
step
by
step,
so
there's
a
page
where
you
need
to
submit
all
information
about
your
application.
So
in
the
beginning
you
need
to
select
if
your
application
is
transactable
or
not.
If,
yes,
if
you
want
to
monetize
your
applications
through
the
team
store
before
publishing
the
application
by
itself,
you
need
to
publish
the
transactable
offer.
After
that,
you
will
have
the
offer
id
and
you
will
add
the
software
id
to
the
app
manifest.
So
your
submission
process
will
contain
two
steps.
A
A
So
you
see,
the
application
is
uploading
and
application
will
be
validated
once
again.
So
if
the
icons
are
fine,
if
the
title
is
fine,
it
will
be
the
same
validation
as
we
had
in
on
developer
portal.
So
if,
for
some
reason
you
forget
to
check
the
application
is
in
the
developer
portal,
you
will
see
errors
and
warnings
here,
so
our
application
is
uploaded
and
everything
is
fine.
So,
let's
go
to
the
next
step.
A
Properties
here
you
can
select
the
industry
and
category
for
your
application,
for
example,
hr
accounting
and
finance
collaboration
up
to
three
categories
and
industry.
So
who
are
your
customers
from
which
industries,
but
in
comparison
with
the
category
industries,
are
not
mandatory
because
you
may
create
the
application,
for
example
like
service
desk
or
for
hr
equipment,
which
is
relevant
for
any
industry
for
any
customer.
So
that's
why
it's
not
needed
to
select
the
the
industry
and
support
document
link.
That's
a
link
which
your
customer
will
use.
A
So
after
you,
edit
languages
that
are
supported
in
your
applications
for
each
languages,
you
need
to
add
app
description.
For
example,
if
I
add
additional
language
from,
for
example,
creation
for
each
of
these,
I
need
I
have
the
separate
list
listing
in
marketplace.
So
let's
go
to
the
english
language
and
see
what
we
should
add.
A
And
here
you
can
use
markdown,
you
can
add
description
from
your
app
manifest.
It
should
be
the
same
so
you
can
use
you
know
summaries
very
short
description
that
summarize
the
main
idea
of
your
application
and
search
keywords,
how
the
app
can
be
found
in
the
app
door
chapter
three
after
that,
you
need
to
add
the
icon
for
your
application
and
you
need
to
add
the
screenshot
here.
A
You
see
the
requirements,
the
size,
the
required
size
of
the
icon,
and
if
you
have
video
instruction
for
users
on
youtube
or
vimeo,
you
can
add
the
link
here.
So
let's
go
back
so
here.
If
you
have
specific
date,
when
your
application
should
appear
in
the
store,
you
can
provide
this
date
right
here.
But
if
not,
you
can
just
skip
this
section
and
the
application
will
appear
in
the
team's
door
and
on
marketplace
when
it
will
pass.
The
validation
and
validation
team
will
tell
you
that
everything
is
fine,
additional
certification
information.
A
So
there
there's
information
for
validation,
team,
for
example,
instruction
how
to
test
your
application.
Please
prepare
it
make
it
more
clear
because
it
will
really
impact
on
the
duration
of
the
validation
process
and
after
that
you
can
edit
here
as
a
pdf
file.
So
the
next
it's
what
I
want
to
focus
it's
at
compliance
here.
We
have
two
programs,
so
the
first,
it's
publisher
at
the
station,
so
publisher
at
the
station.
It's
when
you
fill
out
information
about
your
app,
how
you
work
with
data
where
that
is
stored.
A
If
you
use
any
personal
data
in
your
application,
so
you
do
self-assessment
of
your
team's
app
to
add
more
transparency
for
your
application
and
increase
trust
from
the
customer
side
and
the
microsoft
365
certification.
That's
the
next
step!
It's
when
your
application,
it's
already
published
microsoft,
can
check
that
your
application
follow
or
security
guideline
and
after
that,
your
application
will
be
marked
as
a
microsoft
365
certified,
but
for
the
first
validation
process
for
the
publication
you
needed
to
submit
the
publisher
at
the
station
and
m365
certifications.
It's
on
your
wish.
A
A
Do
you
have
a
policy
that
governs
your
service
level
agreement
for
applying
patches?
So
you
see
that
there's
a
lot
of
questions
on
different
topics.
It's
about
security
standards,
privacy,
identities.
You
need
to
fill
out
this
information
and
I
want
to
show
you
where
and
how
customer
can
check
it.
So
the
first
place
it's
team
store
when
you
find
the
application
in
the
app
description
in
the
app
page.
You
will
see
this
signed
publisher
tested.
It
means
that
partner
provides
information
for
getting
all
of
these
questions.
A
A
So
let's
go
back
to
the
apartment
center.
So
after
that
you
can
go
to
the
manage
product,
name
and
reserve
more
names
to
use
in
another
language
or
to
change
the
product's
name.
So
after
that,
when
you
fill
out
all
of
these
pages,
the
publisher
station
edit
screenshots
videos
instruction
for
the
validation
team
and
everything
is
ready.
After
that,
you
can
go
to
the
product
overview
page
or
any
other
page
and
click
review
and
publish.
After
that,
you
will
see
the
status
of
each
steps.
A
You
remember
that
we
already
provided
the
document
with
a
scenario,
but
here
there's
a
list
of
credentials
and
after
that
the
publish
button
will
be
available
and
after
you
click
this
button,
your
application
will
be
submitted
for
the
validation
for
team
store.
So
what's
next,
so
usually
your
application
will
not
pass
the
validation
process
from
the
beginning,
with
the
high
probability.
A
A
How
this
process
looks
like
the
validation
team
will
use
credentials
that
you
provide,
will
use
the
instruction
to
test
your
application
and
they
will
check
how
you
follow
validation
guidelines
and
if
they
find
that
something
wrong
that
you
need
to
fix
this,
they
will
send
you
the
list
of
pictures
what
should
be
fixed.
For
example,
you
have
notification
board
and
the
notification
would
send
information
from
the
external
system
about
some
events
and
your
books
and
only
send
only
the
message
you
have
new
event
and
the
button
to
the
external
system.
A
Of
course,
it
will
not
follow
the
policy
about
forwarding
user
to
external
side,
because
it
means
that
for
core
functionalities
of
your
bot
user
will
be
forwarded
to
external
side.
In
this
case,
validation
team
may
ask
you
to
add
detailed
information
about
the
event
on
the
adaptive
card.
What
will
be
sent
and
probably
in
most
part
of
cases
user
won't
be
needed
to
go
outside
of
the
teams.
So
the
main
idea
is
to
a
little
bit
change
up
from
tonality
to
make
users
stay
in
teams
and
all
other
issues
are
related
to
the
validation
rules.
A
So
that's
why
I
tell
you
in
the
beginning
it's
one
of
the
important
part
of
building
your
application.
They
will
not
do
the
code
review,
but
the
app
should
be.
You
know
the
user.
Experience
should
be
with
our
guidelines,
so
when
they
send
you
the
list
of
these
issues,
you
will
have
time
there's
no
sla.
When
you
know
like
your
submission
process
will
expire,
you
will
have
time
to
fix
this,
but
please
devote
time
for
this
validation
process,
because
sometimes
it
can
happen
that
partner
developed
all
the
applications
submitted
and,
oh
that's,
fine.
A
We
are
ready
to
work
on
another
project,
but
in
reality
the
validation
team
can
send.
You
know
the
list
of
features
and
new
developers
should
continue
to
work
on.
It
should
change
it
and,
of
course
it
takes
it
takes
time
and
if
there
are
on
another
project,
won't
be
able
to
spend
enough
time
to
fix
these
issues
quickly.
Of
course,
it
impacts
on
the
full
duration
of
the
validation
process.
A
Usually,
duration
of
validation
process
is
one
month,
but
it
can
be
longer
depends
on
the
complexity
of
your
application
can
be
ma
up
to
two
months,
but,
as
I
told
you,
it
also
depends
on
you
how
you
prepare
the
instruction
and
it
depends
how
quickly
you
will
fix
these
issues.
So
after
that,
when
everything
is
ready,
when
you
fix
all
the
issues,
validation
team
approves
your
application
for
the
publication
to
the
store
and
couple
of
business
days.
A
It
will
appears
in
the
app
source
and
in
team
store
so
and
your
customers
and
all
customers
across
the
globe
will
be
able
to
see
your
application
so
and
after
that
you
can,
if
it's
needed,
update
your
app.
For
example,
in
the
beginning,
your
application
contains
only
both,
but
you
decided
to
add
it
up
or
you
decided
to
add
messaging
extension,
you
decided
to
add
a
description,
so
you
have
the
version
update
as
usual.
You
may
have
with
the
with
the
application.
A
In
this
case,
we
have
process
to
work
to
maintain
your
published
application.
So
if
you
have
updates
in
your
app
manifest,
for
example,
you
edit
new
component,
you
change
the
description
in
this
case.
You
need
to
resubmit
your
application
once
again,
so
the
all
process
will
start
from
the
beginning.
You
open
the
partner
center.
You
upload
that
manifest
and
validation
team
will
review
your
application.
Of
course,
usually
this
process
takes
very
short
time.
It
can
be
a
week.
A
A
couple
of
weeks,
of
course,
depends
on
the
component,
but
with
the
small
changes,
the
duration
of
the
validation
process
is
really
very
small,
because
validation
team
is
familiar
with
the
application.
The
most
part
of
the
application
was
validated.
So
that's.
Why
don't
don't
afraid
of
it?
Please
don't
change
the
idea
of
your
application.
You
need
to
update
the
version
in
ad
manifest.
A
You
need
to
update
the
version
of
your
at
manifest,
and
in
this
case
after
the
new
version
of
your
application,
will
be
submitted
to
the
store,
all
your
and
it
will
be
published.
All
your
customers
will
get
notification
that
the
app
was
updated
and
they
will
be
able
to
to
have
the
new
version
of
the
app
that's
one
of
the
advantage
of
using
and
publishing
application
to
the
team
store,
because
in
this
case
you
can
make
changes
once
and
submit
it
for
the
publication
and
all
customers
will
get
it
in
case.
A
If
you
don't
use
team
store
and
you
just
send
your
application
to
each
customer,
I
in
case-
if
you
need
to
make
any
changes,
you
will
be
needed
to
send
updated
that
manifest
to
each
of
them.
So
that's
what
about!
I
wanted
to
tell
you
so
please
read
all
of
these
guidelines
because
that's
key
to
successful
publication
in
the
store
so-
and
I
wish
you
a
good
luck
in
the
building
your
application
and
see
your
app
and
the
team
store.
So
thank
you
so
much
bye,
bye.