►
From YouTube: Microsoft 365 PnP – General Microsoft 365 Developer SIG community call – 24th of June, 2021
Description
Microsoft 365 PnP Community - General SIG call on June 24th. Demos: Getting started with PnP Teams QuickStart, Our learnings from the AppSource submission for Microsoft Teams, Getting started with Microsoft Graph Tag API for managing Microsoft Teams tagging. Summer break and community call schedule updates reviewed. Announced the PnP Recognition Program and an updated Teams sample browser - Teams samples gallery. One new Teams sample was delivered in last 2 weeks. Great work! Check out the new PnP Teams Quickstart. The host of this call was David Warner II (Catapult Systems) | @DavidWarnerII. Q&A takes place in chat throughout the call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly General M365 Dev SIG call: http://aka.ms/spdev-sig-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
We'd
like
to
warmly
welcome
everyone
for
attending
the
microsoft
365
development,
bi-weekly
community
call
it
is
june
24th-
and
I
am
david
warner
principal
consultant
with
catapult
systems
and
pnp
team
member
as
your
host
for
today's
call.
Our
agenda
for
the
call
today
includes
reviewing
updates
for
our
pnp
initiatives,
followed
by
an
optional
picture
time,
which
we
know
everyone
enjoys,
and
then
we're
gonna
see
three
incredible
demos
from
victor
florian
and
annie
on
getting
started
with
pnp
teams.
Quick
start
learning
is
from
the
appsource
submission
for
microsoft.
A
Teams
and
annie
is
going
to
cover
getting
started
with
microsoft,
graph
tag,
api
for
managing
microsoft
teams,
tagging.
To
begin
with,
let's
review
some
of
the
opportunities
to
participate
in
the
community.
You
can
always
demo
a
solution
or
technical
pattern
on
this
call
you're
more
than
welcome
to
contribute
on
github
and,
of
course,
feedback
is
always
welcome,
so
whether
it's
good
or
bad
or
constructive,
we
would
like
to
hear
what
you
are
wanting
to
see
next
now
there
is
a
plethora
of
links
available
to
you.
We
have
developer
videos
for
microsoft,
365..
A
We
have
community
videos,
we
have
open
source
opportunities
to
communicate
with
the
community
and
we
can
see
that
at
github
sharepoint
pnp
office,
dev
microsoft
graph
and
when
it
comes
to
sample
galleries,
there
is
no
rival.
We
have
plenty
of
sample
galleries
available
to
you:
team
samples,
spfx
samples,
power
platform,
samples,
extension
list
formatting.
Oh
my
so
many
samples
available
to
you
now
you'll
be
wondering
how
do
I
keep
track
of
all
these?
A
B
So
we
will
have
a
first
of
all.
We
will
have
a
summer
break
on
the
microsoft
teams,
microsoft,
craft
and
sharepoint
calls,
and
then,
after
the
summer,
starting
from
31st
of
august,
those
will
be
merged
to
a
one
weekly
call
platform
course.
So
basically,
what
we
want
to
do
with
this
one
is
promote,
let's
say
not
to
isolation
based
on
a
product,
rather
the
whole
holistic,
microsoft,
365
platform,
and
our
original
plan
was
basically
to
combine
a
lot
of
the
other
calls
in
here
as
well.
B
So
even
though
it
was
kind
of
an
awkward
thing
as
well,
our
objective
was
to
reduce
the
overall
number
of
the
calls.
Within
a
month.
We
ended
up
increasing
them
with
one
which
is
kind
of
kind
of
awkward
for
sure,
but
basic
idea
is
that
we
will
have
an
engineering
call
on
tuesday
at
8am
in
the
morning
pacific
time.
Whatever
is
that
in
your
time
zone?
That's
6
p.m.
On
night
time
and
then
another
community
call
on
thursday
every
single
week
at
7
a.m:
pacific
time
which
says
5
p.m.
B
On
my
my
location
so
and
that's
kind
of
the
things
and
then
we'll
have
a
few
individual
monthly
re
current
calls
still
existing.
I
will
write
a
blog
post
about
this
one
later
today
and
we'll
share
that
one
out
so
you'll
understand
the
changes
but
again
just
to
repeat
microsoft:
teams,
microsoft,
graph
and
sharepoint
monthly
community
course
will
not
happen
in
july
and
in
august
they
are
on
summer
break
but
showing.
A
A
Now,
let's
talk
about
extensibility,
you
may
be
wondering
how
you
can
get
involved
in
extending
the
experience
within
microsoft.
365.
Well,
we've
got
a
lookbook
that
is
there
for
providing
access
to
information
and
how
you
can
see
demos
of
extensibility
being
taking
place
in
the
microsoft
365
community,
so
aka
dot,
ms
for
slash,
m365
soar,
slash
extensibility
will
show
you
all
kinds
of
opportunities
that
come
in
terms
of
products
and
types
of
apps
and
scenarios
in
which
you
can
see
how
you
can
extend
the
environment
of
your
microsoft,
365
experience.
A
Microsoft
teams
is
obviously
a
very
popular
application.
Now
one
of
the
most
popular
in
microsoft
history.
Well,
you
might
want
to
see
some
samples
on
how
you
can
get
involved
in
creating
and
extending
that
experience
as
well,
so
aka
dot.
Ms
forward
slash
team
samples:
it
is
a
big
opportunity
for
the
community
to
start
building
these
kinds
of
samples,
and
so
we
welcome
everyone
to
start
seeing
how
some
others
in
the
community
are
extending
this
experience
and,
of
course
your
samples
are
welcome
too.
A
A
It
is
a
variety
of
scripts
from
powershell
and
clies
contributions,
of
course,
as
we
are,
an
open
source
and
inclusive
community
are
welcome.
So
this
is
one
of
our
newest
repos
and
we
invite
you
to
take
a
look
at
it.
Aka
dot,
ms
forward
slash
script,
dash
samples.
Now
you
may
be
asking
yourself:
how
do
I
get
involved
in
all
these
initiatives?
A
How
can
I
take
advantage
of
and
contribute
back
well,
there
is
sharing
is
caring.
This
is
an
opportunity
and
a
collection
of
sessions
that
provide
guidance
on
how
to
get
more
involved
in
the
community.
Now
that
may
be
using
these
resources
that
are
available,
it
may
be
contributing
back.
So
if
you
are
wanting
to
get
more
involved,
these
sessions
are
completely
free,
they're,
hands-on,
safe
space
opportunities
for
you
to
get
more
involved
with
the
community.
They
are
not
recorded.
A
We
walk
you
through
how
to
accomplish
a
variety
of
topics
such
as
things
like
your
first
time
contribution
or,
if
you'd
like
to
demo
on
these
calls,
but
you're
a
little
nervous,
first-time
presenter
might
be
perfect
and
of
course,
we
started
up.
Ask
me
anything
opportunities
each
month.
The
next
up
is
teams
development,
starting
on
july,
13th
so
be
sure
to
register
they're
all
free
all
available
aka,
ms
forward
slash
sharing,
is
caring.
A
Now
it
is
a
great
privilege
and
honor
to
announce
formally
the
recognition
program
for
patterns
and
practices.
This
is
a
brand
new
recognition
program.
We
are
starting.
You
may
have
seen
some
of
the
badges
being
shared
yesterday
on
linkedin
and
twitter.
This
is
bringing
a
new
level
to
community
recognition.
We
are
partnering
with
credly
the
same
platform
that
handles
the
microsoft
certification,
badges
and
we
are
going
to
formally
start
recognizing
your
contributions
by
way
of
this
system.
Now
we
only
have
a
couple
badges
out
right
now.
A
A
We
ask
you
to
opt
in
we're
going
to
provide
you
a
form
on
that
page
that
asks
you
to
provide
your
email
address
so
that
we
can
tie
your
contributions
and
as
of
right
now
it's
a
manual
process
where
we'll
be
awarding
and
providing
those
badges
so
bear
with
us
as
we
get
that
process
underway,
but
we
hope
you're
as
excited
as
we
are.
It
is
an
amazing
opportunity
to
get
more
involved
in
the
community
all
right.
Let's
talk
about
pnp.net
libraries
believe
I
saw
bert
on
the
call.
C
C
D
C
Like
a
comment,
all
those
things
that
you
can
do
in
ui,
you
can
do
it
from
the
api
as
well
right
now
and
there's
several
other
smaller
improvements
done
by
paolo
and
me
as
well
going
forward.
The
focus
will
be
on
just
keeping
improving,
merging,
prs
and
suffocation
time
as
well.
So
you
will
see
a
little
bit
slow
down,
maybe
in
in
the
rhythm
of
things,
but
definitely
picking
up
after
holidays
and
going
full
speed
ahead
towards
next
year.
A
E
I'm
here
so
there's
no
big
new
updates.
What
we're
working
on
is
the
next
preview
3.3.0
and
most
significantly,
it's
re-updating
sort
of
some
of
the
packages
and
support
and
new
scaffolding
with
adaptive
card
1.4
universal
actions.
So
hopefully
we
transition
fully
over
to
that
over
the
next
few
weeks.
Otherwise,
the
I
mentioned
two
weeks
ago,
we
the
react
helper
script
library
we're
using.
I
have
an
increase
of
30
thanks
to
the
teams
toolkit,
that's
using
the
same
same
package,
essentially
I'll
tell
some
more
about
the
news.
E
A
F
F
This
is
set
to
release
for
our
next
version,
so
give
us
feedback
we're
working
on
the
documentation
and
getting
started
guide
for
this
provider
right
now.
This
means
that
you
can
sign
into
your
team's
apps,
using
microsoft,
graph
toolkit
without
any
pop-ups
or
resigning.
In
I
know
this
has
been
asked
for
the
community
for
a
while
now
so
feel
free
to
check
it
out
other
than
that
we
added
some
updates
and
bug
fixes
also
the
team's
provider
thanks
to
simon.
F
F
We
also
have
specs
that
are
new
for
two
kind
of
new
features,
and
one
of
them
is
a
new
component
for
people
to
give
feedback.
One
is
the
mgt
file
list
component
is
introducing
uploading
file
functionality
and
we
need
your
help
telling
us
what's
needed.
The
other
one
is
the
new
component,
mgt
search,
so
pr
number
is
listed
in
the
help
plus
improve
section
feel
free
to
go.
Take
a
look
other
than
that.
Let's
build
more
apps.
A
G
G
Who
have
built
this
sample?
So
if
you
haven't
already
figured
out
by
looking
at
the
screen
right,
this
is
a
really
commonly
asked
for
scenario
where
azure
communication
services,
which
allows
you
to
bring
teams,
meeting
functionality
and
chat
functionality
into
your
apps
outside
of
teams.
Here's
a
sample
that
shows
how
to
make
that
work
between
a
team's
user
and
a
consumer
or
a
patient
or
somebody
who
is
who
is
outside
of
teams
using
a
website.
G
So
this
is
a
really
a
really
cool
scenario:
a
really
cool
sample
and
hats
off
to
everyone
who
worked
on
it.
There
have
been
some
updates
to
the
team's
sample
browser
itself,
and
I
want
to
just
thank
hugo
bernier
for
working
on
that
quite
a
bit
and
it's
all
moving
towards
an
even
better
sample
browser
in
the
future,
but
you
should
see
some
some
small
improvements
and
a
nicer
user
interface
on
the
on
some
of
the
sample
browsers
these
days,
including
the
teams.
One.
A
Awesome,
thank
you.
Bob
and
excellent
job
by
the
community
appreciate
all
of
the
samples
that
go
into
making
this
community
one
of
a
kind,
excellent,
optional
picture
time.
Everybody
loves
this.
So
let's
move
our
call
in
all
right.
Give
it
just
a
couple
more
seconds:
everybody's
coming
in
that's
excellent,
all
right!
Let's
give
it
a
countdown
here.
A
All
right,
let's
get
some
waving,
say
hello
to
the
community
awesome.
Thank
you,
everyone.
This
is
one
of
the
best
communities
ever
great
to
see
all
the
faces
and
smiling
faces
that
we've
got
in
this
community
excellent
job
all
right.
Well,
let's
get
into
as
vesta
says
the
stars
of
the
day,
and
that
is
going
to
be
our
demo.
So,
let's
begin
with
victor
getting
started
with
pnp
teams,
quick
start
feel
free
to
take
on
over
the
screen.
E
E
First
of
all,
you
need
to
sign
up
for
codespaces.
It's
currently
in
preview,
so
just
go
to
github.com,
codespaces
and
sign
up
for
that,
and
hopefully
you
get
in
the
preview,
then
once
you've
done,
that
you
just
go
to
ak
dot.
Ms
slash
pnp
teams,
quick
start,
and
that
will
take
us.
Take
you
to
this
github
repo.
It's
very
simple,
github
repo.
E
E
E
So,
just
post
it
here
in
my
notepad
on
the
side,
I
will
need
to
create
a
create
secret
here,
because
we
need
it
for
the
demo
that
you
typically
don't
do
that
when
you
just
create
an
ssl
tab,
but
let's
create
a
secret,
because
we
will
do
on
behalf
of
flow
here
to
get
single
sign-on
support
to
call
into
the
microsoft
graph,
with
some
new,
exciting
features
in
just
a
bit.
The
second
third
thing
I
need
to
do
here
is
expose
an
api.
E
E
Access
as
user
as
user-
and
this
is
all
standard-
is
exactly
what
you
do
and
according
to
the
instructions
of
course,
you
should
put
better
descriptions
in
here,
but
you
just
need
to
add
that
I
need
to
add
the
two
client
applications
that
we
need
for
an
ssl
tab.
That's
two
guides.
You
need
to
know
or
copy
paste,
which
I
prefer
there's
too
many
goods
in
my
head.
So
I
copy
paste
and
let's
do
that
and
do
the
so.
E
The
one
is
for
the
desktop
and
mobile
application
and
one
is
for
the
web
application
for
teams.
So
let's
take
the
second
here
as
well
copy
paste.
I
know
it's
boring
to
see
copy
paste,
but
the
virtual
machine
and
docker
file,
et
cetera,
is
spinning
up
in
the
background.
So
I'll
take
the
time
to
do
this.
E
So
now
I
know
it's
all
set
here,
except
by
the
uri
which
I'll
take
in
a
bit.
Then
I
need
to
assign
some
permissions
to
this
one
and
that
we
do
the
default
permissions
that
we
need
for
an
sso
tab.
Let's
delegate
the
permissions,
it's
email,
offline
access,
open
id
and
profile.
So,
let's
choose
them
and
for
the
second
part
of
the
demo
we
will
need
the
presence
as
well.
So
we'll
add
that
one
presence
read,
add
permissions
and
to
make
everything
simpler.
E
I
grant
admin
consent
directly
now,
so
we
don't
have
to
do
that
later.
So,
essentially,
my
app
is
up
and
running
already
and
hopefully,
if
we
switch
back
over
to
my
code
space
now,
the
code
space
is
actually
set
up,
but
in
the
browser
I
have
vs
code
and,
as
you
can
see
as
well,
let
me
zoom
in
a
bit.
E
E
E
So
this
is
the
cool
part
of
this,
so
this
docker
container
that
we
actually
have
running
in
the
cloud
here,
there's
no
local
installs.
I
can
actually
do
this
on
an
ipad
or
any
any
browser.
Essentially
so
it's
already
pre-installed
the
old
teams
and
the
required
utilities
for
that-
and
I
will
just
click
through
everything
here,
and
the
only
thing
we
will
configure
is
that
we
want
to
use
the
tab
here.
We
want
to
tab,
we
can
skip
the
url
that
would
be
dynamic.
E
He
generated
for
us
no
indicator,
we
give
it
a
name,
it's
configurable
in
a
team
and
yes,
I
want
to
do
azure
ad
ssl
support
for
this
tab.
The
app
id
I
can
copy
paste
it
in
here,
but
I'll
show
you
and
faster
way
to
copy
paste
those
kind
of
things
just
click
through
here.
So
my
project
is
now
scaffolded
and
it's
installing
all
the
npm
packages.
E
E
I
can
do
it
in
here
instead,
so
I
just
copy
paste
application
id
that
I
put
in
my
notepad
put
in
here
and
replace
that
one
and
let's
also
replace
this
one
and
finally,
I
add
the
tab
app
secret
here.
You
typically
don't
need
that
if
you
just
you,
do
an
sso
tab,
but
the
for
the
second
part
of
the
demo.
We
need
the
secret
as
well,
and
I
copy
paste
that
secret
that
I
have
here
see
like
that.
E
E
Like
that,
and
then
I
need
to
change
github
to
github
preview,
and
I
also
need
to
append
sort
of
the
the
the
specific
port
that
I'm
exposing
to
this
application.
Since
this
application
is
running
locally
in
the
machine
on
port
3007,
which
is
defined
up
here,
I
need
to
append
that
one
so
once
done
I'll
save
that
file
and
I'm
actually
going
to
do
turn
off
autosave
here,
that's
a
good
tip
for
you
as
well,
if
you're,
by
default
in
codespaces
autosave
is
set
to
on,
but
that's
super
annoying.
E
E
We
need
to
install
two
more
packages
for
the
second
part
of
the
demo,
so
I
go
npm
install
and
first
of
all,
I'm
going
to
install
the
microsoft
slash
teams
fx,
which
is
a
new
javascript
library
for
the
used
by
the
teams
toolkit
to
to
provide
a
better
single
sign-on
experience
to
get
access
to
the
graph
client
in
non
sharepoint
framework
solutions.
Such
we're.
Doing
in
here
where
we
host
it
ourselves,
but
also
a
server
side
component
to
do
that
exchange
of
token.
E
E
E
Well
there
it
is,
I
need
to
go
over
to
my
app
registration
and
update
that
uri
in
here,
because
if
I
don't
do
this,
the
we
will
get
single
sign-on
errors
so
now
actually
get
this
dynamic,
url
generated
specifically
for
my
code
space
in
here.
If
you
create
new,
if
you
reuse
the
application,
this
is
typically
the
only
thing
you
need
to
to
to
change
in
your
azure
id
application.
E
So
let's
go
back
to
codespaces
and
we're
ready
to
run
this
application
and
to
do
that,
we
type
gulp
code
spaces
serve.
I
run
in
debug
mode,
no
linting,
but
also
append
the
flag
called
publish
here.
That
means
it
would
automatically
publish
my
team's
application
to
the
teams
app
store
and,
as
you
can
see
here,
it's
generating
the
manifest
zipping
the
sipping
it
together,
but
then
then
it
wants
to
log
into
my
tenant.
So
you
can
see
to
sign
in
use
the
web
browser
and
use
this
code.
E
And
if
you
go
back
to
the
browser,
you
can
now
see
it's
uploaded
application
to
the
teams
app
store,
and
you
start
to
build
application,
the
client
side
and
the
server
side.
It
will
take
a
couple
of
seconds
and
once
the
server
is
up
and
running,
which
will
happen
at
any
moment
right
now,
we
need
to
do
a
small
configuration
you
can
see
on
the
right
hand
side
here,
your
application
is
running
on
port
3007
and
it's
available
by
default.
All
ports
are
private.
E
That
means
that
you
need
to
sign
in
to
them,
but
in
order
for
teams
apps
to
work,
the
this
page
has
to
be
publicly
accessible
support.
3007
here
I
right
click
on
that
one
and
make
public
and
we're
all
set,
and
we
should
be
able
to
go
into
microsoft.
Teams
go
to
the
app
store.
I
need
to
reload
it
since
I
just
published
my
app
and
sometimes
I
need
to
reload
it
twice
due
to
some
caching,
and
so
let's
see
here
my
org
pnd
pnp
demo.
That
was
not
the
right
one.
E
We
need
to
reload.
Once
again.
As
I
said,
this
is
a
little
bit
annoying,
but
that's
yeah
due
to
caching
performance,
but
you
typically
only
need
to
publish
once
unless
you
change
something
in
the
manifest
there.
It
is
pnp
demo,
765
click
on
that
one
add
to
team
pmp
setup
tab
and
we
should
have
our
tab
soon,
loading.
E
Something
is
very
slow.
Let's
go
over
here,
see
what
happened
terminal
it
download
the
config.
It
should
be
working.
Why
not?
Let's
try
again
pmp
demo
765
there.
It
is
so
now
it's
working
demo,
god
have
some
fun
with
me
and,
as
you
can
see,
there's
this
old
tab
work.
It
puts
my
name
in
here,
and
that
means
it's
actually
properly
signed
in
without
any
pop-ups
or
anything
having
me.
So
you
got
my
name
in
here.
So
that's
cool
right,
that's
fairly
standard,
but
assume
that
we
want
to
show
the
presence
in
here.
E
How
can
we
do
that
and
we
can't
do
that
with
the
normal
azure
ad
token
that
we
get
from
teamsing
sign
on?
That's
why
I
added
those
two
extra
extra
packages.
So
the
first
thing
is
that
we
need
to
add
a
server-side
implementation
of
this
and
that's
essentially
a
simple
express
router.
So
I'm
just
importing
this
a
simple
auth
router
from
the
team,
simple
auth
package.
E
I
need
to
configure
that
one.
So
I'm
not
going
to
write
all
this
code,
but
essentially
it's
you
copy
paste,
the
same
code
over
and
over
again-
and
I
just
add
it
somewhere
in
here,
for
instance-
so
I'm
adding
a
new
router
so
in
a
post
to
auth
slash
token
we'll
go
to
the
simple
auth
router
and
configure
it
here
with
the
different
dnv
variables
that
I
configured
previously
press
dot
read
and
my
tenant
id.
E
We
can
click
save
and
that
will
actually
recompile
the
backend
for
us
and
let's
go
over
to
the
that,
doesn't
do
anything
to
the
tab
that
we
just
saw.
So
if
we
go
over
to
our
client
side
and
to
the
react
component
that
for
the
tab-
let's
first
add
our
present
in
here
as
the
state
presence
set
press
presence,
equals
use
state
of
type
string.
E
Since
I
said
we
can't
call
directly
into
the
graph,
we
don't
have
the
graph
client
or
anything
in
here
and
what
we
do.
That
is
with
the
help
of
that
microsoft
teams
fx
component,
so
I'm
just
gonna,
do
an
import
like
that
and
then
I'm
gonna
copy
paste
some
more
here
and
that's
the
same
kind
of
thing
here
you
copy
the
page
the
same
thing
over
and
over
it's
in
there
read
me
documentation
how
to
do
that,
but
essentially
it's
a
couple
of
lines.
E
First
of
all,
we
load
the
configuration
for
my
back
in
the
simple
oauth,
the
back
back-end
endpoint,
with
the
tab
up
id
the
uri,
the
tenant
id
and
the
end
point
essentially
the
the
web
server.
We
get
this
from
based
on
that
configuration.
I
can
create
the
team's
user
credential
and
it's
just
creating
like
this.
Then
I
can
get
the
microsoft
graph
client
by
using
teamsfx.create,
microsoft's
graph
client
passing
in
the
credential
and
then
pressing
dot
read
all
the
scopes
that
I
want.
E
E
So
the
reason
I
think
these
co-spaces
are
really
cool.
I
can
talk
about
that
while
we're
rebuilding
here
is
that
I
can
make
these
applications
super
fast
and
hopefully
within
15
minutes,
as
we
do
here
essentially
have
something
up
and
running
test
that
and
validate
that
and
then
once
I'm
done,
I
can
just
throw
this
one
away
and
start
over
again.
If
you
want
to
keep
it.
E
So
let's
go
over
to
this
one
here
and
let's
reload
our
tab
and
let's
see
what
happens
so,
I'm
available.
It
says
here
and
if
I
go
in
here
and
change
my
presence
to
busy
and
it
again,
it
will
actually
show
that
I'm
busy.
So
that's
super
wet
easy.
In
50
minutes
we
created
a
new
teams,
tab
deployed
it.
We
added
graph
capabilities
to
it
and
one
when
I'm
done
like
this,
I
can
just
go
in
here.
A
E
But
I
I
needed
to
add
that
extra
thing
in
there
and
there
with
the
singer
song.
I
think
this
is
super
useful
and,
as
I
said,
it's
been
extremely
convenient,
making
those
one-off
demos
you
want
to
test
something
out
or
install
new
libraries,
and
you
don't
want,
pollute
your
whole
machine
or
wsl
or
whatever
you
have
right.
So
I
think
this
is
perfect
for
those
tests
and
demos.
A
D
So,
let's
start
through
what
we
had
was
an
idea
starting
in
march
2022
at
the
beginning
of
the
pandemic,
our
sharepoint
and
teams,
individual
development
projects
were
going
a
little
bit,
not
not
so
smooth.
So
I
didn't
want
to
to
put
my
colleagues
into
short-term
working,
so
we
decided
hey,
let's
build
an
an
app
for
the
app
store
and
learn
something
and
yeah
what
the
basic
idea
was.
We
looked
through
the
microsoft
teams,
new
devices
and
in
the
top
10
there
was
the
support,
hashtag
functionality
and
we
thought
hey.
This
sounds
cool.
D
D
We
planned
our
texture
and,
of
course
we
need
some
something
to
save
and
stuff
like
that.
So
we
need
some
some
asia
in
the
background
and
we
planned
our
authentication
so
yeah.
Meanwhile,
we
put
it
also
on
on
the
market
to
test
it.
We
presented
to
existing
customers
and
we
put
some
some
cat
node
on
our
website
to
get
a
little
bit
feedback.
What
others
think
about
this
functionality
and
yeah.
The
idea
was
good
and-
and
we
gave
it
a
try
and
started
the
development
and
had
a
few
consumptions
about
it.
D
So
we
started
with
the
principle
of
leads
privilege,
because
we
we
know
that
it's
a
big
issue
when
you
install
something
from
the
store.
It
should
be
yeah
at
least
privilege
and
stuff,
like
that.
So
we
tried
to
to
fight
here
as
freeze
as
possible
to
this
day.
We
want
to
use
our
whole
default
in
order
to
learn
here
for
deployment
and
stuff
like
that,
because,
as
I
said
before,
we
were
only
individual
project
development
and
therefore
yeah.
D
We
also
put
everything
into
devops,
but
we
wanted
to
put
here
the
whole
development
to
staging
and
production
to
the
asia
into
devops
that
we
can
really
yeah
have
a
smooth
deployment
from
new
functionalities
and
stuff
like
that
yeah
then
we
also
looked
at
the
date
step
and
the
adaptive
card
development,
of
course,
because
we
also
only
put
this
in
the
in
the
individual
projects
and
yeah.
Of
course,
we
used
here
the
fluent
ui
and
stuff
like
that,
and
then
also
we
did
our
homework
with
the
ether
architecture
and
stuff
like
that.
D
D
So
this
was
a
result,
as
we
were
known
from
our
individual
development
projects
and
thought
hey
come
on,
let's
put
it
in
the
store,
it
should
be
quite
easy
and
we
started
with
the
documentation
and
found
out
come
on.
That's
not
that
easy,
as
we
thought
we
put
it
on
our
wiki
and
and
created
work
items
based
on
it
and,
as
you
see
on
the
right
side,
yeah,
it
was
nearly
more
work
items
for
for
the
publishing
process
than
for
the
the
building
of
the
app
itself.
Yeah.
D
As
as
I
said,
we
are
not
a
product
company,
we
are
an
individual
development
company,
so
we
had
to
learn
heroes,
a
lot
and
it
took
us
a
really
long
time
for
finishing
yeah
the
whole
things
about
screen
jobs
and
marketing,
material
and
and
stuff
like
that.
So
we
did
hear
a
quite
hard
head
here,
a
quite
hard
time.
D
But
the
basic
problem
was
the
broken
functionality
and
the
broken
functionality
was
that
we
have,
of
course,
a
message
extension
to
to
taxes
and
also
we
of
course
also
used
your
teams
and
stuff
like
that.
To
put
it
in
and
created
the
money
says,
but
we
missed
one
thing
that
we
have,
of
course,
and
compose
extension
and
and
another
one.
D
C
D
Also
again,
there's
four
failures,
also
something
in
the
in
the
manifest,
but
also
again,
some
broken
functionality,
wonderful
and
yeah.
What
problem
was
here,
of
course,
microsoft
tried
it
out
everywhere
and
we
didn't
yeah
thought
about
this
yeah
honestly,
because
for
us
was,
it
was
clear.
We
have
only
draft
api
functionality
to
to
search
messages
in
teams,
channels
and
stuff
like
that,
but
not
in
private
channels
or
in
private,
chats
or
group
chats.
D
So
it
was
clear
that
our
functionality,
our
message
extension,
is
not
useful
in
a
in
a
in
a
private
channel,
but
yeah
is,
of
course
also
there
and
microsoft
tried
it
out
and
we
failed
all
the
grades
for
it,
because
we
showed
some
some
menu
that
it's
not
working
in
a
private
channel.
But
what
we
also
forget
again
was
the
settings
dialogue
and
this
course,
as
you
see,
also
the
settings
they're
a
lot
displayed
blank
because.
F
D
The
context
is
different
and
we
have
no
context
there
for
showing
the
tabs
or
the
text
to
grade
for
this
in
in,
in
this
case
yeah
so
yeah,
we
we
failed
again
and
yeah.
That's
that
was
was
not
cool
yeah
and
then
we
set
back
a
little
bit
and
once
it's,
of
course
we
could.
We
very
easily
put
it
again
in
the
manifest
and
and
submit
it.
D
Unfortunately,
we
have
missed
this
because
we
were
too
enthusiastic
to
get
it
into
the
store.
So
then
we
started
the
real
work
with
the
team,
submission
team
and
yeah.
We
had
a
half
hour
presentation
with
them
and
showing
them
everything,
and
then
they
reached
us
again
with
and
of
course
they
make
a
recording
on
it
and
they're,
showing
this
also
to
the
other
team
members
and
to
get
us
back
with
some
more
detailed
information.
What
we
should
do
and
what
we
should
fix
and
yeah.
D
We
worked
really
hard
on
it,
this
for
better
description
and
for
some
graceful
error
messages
and
also
created
new
logo,
and
I
want
to
show
you
what
microsoft
is
really
doing,
how
far
they
are
going,
and
this
is
really
good
for
us,
because
yeah
they're
doing
here
really
and
a
great
job
to
help
us
for
well.
I
only
can
talk
from
from
our
side,
because
we
are
some
individual
development
company
to
get
here,
really
the
the
focus
on
a
product
and
really
to
see
yeah.
D
What
what
on
what
things
we
should
consider
yeah
and
the
for
example.
They
even
look
on
our
website
for
the
privacy
statement
and
the
terms
of
usage
and
compared
the
the
team's
tag
team
logo
with
the
logo
from
our
website
and
asked
hey.
This
looks
not
a
nice
user
experience.
This
looks
a
little
bit
different
and
so
yeah.
D
You
also
found
to
to
issues
on
android
and
ios
devices,
and
happily
we
could
also
help
microsoft
to
find
a
bug
or
to
to
to
fix
something
on
the
on
the
android
device,
because
we
have
some
deep
linking
from
from
our
message
from
our
message
card
to
to
the
tab,
and
this
was
not
working
in
android
and
yeah.
We
found
out
this.
This
is
really
some
some
issue
on
the
on
the
mobile
platform
and
microsoft
already
fixed
this,
and
so
we
could
move
on
and
yeah.
D
Happily,
we
made
it
to
the
store
around
two
months,
two
months
later
and
yeah.
I
want
to
share
some
lessons
learned
what
what
from
our
side,
but
we
have
learned
that
we
should
consider
this
submission
checklist
from
the
beginning,
of
course,
because
there
are
very
helpful
insights,
for
example,
with
this
yeah
clicking
everywhere
and
doing
everything
and
and
and
consider
what
the
user
is
really
doing.
Not
what
what
the
developer
is
wants
him
to
do
so
to
say
think
about
the
extension
points.
D
But
at
the
first
time
mission
we
we
basically
missed
the
the
client
functionalities.
So
we
yeah
have
included
this
now
and
yeah.
We
first
were
really
afraid,
because
we
had
a
lot
of
of
errors
in
it
in
the
in
the
asia
application
inside,
but
we
found
that
out
that
this
is
coming
from
some
robots
which
are
using
to
try
to
to
sign
into
wordpress
and
stuff
like
that.
So
yeah,
don't
don't
be
afraid
of
these
errors.
D
Sometimes
they
are
not
that
bad
yeah,
yeah
and,
of
course,
as
I
already
talked
about
it
after
the
episode
publishing
the
work
is
not
over
especially
to
consider
what
what
people
are
really
using
or
not,
with
the
application
inside,
it's
really
helpful
and
so
yeah.
Currently,
we
are
thinking
what
to
go
on.
As
we
said,
we,
this
is
free
and
we
we
wanted
to
put
this
for
the
for
the
community
yeah.
We
are
considering
how
to
that.
D
We
maybe
also
put
it
on
github
and
stuff,
like
that
or
yeah,
also
doing
a
little
bit
rework
on
it
and
yeah.
So
if
you
have
some
feedback
for
us,
please
feel
free
and-
and
also
like
I
said
it's
it's
it's
free
of
use
and
and
we
I
think
we
will
really
will
publish
it
on
there
on
the
github
for
open
source.
A
Stuff
lauren
yeah.
Thank
you
very,
very
cool.
Thank
you
as
a
mention
in
the
chat.
This
is
invaluable
information.
No
doubt
this
is
valuable
for
everyone.
That's
looking
to
get
into
this
space
and
you
provided
that
exposure.
So
thank
you.
Next
up
is
annie
kalana
from
microsoft,
getting
started
with
microsoft,
graph
tag,
api
for
managing
microsoft
teams,
tagging
so
annie.
Please
feel
free
to
take
over
the
chat.
H
Okay,
all
right
thanks
david,
so
it
was
great
kind
of
getting
getting
to
look
into
what
florian
had
developed,
because
I
think
that
this
is
kind
of
a
different
flavor
of
something
that's
quite
similar
with
the
tags
that
we're
talking
about
are
people,
centric
tags
and
the
goal
of
those
tags.
I
just
want
to
give
a
little
bit
of
background
before
we
go
ahead
and
jump
into
the
apis.
H
The
the
goal
of
tags
is
to
have
you
quickly
reach
a
group
of
people
within
a
team.
So
what
it'll?
Let
you
do
is
kind
of
categorize
people
based
on
the
organizational
knowledge
that
you
have,
and
that
could
be
something
like
a
a
role
which
is
something
that's
really
popular
with
our
industry
customers,
because
oftentimes
the
the
titles
in
azure,
don't
really
reflect
how
people
do
their
jobs,
also
projects
or
if
people
have
a
specific
certification.
H
It's
helpful
to
be
able
to
know
that
about
people
within
a
team
and
then
once
tags
are
set
up,
you
can
actually
at
mention
them
in
a
channel
or
you
can
use
them
to
start
a
chat
and
then
I'll
just
run
two
quick
videos
of
showing
you
how
to
go
ahead
and
set
up
the
tag.
So
within
teams
you
just
click
on
the
dot
dot
next
to
the
team
and
then
do
manage
tags
and
it'll.
Take
you
into
a
menu,
and
here
you
can
see.
H
I've
got
a
couple
tags
already
configured,
but
if
I
want
to
go
ahead
and
create
a
team
say,
for
example,
I'm
the
I.t
admin,
but
for
some
reason
everybody
always
reaches
out
to
me.
Instead
of
the
entire
team,
I
would
want
to
create
potentially
a
tag
for
the
it
team.
So
then,
that
way,
when
people
go
ahead
and
reach
out
to
the
it
team
that
they're
not
just
pinging
one
person
and
then
pinging
the
next
person,
they
can
just
kind
of
get
everyone
in
the
group.
So
the
other
way
that
we
think
about
it.
H
It's
kind
of
like
a
shortcut
at
mentioning
a
bunch
of
individuals,
but
a
shortcut
for
people
who
may
often
struggle
to
remember
all
of
the
members
of
her
project
team.
So
then,
if
I
am
megan
for
example,
and
I
want
to
go
ahead
and
let
the
it
team
know
about
something,
I
can
kind
of
use
the
tag
that
was
set
up
by
the
itt
team
and
just
kind
of
mention
them
within
a
channel
post.
And
then
what
happens
is
the
it
team
will
go
ahead
and
get
a
notification
and
then,
as
a
user.
H
If
I
see
a
tag
in
a
channel
post,
I
can
hover
over
it
and
understand
who
the
members
are
and
then
there's
also
that
option
to
to
start
a
chat
with
that
tag.
But
I
can
also
do
that
from
the
new
chat,
the
new
chat
menu.
If
I
want
to
start
a
chat
with
all
the
product
managers,
I
can
type
out
product
and
then
it'll
automatically
expand
to
the
members
of
that
tag.
H
If
you
have
company-wide
teams
or
large
teams,
in
addition
to
that,
if
there's
a
cross-functional
project
team,
where
you
want
to
kind
of
categorize
a
group
with
attributes
and
variables
that
are
really
outside
of
what
you
would
know
about
a
person,
that's
another
good
instance
to
create
a
tag
and
then
the
other
reason
is
to
identify
an
expert
or
an
owner,
and
you
know
that's
that's
a
for
example.
We
actually
use
that
in
our
team
to
contact
the
legal
expert
and
all
right.
H
Within
an
organization
people
join
teams,
leave
teams,
so
keeping
membership
up
to
date
is
something
that
can
be
a
little
tedious
and
then
the
third
thing
is
that
the
data
that
people
actually
want
to
create
tags
for
often
exist
in
another
system.
So
one
of
the
things
that
our
customers
are
really
eager
to
do,
and
you
know
we
hope
that
there
will
be
on
this
call.
H
A
Excellent,
very
cool
annie,
thank
you,
and
it's
like
we
planned
it
that
perfect
timing
on
that
nice
job
all
right.
Well,
we
have
the
videos
that
will
be
available,
for
this
call
is
recorded.
Thank
you
victor
florian
and
annie
for
your
amazing
demos.
Today,
exciting
stuff,
always
part
of
the
best
community
in
technology,
the
recording
will
be
available
at
aka
dot.
Ms
forward
slash,
m365
pnp
forward,
slash
videos
you
can
subscribe
to
that.
Follow
us
on
twitter
at
microsoft365,
dev
or
m365pnp.
A
Our
next
general
dev
call
will
be
two
weeks
from
today
july.
8Th
and
the
next
sharepoint
framework
call
will
be
july.
1St
at
7
am
remember
these
weekly
calls
or
bi-weekly
calls
are
still
going
to
be
occurring
over
the
summer.
It's
only
the
monthly
calls
that
have
been
adjusted
and
we
will
see
a
delay
until
the
end
of
august.
For
those
you
can
also
visit
the
collection
of
links
here
at
these
urls,
so
we
invite
you
to
take
a
look
at
them.
Of
course
you
can
get
to
them
all
via
aka.ms4m365
and
thank
you.