►
Description
In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen and Waldek Mastykarz (Microsoft) | @waldekm, are joined by Microsoft Redmond based Visual Studio Development Program Manager - Julia Kasper | @Jujujuliakasper. The discussion explored Julia's role, team and career journey; understanding customer needs and right-timed solution delivery, Microsoft cross org enabled Fusion development, plus Pro and Citizen developer opportunities.
Microsoft and PnP Community delivered 15 articles and videos in the last week!
This session was recorded on Monday, December 12, 2022.
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/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community
A
B
B
But
yeah
it's
it's
better
to
have
a
break
than
because
of
getting
visitors
during
the
holiday
season
is,
is
a
bit
difficult,
that's
complicated,
but
it
is
now.
What
is
it?
It
is
12th
of
December,
and
this
is
going
to
be
released
on
the
13th
of
December
on
Tuesday,
my
name
is
I'm
a
product
manager
in
a
Microsoft
traces,
Microsoft
365
per
platform
areas
with
me
as
a
co-host
is
hi.
B
A
Is
a
PM
at
Microsoft?
She
is
in
the
the
dev,
which
is
the
part
of
Microsoft
that
builds
tools
for
devs
and
she
focuses
on
Fusion
Dev
among
among
other
things.
So
we
would
love
to
talk
to
her
about
all
things.
Fusion
Dev,
where
it's
going
was
in
what's
out,
what's
relevant,
what
are
the
trends
and
what
people
should
pay
attention
to?
Yes,.
B
Absolutely
and
then
after
Julia
interview,
we
will
jump
on
the
weekly
articles,
not
that
many
articles
this
time,
but
you
know
I,
guess
we're
heading
to
the
holiday
season,
so
we
stay
less
and
less
activities
from
people
which
is
good.
That
means
that
people
are
resting
so
which
is
super
super
important
as
well,
but
as
you're
writing,
something
or
if
you're
in
Twitter.
B
A
C
B
C
C
B
C
So
low
code,
how
Microsoft
defines
it
also
from
our
ecos
Eco
perspective
View,
and
we
have
different
tools,
so
one
is
logic
apps
and
the
other
one
is
the
whole
ecosystem
around
the
Power
Platform.
My
role
in
particular,
is
looking
at
the
end-to-end
scenario,
everything
related
to
the
Microsoft
Power
Platform,
and
we
do
have
like
a
lot
of
great
PMS
on
the
logic
apps
team
and
we
do
feel
like
more
developers,
are
interested
in
this
already.
B
C
C
You
you
own
certain
features,
so
they
are
in
particular
overlooking
a
certain
feature
or
a
certain
product
and
Microsoft
figured
out
a
few
years
ago,
which
is
it
is
great
to
have
feature
PMS,
but
it
isn't
so
great
from
a
customer
perspective,
because
of
course
we
only
look
at
our
products
itself
and
we
don't
really
look
beyond
the
the
cosmos
there.
So
that's
why
they
started
to
have
so-called
end-to-end
PMS,
which
are
then
more
interested
in
the
customer
story.
C
So
in
I'm
I'm
talking
about
the
customer
in
my
in
my
use
case,
talking
about
the
developer
and
perspective
itself,
but
my
job
kind
of
is
to
Define.
What
is
the
end-to-end
story?
That
developers
could
be
interested
in
using
low
codes
and
local
tooling,
and
what
different
products
are
involved
in
this
end-to-end
story,
because,
typically-
and
that's
also
something
we
are
seeing
with
a
lot
of
customers-
it's
not
just
one
product
and
as
much
as
we
wish,
it
would
be
only
one
end
product
or
it
would
be
only
Microsoft
most
likely.
That
isn't
the
case.
C
B
A
Think
I
think
I
wanted
to
ask
you.
Do
you
looking
at
the
past
few
years?
How
do
you
see
developers
work
evolve
to
kind
of
Encompass
these
low
code
Technologies
right
because,
like
originally
when
somebody
would
say
say
Dev
like
you
would
instantly
a
person
who
writes
code?
How?
How
has
that
changed?
The
last
few
years.
C
Oh,
that's
a
very
I
love
the
question
so
I
think
it
didn't
really
change.
Even
the
last
few
years,
I
mean
if
we
look
back
even
a
little
bit
further.
We
had
classical
or
typical
developers
just
focusing
on
back
end
and
development.
We
had
typical
developers
just
looking
at
front-end
Technologies.
Then
we
had
this
huge.
C
C
So,
ideally,
Microsoft
marketing
would
have
promoted
it
a
different
way,
but
something
we
are
seeing
is
that
more
and
more
developers
or
more
the
more
technical
people
are
getting
interested
in
using
those
tools,
because,
at
the
end
of
the
day,
it's
just
another
tool
in
the
tool
set
and
whatever
kind
of
gets,
the
work
done
that
you
maybe
liking
to
do,
or
maybe
you
just
have
to
do
at
some
point.
You're
just
looking
at
different
tools
that
you
can
be
using
and
is,
is
benefiting
your
work
to
work
or
your
day-to-day
work.
A
A
B
It's
basically
all
of
the
Baseline
code
is
being
provided
for.
You
focus
on
business
logic,
but
now,
coming
back
on,
I
I
need
to
ask
the
elephant
in
a
room
about
the
elephant
in
a
room.
There's
no
elephant
in
a
room.
I
guess
hopefully
there
isn't,
but
is
the
low
code?
Is
it
that
then
a
threat
for
the
pro
developer
or
what
is
the
future
Direction?
C
And
so
definitely
what
we
don't
want
to
do
is
we
don't
want
to
educate
or
make
Pro
developers
citizen
developers,
because
I
mean
looking
at
the
the
graph
or
like
the
skills
you
will
need
in
the
Futures.
We
have.
We
don't
have
enough
developers,
so
it
wouldn't
be
the
smartest
thing
to
make
them
citizen
developers
so
kind
of
where
their
role
comes
is
in
is
local.
Tooling
is
a
great
way
to
get
a
lot
of
the
jobs
done
easily,
but
not
all
of
the
jobs,
because
it
is
local
tooling.
B
Dude,
you
actually
set
it
in
your
answer.
Just
real
elaborate
that
a
bit
so
as
we
know,
and
until
I
was
referring,
that
the
growth
curve
of
a
demand
for
developers,
the
the
we
cannot
train
developers
fast
enough
to
actually
address
the
demand
for
developers
and
that's
where
the
low
code,
no
code
Solutions
come
really
in,
so
that
so
that
the
positive
customers
can
still
do
business
and
automate
business
processes,
even
though
they
cannot
hire
a
pro
developer
or
a
developer,
because
they
just
doesn't
exist
anymore.
There
isn't
enough
of
them
so
so
test.
B
This
does
not
mean
that
the
pro
development
would
be
going
away,
even
though
every
now
and
then
our
marketing
is
pretty
black
and
white,
and
that's
also
something
within
after
a
while
in
Microsoft
you
real
in
ecosystem.
Everything
goes
in
Cycles
right
now.
Everything
is
like
no
code,
no
code,
nothing
else
matters
I
was
like.
Well,
that's
a
great
Metallica
song
by
the
way,
but
it's
not
the
reality.
So
it's
it's
within
a
few
years
and
the
Pendulum
moves
another
Direction
and,
of
course
the
pro
developers
are
always
needed.
C
A
Is
that
developers
or
Enterprise
devs
right
have
to
think
very
much
a
a
API
first.
Do
you
see
people
do
that
already
right
because
like
if
they
build
something
and
it
doesn't
explose
an
API,
Power,
Platform
or
Fusion
they're
like
there's
nothing
to
connect
to?
So
to
what
extent
do
you
see
necessity
for
a
shift
to
to
happen
yet
where
folks
will
get
the
mindset
of
API
first
or
to
what
extent
do
you
think?
Well,
we
are
there
already.
C
But
it's
more
the
trend
towards
microservices
and
from
there
it's
a
good
approach
to
then
think
about.
How
can
we
next
connect
these
microservices
and
depending
on
the
requirements
or
depending
on
the
use
case?
Maybe
it's
for
local,
maybe
it's
for
no,
this
doesn't
work,
and
now
we
need
our
deaf
or
our
Engineers,
working
with
it
from
a
more
Pro
called
perspective.
So.
B
B
Think
one
of
the
things
so
when
I
first
kind
of
got
involved
a
bit
on
the
Power
Platform,
it's
like
okay,
so
I
need
to
always
build
a
connector
and
I
have
to
be
able
to
connect
to
the
apis
and
then
I
can
get
to
do
the
other
things
and
I
I.
To
be
honest,
sure,
that's
true,
but
that's
not
the
mind
right
mindset,
the
in
the
Enterprise
scale.
We
should
be
thinking
about
the
microservices
and
apis
like
you're
saying
and
then
we
we
need
those
Pro
developers.
B
Then
we
need
somebody
who
understands
those
apis
to
provide
the
connectors
in
place
and
you
can
have
that
connector
Factory
in
place
within
the
Enterprise
level,
and
then
you
will
have
a
funnel
of
even
more
business
application
designers
who
don't
need
to
understand
where
the
data
is
coming
from
or
how
the
data
comes
from
that
just
use
the
connector
in
place.
So
you
don't,
as
you
build
your
power
app,
you
don't
always
start
by
creating
a
connector
and
then
the
power
app.
B
What
if
the
connectors
are
in
place-
and
you
basically
have
the
Baseline
service
layer
within
your
Enterprise
and
that's
way,
your
business,
specialist
and
business
and
local
developers
can
just
take
advantage
of
what's
behind
the
scenes
and
and
that's
maybe
potential
I'm,
just
brainstorming,
and
maybe
some
we
have
all
of
these
plans
in
place
and
the
guidance
is.
But
we
should
kind
of
have
a
white
paper
for
Enterprise
level,
team
structure
and
planning
and
how
you
should
be
thinking
these
layers
rather
than
just
power
app
and
a
connector
and
an
API.
C
B
C
C
If
it's
somebody
on
the
local
side,
then
that's
perfect,
because
then
we
can
use
the
other
person
who
would
be
working
on
it
from
our
engineering
team
doing
something
else
and-
and
it
also
comes
into
preference
too
right
I
mean
everyone.
Every
person
likes
to
work
in
a
certain
way.
So,
for
example,
if
somebody
is
super
passionate
about
opening
up
their
Visual
Studio
every
day,
and
they
don't
want
to
use
any
other
tooling,
then
yes,
that's
perfectly
fine
as
well.
Exactly.
B
B
Yeah
so,
and
as
long
as
I
have
the
connector
in
place,
then
10
sentence
of
power,
apps
developers
or
connector
or
automation
developers
can
actually
take
advantage
of
it.
It's
it's.
It
does
require
a
certain
set
of
mindset,
thinking
a
bit
of
a
switch
on
the
okay.
How
do
we
do
this
in
an
Enterprise
scale
or
Enterprise
level.
A
But
I
mean
like
it,
isn't
it
isn't
different
like
so
a
while
back
I
made
the
analogy
that
you
know
where
in
the
past
in
office
we
would
have
the
macros
we
would
build
in
VBA,
it's
basically
the
same
automation,
but
then
in
a
cloud.
So
you're
not
automating
in
inside
a
file
you're
now
automating
on
the
data
that
are
still
for
work,
but
that
are
stored
in
a
cloud.
And
then
you
combine
that
and
then
the
cool
thing
is
right
that
you
can
also
now
bring
in
your
lob
right.
A
So
it
doesn't
need
to
be
just
like,
like
you,
first
need
to
get
all
of
the
things
you
want
to
work
on
into
a
file
like
an
Excel
sheet
access
database
or
whatever
we
had
in
the
past,
and
only
then
you
can
do
things
on
on
top
right,
like
nowadays
with
connectors,
we
kind
of
expand
the
limits
of
that
to
kind
of
the
workplace,
because
it
isn't
even
M365
it's
any
resource
that
is
exposed
through
an
API.
Okay.
C
Yeah
also
something
I
like
about
this
idea
is
the
topic
of
scalability
right
before
and
if
we
think
about
VBA
here
it's,
it
was
very
much
local
development.
You
had
it
within
your
Excel
sheet
and
you're
the
only
one
knowing
about
this
great
macro.
Maybe
somebody
else
heard
it
then
you're
sharing
it
and
Via.
C
However,
you
shared
it,
but
then
now,
if
we
think
about
more
from
a
scalability
level,
I
can
create
a
connector
and
then
I
can
push
it
to
a
Power
Platform
environment,
for
example,
and
all
of
the
folks
who
have
access
to
this
Power
Platform
environment.
They
can
at
least
see
it.
It
doesn't
necessarily
mean
they
have
access
to
it,
but
at
least
they
are
aware.
C
Okay,
something
has
been
going
on
or
I
might
get
access
to
some
certain
types
of
data
and
it
I
think
in
general
helps
organizations
also
from
the
transparency
or
building
applications
faster,
especially
if
we
look
at
the
challenge
of
demand
and
not
having
enough
M
skilled
people
out
there
who
can
support
such
scenarios.
Yeah.
A
It
also
as
as
you
cough
yes,
yes,
it
almost
sounds
like
wait
in
the
past.
We
already
had
an
Enterprise.
You
know
the
service
catalog
idea
where
there
will
be
an
it,
manage
catalog
of
services
and
apis
and
things
that
they
would
offer
to
business
and
in
a
way
it
sounds
to
me,
like
Power
Platform
connectors,
become
that
they're
kind
of
the
way
it
can
with
a
really
low
effort
advertised
to
business.
What
different
things
they
have
to
offer.
B
B
Occasions,
but
every
single
decade,
every
single,
let's
say,
there's
always
a
trend.
How
we're
going
to
do
this?
Enterprise
catalog
of
services
and
and
of
course,
power,
Power
Platform,
connectors
one
way
of
doing
that,
but
that's
only
for
the
Power
Platform
connectors,
so
most
likely
they'll
say
for
Power,
Platform
usage
and
and
the
logistics
logic
app,
and
all
of
that
maybe
there's
a
separate
layer
again
of
publishing
the
services.
But
it's
it's
actually
kind
of
a
that's.
That's
one
of
the
holy
crails
of
Enterprise
development
has
always
been.
B
B
Now
two
yeah
that
was
really
good
discussion
on
what
are
you
doing
right
now
and
all
of
that
can
can
you
explain
a
bit?
How
did
you
got
to
do
what
you're
doing
right
now
and
and
where
are
you
based
in
not
in
U.S
and
Redmond?
How
did
that
happen?
Can
I
talk
about
your
history?
How
do
you
get
to
be
to
work
on
things?
What
you
work
on,
yes,.
C
And
our
lovely
Munich
office
and
I
went
to
customers,
or
at
least
they
booked
us
via
engagement,
and
we
helped
them
to
implement
different
types
of
solutions.
So
I
did
some
SharePoint
development,
I
started
and
building.
We
had
a
huge
bot
hype
in
Europe
I'm,
not
sure
if
it's
still
there,
but
at
least
whenever
I
was
every
customer
wanted
to
have
some
kind
of
thought
development.
C
So
I
did
a
lot
of
but
teams
development
for
some
of
our
customers
and
at
some
point,
especially
as
a
customer,
you
always
need
to
be
an
engagement,
because
that's
you
need
to
build
your
hour.
Everyone
who
has
been
working
in
consultancy
definitely
knows
so
at
some
point,
I
started
the
the
trend
of
Bot
development
and
decreasing
and
I
was
like
well
what
what
are
some
other
opportunities
that
customers
are
currently
interested
in
and
that's
when
I
heard
for
the
first
time
about
Power,
Platform
and
local,
tooling
and
I.
Remember
my
manager.
C
A
C
I
had
the
same
bias
everyone
else
had
and
but
I
started
to
yes
go
skill
myself
up
I
started
to
learn
a
little
bit
more
about
this
and
I
talked
to,
of
course,
talk
to
our
customers
about
that
talked
about
like
some
of
the
scenarios
that
they
wanted
to
do
and
I
came
across
the
same
challenges
and
we
are
still
seeing
as
okay.
The
customer
has
a
perfect
picture
of
the
app
or
the
like
the
thing
that
they
wanted
to
implement,
but
you
always
with
local
tooling.
C
I
think
it
was
initially
for
30
minutes,
but
then
we
ended
up
talking
one
hour
and
I
basically
complained
to
him
all
about
the
things
that
didn't
really
work
and
I
I
had
so
many
ideas
how
we
can
make
it
better
and
I.
Think
two
weeks
later
he
reached
out
to
me
again
and
he's
like
hey
Julia.
We
are
actually
I'm
searching
for
somebody
for
an
end
to
end
PM,
who
pay
basically
does
whatever
you
are
doing
already,
but
you
keep
it.
C
Now
going
to
pick
to
fix
it
and
that's
how
I
ended
up
in
Redmond
and
I
ended
up
in
originally,
because
with
covet
happening
and
everything
we
thought
about
me
just
staying
in
Munich
and
working
from
there.
But
then
and
I
know.
We
talked
about
this
already
with
different
teams
and
different
time
zones,
and
it
just
very
much
made
sense
for
me
to
be
moving
to
the
US
and
yeah.
That's
how
I
ended
up
in
Redmond
I'm
still
complaining
a
lot.
A
Like
you
have
firsthand
like
you're,
not
you're,
not
it's
not
a
theory
exercise
like
you
had
first
hand
experience
going
through
that
suffering.
The
pains
paper
cuts
as
they're
called,
and
now
you
kind
of
are
in
place
where
you
can
address
all
them,
so
I
think
it
makes
really
it's
really
good.
It
doesn't
get
better
than
that
right
and
I'm
interested.
Also.
How
do
you
stay
in
touch
with
that
music?
As
you
get
to
fix
things?
How
are
you
keeping
up
with
the
new
experiences
and
new
places
to
to
fix.
C
C
That
I
know
that
are
in
the
same
area
and
I
also
want
to
make
sure
that
I
or
I'm
making
sure
that
at
least
once
or
twice
a
week,
I'm
talking
to
customers
because
I
think
they
are
the
ones
providing
actual
feedback
to
us.
So
I
make
sure
that
I'm
still
trying
to
stay
in
touch
with
customers
or
Partners,
because
I
think
they
do
provide
the
real
feedback
because
we
have
our
Microsoft
lens
on
and
we're
like.
Oh,
this
is
how
it's
supposed
to
work,
but
it
never
is
so
yeah.
The.
B
Amount
of
time
you're
showing
somebody
like
back
in
a
few
years
ago
when
there
was
conferences,
everything
else
and
then
there
was
engineering
people
with
there
and
then
go
to
meet
the
partners
and
show
them.
Okay,
did
you
know
the
partners
built
this
one?
What
what?
What?
What
are
they
building?
So
we
never
intended
that
to
be
used
like
that
yeah,
but
yeah,
okay,
fine,
but
that's
a
typical
discussion
now.
B
Can
we
go
back
back
a
bit
on
kind
of
a
for
the
closure
of
the
of
the
discussion
and
pick
on
the
on
the
fusion
development
and
the
work?
What
you're
doing
right
now?
What
what
does
that
mean?
What
are
we
is?
It
is
there's
something
what
we're
going
to
talk
about,
what
are
we
building
in
the
vs
code
or
vs
to
make
division
rep
easier?
So
what
does
that
mean
so.
C
Me
starting
and
like
I
started
as
a
PM
last
year
in
January.
The
first
thing
I
did
is,
first
of
all
writing
down
all
of
my
feedback,
but
of
course,
I
also
have
my
biases
I'm
also
doing
things
in
a
certain
way.
So
I
started
to
interview
other
developers
across
the
world
and
trying
to
figure
out
what
are
some
of
the
struggles
they
are
going
through,
and
then
we
wrote
a
right
paper
about
it.
C
We
shared
it
with
different
teams,
and
we
came
up
with
a
few
things
related
to
products
that
we
feel
like
these.
Are
these?
Are
things
necessary
to
drive
the
fusion
story
or
to
drive
local
Pro
developers
using
local
tooling,
so
something
we
are
currently
working
on
is,
for
example,
how
to
get
started
even
as
a
developer.
So
right
now,
if
I
look
at
any
of
the
Ides
and
we
do
have
a
Power
Platform
extension
and
visual
studio
code,
but
we
don't
have
anything
in
Visual
Studio.
B
C
I'm
opening
up
my
vicious
Studio
I'm
open
setting
up
an
asp.net
web
API
project
and
we
have
our
great
page
of
connected
services.
So
in
the
future
you
can
easily
just
connect
your
local
project
to
a
Power,
Platform,
environment
and
and
then
because
now
with
Dev
tunnels,
it's
a
new
feature
that
we,
the
visual
studio
team,
just
released
as
soon
as
they
hit
F5.
And
now
we
are
just
talking
about
the
inner
loop
right.
C
So
I'm,
still
on
in
my
log
on
my
local
machine
I'm,
still
developing
within
my
inner
loop,
but
as
soon
as
I
am
hit.
F5
I
want
to
see
how
this
is
being
consumed
or
what
I
can
do
on
the
Power
Platform
side.
So
this
will
then
initially
create
a
custom,
connector
or
the
basically,
the
wrapper
around
my
web
API
and
I'm,
then
able,
but
I
still
have
it
running
on
my
local
machine
to
start
exploring
and
connecting
it
with
my
power
out
there,
or
even
with
my
power
automate
floor.
C
If
that's
something
I
want
to
test
and
and
try
out
as
well
well,
so
you
are
able
to
test
and
debug
it
while
running
locally
and
if
we
think
about
even
further,
because
that's
the
inner
loop
right.
If
we
now
think
about
the
the
the
loop
after
the
outer
loop,
not
the
outer
loop
and
it's
all
about
fruity
Loop.
C
If
you
think
about
the
outer
publishing
my
web
API,
how
do
I
then
get
it
into
the
Power
Platform
site
as
well
and
right
now
we
have
a
great
story
with
Azure
API
Management
in
place,
but
we
all
know
because
not
every
customer
is
of
course
using
this
service.
So
there
should
be
another
and
maybe
even
easier
way
to
also
create
a
custom
connector,
just
whenever
you
deployed
it
to
any
kind
of
cloud
service.
Yeah.
A
A
I,
wonder
I
wonder
with
that
to
a
degree
that
is
kind
of
the
same
thing:
where
way
back
when
there
was
a
research
done
that
the
most
popular
type
of
app
built
and
vs
was
a
Windows
Form
app.
It
was
like
why
well
because
that's
the
easiest
way
to
build
an
app
click,
a
button
yeah
right
so
so
I
wanted
to
what
degree
that's
kind
of
dead.
Or
is
it
really
that
people
build
production,
apis
and
publish
from
a
local
box
yeah.
C
It's
surprising
and
that's
what
I
mean
about
still
being
in
contact
with
customers
or
our
end
users
right,
because
they
are
going
to
show
you
how
they
actually
are
using
our
tooling
I
know.
We
have
those
crazy
plans
and
whatever
we
wanted
to
be,
but
it
definitely
makes
sense
to
have
some
interviews
with
them
afterwards
and
seeing
how
they
are
using
it,
and
if
this
is
really
helping
and
them
and
is
solving
their
business
problems.
Yeah.
B
Okay,
a
classic
example:
just
you
need
to
preach
the
cap
of
the
existing
users,
the
division
which
you
have
so
you
don't
actually
jump
aboard
like
five
years
and
they're
like
no.
No,
no,
no,
no
so
a
super
classic
sample
still
makes
me
smile,
because
I
was
working
already
at
Microsoft
at
the
time.
Whenever
we
released
Microsoft,
you
know
Windows
Azure
and
the
first
time
it
was
all
past
Services
platform.
As
a
service
Services,
there
was
no
IIs.
B
B
It
makes
no
sense
in
the
longer
run,
to
use
the
infrastructure
as
a
service,
because
just
it
doesn't,
if
you
can
get
rid
of
it,
but
but
customers
and
partners
like
well
I,
don't
understand
that
I
need
to
have
a
VM
I
need
to
have
a
computer
I
need
to
sign.
It.
I
need
to
look
into
that,
so
you
need
to
kind
of
reach.
B
A
B
A
Then
it's
really
hard
to
bring
them
along
right
because,
like
they
are
here
and
they
need
to
be
there
and
the
first
step
is
here
not
directly
there
right.
So
you
have
to
have
also
that
the
reality
check
where,
where
they
are,
and
what
is
the
first
step
there
I
mean
like.
Maybe
the
easiest
thing
is
allow
you
to
take
your
on-prem
workloads,
put
them
on
a
VM
in
Azure,
and
that
is
your
first
step
towards
the
cloud
from
which
you
step
by
step,
expand
it
to
microservices
and
whatnot
yeah,
absolutely
sure.
C
It's
like
trying
to
get
across
like
the
vision
you
at
some
point
have
and
if
it
does
take,
and
especially
at
Microsoft,
does
take
10
years
or
five
years
that
at
least
you
know
something
you're
working
towards,
and
this
doesn't
like
I
mean
it
can
always
change
on
the
way
right,
especially
talking
to
customers
and
talking
to
different
people
who
are
using
it.
This
can
change,
but
at
least
from
a
vision
perspective.
It's
nice
to
have
something
like
this
and
thinking
about
the
developer
perspective
in
these
scenarios
as
well.
Yep.
B
Absolutely
absolutely
and
that
helps
in
alignment
within
inside
of
Microsoft
as
well,
because
quite
often
we
need
to
work
across
multiple,
multiple,
multiple
organizations,
I'm
conflicting
interest,
and
all
of
that
which
is
a
bit
complicated,
so
cricket
from
a
timely
perspective.
We
typically
do
this
in
every
single
interview.
What's
happening
this
week.
Anything
interesting
I
can
see
from
background
clock
that
it's
344
in
your
location,
so
you
are
in
Germany,
so
yeah.
B
C
Day
actually
just
started,
maybe
two
or
one
hour
before
our
club
was
so
and
especially
typically
before
holidays
I'm,
trying
to
focus
more
on
the
Strategic
work,
like
writing,
documentation,
writing
some
strategy
papers
about
and
where
we
are
with
our
tooling
right
now.
What
we
want
to
do-
and
today
I
actually
have
a
call
with
another
customer,
because
we
have
a
new
that
then
we
have
a
new
linking
or
at
least
in
private
preview
for
next
year
from
Azure
API
management
to
the
Power
Platform.
C
So
right
now
we
want
to
get
some
customers
on
board
who
are
willing
to
test
it
and
give
us
feedback.
So
we
have
our
kickoff
call
with
them
today.
So
that's
always
super
interesting
because
we
get
to
tell
them
kind
of
what
is
in
private
preview.
We
get
to
show
them
a
demo
and
they
are
usually
also
super
excited
about
all
the
things
that
are
coming,
and
so
that
always
definitely
makes
my
day
for
sure.
B
C
Oh
for
sure,
yeah
I
am
I
mean
during
Christmas
everything
slows
down
here,
anyways
and
especially
if
you
make
a
such
a
far
trip
I'm
taking
two
weeks
off
just
being
with
family
and
friends,
which
is
always
nice,
because
now
that
I
live
in
a
overseas,
you
don't
get
to
see
them
that
often
anymore.
So
yeah
I'm
super
excited
about
that
too.
A
B
A
It's
like
we
need
to
do
it
now,
so
I'm,
trying
to
cram
as
much
as
I
can
into
the
last
days,
but
yeah
I
will
be
off
the
last
day
or
the
last
day,
the
last
week
of
the
month,
so
I'm
taking
some
some
time
while
I
do.
But
until
then
it's
it's
all
hands
on
deck
and
doubling
down
on
all
of
the
work
that
I
have
done
and
that
I
want
to
do
now.
Ideally
today,
which
will
not
be
the
case.
B
A
Well,
but
a
while
back
I
I
I
had
the
idea
to
organize
my
work
so
I
had
this
separate
list
into
to
do
and
then
three
things
and
it
was
supposed
to
hold
the
three
days
or
three
things
for
me
to
do
in
a
day.
I
ended
up
having
like
eight
items
in
the
three
items
to
do
in
the
daily
list.
Like
you
know
what
that's
not
gonna
work.
Yes,
it's.
B
A
B
B
That
would
be
one
way
of
doing
that.
So
it
is
what
it
is
so
after
being
in
a
roles
for
a
long
time,
it's
just
impossible
to
do
that,
but
I
still
to
be
fair.
I
still
don't
understand,
for
example,
how
Jeff
Tipper
does
that,
so
he
keeps
on
responding
and
promoting
and
responding
emails
and
everything
it's
like
how.
B
That's
true,
that
is
true.
That's
true!
That
is
so
true
anyway.
Thank
you.
Julia
for
a
great
discussion
enjoy
the
time
off,
really
really
good
to
get
catch
up,
we'll
catch
you
again
on
the
show
at
some
point
to
talk
about
and
maybe
to
talk
about
what
was
then
released
and
what
are
the
things,
what
is
now
being
used
and
all
of
that
stuff.
It's
a
good
way
of
coming
back
on
on
what
we
were
both
following
up
on
your
promise.
Was
it
actually
delivered
or
not
just
kidding
so
I.
B
A
B
Next
time,
thank
you
excellent.
Thank
you,
Julia,
one
more
time
on
the
discussions
really
really
cool,
stuff
and
and
happy
holidays
as
well
good
to
get
some
time
away
or
well.
If
you,
if
people
don't
have
time
away,
they
will
have
a
less
at
least
two,
hopefully
during
holiday
season,
at
least
in
my
case
it
seems
that
I
have
time
to
catch
up
on
things
which
is
good,
but
let's
actually
jump
on
the
weekly
articles
and
code
them
through
what
we
have
there.
So
let
me
share
my
screen.
B
Let's
start
from
a
Microsoft
teams,
blog
Frontline
workers
using
shared
ad
devices,
can
now
use
Edge
and
Yammer
apps
in
the
intros
alone
and
on
Android
alongside
themes.
So
basically,
this
is
the
Direction
Where
We
Are,
investing,
which
is
more
and
more
Frontline
worker
based
capabilities
and
making
sure
that
our
applications
are
more
streamlined
for
the
mobile
experiences
as
well,
because
quite
a
lot
of
actually
Workforce
don't
sit
by
in
the
front
of
the
desktops
right
and
it's
it's
actually
kind
of
interesting
when
I
think
about
it.
A
So
again,
right
it's
being
productive
and
effective
on
the
go
on
your
phone
right
so
and
and
in
this
case,
being
able
to
have
a
wide
board
so
a
place
where
you
can
sketch
take
notes
brainstorm
with
others,
and
this
is
about
the
is
it
update
or
is
it
a
release?
Is
it
an
initial
release
of
the
app
to.
B
B
Really
really
cool
and,
and
it
seems
to
be
actually
pretty
nicely
implemented,
so
you
can
do
a
lot
of
a
lot
of
stuff
in
the
in
the
mobile
phones
as
well,
so
it
gets
more
and
more
natural
to
just
use
the
mobile
phone,
which
is
kind
of
nice,
even
though,
of
course,
I
love.
The
tree
screen
five
screen
set
of
what
I
have,
but
you
know,
if
you
don't
have
that
option
so.
B
A
So
in
November
2022
we
released
apparently
13
new
independent
connectors
right,
so
these
are
the
connectors
for
a
for
apis
that
are
already
built
by
someone
else,
and
then
Community
builds
the
connectors
that
aren't
available
there
there
yet.
So
this
is
all
geared
towards
the
ability
for
folks
to
use
apis
in
power.
Apps
Power
automated
flows
all
object,
apps
to
more
easily
use
these
apis
that
are
already
available.
Yep,
really
really.
B
B
Thank
you
and,
of
course
thank
you
for
everybody
else
who
are
sharing
their
Knowledge
and
Skills,
and,
and
here
as
well
now
we
also
had
an
update
from
the
powerapps
community
and
powerapps
Engineering
site
around
automate
deployments,
with
pipelines
in
Power
Platform
now
in
preview,
and
this
is
now
once
every
time
heading
to
more
and
more
to
the
direction
where
the
power
apps
are
more.
How
would
I
say
it
in
a
nice
way?
Enterprise
ready!
Maybe
is
that
a
nice
way
of
saying
that?
B
Well,
they
are
Enterprise
radio
ready,
but
to
get
more
Alm
governance
processes.
All
of
that
in
place
and
and
of
course,
the
pipeline
system.
One
step
forward
on
that,
so
making
sure
that
you
can
deploy
and
automate
steps
as
part
of
the
the
power
app
development
cycle
really
really
cool
stuff
good
and
by
the
way,
there's
a
nice
Microsoft,
mechanics
video
on
that
one
as
well,
so,
which
is
very,
very
cool.
So,
let's,
actually,
let's
do
that
and
just
get
it
and
make
sure
that
it's
actually
listed
in
our
list
of
things.
B
A
What
copy
right
so,
basically,
the
Manifest
describes
the
shape
of
your
app
right.
So
when
you
build
an
app
for
teams,
you
have
your
code
that
runs
somewhere
in
a
cloud
SharePoint.
Whatever
you
want
to
right
and
then
then
you
also
have
the
package
with
the
manifested
icons
and
demand
manifest
has
info
about
your
apps,
such
as
name
display,
name
description,
but
also
the
things
that
should
that
this
app
does.
Does
it
have
a
bot?
Does
it
have
a
tab?
A
Messaging
extension
task
module
whatever
right,
so
all
of
that
is
in
the
Manifest
and
as
we
introduce
new
things
to
teams
right
and
teams,
apps
that
manifest
evolves
as
well
with
additional
options.
So
this
time
around,
we
have
another
version
with
new
options.
So
if
you're
interested
to
see
what's
new
check
it
out,
absolutely.
B
I'm
kind
of
a
related,
well
not
directly
related,
but
in
in
some
sense
related
it's
well,
it's
related,
but
not
directly.
One-To-One
dependency
on
end
is
the
JavaScript
library
for
teams,
so
there's
only
version
2.6
available
on
that
one
which
has
an
additional
capability.
So
you
can
access
again
additional
capabilities
and
additional
things
and
of
course
this
is
available
at
npm
as
well,
which
isn't
mentioned
on
the
release
notes.
A
Exactly
right
so
a
while
back-
and
we
even
did
a
demo
about
of
this
on
community-
go
I,
built
kind
of
the
same
thing
that
you
have
available
in
Outlook,
which
is
a
way
for
you
to
pick
a
few
folks
from
your
org
and
plan
a
meeting
and
find
a
meeting
time
plan
a
meeting
and
that
was
kind
of
a
control
that
you
could
build.
You
could
integrate
in
your
own
app
that
you
connect
to
Microsoft
365.
A
now
in
this
article
Louisa
kind
of
takes
a
concept,
but
then
she
builds
that
in
powerapps
and
it's
really
cool
to
see
like
how
closely
it
resembles
the
thing
that
I
built
on
MGT
right,
because
in
this
case
she
doesn't
use
an
MGT
right
like
she
builds
everything
from
scratch.
And
it's
really
cool
to
see
like
how
close
it
is.
B
True,
true,
really
awesome
stuff
and
it's
great
to
see
that
we
get
more
of
this
consistency
and
the
experiences
and,
of
course
now
as
long
as
we
can
and
whenever
we
well
personally,
it's
in
a
roadmap
pipeline,
hopefully,
will
happen
sooner
or
later
that
we
can
actually
publish
components
and
controls
for
power
apps
and
at
that
point
capsulating.
All
of
these
are
reusable
controls
as
a
or
something
to
do
for
right
now
and
that's
a
bit
of
a
complicated
thing
to
actually
get
started.
B
So
you
cannot
just
simply
download
the
Json
definition
or
something
and
while
I
use
it
as
a
component,
that's
not
how
it
works,
even
though
there's
well
some
some
ways
of
doing
that.
But
it's
it's
a
bit
more
complicated
than
just
referencing
a
set
of
controls,
and
maybe
at
some
point
who
knows
but
really
awesome
to
see.
B
A
Definitely
it's
been
around
for
a
long
time,
and
yet
it
is
invaluable
even
more
today
than
in
the
past
right
because,
like
given
the
scale
of
the
cloud
like
we
no
longer
go
to
like
give
me
files
from
this
site.
Like
you
don't
query
aside,
you
use
search
because
where
the
files
are
still
stored
is
less
important
to
you
being
able
to
ball
to
find
them
right
and
in
a
cloud.
Indexing
happens
really
fast
right.
So
you
have
this
almost
instant
indexing.
B
B
Nothing
wrong
with
our
documentation,
never
been
so
Peter
verstra
had
a
quickly
find
a
parent
from
the
child
flow
in
power
automate.
So
if
you
have
multiple
flows
Associated
between
each
other,
you
can
argue
how
do
you
find
the
parent
flow
from
the
child
flow?
So
a
nice
blog
post
summary
and
a
reference
point
with
screenshots
again,
which
Peter
is
always
doing
on
explaining
how
this
actually
works
really
really
awesome
stuff.
A
Exactly
what's
new,
it
says
in
SharePoint
framework
1160,
so
as
spfx
evolves,
there
are
new
features
and
also
new
dependencies
that
we
include
in
spfx
and
in
this
case
it's
about
SAS
right.
So
this,
let's
say
CS
or
improved
way
to
write
CSS
to
have
some
of
these
things
like
inheritance,
so
that
you
don't
need
to
repeat
everything
right.
So
what's
new
in
that
area
of
spfx,.
B
Yep
pretty
very
good.
Thank
you
Stefan
on
that
one,
and
then
two
weeks
ago
we
were
in
Copenhagen,
European,
SharePoint
conference,
2022
and
and
Martin
links
to
it
had
a
blog
post
related
on
what
I
learned
at
the
espnc
conference
in
Copenhagen.
These
are
always
good
stories
as
well,
because
they
kind
of
a
recap
their
learnings.
They
recap
the
things
and
what
is
really
cool,
what
was
actually
covered?
B
A
A
That's
still
the
official
name,
but
it's
kind
of
teams
that
is
included
with
Windows
11
and
it's
kind
of
the
non-work
or
basically
teams
for
outside
work,
and-
and
in
this
case
it's
about
how
would
you
use
teams
to
organize
Community
right,
like
maybe
you
have
a
soccer
team
or
hockey
team
or
some
kind
of
other
org
right,
and
you
want
to
have
a
place
to
engage
on
online.
You
can
do
that
nowadays,
on
teams,
yep
actually.
B
Really
interesting
option
as
well
and
it
is
free,
it's
free
themes
for
Life,
whatever
installation,
so
really
really
cool
and
there's
a
nice
interview
with
Amit
Foley
who
say
vice
president
of
product
at
Microsoft
related
on
this
one.
So
there's
a
recording
with
with
that
with
Danielle
Glenn.
Now,
on
the
video
side,
it
was
surprisingly
actually
quiet
as
well
so
Shane
had
a
new
video
six
days
ago,
power
apps
example
using
canvas
for
design
and
a
field
build
so
fully
build,
making
things
pretty
with
containers
and
kind
of
an
Ang
pixel
base.
B
So
basically
building
experience
is
thinking
through.
How
would
we
use
those
and
then
having
a
watch
under
ads?
You
know
because
ads
are
important
so,
but
basically
creating
nice
looking
applications
and
how
do
we
reuse
the
assets
which
are
coming
outside
of
the
the
power
apps
within
the
design?
Well,
that's
not
nice,
nothing,
but
you
know
there
are
different
options
to
make
things
pretty
as
well.
B
So
that's
starting
to
look
this
up
and
then
we
just
had
this
one
opened
and
this
one
was
related
on
the
Power
Platform
management
control
and
visibility,
Alm
and
the
pipelines.
All
of
that
is
being
touched
in
this
Microsoft
mechanics
video
as
well,
which
was
released
four
days
ago,
but
I
guess
that's
it
then
for
this
one.
So
let
me
actually
stop
sharing
last
episode,
any
last
words
before
we
close
up
for
this
year.