►
Description
In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, host – Vesa Juvonen (Microsoft) | @vesajuvonen and Waldek Mastykarz (Microsoft) | @waldekm are joined by Belgium-based consultant - Elio Struyf (Struyf Consulting) | @eliostruyf
The discussion focused on Elio’s experiences in dev tools development, working in Google world as opposed to Microsoft world, opportunities for Partners in Microsoft 365, developer platform allegiances, sorting garbage, and landing your new job as a result of open-source contributions.
No articles are reviewed in this week’s session that was recorded on Wednesday, May 17, 2023.
Agenda items
00:00 – Intro
01:15 – Interview
40:29 – Closing
References
• See the full blog post for this episode in the Microsoft 365 Platform Community blog at https://aka.ms/m365pnp/blog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms/community/home
A
B
B
A
Since
we
learned
2008.,
he
was
away
from
it.
He
was
doing
some
other
things
and
now
he
will
or
will
not
be
back.
That
is
yet
to
be
seen,
but
we
have
a
great.
We
had
a
great
interview
with
him
about
his
past.
Journey
has
Peak
outside
the
demise
of
space
and
I.
Think
that
you'll
find
that
interesting
too,
so
without
further
Ado.
How
about
jump
into
the
interview?
It's
right!
Let's
do
that.
Awesome.
B
With
before
we
started
recording
that
Elio
has
been
a
wave
missing
outside
of
the
Microsoft
world
for
a
while
outside
of
my
no
inside
of
Microsoft,
and
so,
but
welcome
to
the
Microsoft
rpmp
weekly
good.
To
have
you
back.
Can
we
do
a
quick
recap
on
who
you
are
and
then
let's
talk
about
what
we
meant
with
you
not
being
present
for
a
while.
C
Who
am
I?
That's
a
good
question,
still
the
same
person
for
people
that
remembered
me
for
the
people
that
don't
remember
me
or
don't
know
me
even
I'm
Elio
from
Belgium
living
near
Antwerp,
I
worked
in
the
past
as
a
Microsoft,
365,
developer,
Tech,
lead
and
so
on
and
then
stepped
outside
of
the
Microsoft
365
worlds.
C
So
I
thought
hey,
why
not
jump
on
it
and,
let's
start
building
something
completely
out
of
the
Microsoft
365
space
and
yeah
work
on
developer
tools.
So
that's
what
I've
been
doing
for
the
last
I
think
it
was
one
year
and
seven
months,
because
two
weeks
ago
my
contract
ended
suddenly,
unfortunately,
so
that's
it.
B
I
think
that's
that's,
unfortunately,
the
theme
of
the
of
it
the
year
in
many
cases
so
that
the
contracts
and
and
all
of
that.
But
let's
let's
talk
about
that
one
a
bit.
So
we
want
to
learn
it
seven
months
ago,
well,
first
of
all,
you're
you're
all
recovered
from
the
biker
crash,
because
I
know
some
people
remember
that
still
cool.
B
C
Yeah,
so
rapid,
API
or
rapid
wanted
to
be
like
an
ecosystem
for
apis.
Like
you
have
the
app
store
for
iOS
or
for
Androids,
they
had
a
store
for
apis.
They
still
do
so.
If
you
want
to
have
an
API
that
tells
you
which,
whether
it
will
be
today
or
if
you
want
to
send
messages
or
sending
emails.
It's
all
part
of
that
platform.
C
So
that's
that's
one
part
of
the
game.
Then
another
part
is
that
they
had
an
Enterprise
Hub,
which
is
basically
the
same
thing
as
they
had
publicly
available,
but
then
for
internal.
You
can
look
at
it
as
Azure
API
management,
but
a
little
bit
more
because
you
can
do
testing
you
can
do
governance,
leading
and
so
on
around
apis.
C
C
And
then
I
was
building
the
visual
studio
code
tool
and
in
two
months
I
showed
the
proof
of
concept
and
they
was
like,
oh,
but
we
have
to
we're
having
this
electron
application,
which
is
already
in
development
for
six
months,
and
it's
far
from
feature
complete
and
what
you
showed
in
this
proof
of
concept
of
two
months.
That
looks
like
the
real
tool
so
yeah
we
just
killed
electron,
and
then
we
went
forward
with
with
the
tool
in
vs
code
and
what
it
actually
did
was
testing
apis.
C
So
if
you
were
locally
creating
an
API,
you
could
just
do
a
request.
Us
to
your
API,
see
the
response.
You
can
do
batches
of
requests.
You
can
link
requests
like
if
you,
for
instance,
want
to
First
view
an
API
call
for
retrieving
a
JWT
token
and
then
using
that
JWT
token,
for
an
authentication
on
the
next
call.
That
could
also
be
performed,
and
we
were
also
building
a
lot
of
other
Cool
Tools,
like
a
testing
tool
or
a
real
tester,
like
automate
testing
inside
Visual
Studio
code,
which
was
also
linked
online.
C
C
The
API
still
needs
to
work
against
the
test
that
were
defined.
So
that's
also
something
that
we
did
like.
Okay,
then
we
built
it
in
inside
vs
codes
so
that
you
can
just
run
the
same
test
that
you
had
online
locally
to
verify.
If
everything
was
still
working
and
if
you
broke
something
you
could
then
say:
okay,
maybe
the
test
needs
to
be
updated,
because
we
were
doing
this
kind
of
updates,
which
essentially
was
going
to
break
things
out,
which
was
okay
or
the
developer
knows.
C
B
B
A
What
I
want
to
ask
you
like,
if
you
look
back
at
your
jolly
when
you
moved
into
vs
code
space
like
what
was
the
most
intriguing
aspect
of
that
job,
because
it's
way
different
than
what
you've
done
earlier
right,
like
you
worked
a
lot
of
you
know,
SharePoint
portals,
like
the
visual
aspects
and
user
aspect,
and
now
you
kind
of
moves
into
the
devtool
space
like
what
what
intrigued
you
to
go.
There.
C
You're
not
working
you're,
still
working
with
end
user,
but
all
of
a
sudden
your
end
users
become
or
became
developers
which
is
like
putting
on
a
different
hats.
You
can
talking
very
technical
terms
and
you
can
put
technical
things
inside
your
tool.
You
don't
have
to
think
about.
Oh,
this
is
an
end
user,
so
we
have
to
make
it
really
nice
and-
and
the
ux
needs
to
be
really
good
with.
C
But
developers
also
like
to
try
out
things
and
like
to
to
Beta
tests
even
more
so
yeah
I
think
we
went
or
the
the
extension
went
live
in
July
last
year,
but
before
that
we
had
a
lot
of
beta
testers
and
you
could
just
put
something
inside
the
tool
and
say:
okay.
This
is
what
it's
going
to
do
without
any
documentation,
and
you
got
feedback
from
these
developers
right,
not
saying
that
an
end
user
wouldn't
do
that.
C
But
if
it's
like
a
very
technical
tool,
then
probably
an
end
user
is
not
going
to
fully
test
it.
They
probably
say:
okay,
I,
don't
find
my
way
inside
the
product,
so
I'm
not
going
to
to
take
my
time
and
effort
in
it
fair
points.
That's
also
what
we
tried
with
this
developer,
but
we
were
like
surprised
that
they
were
like
yeah
going
for
the
extra
mile
and
really
testing
out
the
products
in
ways
that
we
weren't
thinking
about.
Oh
yeah.
This
is
something
we
can
do
as
well.
A
We
also
we're
also
involved
in
reaching
out
to
devs
in
our
Awards
like
and
if,
if
so,
is
it
as
simple
as
like
you
build
it
and
they
come.
You
know.
You
know
like
the
the
myth
that
is
there
or
is
it
like
where
you
really
like.
Did
you
have
to
take
deliberate
steps
to
find
them
convince
them
to
try
the
thing
you've,
built
and
so
forth,
and
so.
C
C
I
didn't
reach
out,
because
we
had
a
like
a
product
manager
on
top
of
that,
so
he
reached
out
and
he
started
to
talk
with
these
people,
but
we
even
had
design
sessions
with
some
of
these
people
on
okay.
How
would
you
use
this?
How
would
you
use
that?
How
do
you
see
things
combined
together?
Because
in
the
end
we
were
thinking
the
if
you
start
online
in
the
web
browser?
C
C
Okay,
this
is
something
I
can
understand,
not
saying
that
they
were
all
feature
complete
or
all
in
feature
parity
with
each
other,
because
I
I
always
believe
that
that
shouldn't
be
the
case,
because
you're
going
to
do
things
in
vs
code
that
you're
not
going
to
do
in
a
Mac
OS
application
or
on
your
browser.
So
there
will
sometimes
be
more
features
in
vs
code
than
there
are
in
the
browser
and
somewhere
else
so
yeah,
but
at
least
you're
yeah.
If
you
were
doing
requests,
you
want
to
do
the
same
requests
online
as
in
vs.
A
Code,
so
API
being
just
you
know,
a
part
of
a
part
of
a
bigger
ad
that
follows
built
to
what
extent
had
you
take
into
account
the
end-to-end
flow
of
the
overall
work
and
your
place
in
that
versus?
No,
no,
like
we
build
this
tool,
we
only
look
at
our
part
and
we
don't
really
care
if
people
use
us
in
JavaScript
or
some
framework
or
in
Ruby
or
in
go.
C
But
that's
already
one
step
further
in
the
game,
because
if
you
go
back,
you
have
two
types
of
people
or
developers
that
are
going
to
use
the
tool
and
that's
like
an
API
consumer
and
an
API
Creator
and
the
API
consumer
is
pro.
It
can
be,
for
instance,
a
front-end
developer,
calling
the
Microsoft
graph
getting
data
back
in
order
to
know
okay.
This
is
a
data
set
that
I'm
getting
back
so
now
with
these
data
sets,
I
know
what
to
do
for
building
the
UI,
the
API
Creator
Works
differently.
C
They
start
with
building
an
API,
so
they
are
probably
going
to
do
localhost
development.
So
they
want
to
check
what
I
write
right
now.
Is
this
going
to
still
response
in
in
a
correct
response,
or
is
this
going
to
fail
and
and
whatsoever?
So
we
always
thought
about
these
two
profiles.
We
want
to
support
both
of
these
profiles.
Yeah.
A
Yeah
interesting
gives
a
little.
You
were
a
part
of
the
n365
space
for
a
long
time.
Long
time,
I,
don't
know
2006,
seven
ish.
When
you
started
eight
there,
you
go
right,
so
we
see
like
way
back
when
right
and
at
some
point
you
changed
your
scope
of
work
to
things
like
view,
vs
code,
extensions
and
all
that
what
were
like
top
of
Mind
What
were
what
was
the
biggest
change
that
stroke.
You
like
going
from
the
n365
world
into
a
bigger
Dead
Space.
It.
C
I
think
the
biggest
change
was
going
from
Microsoft
365
over
to
Google
space,
so
development
is
still
development,
so
I
I
was
already
creating
a
lot
of
these
extensions.
So
I
already
knew
what
extension
development
was
going
to
be.
So
it's
also
because
of
creating
front
matter
all
right,
which
is
a
CMS
extension
for
vs
code.
It's
because
of
that
extension,
and
because
of
the
traffic
that
was
coming
to
that
extension,
Rapids
was
aware
of
hey.
This
person
is
building
extensions.
C
So
let's
talk
to
this
person,
that's
how
I
got
into
rapid,
so
so
also
a
good
side
way
of.
If
you're
doing
open
source
work,
you
can
actually
find
a
job
with
it,
because
people
are
looking
at
you
and
and
looking
at
what
you're
building.
So
it's
also
good
to
share
inside
the
community,
so
you
will
never
know
what
happens
so.
B
C
The
biggest
difference
is
Google
builds
things
where
you
have
100
feature
completeness
where
Microsoft
is
really
good
at
building
tools
that
are
not
always
like
feature
completes,
but
they
have
like
a
tool
for
doing
whiteboarding,
so
you
can,
or
Microsoft
can
say
if
you
want
to
have
a
whiteboard,
just
open
the
Whiteboard,
and
you
can
start
putting
thoughts
on
the
Whiteboard
in
Google.
You
don't
have
that
in
Google
they
say.
Okay,
we
have
a
good
mail
client,
we
have
a
good
calendar,
we
have
a
good
whatever,
but
we
don't
have
a
whiteboard.
B
C
Necessarily
wrong,
but
the
biggest
issue
is
when
there
is
no
governments
around
all
these
tools
and
a
really
good
example.
Just
before
I
was
laid
off
two
weeks
before
I
was
in
Berlin
and
we
were
actually
talking
about
okay.
How?
What
are
we
going
to
do
this
year
next
year?
An
hour?
Are
we
going
to
divide
our
developers
in
in
inside
silos
or
not?
C
Six
different
tools
were
used
and
then
I
thought
look.
This
is
the
biggest
problem
inside
the
Google
space.
You
don't
have.
You
can
still
have
that
in
Microsoft
uses,
some
people
will
use
OneNote.
Some
people
will
use
PowerPoint.
Some
people
will
use
a
whiteboard,
it's
still
inside
Microsoft's
there.
It
was
Miro
gem,
fake
Jam,
excali,
draw
and
and
three
other
tools
that
I
never
heard
of
and
still
until
the
very
last
day
there
were
every
week
there
was
another
tool
that
I
thought
hey
yet
again.
C
A
I,
don't
know
it's
in
some
tool
where
you
don't
have
the
access
to
because
it's
in
that
tool
and
they
govern
the
access
management
to
it.
So
you
need
to
have
an
account
there
and
you
need
to
be
explicitly
added
because
they
don't
have
the
notion
of
a
team
because,
like
it's
outside
your
horror
parameter.
So
it's
an
interesting
challenge
for
sure.
Now
how.
C
Do
you
also
have
a
lot
of
yeah
I
just
wanted
to
say,
like
there's,
there's
a
couple
of
integrators
like
OCTA:
they
integrate
all
these
applications,
so
we
had
an
application
dashboard,
but
then
still,
if
you
were
going
to
use
another
tool
that
was
not
in
that
dashboard
yet
or
in
the
catalog,
yes
yeah
you
needed
to
tell
them,
but
then
it's
coming
into
that
dashboard.
Only
for
you
not
for
the
rest
of
the
people,
so
they
still
need
to
request
access.
So
yeah
I.
B
A
A
Well,
but
if
even
then,
all
right,
even
if
you
think
about
okay,
like
we
will
use
AED
for
for
SSL,
but
then
we
will
use
all
the
different
tools
where
the
data
is
stored
there,
especially
if
these
are
Cloud
tools,
you
won't
have
a
file
to
store
within
the
tenant.
You
will
have
data
stored
in
an
app
and
unless
you
know
but
like
it
will
not
come
back
in
search,
it
will
not
come
up
anywhere.
B
Right
so
you
will
still
have
calling
out
the
Crasher.
80
is
one
of
those
things
which
are
a
bit
different
than
Google
world
and
in
the
in
the
Microsoft
world,
because
everything
circles
around
Azure
ad
and
quite
often
well
at
least
I
I-
have
a
Windows
hello,
I,
just
tap
the
keyboard
and
both
I'm
in
and
I.
Could
access
on
everything
I
didn't
need
to
worry
about
I.
B
B
B
Related
on
that
one,
you
said
earlier
something
interesting
related
on
the
on
the
Google
and
and
basically
the
the
one
of
the
big
comparison
is
the
right
thing
to
say
that
Microsoft
has
more
offerings
for
Microsoft,
365
customers
and
basically
we
have
a
lot
of
lot
of
out
of
the
like.
You
know
from
Microsoft
as
a
first
party
experiences,
and
is
that
and
in
Google
it's
more
a
partner
opportunity,
but
then
is
that
about?
Is
that?
Does
that
mean
that
in
the
Microsoft
world
there's
no
partner
opportunities?
C
There
are
still
partner
opportunities
for
sure,
and
it
it's
just
creating
the
edit
offering
like
an
intranet
like
teams,
tools
and
so
on.
So
you
also
see
that
in
Google
or
like,
for
instance,
in
slack
that
you
need
to
do
these
things.
So
there's
always
the
needs,
and
there
is
always
like
an
opportunity
for
a
partner
to
build
that
kind
of
tool
to
better
do
some
thing,
which
is
a
problem
to
solve
that
problem.
A
You
mean
like
that
to
you,
you
build
to
keep
track
of
the
content
across
the
different
things,
yeah,
absolutely
that
was
really
brilliant.
That
was
there's
there's
one
thing
that
I
need
more
than
anything
else.
It's
just
that
like
there's,
there's,
as
you
say,
like
five
ways
to
do
everything.
How
do
I
keep
track
of
all
of
that?
It's.
C
It's
even
I
I
thought
it
was
a
requirement
to
have
in
in
Microsoft
and
the
moment
I
started
to
work
in
Rapid.
It
was
like
okay,
I
even
needed
more
insight.
A
Google
space
because
it
was
yeah
searching,
was
so
so
hard.
It's
like
all
the
chats
happened
in
Slack
and
then
yeah.
It's
like
searching
in
in
teams
I,
don't
know
how
it
is
today,
but
two
years
ago
it
was
horrible.
C
So
same
thing
in
slack,
so
messages
are
it's:
it's
just
a
data
dump
and
you
don't
find
anything
in
the
data
anymore,
but
then
it
could
also
be
that
you
have
it
on
Google
and
then
you
needed
to
search
there
and
and
that's
what
some
lies
in
Microsoft,
that
you
can
just
hit
that
search
bar
and
start
looking
and
you
get
files
you
get
chats.
You
get
all
of
these
things.
I
was
advocating
for
for
Microsoft
teams,
because
I
wasn't
aware
that
I
was
going
to
miss
it.
C
So
much
and
one
funny
fact
was
we
had
a
couple
of
Microsoft
people
or
old
Microsoft
people
and
we
started
to
work
in
a
Microsoft
way
inside
slack.
So
slack
still
works
with
just
conversations.
Yes,
you
have
threats,
but
in
order
to
start
a
threat,
you
need
to
reply
on
something.
So
what
we
talked
about
was
if
we
want
to
have
people
really
replying
to
the
threat.
You
need
to
start
making
the
threat.
So
we
first
write
the
title.
Then
we
press
enter
and
then
we
started
to
write
the
content
inside
it
as.
A
C
A
C
B
C
C
That's
like
Microsoft
did
that
and
and
the
first
time
that
I
said
oh,
but
this
is
something
we
can
do
in
Microsoft
teams,
because
you
have,
for
instance,
a
channel
and
then
you
can
put
your
documents
in
a
channel,
so
we
create
a
team
Channel
and
then
everything
is
in
that
because
we
were
still
thinking
about.
How
can
we
share
our
content
because
we
had
it
in
Google
Docs
and
then
we
edited
notion
and
now
we
end
it
on
slides
so
already
three
different
systems.
C
B
C
It
was
not
a
fight
that
I
wanted
to
go
into
and
in
the
end
I
just
said
look.
This
is
what
we
need
and
then
they
always
kept
saying.
Oh
yeah
stop
with
Microsoft
themes.
I
hadn't
set
Microsoft
teams.
I
just
said
this
is
what
we
need,
because
this
is
what
is
missing
and
they
always
filled
in
Microsoft
teams,
but
it's
funny
because
they
they
knew
that
Microsoft
teams
could
do
it,
but
still
the
it's.
A
B
So
if
we
think
about
the
companies
and
all
of
that
there's
a
lot
of
this
historical
package,
especially
Microsoft,
obviously
has
the
historical
package
of
things.
What
happened
in
nine
days
and
early
2000s
and
even
2010s?
Well,
I,
don't
but
anyway,
at
some
point
it
changed
it's.
It's
been
an
interesting
to
see
that's
closely
happening
within
a
company,
but
same
actually
the
same.
B
A
B
A
But
it's
also
I
think
I.
Think
the
background
right
like
like
you
can
imagine
like
you
imagine
that
at
some
point
you
were
a
company
at
a
I,
don't
know
two
or
five
and
like
sharing
a
file
was
not
a
thing
because
you
didn't
have
a
file
so
like
two,
like
slacks
I
mean
like
I
use
slack
for
a
long
time.
The
first,
my
first
experience
with
teams
was
like
I
I.
Couldn't
like
I,
couldn't
wait.
A
How
can
we
get
off
teams
back
to
slack
yeah
because
back
then,
and
it
was
really
early
on
and
it
was
really
bad
compared
to
just
like,
like
you
was
just
like
Lightning
Fast
right,
so
that
was
my
first
experience
and
back
that
we
didn't
need
anything
else
like
Chad
was
just
enough
and
we
had
then
back
then
we
would
use
zoom
for
calls
and
it
just
works
perfectly
fine,
as
the
company
evolved.
It's
exactly
as
you
say
we
needed
to
do
this.
We
needed
to
do
that.
A
We
needed
a
few
more
things
and
that
and
then
it
becomes
a
bolt-on.
How
can
we
tie
together
these
five
different
things
that
are
that
haven't
been
built
to
work
in
in
at
tandem,
and
then
it
becomes
really
hard
because
you
need
to
like
shoestring
them
like
how
can
I?
We
can
do
this
and
you
can
make
it
work,
but
it's
not
optimal
because
it
was
never
meant
for
that,
and
then
you
start
at
a
comparison
like
well.
A
We
can
it
just
works
in
teams,
but
if,
if
you
depart
from
tool
that
does
like
a
very
TurnKey
thing,
optimized
for
one
specific
case
with
everything
else
that
we
do
sure
like
you
know
like
how
often
do
we
get
the
comments
like
it's
not
crafted?
It's
not
this.
It's
not
as
polished.
Well,
maybe
maybe
not,
but
it
all
depends.
What
is
it
that
you
need
exactly
if
you
need
this
one
specific
thing
for
this
one
specific
case
sure
there
are
tools
optimized
for
exactly
that.
B
A
A
C
A
B
B
But
it's
it's
yeah!
It's
it's
interesting
to
see
the
well,
especially
in
the
teams
just
coming
and
close.
Maybe
closing
these
teams
threat
in
here
discussion,
but
it's
interesting
to
see
how
mature
it
has
grown
to
be
so
and
and
of
course,
the
first
impressions
and
I
the
the
funny
advertisements
in
New,
York
Times
or
whenever,
where
people
are
welcoming
competitors-
and
you
know
all
of
that
stuff-
it
looks
pretty
awkward
at
this
moment
of
a
time.
But
it's
it
it's
it's
surprisingly
good
and
reliable.
We're
even
recording.
B
That's
actually
people
right,
that's
actually
a
really
good
point
as
well,
because
people
quite
often
what
happens
when
I
talk
about
the
Microsoft
12.
It
says
yeah,
but
Microsoft
is
not
in
the
the
consumer
space.
They
tried
all
of
these
social
things
and
it
all
fails
and
everything
like
that,
which
is
like
that's
true,
but
have
you
ever
checked
details
on
what
happens
in
the
business
world
and
in
the
in
the
actual
Enterprise
world
or
the
mid-size
mean
small
mid-size
market
and
when
you
go
there
and
you're
no
longer
just
a
a
student,
it's
like.
A
B
The
education
part
is
interesting
because,
of
course,
all
of
the
little
large
companies
in
a
in
their
good
will
offer
this
at
their
services
and
products
for
free
for
education
purposes,
and
then
the
schools
need
to
pick
and,
and
it's
a
really
weird
process
on
how
they're
picking
you
know
which
which
one
to
choose
in
which
city
and
yeah
it's
with
my
kid
within
the
past,
what
I
said
five
to
six
years
already
in
school,
we've
been
using
Google
Hangouts
teams,
and
it's
like
it's
like.
Okay.
A
C
B
B
Let's,
let's
actually
talk
about
a
bit
about
how
do
you
coming
back
on
the
partner
opportunities
and
the
and
the
things
what
we
can
do
within
the
Microsoft
trades
is
the
five
and,
of
course
you
have
your
precious
ideas
and
all
of
those
which
you
don't
want
to
share.
But
how
do
you
see
that
Microsoft
race
is
quite
well
to
evolve,
for
partners
and
and
what
are
the
things
and
to
come
any
any
tips
and
considerations
how
Partners
should
be
approaching
Microsoft
3
is
Justified
all
right,
so
it's
not
like.
No.
No.
C
There
are,
there:
are
some
secret
songs,
I
think
it
just
if
you
have,
if,
if
you
see
a
problem
and
most
of
the
time,
it's
something
you
see
yourself
and
start
talking
with
other
people
and
then
that's
how
I
got
into
scroll
with
hey
I.
Have
this
problem?
Do
you
have
this
problem
as
well?
Oh
you
have
it,
you
have
it.
You
have
YouTube
yeah
start
looking
at
how
you
can
start
integrating
it
inside
of
Microsoft
space
and
I.
C
As
I
said,
Microsoft
is
pretty
open
for
sure
now,
with
Microsoft
graph
being
the
one
API
to
call
and
to
be
calling
all
other
services,
not
when
we
were
doing
the
things
that
we
did
in
the
past,
like
Mina
weldick
on
SharePoint
and
then
calling
into
another
service
and
another
service
and
taking
care
of
so
many
different
authentication
layers
and
so
on.
It's
way
more
easier,
so
it's
you
can
build
inside
Microsoft
or
you
can
build
outside
of
it,
but
still
connect
it
and
I.
Think
as
a
partner.
C
You
have
both
of
these
opportunities
like.
If
you
run
to
really
tightly
couple
your
applications,
you
can
do
so,
but
then
you
always
need
to
be
aware
of
yeah.
Microsoft
can
also
do
breaking
changes
to
your
apps
if
you're
two
couples,
if
you're
going
to
decouple
yourself
but
then
say:
okay,
go
to
this
external
websites
because
that's
where
our
app
lives,
that's
also
something
I
hear
from
or
I
heard,
from
a
lot
of
Partners
and
from
a
lot
of
customers.
C
Then
it's
not
a
Microsoft
tool,
anymore
yeah
and
then
it's
like
a
other
tool
and
then
it's
very
hard
to
convince
people
to
use
that
tool.
Yeah
I've
been
in
a
couple
of
meetings
the
last
couple
of
weeks
with
with
customers
from
a
company
I'm
not
going
to
talk
about,
and
that
was
one
thing
that
they
mentioned,
that
this
is
for
them
it's
a
no-go
when
something
is
outside
of
the
Microsoft
world
and
only
allowing
you
to
use
your
Microsoft
login.
C
C
I
can
only
say
that's
that
it
would
work
much
better
for
me
again
than
how
it
was
working
in
Microsoft
or
in
in
slack,
so
I
haven't
been
using
Microsoft
teams
for
a
long
time
now,
just
for
chatting
with
you
guys
and
for
for
doing
other
follow-ups
and
for
some
meetings
but
yeah,
it's
it's
already
way
more
better
than
than
what
it
is.
What
I
was
using
in
Rapid
like
well
like
mentioned
Zoom.
C
C
One
good
thing
about
Microsoft
teams:
it's
that
it's
combining
all
of
it
and
it's
giving
you
the
opportunity
to
chat,
to
call
to
plan
meetings
to
integrate
your
own
applications
so
and
there's
probably
for
partners
a
lot
of
opportunities
to
to
extend
their
own
applications
inside
Microsoft
teams
as
well.
Yeah.
B
Cool
I
guess
we're
running
out
of
time,
so
we
need
to
stop
again
the
discussion.
There
would
be
a
lot
of
things
to
talk
about
I.
Guess,
that's
it
for
now.
Thank
you.
Ilya
joining,
really
really
cool
to
catch
up
good
to
have
you
back
on
the
Microsoft
365
worlds,
even
though
it
wasn't
necessarily
the
plan
a
while
ago.
But
you
know
their
life
goes
Life,
Changes,
exactly
exactly
so
we'll
good
to
have
it
back
anyway
and
and
we'll
see
what
you
will
start
doing
after
after
a
while.
A
B
Next
Journey
so
perfect,
very
good
thanks
Elia
and
thanks
for
joining
and
we'll
go
jump
and
closing
the
broadcast
or
the
video
with
the
mobile
deck
as
separately.
But
thank
you
for
this.
Thank
you
very
much
thanks
for
having
me
an
excellent.
Thank
you
Elio,
one
more
time
on
the
on
the
discussions
and
as
we
said
when
we
did
the
intro
no
articles
this
week.
But
let's
do
a
quick
recap:
what's
happening
next
week,
I'm
pretty
sure
that
what's
what's
happening.
B
A
Yes,
assuming
you
would
get
this,
you
will
get
this
as
soon
as
it's
out
there.
Yes,
we've
done
a
keynote
at
the
European
collaboration
Summit
in
Dusseldorf
Germany.
We,
you
are
yet
to
hear
the
keynote
from
build,
I,
think
roughly
I,
don't
know
which
time
exactly
in
the
world.
We
are
doing
we're
airing
this
episode,
but
it
might
be
very
close
to
the
keynote
at
build.
A
What
else?
So,
basically,
throughout
the
week
it's
going
to
be
European
collaboration
Summit,
we
will
be.
Some
of
us
will
be
at
build,
so
there
will
be
a
ton
of
new
cool
things
and
I
don't
pay
attention
to
that.
You
will
be
for
me
seeing
people
in
person
in
this
first
time
since
four
years,
mind
blown
I
would
lie
if
I
wouldn't
say
I'm,
anxious,
I
am
excited,
I'm
excited
to
be
there.
I
will
be
a
part
of
the
keynote.
A
A
What
else
is
there
I
think
that
will
be
for
a
big
part
majority
of
my
week
and
then
in
parallel,
a
few
days
back,
we
announced
the
team's
Global
hack,
which
is
a
virtual
hackathon
that
is
going
to
happen
online
on
June
1
through
15..
That
is
the
greatest
opportunity.
Yeah
yeah,
it's
it's
almost
there
right
like
time
flies
so
and
they'll
be
the
opportunity
for
you
to
take
everything.
You
learn
whether
you
attended
to
build
in
person
or
virtually
or
you've
been
to
the
ECS
conference.
A
That
will
be
the
opportunity
for
you
to
put
everything
you've
learned
in
practice
like
do
like
really
experience
it.
Hands-On
meet
product
groups,
meet
MVP
experts,
check
out
samples,
check
out
the
content
that
we've
got
and
build
some
hacks,
send
them
on
time
and
make
a
chance
for
a
cool
price,
because
we
have
a
song.
We
have
a
few
cool
things
to
give
out
to
the
best
hacks,
so
definitely
definitely
like
you've
got
nothing
to
lose.
A
B
Absolutely
you
pretty
much
summed
up
everything
what's
going
to
happen
for
me
next
week
as
well,
so
it's
easiest
and
then
catching
up
on
things.
Of
course,
Community
calls
happening
as
well,
and
all
of
that,
and
and
luckily
this
time,
I
actually
to
be
fair,
I'm
super
happy
that
it's
only
two
days
or
three
days,
technically
the
ECS
and
then
you
can
fly
back
home
because
the
the
Las
Vegas
trip
a
while
back.
It's
it's.
B
It's
surprisingly
taxing
after
many
of
the
years,
and
then
do
you
really
want
to
get
back
on
this
traveling
thing,
because,
as
I
said,
meeting
people
is
fun,
but
I
know
that
you're,
an
introvert
I'm,
an
introvert
which
doesn't
always
kind
of
relate
people,
don't
necessarily
kind
of
understand
that
you're
an
introvert
with
an
imposter
syndrome.
It's
like
really
yes,
definitely
and
I
would
rather
choose
to
walk
with
the
dogs
in
the
forest.
Rather
than
doing
that.
So
but
it's
fun
to
see
people.
B
A
I
mean
like
you
need
to
you
need
to
to
balance
it
out
where
you
take
the
time
to
talk
to
folks
on
their
hand,
like
you
also
have
a
quiet
time
by
yourself
or
with
a
small
group
of
friends,
kind
of
decompress
and
get
the
energy
up
so
that
the
next
day
you
can
be
there
around
for
folks,
because
if
anything
else,
I
love
to
hear
from
folks
there's
nothing
better.
For
for
me
to
learn
from
folks
like
hey
like
how
do
they
use
our
stuff
in
practice?
How
do
they.
A
And
even
the
things
you
know
the
rough,
the
hard
truth
like
this
doesn't
work.
This
is
hard
I
love
to
hear
about
it,
because
why?
Because
now
I'm
in
a
position
where
I
can
work
with
others
to
fix
that
I
just
need
to
know,
and
that
is
really
exciting
thing
for
me
at
least
to
get
out
there
and
get
out
to
folks
and
seek
them
out
and
basically,
if
you
have
an
opinion
on
something
I'd
love
to
hear
it,
yep.
B
Absolutely
same
here,
100,
so
looking
we
are
looking
forward
to
ECS
and
then,
of
course,
please
keep
on
have
providing
that
feedback
throughout
our
community
channels
in
the
community
course
and
the
forms
and
all
of
that,
what
we're
providing
all
the
time
so
for
those
who
cannot
necessarily
be
in
the
ECS
or
in
build
to
provide
the
feedback,
there's
multiple
ways
of
doing
that.
So
don't
you.
B
B
I
guess
with
that
I
guess
we're
good
to
go
so
no
articles
this
time
as
videos
were
recording
two
days
after
the
previous
episode,
there's
no
point
actually
covering
one
or
two
articles,
and
so
we'll
have
more
next
time.
But
thanks
everybody
for
watching
or
listening
and
depending
on
your
chosen
option
and
we'll
be
back
within
a
week.
Cheers
thank.
A
You
no,
we
will
be
back
well,
I
mean
we
will
be.
We
yeah
that
doesn't
matter
we'll
be
back
in
a
week
after
we
air
this.
Yes,
but
we'll
be
back
with
a
week
and
a
half
of
Articles
and
news,
and
we
will
have
exciting
news
from
build.
Recapping
build
recapping
ECS
regarding
everything
else
in
between
so
definitely
sure
sounds.