►
From YouTube: Microsoft Teams community call-July 2020
Description
This month’s call featured the Microsoft Teams Toolkit for Visual Studio Code, where our duo of experts Karthig Balendran and Allen Snow walked us through a live demo showcasing the capabilities and benefits of the toolkit. Then Emily Chen shared an ask for feedback from the community to enhance the Microsoft Teams developer experience for the Microsoft 365 Developer Program.
Resources
Microsoft Teams Toolkit for VS Code https://aka.ms/AA928pl
Microsoft Teams Toolkit for VS Code (Preview) https://aka.ms/AA928pq
Microsoft 365 Developer Program https://aka.ms/M365DevProgram
Feedback for the Developer Program https://aka.ms/TeamsFocusGroup
Stay connected
Twitter https://twitter.com/microsoft365dev
YouTube https://aka.ms/M365DevYouTube
Blogs https://aka.ms/M365DevBlog
A
Welcome
to
the
july
microsoft
teams,
community
call.
We
have
a
couple
things
today:
the
microsoft
teams
toolkit
for
visual
studio
code
and
the
microsoft
365
developer
program.
They'll
talk
about
some
feedback
that
they're
looking
for
and
what
we're
doing
with
microsoft
teams
there
and
I'm
going
to
let
karthig
and
alan
take
over.
B
C
C
C
So
we're
here
today
to
talk
to
you
about
the
microsoft
teams
toolkit
the
visual
studio
code.
Now
the
toolkit
is
an
extension
that
we
made
for
visual
studio
code
that
helps
you
build
a
teams
app
and
when
I
say
teams,
I'm
talking
about
an
app
that
you
can
install
for
teams.
That
extends
one
of
our
extension
points
in
the
team's
client.
This
toolkit
is
available
for
visual
studio
code,
but
it's
also
available
for
visual
studio.
C
C
You
can
also
download
it
directly
from
from
visual
studio
code
and
the
rest
of
this
presentation.
At
least
my
portion
of
it
will
be
demo
heavy,
so
I'm
gonna
start
sharing
my
screen
and
walking
through
that
before
we
open
up
the
floor
to
q.
A
also,
please
do
feel
free
to
post
your
questions
in
the
chat
thread.
C
Alan
will
be
moderating
the
q
a
and
if
he
decides
something
is
pertinent
to
what
I'm
talking
about
right
then,
and
there
he's
going
to
interrupt
and
just
ask
the
question
otherwise
we'll
be
opening
up
the
floor
towards
the
end
for
a
q
a
so.
If
you
ever
forget
what
those
links
are
to
find
the
extension
in
the
visual
studio
marketplace
online,
you
can
also
just
search
for
it
from
this
extensions
tab
in
visual
studio
code
and
there
it
is
right
there
we're
up
to
version
1.03
we're
not
perfect.
C
C
C
If
you
want
to
take
advantage
of
that,
so
I'm
going
to
close
this
now
and
open
up
the
toolkit
and
I'm
going
to
assume
for
the
time
being
that
everyone
on
the
call
is
a
mix
of
an
experienced
and
inexperienced
teams
developer
and
the
first
thing
that
you
really
should
be
doing
as
you're
venturing
out
into
the
land
of
teams.
Development
is
familiarizing
yourself
with
what's
possible
when
it
comes
time
to
building
a
teams
app.
C
So
we
have
different
extensibility
points
and
if
you're
new,
it
can
be
a
little
bit
confusing
to
hear
about
what
those
are.
So
I
would
recommend
getting
familiar
with
those
extensibility
points
are
and
when
I
say
extensibility
point
I
mean
the
the
parts
of
the
teams
ui
that
you
can
actually
extend
when
you
are
building
on
an
app
and
let
me
just
quickly
go
for
what
that
might
look
like
and
if
I
can
shrink
some
of
this,
maybe
not
okay.
C
C
If
you'd
like
there
are
also
bots,
these
are
conversational
bots.
I
think
you
know
what
those
are
that's
somewhat
intuitive
term
and
then
lastly,
there
are
messaging
extensions.
Messaging
extensions.
Allow
you
to
extend.
Let
me
just
pop
open
my
window
again
really
quickly.
You
guys
can
see
who
I'm
talking
with
that's
fine,
so
anything
you
see
here
is
the
messaging
extension.
It
allows
you
to
populate
the
message
that
you're
typing,
with
with
rich
data.
C
C
C
All
right,
it's
just
going
to
go
in
here,
and
this
is
where
I,
where
understanding
what
these
terms
mean
comes
in
handy,
what
a
tab
is
what
a
plot
is,
what
a
what
a
messaging
extension
is.
So
please
do
check
out
that
link
that
I
shared
and
familiarize
yourself
with
this
terminology
and
these
parts
of
the
team's
client
from
here
on
in
though
building
an
app
is
relatively
very
straightforward.
C
I
went
over
what
that
is,
but
building
one
out
is
also
relatively
straightforward
in
that
there
is
a
node
express
server.
That
is
listening
for
incoming
requests
to
your
server
and
then,
when
a
request
comes
in,
it
forms
a
response
and
we'll
send
it
out,
and
the
more
common
way
of
sending
a
response
out
back
to
the
team's
client
is
from
an
adaptive
card.
So
building
these
two
components
are
very
similar.
It's
just
a
matter
of
how
the
user
interacts
with
it
and
experiences
it
from
the
client.
C
The
simplest
thing
you
can
do
is
to
build
a
tab
and
that's
what
I
suggest
everyone
do
if
this
is
the
first
time
they're
building
a
microsoft
teams
app
because
it's
going
to
be
a
very,
very
familiar
experience
for
you.
If
you've
built
a
react
app,
so
we're
going
to
create
a
personal
tab
and
a
personal
tab
is
a
tab.
C
That's
only
available
to
the
user,
who
has
installed
the
app
or
has
had
the
admin
installed,
the
app
to
their
teams,
client
on
their
behalf,
so
you're
not
going
to
be
sharing
the
ui
of
this
tab
with
anybody
other
than
yourself.
It's
not
going
to
be
exposed
and
as
a
tab
in
a
group
chat
or
a
team's
channel
tab.
C
You
can
find
all
of
the
source
code
for
your
project,
the
scaffolding
right
here,
and
if
you
look
in
the
components
folder,
you
can
see
all
of
the
react
components
that
we've
created
our
goal
with
the
scaffold
was
really
to
optimize
for
onboarding
and
learning
making
it
super
streamlined
for
developers
who
may
now
have
built
on
top
of
the
microsoft
stack
before
to
be
really
familiar
with
this.
So
our
code
base
is
in
vanilla,
javascript
and
these
components
are
all
in
react.
C
If
you
look
very,
if
you
I'll
quickly
go
over
the
details
of
the
scaffold,
the
app.js
file
contains
all
of
your
routing
information.
I
won't
go
into
the
details
of
this.
It's
pretty
straightforward,
but
basically
for
our
tab-based
app.
We
are
going
to
have
your
base
tab.
That
has
the
content
that
we
want
to
show
the
user.
Our
teams
applications
do
require
that
you
have
a
link
to
your
privacy
statement
as
well
as
terms
of
view,
so
we
have
components
here
that
will
cover
that
right.
Now,
it's
super
bare
bones.
C
C
But
this
we
feel
will
do
a
good
job
of
really
familiarizing
yourself
with
what's
possible
and
if
you
choose
to
extend
it,
this
is
a
good
starting
point
as
well.
We've
tried
to
keep
very
bare
bones,
so,
as
you
can
see,
when
you
open
up
your
tab-based
app,
what
we're
doing
is
getting
the
team's
context,
setting
that
context
to
your
react
act
state
and
then,
when
you
render
it
we're
grabbing
your
username
from
the
context
and
then
displaying
it.
C
C
Just
so,
we
can
see
it
running
and
it's
running
right
now
and
as
it's
installing,
I
will
quickly
go
over
some
other
parts
of
the
team's
toolkit.
Okay.
So,
as
I
mentioned
already,
oh
by
the
way,
the
readme's
here,
you
can
just
follow
these
instructions
here
to
learn
how
to
get
started
with
with
developing
your
personal
app,
though
one
problem
I
will
go
over
right
now
is
that
launching
your
app
directly
from
visual
studio?
This
is
currently
broken.
C
Unfortunately,
apologies
so
normally,
once
you
do
everything
you
need
to
do
you
simply
just
go
to
this
debugger
button
and
hit
run
start
debugging
or
just
press
f5,
and
your
app
will
get
side
loaded
launched
to
your
team's
client
automatically.
That's
not
supported
right
now,
so
you're
going
to
have
to
do
it
the
old-fashioned
way,
which
is
not
too
much
of
a
pain.
C
You
just
need
to
make
sure
that
you
get
the
zip
file
from
this
published
folder
and
upload
it
to
your
tenant
and
I'll
plug
michael's
office.
365
developer
program
really
quickly
here,
because
you
in
order
to
actually
sideload
or
install
the
teams
in
order
to
sideload
or
install
a
teams
app
to
your
team's
client.
C
If
you
don't
have
that
permission-
and
you
should
do
this
anyway-
go
to
the
office
365
developer
program-
and
I
think
michael,
has
already
posted
a
link
to
that
and
sign
up
for
a
developer
account
and
do
all
of
your
development
from
that
development
account
so
you're
not
running
into
any
permissions
issues,
saying
that
you
can't,
for
example,
install
an
app
and
also
just
so
that
you
have
a
nice
clean,
developer
tenant
for
anything.
You
need
to
do
in
azure,
so
make
sure
you
go
and
do
that.
C
C
C
It's
hosted
like
a
website,
so
it
throws
down
a
server
some
server
somewhere
and
when
you
install
it
into
the
team's
client,
you
are
more
or
less
just
linking
to
that
from
the
team's
client,
if
you
can
think
of
the
team's
fight
in
this
case
as
a
browser
and
we're
just
directing
the
user
to
the
server
where
that
tab
experience
is
being
rendered
and
returned
to
teams,
so
nothing
is
getting
installed
on
the
team's
client.
This
is
not
like
building
an
ios
app
or
an
android
app.
C
There's
nothing
running
on
your
machine
and
traditionally
how
you
install
an
app
is
to
push
two
icon
files.
You
can
see.
We
have
one
icon
file
here
and
one
icon
file
here
and
this
manifest.json
file.
We
package
it
up
into
a
zip
file
like
development.zip,
and
then
we
install
that
zip
file.
Now
this
contains
all
the
information
that
the
team's
client
needs
to
display
that
your
app
in
the
team's
client.
C
This
content
url
will
contain
the
address
where
your
tabs
content
will
be
served
from
okay.
Now,
normally,
this
was
done
with
app
studio,
which
is
an
app
in
teams.
This,
the
process
of
editing
this
manifest
file
is
called
manifest.
Editing,
obviously-
and
this
was
done
in
app
studio-
we've
brought
that
experience
into
the
team's
toolkit,
and
now
you
can
just
edit
your
manifest
from
the
toolkit
directly
okay.
So
this
should
be
a
very
familiar
experience
for
you
if
you've
already
played
around
with
app
studio
in
microsoft
teams.
C
We
do
the
we
capture
the
bot
id
for
you
at
provisioning
time
when
you're,
selecting
a
project,
and
we
inject
all
the
necessary
details,
like
your
app
id
and
bot
secrets
into
the
necessary
places
of
the
manifest
file
and
the
env
files
that
you
have.
I
would
like
to
point
out
that
there
are
two
emv
files
at
this
point.
One
of
them
is
your
development,
environment,
dot
emv,
and
this
emv
file
will
feed
your
manifest.json
file.
C
So,
for
example,
right
now
it
says
that
my
base
url
will
be
localhost
3000.,
I'm
going
to
have
to
change
this
now,
because
a
local
host
works.
Fine.
If
you're
going
to
be
running
your
team's
app
directly
from
from
visual
studio
code
with
f5,
and
this
should
work
for
me,
because
I've
already
done
some
of
the
prerequisites
for
that.
But
if
this
is
your
first
time
you
have
two
choices.
Let
me
go
over
that.
C
Actually,
if
you
would
like
to
run
your
app
serve
your
app
from
localhost
you're,
going
to
have
to
add
a
trusted
certificate
for
your
localhost
server,
and
there
are
instructions
on
how
to
do
that.
You
can
follow
this.
If
you
don't
want
to
do
that,
you
need
a
tunneling
service
like
ngrok,
which
is
the
one
we
recommend
to
tunnel
from
your
local
server
to
the
team's
client,
okay
and
for
simplicity.
C
I'm
not
going
to
do
that
right
now,
we're
just
going
to
run
from
a
local
host,
but
just
understand
that
if
you're
going
to
be
running
from
localhost
click
on
this
link
here
add
a
trusted
certificate
for
localhost,
so
that
teams
doesn't
block
the
installation
of
apps
from
localhost
all
right.
So
we
finished
installing
oh
also
base
url
10
version,
10
full
app
name.
If
you
look
at
the
json.manifest
file,
these
are
placeholder
values.
C
If
you
update
the
development.emv
file,
you
will
update
the
placeholders
in
the
manifest.json,
because
some
of
these
values
will
appear
multiple
times
to
save
you
some
time.
You
can
use
the
environment
file
to
do
that,
and
also,
if
you
create
another
env
file
in
another
zip
file,
let's
say
production.env
and
production.zip
or
local.nav
and
local.zip.
C
Each
of
those
are
treated
as
another
development
environment
in
your
edit
package
service.
Okay,
all
right
anyway
enough
with
the
boring
stuff.
Let's
start
this
and
see
how
it
goes
now
I
mentioned
already
that
normally
I
would
be
hitting
the
debugger
and
pressing
f5.
This
experience
is
currently
broken
and
also
the
way
it's
implemented
right
now.
This
is
being
remediated.
C
But
if
you
do
this
right
now-
and
it
works
right
now,
it
will
also
exit
your
team's
client
and
restart
it,
and
I
don't
want
to
stop
talking
to
you
guys,
so
I'm
not
going
to
do
that.
We're
going
to
do
the
boring
way.
We
are
going
to
side
load
this
app,
but
let's
first
wait
for
the
server
to
finish
running,
oh
and
if
anyone's
curious.
There
is
no
server
logic
here
in
the
scaffold,
because
we're
using
create
react
app
to
provide
the
scaffold.
It's
very
bare
bones,
routing
supported,
but
back-end
calls
aren't
supported.
C
We
do
have
work
coming
down
the
line
to
incorporate
if
you,
if
you're
interested
a
separate
server
to
serve
your
front,
end
sorry
to
serve
your
the
backing
capabilities
for
your
front
end,
so
you
expect
to
see
that
in
the
near
term-
okay,
it's
running
so
if
side
loading's
enabled
for
your
organization.
This
is
how
you
do
it
go
to
the
apps
icon
here
and
upload
a
custom
app
and
we
are
going
to
go
to
oh,
no.
What
did
I
call,
I
think,
was
contoso
tab.
C
C
Okay,
that's
fine!
Okay!
Normally
you
would
not
see
a
message
here
displaying
your
name.
I
have
a
feeling
that
my
computer
is
really
slow
today
for
some
reason-
and
it's
not
cooperating
so
I'm
going
to
come
back
to
this
and
also
refresh
this,
but
in
the
meantime,
I'm
going
to
go
over
the
other
parts
of
the
toolkit.
C
It
can
quickly
just
look
at
your
manifest
file
and
see
if
anything
will
prevent
it
from
being
blocked,
prevent
your
app
from
being
published
to
the
office
app
store,
app
source,
slash
teams,
app
store,
okay,
and
this
is
a
nifty
new
feature
in
preview.
I
shouldn't
show
everyone
here
this,
but
that's
fine.
E
C
Well,
thank
you.
Lastly,
bots.
If
you
are
building
a
bot,
I
mentioned
earlier
that
a
team
spot
is
powered
by
a
microsoft
bot
framework
bot
and
when
you
create
one
via
app
studio
from
the
tool,
there's
going
to
be
a
configuration,
there's
going
to
be
an
app
there's
going
to
be
an
instance
of
an
app
registration
in
azure
that
you
can
manage
and
to
save
you
time
from
having
to
go
to
azure,
to
configure
a
bot
configure
your
bot.
C
We
are
bringing
that
information
here,
so
you
will
go
here
to
do
things
mainly
these
are
you
will
most
likely
come
here
to
get
passwords
for
your
bot
and
update
the
endpoint
address
for
your
bot?
I
don't
suspect
you're
going
to
be
coming
here
for
much
else,
but
these
are
very.
These
will
be
common
tasks
that
you
do
if,
for
example,
you
aren't
using
a
paid
pengrock
subscription
so
for
it,
which
would
mean
that
the
domain
for
your
bot
endpoint
will
be
dynamic
and
changing
all
the
time.
C
Also,
I'd
like
to
point
out
that
you
can't
bots
currently
have
to
be
behind
a
tunneling
service,
so
I
suggest
that
if
you're
interested
in
building
a
bot
or
a
messaging
extension
that
you
familiarize
yourself
with
ngrok,
you
know
it's
a
great
product.
We
are
doing
some
work
to
see
if
we
can
get
away
get
around
this
requirement
in
the
future.
C
D
C
That
explains
that,
in
that
case,
this
is
how
engroc
works,
so
I've
already
installed
ncrack.
So
ingrec
is
a
very
simple
command
line
utility.
So
I'm
going
to
open
up
a
tunnel,
an
http
tunnel
and
it's
going
to
be
pointing
to
localhost
and
alan,
I
think,
was
poor
3000
and
I
have
a
paid
subscription
to
ngrot
and
what
that
means
is.
C
I
can
provided
a
fixed
sub
domain
and
that
sub
domain
is
going
to
be
assigned
to
me
if
it's
available,
if
you
don't
have
a
paid
subscription,
you
can
do
everything
I'm
doing
except
you
can't
use
the
subdomain
field,
and
let
me
show
you
what
happens
when
I
enter
this
program:
basic
okay.
There
we
go
okay,
so,
as
you
can
see,
https
teamflex.io
is
now
being
directed
to
http
localhost.
Oh
alan!
Is
that
right
should
it
be
https,
or
is
this
fine.
D
C
Okay,
so
I'm
first
of
all,
I'm
going
to
make
sure
that
my
base
url
is
pointing
to
my
ngrok
url.
So
it's
going
to
be
http.
Pardon
me
https,
themeflix.ngroc.io,
okay,
so
now
my
team's
app
will
know.
That's
where
it
needs
to
look
and
I'm
going
to
close
this
and
one
more
thing
this
env
file-
normally
we
require
https
to
be
on,
but
we're
going
to
be
debugging
from
local
hosts.
So
I'm
going
to
set
this
to
false
okay
and
I'm
going
to
leave
ngrok
running
and
I'm
going
to
restart
this.
C
D
C
Okay,
so
deploying
to
azure
we're
doing
work
to
simplify
that
streamline
that
nothing.
I
can
discuss
right
now
because
it's
super
early
into
development
and
also
heard
something
about
ci
cd,
so
first
up
on
hosting
we're
working
on
the
story.
For
that,
that's
something
we're
actually
gonna
work
on
working
on
in
age
two,
but
there
isn't
very
much.
C
I
can
share
right
now
because
it's
very
we're
very,
very
early
into
the
stages
of
figuring
that
part
out,
but
know
that
that's
on
the
horizon,
with
respect
to
cicd
that
is
also
on
the
horizon.
We
just
have
to
figure
out
the
best
way
to
incorporate
that
into
what
we're
doing,
while
adding
enough
value
to
justify
the
work.
So
we
already
have
excellent.
C
If
you
haven't
tried
it
already.
I
urge
you
to
go
and
install
the
azure
tools,
extension
pack,
which
will
give
you
a
nice
little
bag
of
tricks
if
you
are
deeply
embedded
in
the
azure
stack
and
you
can
set
up
a
continuous
integration,
continuous
delivery
pipeline
that
way
do
think
that
there
is
a
gap
we
currently
have
in
that,
when
you're
updating,
a
teams
up,
you're,
really
updating
two
things:
you're,
updating
the
surfaces
of
the
power
of
the
app
and
you're,
also
updating
the
client
ui,
sometimes
not
always.
C
So
we
have
some
work
to
do
to
really
light
up
this
feature,
but
it's
also
on
our
backlog
and
it's
something
that
we
want
to
deliver
in
the
near
term,
but
just
no
concrete
plans
right
now,
so
my
server
is
running.
I'm
going
to
now
sideload
this
app
again
and
what's
cool
about
this
is
if
you
update
any
env
file
value
we
do
generate
and
we
update
the
json
and
we
generate
a
new
zip
file
for
you.
So
at
this
point
I
should
have
nothing
more
to
do
than
to
open
up
the
teams.
C
D
C
C
So
first
of
all
you
are
you
have
I'm
assuming
that
you
have
visual
studio
and
code
installed.
You
have
the
toolkit
installed.
You
have
node.js
installed
and
also
you
have
a
developer
account
because
I'm
going
to
assume
that
many
of
you
are
working
for
large
organizations
where
you
may
not
know
who
your
team's
admin
is.
The
person
that
can
actually
give
you
permission
to
install
lapse
so
go
get
an
m365
developer
account
and
get
that
set
up.
C
So
you
have
the
team
kit,
you
open
up
the
team,
the
toolkit
and
you
build
a
personal,
app,
npm,
install
and
start
which
will
take
you
to
this
part
right
here.
Okay,
assuming
f5
works,
you
don't
have
to
do
anything
else,
other
than
well
adding
a
trusted
certificate
for
localhost
which
we're
working
to
get
around
and
also
you
have.
You
should
set
your
team's
client
to
developer
preview
mode,
okay
and
in
order
to
do
that,
there
are
instructions
in
that
link.
C
Actually,
I
won't
go
through
that
right
now,
because
we're
running
short
on
time,
but
there
are
instructions
on
link
on
how
to
set
your
team's
client
to
developer
preview
mode,
but
there's
a
switch
somewhere
in
the
ui
that
you
just
need
to
toggle.
Okay,
once
that's
done,
what
we're
going
to
do
is
simply
go
to
the
debugger
and
hit
run.
C
C
Okay,
you
get
this
random
number
for
the
sub
domain.
That's
going
to
change
every
time
you
restart
and
graph,
so
just
have
ngrok
running
and
make
sure
that
it's
pointing
to
http
localhost
3000
and
in
the
emd
file.
You
want
to
set
http
to
false.
If
you're
going
to
go
this
route,
we
did
have
another
set
of
instructions
at
one
point
on
how
to
the
golden
path
for
getting
your
app
installed
without
f5.
I
think
I
looking
at
this
now.
I
should
probably
go
add
that
content
back
in
until
we
fix
the
f5
experience.
C
So
once
again
there
are
two
nv
files
and
need
to
make
updates.
So
you
want
to
update
this
base
url
to
whatever
random
subdomain.ngroc.io
was
provided
to
you
by
ngrok
and
make
sure
you
use
the
https
endpoint,
because
teams
needs
your
apps
to
be
served
from
a
secure
location.
Okay.
The
second
thing
you
want
to
do
is
set
your
https
environment
variable
to
false
in
the
environment.
C
D
Did
you
go
over
like
if
you
didn't
want
to
use
ngrok
and
just
the
only
point
was
was
just
you
know,
so
you
don't
want
to
use
ngrok.
You
could
leave
everything
the
same,
but
just
follow
the
instructions
for
creating
that
vocal
certificate
which
you
know
it
takes
like
five
minutes
or
something
it
takes
five
minutes
yeah.
D
C
C
C
A
D
A
A
D
C
A
B
So
I
look
at
how
to
enable
developer
to
build
higher
quality
app
and
that's
from
documentation
to
control,
building
control
libraries
to
the
validation
tool
you
have
seen
in
the
toolkit
and
now
I'm
working
with
michael
on
the
developer
o365
program
to
see
how
we
can
empower
teams
developer
there.
So
just
a
really
quick
background.
The
o365
developer
program
gives
you
free
tenant
that
you
can
use
to
test
your
app
or
just
play
around
for
demo
purposes
and
stuff,
and
right
now
we
provide
the
empty
tenant
to
you.
B
B
E
A
E
I
think
it
would
be
probably
most
useful
if
people
just
wanted
in
the
chat
window
to
identify
what
are
the,
what
are
the
things
that
are
the
the
biggest
challenges
that
you
face
as
a
teams
developer,
we'd
love
to
just
get
some
of
that
feedback.
I
don't
think
we
can
really
show
any
of
the
concepts
in
this
forum,
but
we'd
like
to
just
understand,
pain
points,
and
you
know
if
they
were
like
the
top
three
things.
You'd
love
to
see
us
make
easier
for
you.
A
E
Earlier
earlier,
in
the
chat,
I
also
gave
you
a
tip
that
if
you
have
a
visual
studio,
pro
or
visual
studio
enterprise
subscription,
your
microsoft
365
developer
subscription
will
actually
be
automatically
renewed.
So
if
you
look
into
the
chat
scroll
up
in
the
chat,
you'll
see
how
I
show
you
that
if
you
do
have
those
subscriptions
already,
that
is
a
way
to
actually
have
a
subscription
perpetually.
As
long
as
you
have
a
valid
visual
studio
pro
or
enterprise
subscription,
but
for
people
who
just
joined
the
dev
program.
E
Normally
it
is
valid
for
90
days
and
then
and
then
it
expires
unless
you
are
actually
using
it
as
a
developer.
If
you're
using
it
as
a
developer,
then
we
capture
telemetry
based
on
that
and
we
will
renew
it
for
as
long
as
you're
actually
using
it.
So
and
and
one
of
the
reasons
why
we
want
to
develop
more
capabilities
for
teams.
E
B
E
In
the
office
that
has
taken
over
somebody's
job,
then
they
just
need
to
create
their
own
subscription.
There
are
tools
that
are
out
there
to
migrate,
so
if
you've
actually
got
credentials
for
both,
there
are
ways
in
which
you
could
migrate
data
from
one
to
the
other
after
you've
created
the
tenant.
We
don't
allow
you
to
do
that.
E
E
E
E
You
know,
they've
even
got
pre-populated
with
emails
and,
and
so
those
are
two
different
sample
data
packs
that
are
available
that
allow
you
to
pre-configure
your
your
your
your
sandbox
we'd
love.
To
add
to
that,
though,
and
make
it
much
more
exciting
for
teams
developers
and
we
we
just
launched
one
for
sharepoint,
so
sharepoint
framework
and
we'd
love
to
do
something
similar
for
teams,
and
that's
one
of
the
reasons
why
emily
and
I
are
partnering
together
to
get
your
feedback
to
figure
out
what
are
the
most
important
things
that
you'd
like
to
see
there.
E
E
E
Yes,
and
we
don't
allow
two
to
three
tenants
per
account
for
a
normal
subscription.
If
you
have
a
multiple
visual
studio
subscriptions,
for
example,
you
might
have
a
visual
studio
pro
subscription,
but
you
also
have
a
visual
studio
enterprise
subscription.
You
can
end
up
getting
multiple
tenants
that
way,
but
that's
really
the
only
way
you
can
get
multiple
tenants.
The
maximum
number
of
tenants
per
account
is
one.
E
Sorry,
if,
if
you're
looking
for
multiple
users,
every
tenant
has
25
users,
so
sorry
I
was,
I
was-
may
have
misunderstood
the
question.
But
can
you
get
multiple
tenants?
The
answer
is,
no.
Can
you
have
multiple
users?
Absolutely.
The
tenant
is
pre-configured
for
25
users,
including
the
admin,
so
you
have
admin
plus
24
other
users,
and
so
you
can
have
multiple
developers
that
are
using
that
tenant.
If
you
want
them
to.
A
A
So,
okay,
any
other
questions
that
anyone
has
okay,
so
make
sure
that
you
provide
feedback
for
teams.
If
you
have
questions
about
anything
developer
related,
we
have
our
documentation
and
then
our
link
to
feedback
which
is
just
aka.ms
teamstab
feedback
and
then
just
to
wrap
up
real
quick.
The
recording
will
be
available
on
our
developer
youtube
channel,
which
you
can
subscribe
to.
So
it
will
give
you
updates
when
all
videos
regarding
community
calls
trainings
all
snap
videos
and
other
things
related
to
the
microsoft
365
developer
platform
will
be
available.