►
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 Netherlands based CTO Low-Code Solutions and Microsoft MVP - Albert-Jan Schot (BLIS.digital) | @appieschot.
The discussion explored Fusion development, low code - pro code integration opportunities for Partners, exposing an application on a Teams tab vs connectors, and need for pro developers in 5 years.
Microsoft and PnP Community delivered 24 articles and videos in the last three weeks! This session was recorded on Monday, December 12, 2022.
Agenda items
• 02:26 – Interview
• 43:52 – Weekly Articles
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
C
B
A
year
right,
that's
true!
That
is
a
year
later.
That's
actually
a
good
point
anyway
good
to
be
back,
and
it's
it's.
Actually.
It
was
an
awesome.
Few
weeks,
I
was
working
throughout
the
holiday
season
and
not
that
many
incoming
messages.
It's
actually
absolutely
brilliant,
because
there's
a
this
time
to
do
the
stuff,
rather
than
answering
on
incoming
questions
so
now
the
system.
B
C
He
is
one
of
our
MVPs,
he
didn't
know
for
how
many
years,
seven
or
eight
already
so
time
flies
and
we
talked
or
we're
going
to
talk
or
we
talked
about
Fusion
development.
Power
Platform.
Is
it
or
is
it
not
and
a
great
space
for
Partners?
Why
would
you
care?
Why
would
you
if
you
build
apps?
Why
would
you
care
about
integrating
them
with
Microsoft,
365
and
Azure?
So,
if
you're
interested
in
all
that
and
if
you're
with
us
I
hope
you
are
tune
in
to
do
the
interview.
B
There
we
go
cool
anyway,
let's
jump
on
the
on
the
interview
right
away
with
EPI
and
then
come
back
on
the
weekly
articles,
which
are
a
bit
longer
than
a
week
at
this
time.
But
you
know
we'll
come
back
welcome,
Happy
joining
us
on
the
BMP
weekly
episode,
192
and
before
we
actually
get
to
the
topic
of
this
week.
So
you've
been
actually
on
the
show.
D
B
D
B
Time
flies,
yeah
time
flies
when
you're
having
fun.
Absolutely
now
now,
you'd
say:
let's
actually
start
from
my
work
side.
You
said
that
Bliss
does
cool
stuff
for
Azure
and
Microsoft
racist,
five,
not
forgetting,
but
of
course
Power
Platform.
What
does
that
mean
in
practice?
What
is
cool
stuff?
What
does
the
cool,
what
defines
as
a
cool
stuff.
D
So
what
we
do
is
we
build
software
for
customers,
like
probably
make
sense,
but
a
lot
of
us
customers
are
SAS
Solutions
or
our
building
SAS
Solutions
or
are
considering
buildings
as
Solutions.
So
on
the
one
end
we
build
custom
SAS
Solutions
on
Azure,
using
all
the
Azure
goodies
that
that
we
get,
and
over
the
last
year
I
joined
the
company
for
30
nor
40
months
now,
I've
been
involved
with
doing
a
lot
of
low
codes,
and
my
background
is
m365..
D
So
what
we're
trying
to
do
is
to
gather
with
all
the
stuff
that
we're
already
building
in
Azure
to
introduce
whether
we
call
it
Fusion
development
or
not
or
introduce
the
fusion
development
approach.
And
if
you
look
at
what
you
see
happening
in
Azure,
is
more
and
more
services
that
you
can
turn
on
that.
You
can
use
that.
You
can
well
stop
bothering
with
all
the
technical
details
and
just
start
using,
and
we
see
the
same
thing
happening
in
M365.
D
So
what
we
believe
is
that
Fusion
development
is
where
it's
starting
to
get
interesting,
because
why
would
you
bother
building
the
gazillion
login
prompt
if
you
can
use
Azure
active
directory
or
why
would
you
build
your
own
interface
to
render
line,
charts
or
bar
charts
if
you
can
use
power
bi?
So
that's
for
us,
let's
say
cool
stuff.
We
we
really
hope
to
do
Mission
critical
stuff.
So
we
we
help
customers
with
which
solutions
would
we
call
Mission
critical,
meaning
that
if
it
breaks
there
is
a
problem?
D
D
So
so
what
we
see
is
there
are
companies
who
are
starting
out
on
Microsoft
Technology
either
because
someone
there
heard
from
Microsoft
or
is
aware
of
Microsoft
or
error
using
stuff
that
is
in
the
Microsoft
ecosystem.
So
that's,
let's
say
type
one
company
already
doing
stuff
in
Azure
and
like
oh
wait,
we
know.net,
we
know
Azure,
we
might
want
to
use
those
components.
What
we
also
see
is
customers,
who
are
not
necessarily
in
the
Microsoft
stack
but
might
have
done
things
with
Microsoft,
technology.net
or
and
those
are
two
types
of
distinguished
customers.
D
They
have
different
needs
and
and
different
requirements,
but
as
soon
as
there's,
let's
say
a
hint
of
Microsoft
already
attached
to
a
product
or
a
service,
it
really
starts
making
sense,
because
one
of
the
things
that
we
try
to
do
is
not
to
reinvent
the
wheel.
So
you
probably
start
with
single
sign-on
Azure
active
directory
identity,
which
is
really
interesting
because
once
you're
in
that
active
directory,
then
you
can
start
thinking
about.
Maybe
you
want
to
do
custom
connectors
with
locals.
D
Maybe
you
want
to
expose
Your
solution
within
teams
or
in
the
app
source
for
that
matter.
Maybe
you
want
to
integrate
them,
365
search
experience
and
what
we
see
there
is
that
the
discussions
that
we
have
a
lot
is
we
built
websites
portals
all
kinds
of
of
things
where
the
first
step
is
never
we
want
to
do
things
in
the
n365
worlds.
It's
just.
We
need
a
solution,
but
once
it
once
it's
there,
then
the
next
question
is
going
to
be.
D
Can
you
start
thinking
with
us
how
we
can
expand
our
reach
and
one
of
the
things
if
you
have
a
solution
and
you're
trying
to
remarket
your
own
solution?
Why
wouldn't
you
put
it
in
appsource
because
all
of
a
sudden
there's
a
lot
of
M365
users
out
there,
who
might
be
then
able
to
use
your
solution
or
there's
a
lot
of
users
that
are
now
using
low
code?
I
mean
you
see
the
Gartner
reports
where
they
say,
like
75
percent
of
of
all
software
will
have
a
local
component
within
2025.
B
So
exposing
their
application
as
part
of
whatever
the
Business
Solution
is
what
the
end
users
are
building
using
the
fusion
Dev
model
is
that
yeah.
The
connectors
model
is,
of
course,
the
the
way
of
doing
this.
One
way
of
doing
that
and
there's
just
multiple
other
ways
of
doing
that
as
well.
Probably
connectors
is
the
easiest
way
to
do
that.
Let's
start
the
right
way
of
saying
that.
D
Yeah
yeah
I
would
say
it
always
starts
with
making
sure
that
you
have
single
sign-on
with
the
Azure
active
directory.
That's
like
step
one
and
then
step
two
is
either
integrate
within
teams
or
integrate
with
locals,
and
teams
could
be
as
easy
as
just
making
sure
that
the
app
is
high
frames
and
I'm
I'm
cursing
a
bit
here,
but
just
having
it
as
an
app
in
teams
it.
B
Just
coming
back
on
the
Azure
Ada
thing,
I
I
still
remember
when
I
was
working
as
a
consultant
in
the
Microsoft
Consulting
Services
many
many
moons
ago.
That
was
still
that's
been
a
while,
but
at
that
moment
we
were
still
kind
of
a
hunting
down
on
getting
all
of
the
customers
to
Azure
ad
and
obviously
that's
kind
of
that
penetration
present.
That's
is
high
enough.
That's
no
longer
really
a
growth
area,
and
now
it's
more
about
okay.
Now
we
are
here.
B
D
D
What
we
see
is
that
there
are
software
vendors
out
there
who
started
out
doing
only
AWS,
or
only
slack
Integrations
like
the
they're,
not
into
the
Microsoft
ecosystem,
but
even
those
are
now
approaching
or
are
now
having
discussions
saying
hey:
what
can
we
do
to
at
least
make
our
app
available
on
those
platforms
rather
than
staying
away
from
it?
They
are
slowly
at
least
embracing.
What
is
what
is
possible?
That's
this!
B
Good
point,
but
but
the
teams
use
it
all
up
worldwide
is
so
high
that
people
are
basically
saying.
Okay,
we've
been
focusing
now
on
slack,
but
yeah.
We.
What
is
that
teams
thing?
What
if
we
would
also
expose
our
application
over
there
now
for
those
who
do
not
know
and
I
kind
of
know,
this
question
how
hard
it
is
to
expose
the
application
in
teams.
C
D
How
far
you
want
to
do
the
integration,
if
you,
if
you
were
having
a
let's
say,
if
you
have
a
solution
where
you
have
single
sign-on
with
Azure
active
directory,
exposing
it
into
teams
is
pretty
straightforward.
If
you
want
to
integrate
the
more
advanced
scenarios,
think
about
adaptive
cards,
think
about
messaging
extensions,
then
it
becomes
a
bit
harder.
You
have
to
do
a
bit
more
work
and
well
saying
it
becomes
harder,
is
not
necessarily
the
right
way.
You
have
to
do
more
work.
C
Well,
so
on
that
now
what
I
wanted
to
ask
is
what
kind
of
type
of
integration
do
you
see
the
most
with
your
audience
and
customers
you
work
with
when
it
comes
to
teams?
Do
they
really
lift
and
shift
the
whole
app
as
a
tab,
or
are
they
really
interested
more
in?
You
know
the
contextual
experience
as
it's
called
with
messaging
accessions
and
Bots
that
are
really
a
part
of
the
the
chat.
D
That's
that's
where
it
gets
a
bit
weird.
The
the
easiest
way
is
just
exposing
your
ad
as
a
tap.
That's
like
straightforward,
easy.
We
see
a
lot
of
customers
who
are
are
doing
that.
What
we
also
see
is
that
customers
who
are
having
let's
say
more
advanced
software
being
built-
let's
say
I-
want
to
build
a
a
learning
solution
or
I
want
to
build
another
complex
technology.
Then
it
makes
sense
to
leverage
all
of
the
team's
integration.
D
So
you
might
want
to
do
messaging
extensions
or
if
you
want
to
do
something
with
e-learning,
you
might
want
to
integrate
into
meetings
as
well,
so
you're
going
to
do
a
meeting
extension.
If
you
have
notifications
in
your
application,
then
it
definitely
makes
sense
to
do
adaptive
cards
and
send
those
as
notifications.
So
it's
again
it
depends
a
bit.
It's
not.
The
answer
that
that's
easiest
to
be
honest,
doing
tabs
obviously,
is
always
almost
like
the
the
101.
B
D
B
D
Okay,
if
you
don't
have
active
directory
integration,
and
this
the
first
step
would
be
to
well
start
thinking
about.
Okay,
do
we
need
that
for
our
solution,
because
then
you
have
single
sign-on
experience,
or
do
we
accept
that
if
you
build
a
team
step
that
you
might
need
to
sign
into
that
step
again,
if
you,
if
you
go
there.
B
D
No,
you
don't
have
to,
but
to
be
honest,
the
best
experience
would
be.
If
you
would
have
that
I
mean
absolutely
single.
Sign-On
is
2023,
something
that
most
users
would
expect
you
to
to
have
I
would
say
from
there.
Then
you've
got
a
few
options.
You
can
do
everything
yourself.
You
can
use
the
PNP
generator
that
there
is
to
generate
a
teams
app
or
you
can
you
can
build
everything
yourself.
D
I
mean
that's
up
to
you,
but
in
the
end
a
team
step
is
nothing
more
than
a
zip
file
containing
some
some
Json
two
icons
and
a
Azure
active
directory
application
registration
that
might
be
used
by
the
tab
and
that
that
requires
some
configuration.
So
I
can
say
whether
it's
a
day
or
a
week's
worth
of
work.
But
it's
not
it's
not
months
of
development
work.
If.
B
B
C
Yeah
yeah
yeah,
yeah
I,
guess
it
is,
it
is
like
it's,
as
you
said
right
in
the
end,
it
depends.
What
is
it
that
you're
after
right,
because,
like
putting
your
whole
app
into
an
iframe?
Yes,
it's
an
easy
dick.
You
can
say
we're
in
teams,
but
is
this
really
the
optimal
experience
for
users?
Maybe
maybe
not
right?
So
maybe
there
are
other
scenarios
that
are
more
leaning
themselves
towards
other
things
like
a
messaging
extension
where
you
can
use
the
app
directly
within
the
context
of
a
chat
right.
So
again
it
depends
right.
D
Yeah
and
there
you
would
go.
Let's
say
you
have
a
custom
learning
solution.
Then
it
makes
way
more
sense
to
integrate
on
other
topics
compared
to
let's
say
you
want
I,
don't
know,
I
want
to
book
lunch
then
having
a
launch
app
as
a
tab,
which
is
just
an
iframe
where
I
can
say
yes
or
no
might
be
sufficient.
If,
like
I'm
at
that
level
of
maturity,
if
I'm
a
Gen
X
company,
where
everyone
is
like
24,
then
a
chatbot
might
make
more
sense.
Yeah.
B
Yeah
makes
perfect
sense.
Now
can
look
back
on
what
we
we
talked
about,
started
discussion
on
fuse
and
Dev,
and
fusion
devious,
obviously
growing
term
and
low
code
no
code,
all
of
that.
But
what
what
does
the
fusion
Dev
means
in
practice?
Is
that
a
is
that
a
real
opportunity
for
partners
to
look
into?
Is
there
business
there?
Are
you
making
money.
C
What
what
do
you
see
as
as
that's
a
good
question,
Fusion
death
right
because,
like
otherwise
like
we
will
like
people,
will
assume
their
own
things?
It's
like
yeah,
but,
and
we
kind
of
end
up
arguing
not
being
aware
that
we're
talking
about
the
different
things.
So,
let's
start
with
the
definition.
First.
D
So
for
me,
if
you
look
at
I,
think
Microsoft
did
a
white
paper
about
it
where
they
say:
you've
got
makers
and
you've
got
developers,
Pro
developers
and
those
two
people
are
together
talking
about
using
these
elements
for
us
the
way
that
we
pitch
it
is
that
there's
actually
three
or
maybe
four
rules,
you've
got
makers
and
makers
is
a
group
of
people
or
a
group
of
people
who
are
happy
to
Tinker
a
bit
with
technology
and
typically
that
are
not
necessarily
only
people
who
are
using
the
Power
Platform.
They
could
be.
D
People
who
are
really
good
at
Excel
or
making
really
complex
calculations
in
Excel
could
be
people
who
are
still
using
SharePoint
designer
workflows.
So
there
is
a
bunch
of
people
out
there
who
are
yeah
I
know,
but
they
are
there.
There
is
a
bunch
of
people
out
there
who
alike
experimenting
themselves
like
to
like
to
play
around
with
what's
possible,
they're,
typically
pretty
self-reliant,
figuring
things
out
and
making
things
happen.
D
It's
if
it's
not
ready
there.
So,
let's
say
within
low
code
you're
missing
something
you
might
want
to
do.
Custom
components
you
might
want
to
do
custom
connectors
anytime,
the
word
custom
pops
up,
then
you'll
probably
need
a
developer
and
if
you're
in
an
Enterprise
organization,
you
might
need
an
architect
to
make
sure
that
things
like
governance
and
Alm
are
configured
according
to
the
business
needs.
As
well
yeah,
so
for
us,
that's
that's
Fusion
development
yeah.
What
we.
B
D
What
we
that
there
is
really
a
lot
of
interest
in
in
the
market
around
hey.
We
see
all
these
types
of
advantages
of
using
low
code
time
to
to
develop
our
time
to
Market.
All
that
all
kind
of
things
around
security
are
are
being
taken
care
of.
Well,
that's
not
always
completely
true,
but
a
lot
of
things
are
are
in
the
box
and
and
you
can
use
them
versus
with
full
code.
D
You
need
to
use
Frameworks
depend,
be
dependent
on
Frameworks,
have
your
own
best
practices,
which
is
all
fine
and
well,
but
if
it
then
takes
a
bit
longer
to
get
something
live,
then
low
code
could
be
a
good
alternative,
and
what
we
see
happening
is
that
a
lot
of
customers
are
at
least
asking
questions
about
that.
Saying:
hey
we
see
this
happening
in
the
market.
Does
it
make
sense
for
us?
D
B
Actually
kind
of
a
good
way
of
also
defining
the
the
the
Power
Platform
or
no
code
low
code,
let's
say
movement,
which
is
all
about
it's.
Actually,
you
might
actually
kind
of
say
that
power
amps
is
a
mature
enough
platform,
so
it's
configurable
enough
for
the
business
users
for
their
purposes,
but
that
doesn't
mean
that
we
wouldn't
need
the
developers
and
we
wouldn't
need
the
is
it
the
ID
processor
architects
who
are
defining
the
rules
and
defining
the
connectors
and
everything
else.
B
So
Julia
Casper
was
in
the
show
before
our
holiday
break,
and
we
were
just
talking
about
this
kind
of
a
the
kind
of
a
three
actually
three
different
people.
So
it's
not
just
the
random
end
user
from
HR
is
like
yeah
I'm
going
to
be
a
now
developer.
No,
no,
no,
certainly,
probably
not
in
some
cases
it
could
be.
B
Who
knows,
but
it's
quite
often
that
there's
the
pro
developers
who
are
then
creating
those
connectors
and
reusable
configurable
bits
and
pieces
based
on
then
the
architect
role,
which
is
defining
the
rules
and
alms
and
cadci
whatever
the
the
corporate
governance
in
place,
which
are
then
exposing
subset
of
those
services
and
and
configurable
options
for
the
builders.
So
it's
it's
actually
a
good
way
of
thinking
that
there's
a
three
different
section
so
to
say,
yeah.
D
D
Of
so
so
what
we,
what
we
typically
do
in
our
sales
page,
is
we
start
with
a
few
slides
on
what
we
believe
low
code
is
so
one
of
the
slides
that
is
in
there
is
that,
for
us,
low
code
has
nothing
to
do
with
a
Power
Platform,
at
least
not
in
the
way
that
we
position
that
slide.
We
always
say:
okay,
when
you
start
thinking
about
logos,
it
typically
misses
some
proper
governance.
It
misses
some
ownership.
D
There
is
no
documentation,
there
are
a
lot
of
things
and
that's
for
us
what,
where
we
see
a
risk
with
low
code?
If
you
don't
don't
take
care
of
that,
then
you
will
have
a
problem
there,
and
that,
for
us,
is
typically
the
same
that
we
saw
in
SharePoint.
We
could
go
rampant,
creating
I,
don't
know
completely
relational
database
models
in
SharePoint
lists,
with
local
columns.
D
That's
all
fine,
if
you
like
10
records,
if
you've
got
more
and
you
have
a
problem.
So
when
you
talk
about
low
codes
successor
might
be
a
too
big
of
a
leap
but
yeah.
Definitely
it's
the
same.
I
don't
know
Excel
macros.
There
were
a
lot
of
people
good
at
building,
Excel
macros.
Is
it
a
sustainable
model,
not
sure,
especially
not
in
2020.
D
C
And
I
think
maybe
the
difference.
There
is
right
that
I
think
the
biggest
promise
that
we
have
in
Power
Platform
are
connectors
right
and
the
ease
that
with
which
we
can
connect
to
LLB,
meaning
other
systems
out
outside
in
SharePoint.
You
could
do
it
in
a
past
with
BDC
and
all
of
that,
but
it
wasn't
as
simple.
To
be
honest,
it
was
a
simple
to
bcsbdc,
depending
what
version
we're.
D
So
so
you
could
say
yeah,
so
you
could.
You
could
say
that
the
success
of
the
power
plus
firm
in
in
part
has
to
do
with
the
fact
that
everyone
can
just
get
started.
I
mean
you
don't
have
to
have
a
degree.
If
you,
if
you're
able
to
read
a
few
sentences,
there
is
a
lot
of
learn
material
to
get
your
first
flow.
I,
don't
know
automate
some
processing
of
your
email
or
automate.
D
Something
in
your
calendar
really
really
easy
to
get
started,
and
then
you
can
grow
from
there
to
rebuild
it
or
share
it.
With
some
colleagues
and
all
of
a
sudden,
it's
team
owns
and
I
think
that
the
next
thing
is-
and
you
see
that
happening,
that
a
lot
of
the
announcements
that
you
have
now
around
the
Power
Platform
are,
let's
say
the
Enterprise
level.
D
So
that's
the
next
big
step
growing
from
me
to
your
team
to
a
real
Enterprise
solution,
and
that's
for
me
where
Fusion
development
starts
if
you're
building
something
that
only
runs
for
you,
you're,
probably
not
gonna,
build
too
much
cash
system
code.
I
mean
I
probably
would
because
I'm
a
developer
and
I
like
to
play
with
things,
but
a
typical
user
wouldn't
probably
do
that.
If
it's
starting
to
be
shared
within
a
team,
then
you'll
probably
reuse,
some
of
the
stuff,
that's
built
on
the
Enterprise
level,
whether
it's
teaming
or
custom
connectors.
D
And
then,
when
you
go
to
the
Enterprise
level,
that's
where
real
effusion
development
starts
to
take
off
an
Enterprise
architect
might
say:
hey
we're
going
to
expose
this
system.
We
need
custom
connectors
for
that
or
we
want
to
do
more
with
power
pages.
So
we're
going
to
invest
in
having
some
power
Pages
templates
available
that
we
can
use
as
a
sample
scenario.
C
I
think
the
interesting
part
is
right
because,
like
we,
as
you
said,
it's
really
easy
for
everybody
to
start
whether
it's
building
a
a
power
app
or
a
flow,
or
you
have
a
cat
walking
across
your
screen.
There
you
go
right,
so
it's
really
easy
to
start,
but
we've
probably
all
seen
like
really
elaborate
examples
to
the
point
where
people
are
building
physics,
engine
and
power,
apps
or
people
have
like
really
complex
flows
that
don't
fit
on
a
single
screen
on
a
really
big
screen
right.
C
So
in
a
way
to
paraphrase
you
know,
a
movie,
we
probably
all
know
like
a
license
to
use.
Powerapps
is
also
in
knowing
when
not
to
use
it.
So
where
do
you
see
a
place
where
you
should
like?
If
you
want
to
do
this,
you
should
stop
think
again
think
twice.
If
that's
really
what
you
what
you
want
to
do,
because
there
will
be
a
consequence
down,
the
road
can
I
answer
about
this.
D
D
If
you
don't
have
those
resources
or
you
expect
I,
don't
know
someone
signing
in
every
two
or
three
days
and
you
might
have
a
maximum
of
100
concurrent
users,
then
it's
probably
cheaper
to
use
power
Pages,
it's
the
same
with
for
me
power,
automate
versus
logic.
Apps.
There
are
things
you
cannot
do
in
logic
apps,
because
there
are
are
connectors
in
power
in
power
automate
that
are
not
available
in
logic
apps.
At
the
same
time,
it
might
require
you
to
do
Premium,
Power
automate
stuff,
which
is
a
premium
license.
D
So
then
it
might
be
cheaper
or
you
might
want
to
switch
from
premium
to
a
consumption
based
model.
So,
like
any
I
would
say
software
project,
there's
licensing,
there's
resources,
there
is
timing
constraints
and
all
those
constraints
determine
whether
it
will
be
I.
Don't
know,
power,
automate
logic,
app,
whether
it
might
be
a
custom
function
or
a
Docker
container
running
something
so.
B
D
For
ourselves,
we
have
sort
of
a
decision
three
when
to
use
what
we've
been
discussing,
that
for
the
last
six
months,
that
we
should
do
a
few
blog
posts
about
that.
So
that's
still
that's
still
on
the
list.
There
is
a
lot
of
content
out
there
that
you
can
use
to
map
what
you
need,
but
yeah.
It
would
be
interesting
to
see.
Hey
I've
got
this
problem.
What
would
sit
best
to
this
solution?.
B
C
Yeah
I
think,
like
the
aspects
you
mentioned,
like
things
like
pricing,
the
license
and
all
that
that
these
are
important
and
also
things
like
skills,
but
then
the
thing
that
I
aim
for
at
initially
was
really
the
complexity.
Part
right.
Imagine
that
money
isn't
isn't
irrelevant
aspect.
Let's
assume
that
you
could
build
a
game
in
powerapps.
Should
you
do
that?
I,
don't
think
so
right,
because
I
saw
you
will
hit
the
limits
right.
B
C
D
D
The
idea
is
that
there
is
this
bird.
The
bird
is
in
the
Stream
and
if
you
press
a
button,
the
bird
goes
up
a
bit
and
then
slowly
goes
down
again
so
I
understand
what
yeah
you
have
to
go
through
an
obstacle
course
it's
kind
of
like
Mario,
but
then
with
the
birds.
There's
one
button,
you
can
press
the
space
button
or
you
can
tap
your
screen.
D
And
the
whole
goal
of
the
game
was
to
last
as
long
as
possible
and
make
the
end
and
see
what
happens.
So
you
could
build
that
in
in
power
apps
and
it
it
wouldn't
be
too
complex
to
do
that
and
it's
still,
it
is
complex,
I
know,
but
compared
to
I,
don't
know.
Building
I
I
think
I
saw
Wolfstein
three
3D
being
built
in
by
someone
like
like
a
3D
ish
game.
I
was
like
holy
crap.
This
is
insane
I.
D
B
A
D
D
Step
like
yesterday,
yeah
there's
no
budget.
It
has
to
be
free
yeah
that
no,
so
one
is
timing.
Two
is
we
try
to
get
some
feeling
about
the
technical
complexity,
and
that
is
for
us
to
do
with
how
many
screens,
how
many
data?
What
are
we
trying
to
do
with
the
data,
because
one
of
the
advantages
that
you
have
in
the
Power
Platform,
if
you
use
dataverse,
is
things
like
data
flows
and
all
kinds
of
business
rules.
You
can
apply
to
your
data.
D
So
if
it's
like
a
business
solution,
then
it
definitely
makes
sense
and
we
try
to
understand
who
will
be
using
the
solution.
So
is
it
if
it's
like
sort
of
a
website
where
someone
can
fill
in
a
form,
then
the
Power
Platform
might
not
necessarily
be
the
best
way
to
use.
If
it's
a
internal
application,
then
it
might
work.
If
it's
a
SAS
solution,
then
probably
won't
be
Power
Platform
either.
So
we
try
to
get
something
around
that.
D
That's
what
we
typically
do
in
an
intake
to
to
let's
say
pitch
whether
it
will
be
locals.
If
it's
not
going
to
be
local,
we
always
will
pitch
the
fusion
development
approach,
but
because,
if
you're
using
Azure,
then
you
can
still
make
sure
that
our
custom
connector
is
available
that
things
like
logic,
apps,
are
being
used
just
to
prevent
that
you
have
to
reinvent
everything.
Yeah.
B
So
it's
not
a
one-off
implemented
for
that
scenario.
It's
more
flexible
for
future
adjustments
and
all
that
thanks
yeah
makes
sense
now
and
then,
let's
come
back
on
the
on
the
one
question
still
which
which
we
ask
or
when
we
jump
too
many
questions
ahead.
Is
this
really
a
partner
opportunity
and
business?
Is
there
money
on
it?
Is
that
a
because
you,
actually
you
defined
it,
really
nicely
that
it's
not
necessarily
for
your
customers
and
for
your
project?
It's
not
that
you
just
enabled
the
fusion
Dev.
B
D
So
what
we
see
is
that
things
like
the
starter
kit
or
Center
of
Excellence
Landings
on
things
that
are
all
things
that
you
can
help
a
customer
with
just
to
get
started
once
that
is
in
place.
You
can
help
them
and
that's
something
we
don't
do,
but
we
see
companies
doing
on
the
adoption
side
of
things
so
growing
their
local
practice
and
then
the
interesting
things
happen
is
that
a
company
starts
building
their
own
Solutions,
but
because,
as
a
partner,
you
see
so
many
different
solutions
and
different
customers.
D
You
have,
let's
say
a
broader
Insight
in
what
is
possible
or
what
is
best
practices.
What
would
work.
So
what
we
see
happening
is
from
time
to
time
we
get
asked
back
to
assist
or
review
things
that
they've
been
building
or
we
get
caught,
get
a
call
saying:
oh
we've
got
this
massively
complex
solution
that
we
need
to
build.
Can
you
have
a
look
of
it
at
it,
whether
it
makes
sense?
D
So
we
had
a
customer
calling
around
sap
integration
and
they
want
to
do
custom,
Dynamic
pricing
based
on
AI
models
in
Azure,
and
they
were
like,
oh
that,
Azure
and
and
sap
don't
integrate
the
way
that
we
run.
Can
you
build
a
an
intermediate
app
where
we
could
pull
in
data
from
both
and
you
can
have
some
screens
where
you
could
say?
D
I
want
this
and
that
and
then
and
then
write
it
back
to
sap
and
we're
like
that
sounds
like
a
pretty
good
good
opportunity
for
Loca,
because
all
the
technical
complexity
is
either
in
Azure
or
in
sap
and,
of
course,
we'll
need
to
build
complex
screens
and
you'll
need
to
think
about
the
ux
and
the
way
it
works.
But
in
a
way
it's
just
business
logic
being
built
and
that's
really
really
easy
or
easy.
That's
really
where
the
Power
Platform
shines.
So
for
that
that
definitely
makes
sense.
C
Also
in
our
aspect
to
add
to
that,
especially
for
our
devs.
Another
part
where
it
shines
is
off.
If
there's
one
thing
that
is
really
the
hardest
thing
on
earth
is
off
like
like
getting
the
right
thing
to
authenticate
like
it
takes
a
lot
of
time
to
do
it
right,
yeah
and
in
Power
Platform.
You
have
a
connector
which
is
like
a
few
clicks
and
it's
there
and
it
does
the
whole
all
of
and
tokens
and
refreshing
for
you.
So
even
as
a
Dev,
it
makes
perfect
sense.
C
Like
you
build
an
API
that
is
be
behind
aad
like
on
Azure,
you
can
do
it
really
easily
without
any
code
right,
so
you
can
put
in
front
easy
auth,
attach
it
to
your
AED,
and
you
have
Now
API
behind
ad
within
your
Arc
yeah
right
and
then
how
to
to
connect
to
it.
Well
from
Power
Platform,
you
build
a
a
connector,
and
that's
just
all
of
us,
but
you
don't
need
to
fiddle
with
that.
C
B
D
B
And
and
by
the
way,
absolutely
I
think
me,
and
while
the
Clark
in
a
completely
the
same
conclusion
with
this,
because
we
know
that
the
required
number
of
developers
is
going
exponentially
up.
So
basically
the
low
code
is
addressing
that
demand,
but
it
doesn't
mean
that
we
would
have
less
Pro
developers
because
the
amount
of
required
Pro
developers
are
actually
going
up
as
well.
So
it's
it's
just
a
addressing
that
demand
within
the
ecosystem
as
well.
C
Yeah
I
think
there's
going
to
be
two
things
right
like
for
one
we're
raising
the
bar
right
because,
like
so
much
Cool
Tech
is
available,
I
mean
we
already
see
it
with
the
chat
GPT
right
like
so
many
cool
things
can
be
done
without
you
having
necessarily
the
skills.
Beyond.
Writing
the
right
prompt
right,
so
we,
in
our
words,
the
tag
that
we
have
available
to
us,
raises
the
bar
with
the
things
that
we
can
now
build
to
do
because
of
the
tech
available.
C
More
things
will
be
built,
so
more
problems
in
the
business
will
be
optimized
and
and
automated,
but
then
devs
will
have
still
need
and
capacity
to
build
more
complex
things
right.
So
if
one
I
think
it's
it's
great,
because
it
frees
developers
and
limited
resources
that
they
have
and
the
unique
skills
that
they
have
to
work
on
truly
complex
things,
as
opposed
to
centering,
did
on
a
page
yep.
D
And
then
oh
I've
got
my
birthday
with
parts,
and
then
there
was
like
okay
10
of
the
customers
wanted
to
do
some
minor
tweaks
or
you
would
still
have
to
pull
the
code,
but
it's
not
that
I
spent
less
time
working
for
those
customers.
I
just
spent
less
time,
building
a
birthday
web
art
and
could
build
customer
specific
requirements
or
yes,
business
related
problems
could
be
tickled
rather
than
spending
money
on
listing
who
had
their
birthdays
the
coming
week,
so
I
see
the
same
happening
with
with
low
codes.
It's.
B
D
B
D
B
Let's
jump
on
those
with
the
world
like
excellent.
Thank
you
happy
one
more
time
on
the
on
the
discussion
and
it
wasn't
actually
an
interesting
coincident.
This
wasn't
really
a
plan
that
this
was.
The
previous
episode
was
with
Julie
Julia,
and
we
talked
about
almost
the
same
topic.
Actually
so
because
Fusion
Dev
it's
good
to
get
the
basically
two
perspective,
the
Microsoft
perspective
and
then
also
the
partner
perspective
on
the
same
topic
right
because
yeah.
A
B
Now,
let's
jump
on
the
on
the
weekly
articles,
and
so
we
do
have
articles
from
the
past
few
weeks
and
we
did
a
a
kind
of
a
random
selection
of
things,
because
obviously
we
cannot
go
all
of
the
awesome
stuff.
I
have
been
going
through
pretty
quiet
actually
from
a
Microsoft
site
within
the
past
three
weeks,
which
is
understandable,
but
at
least
in
a
developer
block.
We
had
this
awesome
announcement.
C
Yes,
definitely
I
can
right
so
last
year,
I
think
it
was
beginning
of
December.
We
released
a
community
preview
of
Microsoft
graph
developer
proxy,
which
is
a
tool
that
allows
you
to
model
API
errors,
and
originally
that
was
on
Microsoft
graph
in
version
0.3,
which
were
released
last
week.
We
extended
that
to
basically
any
API,
whether
Microsoft
graph,
SharePoint
arrest,
see
some
or
any
custom
API
you
might
have.
C
You
can
use
this
tool
to
model
four
to
nine
throttling
500
errors,
basically
any
kind
of
error
that
your
app
reasonably
might
experience
in
production
and
that
you
want
to
test
your
code
and
see.
Will
this
app
handle?
Basically,
these
errors,
the
way
it's
intended
to
right
because,
like
oftentimes
well,
what
we
see
is
that
service
errors
are
elusive,
they
happen,
but
they
never
happen
on
your
tenant
of
one
on
your
trend
of
one
developer
tenant.
You
have
things
always
work,
which
is
like
really
hard
to
test
your
code.
B
C
C
Now,
yeah,
though,
because
so
we're
so
just
recently,
and
let
me
give
you
a
bit
of
a
sneak
peek
on
the
CLI
team-
we've
been
thinking
about
ways
how
we
could
include
the
Microsoft
graph
developer
proxy
in
our
CI
pipe,
so
that
we
can
verify
it
as
yet
another
way
to
test
our
code
right
because,
like
we
invested
heavily
in
tests,
we
mock
apis,
but
we
also
want
to
see
like
one
have.
We
mocked
everything
the
right
way.
C
So
what
if
there
is
an
actual
error
and
two
have
for
everybody
else,
who's
interested
in
doing
the
same
kind
of
reference.
We
can
point
like
hey
like
if
you
want
to
bring
proxy
to
your
CI
pipes,
to
test
your
code,
here's
a
reference
you
can
look,
because
all
of
that
is
open
source.
So
you
can
just
have
a
look
at
our
setup,
the
actions
that
we
have
in
in
place
and
you
would
be
able
to
reuse
that
based
on
our
work.
C
So
that's
something
that
we
discussed
past
week
and
we
are
everybody
on
the
team
is
like
highly
pumped
about
doing
this.
So
I
think
it's
just
a
matter
of
time.
Before
that
is
available,
but
getting
back
to
CLI
in
the
on
the
last
day
of
2022,
we
did
another
release,
so
we're
released
version
6.1
with
more
commands
and
enhancements
to
help
you
manage
Microsoft
365
and
your
SharePoint
framework
projects
and
a
few
big
areas
that
we
we
tackled.
C
This
time
around
found
was
adding
support
for
upgrading
your
SharePoint
framework
projects
to
the
recently
released
version.
1.16.1
we've
added
more
Power
Platform
commands
to
help
you
do
more
stuff
in
that
area
and
then
another
one
cool
addition
is
the
markdown
output.
So
if
you
want
to
have
a
way
to
document
your
setup
or
your
farm
or
whatever
else
you
do,
you
can
now
get
a
report
in
MD
right.
So
imagine
the
list
of
your
whatever
you
have
sites
accounts
lists.
B
Referencing
documentation,
videos,
assets,
all
of
that
stuff
which
is
available
within
our
location,
just
to
kind
of
a
recap.
What
was
this
all
about?
Because
quite
often
you
you,
we
kind
of
forcefully
Force
accidentally
focus
on
Advanced
scenarios,
but
not
on
the
hey
I'm,
a
new
person
I
need
to
start
building
something
on
Microsoft
365.
B
How
would
I
do
that,
and
this
series
actually
goes
linking
through
the
the
previous
article
and
always
the
the
upcoming
article
as
well,
or
it's
going
to
be
updated
when
there
are
new
article
is
out,
so
you
can
easily
then
follow
up
on
the
series
afterwards
as
well.
So
it's
not
a
time
sensitive
thing
and
talks
about
the
different
scenarios
and
things
like
using
Microsoft,
Graphics,
spfx
Solutions
or
what
is
the
tenant
or
side
scope
deployment
so
more
stuff
on
this?
C
B
They
will
say
also
a
great
blog
post
from
Louisa
freeze
related
on
material
design,
component
library
and
for
power.
Apps.
They
actually
lose.
Freeze,
April
and
Robin
did
a
reason.
Their
Community
called
demo
on
this
one
as
well
and
basic
idea
here
is
that
well
they
they
created
this
design
model
where
the
look
and
feel
of
the
power
apps
have
been
improved
so
and
then
you
can
actually
increase
experience
and
make
make
things
better
and
it's
all
available
as
a
design
toolkit
in
the
GitHub.
B
So
that's
going
to
help
on
people
to
make
good
looking
power
apps
using
the
existing
components,
and
they,
of
course
take
contributions
as
well.
So
if
we
would
love
to
have
a
model
where
we
built
one
or
two
well,
a
set
of
controls
and
reusable
designs
together
with
Community,
because
you
know
that's
how
it
should
be,
we
as
a
community
are
so
so
much
stronger
as
we
build
things
aligned
together
rather
than
a
jillion
of
computing
messaging
and
all
of
that
stuff.
B
A
B
Luciferies
had
a
extend
f80
to
add
to
pronouns
to
people
cards
component
in
powerapps,
so
she's
kind
of
a
testing
out
a
designs
related
which
will
align
with
the
craft
toolkit
but
in
power
apps,
and
you
can
of
course
make
the
power
absolute
similar
as
craft
toolkit.
You
cannot
use
craft
toolkit
assets,
at
least
for
now
in
powerapps,
but
there's
a
interesting
scenarios,
potentially
there
in
future
and
she's,
basically
explaining
how
you
could
introduce
a
pronouns
in
the
card
like
she
her
underneath
the
name
in
here.
B
So
that's
that's
kind
of
the
storyline
within
this
blog
post.
What
do
we
need
to
do
to
add
that
additional
attribute
to
Azure
80
user
object
and
how
do
we
then
expose
that
using
the
graph
apis
so
really
really
cool
stuff?
Now
then,
David
had
a
awesome
announcement
on
Friday,
which
is
getting
a
lot
of
attention.
C
That,
yes,
we
have
program
in
the
Microsoft
365
platform
Community,
where
we
issue
digital
badges
for
all
different
kinds
of
things.
You
can
do
within
Community,
whether
you
speak
on
community
call
write
a
blog
Post
article
submit
a
sample,
contribute
to
one
of
the
many
projects
that
we
have.
It's
a
small
way
for
us
to
give
back
and
recognize
and
reward
your
work
right
also
for
a
way
to
for
you
to
be
able
to
show
that
to
everyone
else
right.
C
So
we
did
that,
and
for
this
year
we-
or
at
least
we
start
a
year
with
a
set
of
new
badges
along
more
projects
and
more
ways
to
recognize
your
awesome
work.
So
we
will
have
badges
for
list
formatting
sample
adaptive
card
extension,
CLI,
PNP
power,
show
Community
contributor
in
the
Microsoft
365
and
Power
Platform
Community
as
at
large
and
then
Power
Platform
samples
sharing
is
carrying
initiative,
independent
publisher
for
Power,
Platform
connectors
and
many
many
more
to
come.
A
C
B
Great
work
on
David
under
the
science
and
and
coordination
of
this
one
as
well
so
really
really
awesome
stuff.
Now
we
also
had
a
new
article,
some
some
new
things
which
happen
within
the
past
week,
so
Market
Anderson
had
a
new
blog
post
related
on
sharepoint's
list
and
libraries,
modern
versus
classic
view
settings,
and
this
is
kind
of
a
Market's
always
looking
into
having.
B
Can
we
please
have
everything
in
the
modern
until
for
now,
there
are
certain
settings
and
configuration
options
which
will
make
you
to
say
the
classic
settings
and
configuration
options
in
list
and
libraries
and
and
he's
basically
calling
out
the
settings
where
you
need
to
fall
back
on
classic,
and
this
is
actually
going
to
help
Microsoft
to
then
address
this
gaps
sooner
or
later.
So
thank
you,
Mark.
On
helping
with
that.
C
Yeah
absolutely
so.
This
is
a
really
cool
thing,
because
what
you're
seeing
on
the
screen,
if
you're,
looking
the
recording
right,
you're
seeing
a
delve
like
profile
page?
Yes,
but
it's
built
on
top
of
a
SharePoint
list.
So
you
have
the
data
in
the
list
like
a
person
info
with
their
about
projects,
that
they
do,
skills,
expertise,
schools
that
they
they
come
either
the
badges
that
they
have
with
whom
they
work,
basically
a
Dell
like
profile
page
but
then
build
on
top
of
a
SharePoint
list.
C
That
is
insane
that
reminds
me
so
much
about
of
a
single
page
ad
that
I've
built
a
while
back
I
think
with
angular,
even
something
like
10
years
ago,
probably
even
more
right.
It
was
basically
the
same
thing
kind
of
like
Hey.
How
could
we
have
a
richer
experience
to
Showcase
a
person's
profile
right
and
then
like
as
someone
we
had
delve,
but
now
you
could
build
a
similar
experience
on
top
of
a
SharePoint
is
that
is
insane.
This
is
really
cool
to
see
like
how
far
you
can
take
it.
Yeah.
B
This
is:
is
this
actually
real
world
production
ready?
No,
not
really!
That's
not
the
intend.
That's
as
such,
it's
more
on
how
far
we
can
take
the
the
list,
configuration
and
formatting
dependency
and
what's
the
art
of
possible
there
related
on
that
one.
The
Tweet
actually
has
links
to
the
micro
phrases,
five
unified
sample
gallery
and
from
here
you
can
easily
then
access
the
information.
B
C
B
True,
the
really
really
cool
stuff.
Thank
you.
Feder
Rico,
as
Sapia,
is
the
the
person
who
actually
provided
the
sample
so
really
radical
stuff.
So
now,
Marcus
Miller
had
a
dual
blog
post
and
what
I
will
explain
what
the
Dual
blog
post
actually
means
or
double
samples,
and
that
this
is
really
about
having
a
Microsoft
teams,
application
exposed
in
a
Microsoft
365
app
either
spfx
version
or
they're,
not
at
the
yo
teams,
person,
meaning
the
native
Microsoft
teams,
app
version.
B
It
could
be
just
as
well
teams
toolkit
version,
your
teams
and
teams.
Toolkit
versions
are
pretty
much
the
same,
so
they're
outputting
externally
hosted
application.
Spfx
version
is
the
one
which
is
the
Microsoft
365
hosted
application,
but
basically
a
blog
post
explaining.
How
would
you
do
that?
And
how
would
you
expose
the
the
application
to
be
then
available
across
multiple
applications
and
what
are
the
settings,
how
to
identify
where
you
are?
B
How
can
it
behave
differently
based
on
the
host
where
you're
actually
located
and
the
implementation
isn't
actually
pretty
pretty
decent
controls
and
all
of
that
implemented?
And
in
here
the
second
one
is
basically
the
yo
teams
version
and
I
said
it
could
be
just
as
well:
teams
toolkit,
it's
externally
hosted
application
style
and
basically,
how
do
I
create
those?
What
are
the
outputs,
how
do
I?
How
do
I
do
the
implementation
of
that
in
the
Microsoft
teams?
B
It's
actually
pretty
cool
that
you
can
have
almost
a
similar
style
experience
and
then
it's
up
to
the
developer
to
decide.
Do
we
need
to
host
this
externally?
Do?
Does
that
provide
value?
Can
we
host
that
internally,
using
spfx
and
or
in
Microsoft
trade
65?
What
is
the
right
way
of
doing
things,
so
both
of
them
have
their
own
advantages
and
disadvantages.
Of
course,
thank
you.
Marcus
on
that
one
we
have
an
article
from
Leon
arms,
Armstrong,
Armstrong,
Arms,.
C
Yeah
this
is
this:
article
is
about
Microsoft
syntax
pay
as
you
go,
configuring
an
analysis
and
I
think
it's
about
like
setting
up
the
first
steps
for
you
to
be
able
to
use
syntax,
and
how
do
you
set
up
your
tenant
to
be
able
to
use
it?
What
are
the
different
options
for
building
and
so
forth?
And
so
on?
So
a
really
nice
breakdown
of
the
different
options
that
you
have
to
take
in
your
tenant
in
Azure,
to
get
everything
in
place
to
be
able
to
use
the
power
of
syntax
yep.
B
And
and
again,
Microsoft
index
is
the
content
management,
automation,
artificial
intelligence,
machine
learning.
Behind
of
the
sense
it's
it's
actually
pretty
mind-blowing
when
you
see
it
in
accent
and
and
the
way
it's
going
forward,
leaps
or
forward
with
all
of
the
new
releases
and
features
which
are
coming
up
now,
then
we
had
a
article
from.
Let
me
click
that
one
from
sudharson
related
on
PMP
react
controls,
part
8,
folder
picker.
B
B
Do
that,
one
there
we
go,
but
how
you
can
actually
do
the
the
the
bigger
implementation
in
place
and
how
you
can
access
the
information,
how
we
show
a
panel
on
the
left
side,
and
so
these
are
the
BMP
reusable
controls
which
will
improve
your
productivity
as
a
developer
if
you're
building
for
spfx
and
there
we
go
now
I'm
out
of
from
there
and
there's
an
even
a
sample
available
on
that.
Then
there
was
an
article
from
Michaela.
C
D
C
B
Why
isn't
that
in
product?
That's
a
good
question:
we
we
should
have
a
a
baseline
components
from
the
products
we've
been
a
pretty
in
hesitant
to
actually
provide
Baseline
components.
So,
for
example,
with
one
of
the
examples
being
the
web
part
title
as
an
example:
it's
it's
provided
through
BMP
controls
not
through
the
product
and
not
to
provide
any
two
or
BNA
that
implementation
Styles.
But
again
we
could
actually
have
this
kind
of
a
based
on
component
coming
from
the
product
as
well.
So
fair
point,
good
feedback.
B
Okay,
we'll
see
what
we
can
do
in
the
future,
so,
but
really
really
cool
and
I
know.
Michael
is
scheduled
to
actually
do
a
live
demo
on
this
one
in
community
call
pretty
soon
as
well
so
good
to
see
that
one
in
practice,
then
we
had
a
a
new
sample:
Microsoft
teams,
apps
sample
from
Alex,
Clark
and
and
his
friends
related
on
the
request.
B
B
C
Yeah
and
it's
not
one,
so
this
is
a
first
part
of
series
that
he
that
he
has
about
using
device
of
graph,
API
and
Power
Platform
right.
So
Microsoft
graph
is
the
API
to
data
and
insights
that
you
have
stored
in
Microsoft,
365
right
and
you
can
get
anything
and
everything
through
it.
You
can
get
info
about
users.
Group
application,
calendars,
emails,
you
name
it
tons
of
info
available
to
you
through
this
API
and
Peter
goes
through
the
stuff
like.
How
would
you
use
graph
right
when
there
is
no
connector?
B
Yep,
it's
pretty
radical
stuff
as
well.
Thank
you
for
that
then
Workman.
This
responded.
I
had
a
blog
post
from
a
19th
of
December
building,
Microsoft
teams,
app
posting
message
to
teams
on
behalf
of
the
current
user,
which
is
a
quite
common
scenario,
actually
so,
basically
working
as
the
user
as
you
are
operating
against
the
Microsoft
teams,
and
how
would
you
do
that
and
that
implementation
details?
Thank
you
bartaman
on
that
implementation
reference
in
practice.
So
this
is
basically
that's
the
message,
but
you're
not
posting
that
as
a
bot.
B
C
Yes,
that
was
just
an
announcement
that
we
picked
up
on
and
that's
an
interesting
thing.
So
apparently
at
Microsoft
we
release,
or
we
experiment
with
a
new
text
to
speech.
I
guess
AI
based
technology
right.
That
allows
you
to
reproduce
speech
on
a
very
small
sample
of
text
that
that's
incredible,
like
imagine
how
productive
you
can
get
like
if
you
need
to
I,
don't
know
dub
videos
or
record
yours
speech
on
their
video
and
I
write
some
stuff
or
maybe
there's
somebody
who
who
cannot
read
right
and
they
want
to
read
the
message.
C
B
C
B
C
B
Whole
week,
cool
and
then
three
more
videos
and
then
we'll
close
up
for
the
for
the
episode.
So
first
of
all,
Paulo
had
a
new
video
on
hosting
SharePoint
framework.
1.16
web
Parts
in
office
and
outlooks
are
basically
building
Microsoft.
Racist,
provide
applications
with
spfx
part
is
just
about.
If
you
come
from
a
SharePoint,
World
web
part
kind
of
makes
sense.
It's
a
web
part
which
are
exposing
in
Outlook
or
in
office.com.
If
you
don't
come
from
a
webpal
from
a
SharePoint
World
web
part
is
just
it's
a
panel.
It's
a
component.
B
It's
a
widget,
it's
a
widget
widget,
which
is
basically
the
component,
which
is
then
the
application
for
Outlook
and
office
and
for
SharePoint
and
for
themes,
and
he
talks
about
how
to
actually
make
that
happen.
So
you
can
reuse
exactly
the
same
piece
of
code
across
the
different
applications,
including.
C
B
Well,
spfx
is
a
industry
standard
technology
and
you're
using
West
Stack
development,
and
it's
automatically
hosted
with
a
single
sign-on
automatically
happening
in
Microsoft
365..
It's
really
the
easiest
way
to
build
your
react
components
and
expose
cool
applications
in
Microsoft
365.,
so
mic
probe,
yes
good
and
then
April
I
had
a
new
video
related
on
disk
reservation.
Powerapps,
template
maker
reservations
easier
and
that's
a
really
cool
sample
as
well.
So
it
talks
about
the
existing
example,
which
is
available.
How
do
I
get
that
into
a
use?
How
that
just
behaves
and
all
of
that
stuff?
B
But
it's
out
it's
actually
also
kind
of
a
showcasing
things.
What
people
didn't
necessarily
understand?
What
was
the
the
point
of
the
video,
the
technology?
What
would
be
the
benefits
out
of
it
so
good
way
of
reusing
the
the
videos
and
reusing
the
assets
and
then
I
think
he
is
actually
he's
calling
out
also
how
many
views
some
of
the
videos
like
we're
getting
so
really
cool
stuff
as
well
yeah
cool
and
you
will
get
double
chain
there.
We
go
good
good,
excellent,
what's
happening
this
week,.
C
Planning
planning,
as
people
get
back
to
work,
we
can
finally
get
to
plenty
in
a
sense:
well,
not
really
planning,
but
more
alignment
and
agreement
we
planned
already.
We
have
plans
in
place.
Now
is
the
time
to
align
double
check
that
we
are
still
in
sync
and
execute
execute
execute.
So
you
will
be
hearing
more
from
us,
or
at
least
from
me
in
many
ways
like
we
will
keep
building
CLI
for
Microsoft
365.
C
B
And
on
my
side,
quick
teasers
at
the
time
when
this
video
goes
out,
we
should
have
already
released
the
Microsoft
graph,
Pages
API
for
preview
and
Microsoft
graph,
and
there's
going
to
be
announcement
on
that
one.
This
week
we
also
have
the
new
Microsoft
learn
module
for
Viva
Ace
development,
which
is
going
to
be
announced
on
Wednesday
so
day
before
day
after
the
district
goes
live
depending
again,
when
you're
watching
this
there's
going
to
be
announcement
related
on
Viva
toolkit
and
a
lot
of
other
stuff
actually
happening.
B
B
Sure
that's
why
we
have
the
community
calls.
So
people
can
actually
ask
questions
so
absolutely
if
they
say
there's
a
there's,
a
quite
difference.
So
in
some
of
the
videos
we
even
have
the
video
in
YouTube
and
then
we
have
the
community
called
recording,
as
on
top
of
that,
because
that's
actually
cool.
So
it's
not
overproduced
and
it's
live
and
there's
a
certain
amount
of
difference
when
it
happens
like
I.
Don't
think
so.
Yes,
exactly
exactly
that's
it.
For
now,
we'll
get
back
at.
C
B
We'll
be
we'll
be
back
within
a
week.
Thank
you,
Abby,
one
more
time
for
the
discussions
and
thanks
everybody
for
watching
keep
the
feedback
coming
and
if
you
have
good
ideas
on
who
would
you
like
to
see
as
our
visitors,
let
us
know
and
we'll
we'll
reach
out
and
see
who
we
can
get.
Thank
you
for
that
thanks.
Everybody
cheers
bye.