►
From YouTube: Microsoft Teams App Camp - Anatomy of a SaaS Application
Description
This module introduces you to the anatomy of a SaaS Application
This video is part of a series in a playlist about Building apps for Microsoft Teams: https://www.youtube.com/watch?v=hFwLfG95rVU&list=PLR9nK3mnD-OW5yCjKO0K8b-Xi4Ci1iBlU
➡️ Next video on this series - https://www.youtube.com/watch?v=5B50MusyNR8&list=PLR9nK3mnD-OW5yCjKO0K8b-Xi4Ci1iBlU&index=6
⬅️ Previous video on this series - https://www.youtube.com/watch?v=nuOjlTnoj7s&list=PLR9nK3mnD-OW5yCjKO0K8b-Xi4Ci1iBlU&index=4
#Microsoft365 #AzureAD #MicrosoftTeams
In this video, you will learn about
• What is a SaaS offer
• Components of SaaS applications
• How to use the Partner Center for technical configuration
• Purchasing a SaaS offer in App Source
• SaaS offer landing page
• SaaS offer publisher portal
• Licensing service
• Components of the complete solution
📖 All workshop content including hands-on labs can be found here: https://aka.ms/app-camp
✨ Demo Presenter
• David Starr (Microsoft)
📃 Agenda
0:00 Introduction
1:39 What is a SaaS Offer
2:36 Components of SaaS Applications
5:35 Partner Center technical configuration
6:18 "Other parts of Partner Center"
7:15 Purchasing a SaaS Offer in App Source
9:39 SaaS offer Landing Page
11:21 SaaS offer publisher portal
13:12 Licensing Service
13:51 Components of the complete solution
📝 Learn more
• YouTube playlist for this video series - https://www.youtube.com/watch?v=hFwLfG95rVU&list=PLR9nK3mnD-OW5yCjKO0K8b-Xi4Ci1iBlU
• Overview on Microsoft Teams extensibility - https://learn.microsoft.com/en-us/microsoftteams/platform/overview
• Design guidance for Microsoft Teams apps - https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/design/design-teams-app-overview
• Sample Microsoft Teams apps with code - https://adoption.microsoft.com/en-us/sample-solution-gallery/?product=Teams&sortby=creationDateTime-true&page=1
💡 Learn more about the Microsoft 365 & Power Platform community
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 & Power Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 & Power Platform - http://aka.ms/community/homehttp://aka.ms/m365/community
Sharing is caring! You are awesome! 🧡
A
Hi
and
welcome
to
teams
app
Camp,
I'm,
David
Starr
and
in
this
video
I'm,
going
to
walk
through
components
of
a
SAS
offer
in
the
Microsoft
commercial
Marketplace,
specifically
through
appsource.
This
will
give
you
an
understanding
to
get
started,
building
your
SAS
offer
and
the
resources
to
understand
technical
details
at
an
even
deeper
level.
So,
let's
get
started.
A
Firstly,
this
video
will
give
you
a
working
knowledge
of
SAS
offers
in
the
commercial
Marketplace,
which
is
key
for
success
with
the
monetization
lab
in
teams
Camp
to
perform
the
monetization
lab
note
that
you
will
already
have
needed
to
complete
Labs
A1
through
a03
all
right.
So
what
are
we
going
to
do
in
this
video?
Firstly,
we're
going
to
talk
just
a
little
bit
about
SAS
offers
in
general
and
then
we're
going
to
demo
everything
else,
including
using
partner
Center,
to
set
up
your
offer
at
least
the
technical
configuration
component.
A
Let's
start
by
talking
just
a
little
bit
about
what
SAS
offers
are
and
how
we
might
use
them
in
the
context
of
teams.
App
Camp.
Firstly,
SAS
offers
are
a
type
of
offer
within
the
Microsoft
commercial
Marketplace
and,
of
course,
SAS.
Bean
software
as
a
service
and
what's
really
interesting
about
them,
is
that
they
can
provide
functionality
of
a
team's
application
right.
So
it's
a
SAS
application,
that's
essentially
wrapped
by
teams
in
some
way
that
allows
the
SAS
application
to
be
exposed
as
a
teams
app.
A
There
are
several
components
of
SAS
applications
and
some
are
required.
Some
are
optional
and
we're
going
to
have
a
quick
look
at
what
those
might
be.
Firstly,
we
do
need
to
configure
our
SAS
application
and
partner
Center
there's
a
lot
of
business
information
that
goes
into
this
configuration
of
our
offer,
but
for
our
purposes
we're
going
to
investigate
the
technical
configuration
aspects
of
setting
up
partner
Center.
Also,
we
need
a
landing
page,
and
that
is
a
page
where
your
customers,
your
subscribers,
will
go
to
configure
their
subscription
with
you
as
an
ISP.
A
This
page
must
have
Azure
active
directory
single
sign-on.
However,
it
does
not
need
to
live
on
Azure.
This
can
live
anywhere
on
the
internet.
Correspondingly,
we
need
a
web
hook
that
we
also
configure
in
partner
Center.
This
web
Hook
is
responsible
for
receiving
posts
from
the
marketplace
whenever
something
happens
to
a
subscription.
A
So
when
a
subscription
State
changes
say
from
subscribe
to,
unsubscribed
you'll
get
a
notification
on
your
web
hook
and
finally,
we
need
a
Licensing
Service
when
we
use
per
user
licensing
on
our
SAS
offer
and
that
Licensing
Service
is
another
thing
that
you'll
need
to
build.
There
are
some
optional
components
to
include
a
publisher
dashboard.
This
is
a
simple
website
or
something
to
that
effect.
A
That
allows
you
to
Monitor
and
manage
your
subscriptions
or
the
subscriptions
of
your
customers,
and
it
typically
reads
from
a
database
that
your
web
hook
would
write
into
ensuring
continuity
of
subscription
State.
Then
you
can
think
about
automated
provisioning
of
your
customer
account,
so
it
isn't
required
that
one
actually
automate
the
provisioning
of
customer
accounts.
It
could
be
something
that's
done
in
a
manual
fashion.
However,
doing
so
in
an
automated
way,
really
speeds
up
your
operations
and
allows
you
to
spend
your
Technical
Resources
elsewhere.
A
Finally,
consider
automated
cleanup
of
account
information
for
your
customers
when
they
unsubscribe
from
your
service.
This
is
really
important
in
countries,
for
example,
that
support
the
gdpr
standard
and
even
states
in
the
United
States,
where
there
are
requirements
that
people
can
request
to
be
forgotten,
so
go
ahead
and
forget
them
automatically
when
they
unsubscribe
from
your
product.
Now,
with
that,
let's
jump
into
partner
Center
and
have
a
look
at
the
technical
configuration
required
to
set
up
a
SAS
offer.
A
This
is
a
SAS
offer
in
partner
Center.
The
portal
through
which
you
set
up,
configure,
publish,
maintain
and
monitor
your
offers
that
you
create
for
the
commercial
marketplace
now.
This
particular
offer
is
for
contoso
coffee
and
note
that
it's
a
per
user
licensed
offer
now
we're
going
to
skip
all
of
the
parts
of
partner
Center
that
you
can
learn
about
elsewhere
and
we'll
talk
about
elsewhere
later
in
this
video,
but
for
now
we're
going
to
jump
right
down
to
technical
configuration
and
note
that
there
are
several
things
that
are
required
as
part
of
technical
configuration.
A
First
of
all
that
landing
page
URL
that
we've
talked
about
and
notice.
This
does
not
have
to
be
hosted
on
Azure.
This
can
be
anywhere
on
the
internet
and
that's
true
of
the
connection
web
hook
as
well
that
we
see
configured
on
this
page.
Finally,
we
put
in
the
Azure
active
directory,
tenant
ID
of
the
solution
and
the
application
ID
of
the
solution.
That
is,
you
have
in
your
application,
an
application
registration
and
we
put
in
the
ID
of
that
application
registration.
A
Partner
Center
allows
a
preview
of
this
capability
before
we
actually
go
live
it's
in
the
publisher,
sign
off
phase
we're
going
to
select
app
Source
preview,
which
will
bring
up
a
page.
That
is
exactly
what
your
customers
will
see
after
they
have
found
your
product
in
appsource
and
they've
decided
they
want
to
get
it
now
and
buy
it
so
they're
going
to
select
the
button
get
it
now,
and
this
will
take
them
through
a
purchase
process.
A
Now
we
have
two
plans
that
we've
created
as
part
of
this
offer
gold
and
silver
note
that
each
plan
is
zero
dollars
now.
This
is
simply
because
this
is
a
demo.
Of
course
your
product
would
cost
some
amount
of
money
per
user.
Now,
let's
select
next
we'll
fill
out
our
billing
terms,
I'm
going
to
select
off
for
recurring
billing
and
the
number
of
users
that's
been
specified
for
this
offer
is
up
to
10..
Now
your
offer
is
probably
going
to
have
many
more
user
capabilities.
A
This
is
just
for
demo
purposes,
I'm
going
to
purchase
three
licenses
as
part
of
this
purchase
process.
Next
I
go
to
the
checkout
page,
which
allows
me
one
final.
Look
through
the
offer
before
I
decide
to
go
ahead
and
purchase.
It
note
I
need
to
select
the
billing
profile
here,
so
I'll
select
my
elegant
code,
billing
profile
and
finally
I'll
click
on
accept
agreement
and
place
order.
A
Great
now,
we've
deployed
our
SAS
application,
but
as
a
customer,
I
may
need
to
configure
my
account
with
the
isv
or
independent
software
vendor
the
company
that
made
the
software
to
do
that.
We
go
to
the
offers
landing
page
to
get
to
that
landing
page.
We
simply
select
configure
SAS
account.
Now
remember
this
can
go
to
any
page.
A
That's
on
the
web
and
here's
our
active
directory
single
sign-on
I'm,
going
to
select
my
Microsoft
account
to
sign
in
with
Azure
active
directory
and
I,
see
the
details
of
my
subscription
displayed
on
the
screen
one
last
time
before
I
choose
to
actually
send
notification
to
the
isv
that
I
want
the
subscription
to
be
activated
notice
too.
There
is
up
in
the
URL
a
token
that
has
a
munched
up
string
there
and
what
this
is
used
for
when
you
build
your
landing
page.
A
A
A
The
last
thing
we're
going
to
have
a
look
at
is
a
publisher
portal.
Now
note
this
is
not
necessary,
but
it
is
extremely
useful
to
have
a
publisher
portal
so
that
you
can
manage
and
monitor
your
customers
subscriptions
I'm,
going
to
jump
into
a
publisher
portal
that
our
team
has
created
and
note
that
it
gives
me
Azure
actor
directory
single
sign-on
in
this
case,
just
for
my
tenant
and
I'll
go
to
subscriptions
and
note
that
we
have
a
new
subscription
up
here
that
has
a
subscription
name
of
SAS
accelerator
gold
per
user.
A
This
is
the
subscription
and
the
plan
that
we
purchased
just
a
few
moments
ago
and
notice
that
there
is
a
quantity
of
three
that's
been
designated
as
part
of
the
purchase.
The
state
of
the
subscription
is
still
in
pending
Activation.
So
let's
say
that
I
as
the
isv
now
need
to
go
provision
information
into
my
application
that
is
going
to
actually
serve
up
those
three
licenses
now
I've
done
that
so
I'm
gonna
go
ahead
and
activate
this
account.
So
I'll
review
it
one
last
time
and
then
activate
this
account
note.
A
A
Now,
let's
have
a
look
at
a
Licensing
Service
and
what
role
that
might
play
well,
it
turns
out
that
when
you
select
per
user
pricing
for
your
SAS
offer
you're
going
to
need
a
Licensing
Service.
This
licensing
service
is
going
to
ensure
that
various
things
are
true
like.
If
a
customer
has
purchased
three
licenses,
then
your
SAS
application
needs
to
ensure
that
no
more
than
three
licenses
are
actually
allowed
to
be
used
at
one
time.
A
Here's
a
quick
look
at
the
whole
ecosystem
and
the
components
of
a
complete
SAS
solution
and
who's
responsible
for
which
pieces
things
in
blue
come
from
Microsoft,
that's
appsource
and
the
team's
App
Store.
Obviously,
and
you
adds
the
isv-
are
responsible
for
that
landing
page.
We
discussed
the
web
hook
of
course,
and
finally,
your
SAS
application
that
lives
within
teams,
but
there
is
one
more
piece
and
it's
that
Licensing
Service,
that
we
talked
about
that
typically
will
write
information
into
a
database
that
will
be
read
by
the
SAS
application
itself.
A
I
want
to
thank
you
for
joining
me
in
this
brief
tour
through
SAS
offers
in
appsource
and
I'd,
like
particularly
to
point
you
to
an
additional
resource
where
you
can
learn
a
lot
more
detail
about
building
your
SAS
application
and
that
is
AKA
dot,
Ms
slash
mastering
the
marketplace
and
if
you
want
to
go
directly
to
SAS
offers,
put
a
slash
SAS
on
the
end
of
that
and
with
that.
Thank
you
very
much
for
your
time
and
good
luck.
Building,
SAS
applications
for
your
teams,
app.