►
From YouTube: PowerShell 7 2 with Jeff Hicks
Description
PowerShell v7.2 is now a GA release. See what new features are available and how you can customize the screen prompts with the new variable that contains ANSI terminal colors."
Join Jeff Hicks for a look at the new PowerShell v7.2 GA release and learn about the new features available!
Speaker Bio:
Jeff Hicks is a a long-time Microsoft professional, a multi-year Microsoft MVP in Windows PowerShell (now Cloud and DataCenter Management), and an IT veteran with almost 30 years of experience, much of it spent as an IT consultant specializing in Windows server technologies. Jeff designs solutions, deploys the technology, and provides expertise on business system performance, architecture, and security. Jeff as an independent author, teacher, and consultant. He's co-authored or authored several books, course-ware, and training videos on administrative scripting and automation.
About RTPSUG:
We're a group of PowerShell pros from all walks of life who love to share ideas with fellow community members. Our meetings are open to anyone who would like to talk about and learn more about how to PowerShell!
A
Good
evening,
everyone
or
good
afternoon,
depending
on
where
you
are
thanks
for
having
me
back
again,
I'm
going
to
talk
about
powershell,
7
and
maybe
answer
some
questions.
Show
you
some
things
for
those
of
you
who
haven't
got
on
board
and
answer
my
question.
But
what
are
you
waiting
for?
So
that's
what
we're
going
to
look
at
here
tonight,
so
powershell
7.2.1,
that
is
the
current
shipping
version
of
powershell.
A
For
those
of
you,
who've
been
waiting
and
wondering
powershell.
7
is
no
longer
a
v1
product.
You
know
we've
had
powershell
7
for
quite
a
while
if
you've
been
waiting
thinking.
Okay,
let's
wait
to
pop
microsoft,
gets
all
the
bugs
out
of
it.
Well,
it's
there's
always
going
to
be
something,
but
it's
no
longer
v1.
So
if
that's
what
you
were
waiting
for,
you
should
be
able
to
get
rid
of
that
idea
and
just
start
adopting
powershell
7.
A
development
for
powershell
seven
is
ongoing
right
now.
The
cadence
for
microsoft
is
a
ga
once
a
year
and
then
an
interim
release
every
six
months.
So
right
now
we're
in
seven
point
two
point
one.
I
think
the
point
one
was
a
quick
re-release
to
fix
a
bug
or
something
so
powershell.
Seven,
that's
where
microsoft
is
spending
all
of
their
time
and
money
windows
powershell
at
this
point,
if
you
didn't
get
the
memo,
you
should
consider
it
deprecated.
A
It's
not
going
away,
it's
not
going
to
disappear
and
we
still
have
vbscript
that
you
can
run
on
windows,
11
and
no
one's
been
using
vbscript
for
close
to
20
years.
So
windows
powershell
is
not
going.
I'm
sorry,
it's
not
going
away,
but
it's
no
longer
being
developed.
In
fact,
this
also
includes
the
partial
iz.
A
So
if
there
is
something
that,
for
some
reason,
does
not
run
in
powershell
seven-
and
this
was
the
case
with
powershell
seven
one-
the
app
x
modules,
for
example,
would
not
run
because
there's
a
limitation
in
dot
net
core
we're
fine,
no
big
deal.
I
would
just
then
hop
into
windows,
powershell
and
use
the
fbx
command
list.
If
I
needed
to
so
you
can
retain
windows
powershell,
but
you
can
still
jump
into
powershell
7
and
make
that
your
primary
shell
and
that's
really
what
I'm
doing
this
year.
A
A
You
can
upgrade
powershell
on
your
management,
desktop
or
jump
server
wherever
you
are
running
your
powershell
console
or
running
your
scripts
from
that's
the
place
that
you
need
to
run,
powershell
7.2
or
whatever
the
current
version.
Powershell
7
is.
When
you
get
around
to
upgrading
to
it,
we're
not
going
to
worry
so
much
about
the
servers.
A
Your
servers
can
they
can
stay
at
windows,
powershell
5.1!
You
don't
have
to
upgrade
everything
in
your
environment.
The
only
place
where
I
encourage
you
to
move
to
powershell
7
is
on
your
desktop.
Your
admin
desktop
where
you
are
running
and
writing
your
code,
because
you're
still
going
to
use
remote
management,
so
you
use
powershell
remoting
that
doesn't
change
you
and
you're
using
remoting
right
you're,
not
logging
into
servers
that
sort
of
thing.
A
So
as
long
as
you're
using
powershell
remoting
and
doing
all
the
things
that
we
used
to
do
and
are
still
doing,
you
can
still
do
that
from
a
powershell
7
box.
You
can
manage
those
windows,
5
1
servers
with
invoke
command
and
entropy
of
session,
and
it's
going
to
continue
to
use
the
device
man
protocol
and
the
winner
m
and
all
that
stuff
everything
we've
been
doing
all
along.
That
does
not
change.
A
If
there's
some
feature,
that's
in
powershell
7
that
you
want
to
take
advantage
of
in
a
remoting
session,
say:
there's
a
new
commandlet
or
a
new
parameter,
or
some
bug
fix
for
a
commandlet
that
didn't
work
in
five
one,
but
it
works
now
in
v7,
and
you
want
to
run
that
on
a
remote
server
in
a
remoting
session
yeah.
Then
you
might
need
to
push
that
server
up
to
powershell
7.,
but
don't
feel
that
god
I
have
to
upgrade
all
my
servers.
No,
you
don't.
A
A
You
can
have
a
five
one
endpoint
and
the
7.2
endpoint
on
the
same
box
or
you
can
go
to
ssh
something
we'll
talk
about
a
little
bit
later,
so
some
other
reason
why
I
think
you
should
be
considering
if
you're
not
already
using
powershell,
seven
there's
a
much
better
shell
experience
I
mean
I
spend
my
days
in
a
powershell
prompt,
I'm
thinking.
Some
of
you
are
using
powershell
interactively
to
do
things
in
your
network.
A
A
A
It
saves
us
some
keystrokes
I'll
show
you
that
here,
if
you've
not
seen
that
before
new
command
like
get
air,
microsoft
has
revisited
the
whole
error
object
and
made
a
little
bit
easier
to
work
with
it's
really
cool
stuff
with
ansi
rendering.
I
love
this
stuff.
I'm
spending
a
lot
of
time
playing
with
playing
with
this
feature
a
command
prediction
which
technically
is
a
ps,
read
line
feature,
but
it
really
comes
to
play.
A
I
think
in
powershell,
seven
much
better
performance
in
powershell,
seven,
a
lot
of
you,
I
know,
have
heard
about
the
dash
parallel
parameter
with
for
each
object.
There's
a
new
console
based
progress
bar
in
powershell
7.2
I'll,
give
you
a
peek
at
that.
If
you've
not
seen
that
before
and
the
usual
updates
to
the
commandlets
and
engines
a
lot
of
things
that
microsoft
has
worked
on
to
make
powershell
7,
faster
and
more
efficient
and
certainly
remoting.
A
A
So
I'm
going
to
jump
into
powershell,
sorry,
vs
code
and
I'm
trying
to
figure
the
best
way
to
do
this.
Sir,
there's
a
bitly
link
and
I'll
share
this
again
later,
but
if
you
want
to
take
note
of
that,
grab
a
screen
capture.
Whatever
my
demo
file,
I'm
going
to
go
through,
invest
code,
you
can
grab
from
a
github
gist
and
that
link
will
take
you
to
it.
B
A
A
So
one
of
the
things
we
have
in
vs
code-
I'm
sorry
in
powershell
seven.
There
are
like
some
new
powershell
variables.
That
start
with
is.
Let
me
just
try
to
get
my
screen
here.
So
let's
do
get
variable
is
so
you
could
use
these
from
the
console
in
your
scripts.
To
say:
hey
am
I
running
on
a
windows
box
on
a
mac
and
on
linux
or
windows.
A
So
that's
kind
of
a
handy
little
thing
to
know.
If
there
is,
of
course
the
ps
edition
get
my
keys
to
work
here
there
we
go
ps
edition
for
core
or
powershell
7
you'll
get
core
on
windows
powershell.
It
will
be
desktop
and
of
course,
the
ps
version
table,
which
we
all
know
about
and
you'll
see
that
a
little
bit
different,
I'm
going
to
use
a
wsl
command
to
get
to
my
ubuntu
instance.
A
And
look
at
the
version
table
on
linux
box
because
you
get
a
little
bit
a
slightly
different
look
there.
So
you
can
see
the
platform
there
is
unix
versus
win32mt
for
windows
and
that
sort
of
thing,
so
we
have
some
things
in
powershell
7
that
make
it
a
little
bit
easier
to
determine
hey
what
platform
am
I
on.
A
A
A
A
A
What
you
might
want
to
do,
if
you
have
some
long-running
things
you
want
to
run,
but
you
don't
want
to
sit
around
and
wait
for
that
first
command.
To
finish,
you
want
to
go
to
lunch,
so
I
say
I'm
going
to
chain
this
command,
I'm
going
to
hope
that
it
finishes
and
when
it
does,
then
I
want
to
run
another
command,
and
you
see
I
have
a
demo
here
in
a
second
where
you
can
chain
a
bunch
of
these
things
together.
A
So
chaining,
though,
can
affect
the
output.
So
let
me
create
a
variable
here
to
my
other
laptop
and
I'm
going
to
do
test
ws
man
and
then,
if
it's
successful,
then
run
get
volume.
Now
you
see
the
output,
there
is
kind
of
funky,
that's
not
what
you
would
normally
expect
and
that's
because
what's
happening
is
both
commands
are
running
in
the
same
pipeline
and
so
you're
getting
two
types
of
objects
coming
through
the
pipeline.
A
A
A
A
A
A
I
look
at
this
more
for
actual
the
experience
of
working
in
the
shell.
Some
people
may
find
this
a
little
more
useful
and
that's
also
true
of
the
ternary
operator.
So
normally
we're
used
to
you
know,
if
parentheses.
So,
if
some
condition
is
true,
then
we're
going
to
run
some
code
else.
We
can
run
some
other
code
or
there's
also
else.
If
the
ternary
operator
has
some
code
that
has
to
evaluate
as
true
or
false,
then
it's
a
question
mark.
Then
you
run.
A
A
A
So
if
the
day
of
the
week
equals
wednesday,
then
I'm
going
to
run
my
would
we
midweek
back
up?
Otherwise
I'm
not
going
to
do
anything
it's
for
me
personally,
I
would
just
assume
if
I
was
putting
this
in
a
script,
I'm
probably
going
to
continue
to
use
if
an
if
statement,
but
if
I'm
doing
something,
quick
and
dirty
at
the
console,
the
trinity
operator
saves
me
some
keystrokes
and
could
be
a
little
faster
and
easier
to
work
with.
A
A
A
So
test
difference,
man
worked
so
get
volume
ran.
Otherwise,
if
it
had
not
been
around,
then
I
would
have
done
right
warning
and
that's
what
would
have
come
up
to
the
screen
so
like
this.
So
let's
change
to
a
bad
server
name
same
command,
and
now
I
get
the
the
warning
again.
You
could
easily
write
this
with
an
if
else
statement,
but
some
people
really
like
this
ternary
operator
and
again
it
can
make
your
life
a
little
bit
easier,
maybe
at
the
console
kind
of
once
you
get
familiar
with
the
syntax
of
it.
A
What's
nice
here,
is
we
get
better
formatting
of
the
error
object
so
before,
and
we
still
have
dollar
error
that
still
exists.
That
variable
hasn't
changed
still
has
a
list
of
all
of
the
errors
that
have
happened
in
the
same
order,
but
I
can
now
pipe
this
to
get
error
and
get
a
formatted
nicely
formatted
view
of
that
error
message.
A
A
A
To
parse
the
bot
that
up
to
parse
the
error
object
into
something
that
might
be
a
little
more
meaningful,
but
having
that
get
error
command
makes
it
much
easier
to
look
into
the
errors
that
you
have
gotten
in
your
powershell
session.
Any
questions
on
that.
Are
we
good
with
that
that
look
interesting
to
anyone?
A
A
You
can
use
ansi
and
windows
powershell,
but
you
have
to
use
the
character,
27.
and
escape.
That
is
the
escape
character
that
you
would
use,
I'm
not
going
to
get
into.
You
know
what
ansi
is
and
all
of
that,
but
this
becomes
a
nice
easy
way
of
adding
some
color
and
style
to
your
powershell
work,
which
microsoft
has
done.
A
Now
some
of
these
settings
will
overwrite
the
host.private
data,
which
is
what
we
used
to
use
in
the
past,
or
they
might
be
controlled
by
the
hosting
application,
for
example-
and
this
is
probably
not
going
to
work
here
so
if
I
run
white
right
warning,
I'm
getting
basically
the
color
hopefully
comes
across
on
the
screen
that
you
see
here.
That
is
this
value,
which
is
also
the
same
as
the
yellow
value
in
host
dot.
Private
data,
which
is
really
what
I'm
using
here
bill
host.
A
So
host
up
private
data
see
the
warning.
Foreground
color
is
yellow
and
that's
really
what
the
yellow
is
here.
One
thing
to
be
aware
of
these
colors
and
the
way
that
they
look
may
vary,
especially
if
you're
using
windows,
terminal
and
different
color
schemes.
So
that's
why
it's
nice
to
see
what
they
look
like,
but
you
may
want
to
change
some
settings
where
you
can
change
them
to
make
something
a
little
bit
easier
to
read,
based
on
your
color
scheme
anyway.
A
A
B
A
A
B
A
Now
some
of
these
settings
like
the
foreground
settings
and
the
background
settings
these
are
hard-coded.
You
cannot
change,
for
example,
what
the
code
is
for
black,
but
you
can
use
these
settings
so
that
you
don't
microsoft
added
these,
so
that
you
don't
have
to
try
to
figure
out
okay,
what's
the
ansi
setting
for
magenta,
if
I
want,
I
can
say
you
know
what
I
want
my
table
header
to
use
the
background
bright
black.
So
I
want
to
use
this
that
setting
there.
A
I
don't
have
to
know
that
it's
100
m
all!
I
can
see
that
that's
background
bright
black
and
just
set
the
table
header
setting
to
that
and
go
back
to
get
process,
and
now
I've
changed
that
table
header
again.
If
this
is
something
that
I
want
all
the
time,
I
would
just
put
that
command
in
my
powershell
profile.
A
A
In
fact,
I
like
that.
I
might
end
up
making
that
part
of
my
profile,
but
this
is
where
you
have
to
test
it,
because
that
may
look
different
in
different
color
schemes
based
on
what
you're
running,
if
you're
running
a
windows
terminal
in
vs
code.
I'm
sorry
if
you're
running
powershell
in
windows,
terminal.
A
A
A
A
File
info
come
to
life,
and
so
every
time
you're
in
a
directory
and
doing
a
directory
listing
you'll
get
these
values,
and
you
can
customize
that,
if
you're
interested
in
learning
more
about
ps
style,
I
just
haven't
had
an
article
published
a
week
or
so
ago
on
four
sysops
I'll
have
the
the
link
here.
That
goes
into
much
greater
detail
about
this
and
also
shows
you
how
to
customize
the
the
file
settings.
That
sort
of
thing
that's
really
fun.
A
A
A
A
A
A
A
A
B
A
Might
but
I
I'm
all
set
up
to
be
using
the
integrated
console,
so
I
you'd
have
to
experiment,
I'm
always
using
the
integrated
console.
So
I
I
think,
because
you
know
a
lot
of
stuff,
I'm
showing
you
like,
like
the
the
ps
style
and
the
command
prediction,
that's
stuff.
That
makes
much
more
sense
and
I
use
all
the
time
when
I'm
in
the
my
windows
terminal
powershell
sessions
actually
running
commands.
If
I'm
in
vs
code,
I'm
writing
scripts
and
functions
and
the
integrated
terminal
is
really
just
to
see
what
is
going
on.
A
A
So
this
is
the
console
grid
view.
So
it's
a
grid
view,
but
it
runs
in
the
console
and
you
can
select.
You
can
come
down
here
and
you
can
select
things
and
the
selecting
kind
of
happens
automatically.
I'm
just
hitting
the
space
bar
hit
enter
and
then
it
just
automatically
passes
them
through
to
the
pipeline.
A
A
I
kind
of
like
that
better
than
upgrade
view
because
sometimes
upgrade
view
you
can't
control
how
wide
it
gets,
because
I
have
a
really
wide
monitor
most
time
when
I
launched
that
it
ends
up
spreading
across
my
entire
44
inch
monitor
and
I
got
to
resize
and
it's
just
a
nuisance.
I
really
like
the
out
console
grid
view.
Again,
that's
only
a
powershell
7
feature
and
it
does
not
work
in
powershell
remote.
A
A
A
A
A
We
don't
have
the
problem
with
the
progress
bar
in
5.1
of
overriding
text
that
would
used
to
be
in
your
console
and
it
performs
much
faster
now.
One
drawback
is
that
you
may
lose
some
data
because
we
no
longer
have
the.
I
believe
it's
current
prog
current
operation
that
gets
omitted,
I
believe,
from
the
output.
So
if
you
have
scripts
that
are
using
that,
you
may
need
to
adjust
your
code
if
you
want
to
take
advantage
of
the
new
progress
bar.
A
A
The
whole
point
of
for
each
parallel
is
that
you're
able
to
run
a
script
block
in
parallel
running
basically
in
multiple
run
spaces.
So
there's
some
overhead
involved,
not
everything
runs
faster,
just
because
you're
running
it
in
parallel.
You
really
want
to
limit
this
to
things
that
are
going
to
take
a
long
time
to
run
and
can
run
you
know
simultaneously
or
in
multiple
run
spaces,
and
you
can
throttle
the
number
of
run
spaces
that
your
kick
off
and
that
sort
of
thing.
A
So
I
have
some
code
here
which
I'm
not
going
to
run
this
script
block
here
is
basically
a
function.
An
unnamed
function,
that's
going
to
do
a
directory
listing
of
a
file
of
a
folder
and
then
print
out
an
object
that
shows
me
how
many
files
are
in
the
folder,
how
big
it
is,
and
that
sort
of
thing.
So
when
I
run
this
for
about
five
locations
here
that
takes
about
40
seconds
to
run,
but
I'm
going
to
run
it
with
the
for
each
parallel.
A
A
And
then,
if
you
look
at
the
end
right
host,
you
can
see
that
they
are
ending
at
different
times
and
it's
finishing
up
during
the
windows
directory
right
now,
which
just
take
another
moment,
and
this
should
run
about
half
the
time.
At
least
it
has
been
in
my
testing
all
right,
so
that
didn't
run
that
much
faster.
Now
in
this
particular
case,
you
know
the
other
thing
I
have
going
against
me:
potentially
is
disk
contention
or
other
things
going
on
on
my
system.
A
A
A
A
A
A
A
A
A
I
don't
we'll
get
sidetracked
trying
to
that's
a
that's
a
whole
other
presentation
on
how
to
set
this
all
up,
and
for
my
linux
boxes,
like
the
fedora
box,
I
didn't
get
prompted
for
a
password
because
I
had
got
ssh
keys
set
up
for
that
particular
server.
Otherwise
it
would
have
prompted
me
for
credentials.
A
B
A
A
A
A
A
A
B
A
The
windows
boxes
put
that
in
the
windows:
powershell
module
directory,
the
powershell
7
box
like
server
1,
even
though
it's
running
windows,
it's
running
ssh
and
I
connected
to
powershell
7
on
it,
and
so
it
installed
in
the
powershell
7
directory,
which
is
powershell
and
those
modules.
So
when
you're
doing
this
kind
of
cross-platform
remoting,
you
do
have
to
take
into
account
and
add
logic
to
your
code.
A
A
A
A
A
A
B
A
All
right,
so
I'm
just
going
to
leave
I'm
not
going
to
go
into
full
screen.
I'm
just
going
to
leave
the
slide
here
and
kind
of
answer,
some
questions
or
or
ask
the
question
for
those
of
you.
What's
holding
you
back
for
those
of
you
who
are
not
running
powershell
7,
what
is
the
the
roadblock
or
what
is
the
perceived
roadblock?
Maybe
I
can
answer
that
or
get
you
pointed
in
the
right
direction.
B
A
Yeah
I
mean
again,
you
can
you,
can
install
powershell
7
side
by
side?
It
has
its
own
execution
policy.
Has
its
own
remoting
end
points?
Now
there
are
some
things
that
we
don't
have
in
powershell,
seven
like
there's,
no
gia
dsc,
which
is
being
worked
on.
I
think
gia
might
be
being
worked
on,
but
you
still
have
windows
powershell
for
the
for
those
things.
If
you
need
them.
A
B
A
A
B
B
A
B
It
was
actually
what
introduced
me
to
it,
and
you
know
kind
of
kicking
and
screaming
a
few
years
ago,
and
I'm
I'm
really
glad
that
it
did
but
a
majority,
I
wouldn't
say
a
majority,
well
yeah
majority
of
what
I
use
it
for
is
administration
of
that
stuff.
It's
way
faster
than
using
the
the
web
portals
that
oh
yeah
yeah
in
seconds.
A
A
Get
for
the
github
thing,
hopefully
someone
grabbed
that
my
blog,
my
github
repo,
which
all
my
modules
are
up
there.
You
know
phil
talked
about
you
know
looking
at
github
code,
so
you're
more
than
welcome
to
browse
through
the
variety
of
stuff
that
I
have
there
and
then
the
last
thing
just
to
let
people
know
about
something
new
that
I've
started
this
year.
A
Is
I
have
a
kind
of
a
premium
newsletter
on
sub
stack
that
is
subscription,
based
that
I'm
writing
about
three
or
four
articles
a
month
that
are
really
deep
dive
into
the
culture
of
powershell
and
not
so
much.
You
know
necessarily
how
to
do
something
about
why
you
should
do
it
using
powershell
and
so
that,
if
that's
something
that
might
interest
you,
you
could
try
for
a
month
or
there's
there
are
free
subscriptions,
you
can
sign
up
for,
but
you
won't
get
the
full
experience,
but
that's
something
that
I
have
out
there.
B
B
A
A
B
A
B
A
That
comes
back.
I'm
always
telling
people
read
the
help,
even
for
commands
that
you
think
you
know,
because
there
may
be
an
example
that
maybe
you
didn't
recognize
before
didn't
realize
it
was
there
or
didn't
register
with
you,
and
it
says
oh
well,
that
solves
my
problem
or
you
discover.
Oh
there's
a
new
parameter,
for
example,
in
powershell
7
there
are
new
parameters
to
convert
to
html.
A
So
if
you
you're
right,
if
you
don't
go
and
look
at
that
command
lit
and
look
at
the
help,
you
won't
discover
that
and
they
may
be
things
that
you
need.
So,
as
you
are
working
on
your
code
say
you
know
what
I
haven't
looked
at
the
help.
First
of
all
update
the
help
and
say
I
haven't
looked
at
the
help
for
you
know,
convert
to
html
in
a
while.
Let's
see,
if
there's
anything
new,
that's
just
a
habit.
You
have
to
get
into.
B
A
A
They
kind
of
did
that
with
help
right,
so
you
no
longer
get
the
full
help.
When
you
saw
on
a
new
powershell
install,
you
have
to
go
and
update
the
help,
and
I
think
that
the
it's
the
same
logic
for
the
engine.
You
know
they
don't
want
necessarily
to
make
powershell
7
the
default
or
you
know
add
it
to
be
the
default.
A
A
A
B
Well,
I
think
I
think
john's
comment
about
how
they're
working
to
get
it
into
the
as
an
installed
feature,
and
that's
where
my
frustration
is
just
is
that
you
know
hey
they're
still
pulling
along
powershell.
Five
is
like
the
base
based
install.
I
understand
that
the
hey
there's
a
faster
cadence,
but
at
least
some
version
of
it.
B
A
A
A
If
they
did
that
today,
at
the
end
of
the
year,
those
people
who
are
running
those
machines,
they
would
then
have
to
go
and
update
version
seven
or
for
someone
who's
installing
a
new
version
or
a
new
install
of
windows.
Server.
They
get
the
old
version
and
then
they
have
to
immediately
turn
around
and
update
it
to
the
new
version,
whereas
if
they
just
install
windows,
server
and
then
install
the
pieces
that
that
they
want
to
add
like
powershell,
7
and
then
they're
getting
the
latest
version.
A
And
I
I
yeah
I
I
I
understand
the
the
concern
and
a
lot
of
people
feel
that
they,
it
would
be
easier
if
it
was
already
there,
but
you
all
know
how
to
script.
Powershell
and
the
the
installation
mechanisms
for
installing
powershell
seven
are
all
incredibly
scriptable,
except
for
maybe
wingate,
and
it's
not
that
hard.
We
all
know
how
to
deploy
software
to
servers.
So
that's
not
you
know
black
magic
or
anything.
B
A
B
All
right,
well
again,
thanks
everybody
for
coming
and
we're
going
to
kind
of
take
this.
You
know
the
after
party
is
going
to
begin,
but
thanks
everybody
for
coming
and
remember.
In
two
weeks
we
are
going
to
have
jeremy
brown
he's
going
to
do
a
discussion
on
azure
graph
where
he's
doing
azure
stuff
and
then
talk
about
powershell
module
with
microsoft,
graph
and
he's
looking
for
some
examples
and
stuff
like
that.
So
he's
working
on
that
and
then
in
a
couple
weeks
we'll
actually
have
autumnator
on.
B
So
we
have
some
good
things
coming
up
in
the
lineup
and
if
you
certainly
do
want
to
speak
with
us,
let
us
know
and
we
can
get
some
topics.
There
are
topics
that
you're
looking
for
that
you
haven't
seen
or
you
want
to
have
a
speaker
reach
out
to
us.
Let
us
know
and
we'll
certainly
engage
with
them,
and
so
thanks
everybody
have
a
good
night.