►
Description
This month’s in-depth topic: Get change notifications delivered via Azure Event Hubs. Brief introduction to Microsoft Graph change notifications (WebHooks) followed by a change notifications delivered via Azure Event Hubs demo. This new Microsoft Graph platform capability gives developers using change notification features in Microsoft Graph the option to get change notifications delivered to their applications more quickly and at scale using Azure Event hub. An end-to-end demo steps viewers through provisioning and configuration of all necessary resources. Microsoft Program Manager presenters - George Juma and Kalyan Krishna. This session was recorded on April 15, 2021. Live and in chat Q&A throughout call.
Stay connected:
• Twitter https://twitter.com/microsoft365dev and @azuread
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog and https://aka.ms/m365pnp/community/blog
• Recurrent Invite https://aka.ms/IDDevCommunityCalendar
A
I
am
a
program
manager
in
the
microsoft
identity
division
closely,
working
with
developers
on
various
features
of
our
identity
platform
and
microsoft.
Graph
with
me
is
george
george.
You
want
to
introduce
yourself
yeah
sure
my
name
is
juma
judge,
I'm
a
program
manager
with
the
change
tracking
team
in
microsoft.
A
This
is
a
feature
that
we
built
or
to
help
the
developers
who
are
using
the
change
notification
features
of
microsoft
graph
to
get
changes
delivered
to
their
application.
We
have
added
support
for
these
via
azure
event,
hubs
to
help
you
with
a
lot
of
scalability
and
compute
issues.
So
without
further
ado,
I
we
will
basically
agenda
cover
the
following
in
the
session
today
for
those
of
you
who
are
quite
familiar
with
the
change
notification.
A
We'll
just
cover
briefly
cover
microsoft
graph
and
what
change
notification
is
before
jumping
into
the
actual
topic
in
the
hand,
and
then
we
will
talk
about
the
change
notification,
delivery
via
event
hubs
and
we
will
have.
We
have
made
time
for
a
full,
fledged
demo
that
you
can
see
how
all
of
this
comes
together
in
an
application
via
and
the
various
places
in
azure
portal
that,
where
you
have
to
set
this
up
so
going
forward.
Just
a
brief
introduction
to
microsoft,
craft
microsoft
graph
is
the
api
for
microsoft.
A
This
is
our
api
of
choice,
going
forward
for
all
microsoft
products
and
is
constantly
evolving
to
address
newer
features
and
newer
products
that
microsoft
keeps
building
and
bringing
into
the
market.
The
graph
api
is
quite
rich.
One
of
the
features
that
it
also
supports,
apart
from
a
usual
c
or
ud
operations,
is
the
ability
of
your
application
to
track
changes
with
webhooks
or
also
known
as
change
notifications.
A
So,
for
example,
if
you
like
to
have
your
application
notified
of
all
the
changes
in
the
users
that
are
present
in
a
tenant,
you
can
either
use
a
delta
query
which
will
let
you
know
what
changes
have
happened
in
the
in
the
user's
side
of
a
tenant
like.
Maybe
a
number
of
users
were
deleted,
updated
or
added,
or
you
can
do
so
by
or
this
is
this
is
enabled
by
you.
Making
delta
queries
calls
periodically.
A
What
graph
also
supports
is
that
you
should
not
bother
with
delta
querying
at
all.
You
can
basically
set
up
change
notifications
to
listen
to
all
changes
on
the
user
side
of
things
or,
instead
of
and
now
instead
of
you
making
calls,
it
is
the
microsoft
graph
which
will
make
a
call
to
your
application
to
notify
you
of
all
the
changes
that
are
happening
on
the
user
side
of
things
very
powerful
allows
applications
to
be
notified.
When
data
changes
in
microsoft
graph,
you
can
subscribe
to
a
set
of
notifications.
A
You
do
not
have
to
subscribe
for
the
entire
set
of
notifications
for
a
tenant.
You
can
choose
the
supported
entities
like
users
and
groups.
You
can
renew
subscriptions
because
subscriptions
are
not
forever.
You
get.
You
get
to
subscribe
for
a
change
notification
for
a
certain
entity
and
actions
for
for
a
certain
amount
of
time,
and
this
is
also
something
which
is
used
for
delta
querying.
A
So
if
you
are
confused
about
or
you
struggle
with,
what
is
the
best
interval
to
delta
queries,
the
change
notification
is
used
as
one
of
the
ways
to
basically
get
a
notification.
The
data
is
changing
and
it
is
time
for
the
application
to
do
delta
query.
This
is
the
what
generally
the
web
hooks
or
change.
Notifications
are
again,
as
I
mentioned,
we
have.
They
are
quite
popular
for
events
like
messages
events,
contacts
users,
you
can
keep
your
data
up
to
date.
You
don't
have
to
poll
at
regular
intervals
and
microsoft.
A
If
you
have
an
application
developer,
you
will
basically
set
up
a
subscription
and
you
will
develop
a
client
application
which
should
provide
a
web
service
which
is
facing
internet
and
can
receive
notifications
from
microsoft
graph.
So
that's
how
the
applications
come
together
with
this
introduction
of
change
notification,
I
would
we
have
a
couple
of
questions
for
you
and
we
were
hoping
if
you
could
basically
give
us
some
answers
for
in
the
chats
window.
A
Okay,
that's
a
good
answer.
We
should
have
given
e
as
none,
so
we
forgot
to
do
that
so
yeah,
you
can
say
none
as
well.
Thank
you
cool.
I
think
we
are
done
with
this
one.
So,
let's
move
to
the
next
question:
do
you
use
change
notifications
in
your
applications
today?
How
many
of
you
are
familiar
and
already
using
it
in
your
code?
A
The
question
was
more
specific
to
microsoft,
graph.
Okay,
I
take
it
that
we
are
done.
Thank
you
for
your
answer.
It
seems
like
most
of
you
have
not
used
change
notifications
and
I
I
hope
that
the
brief
very
brief
overview
that
I
had
covered
was
useful.
If
you
need
to
just.
I
will
post
a
couple
of
links
later,
which
has
a
set
of
resources
and
recording
that
I
did
up
for
this
community
call
only
on
an
introduction
and
demo
or
to
get
started
and
change
notifications.
A
You
would
find
it
quite
useful
to
get
started
if
you,
if
this
feature
and
the
change
notifications
as
a
feature
in
general,
is
of
interest
to
you
with
that.
I
will
move
on
to
the
next
slide
and
introduce
you
to
this
particular
feature,
which
is
to
get
change
notifications
delivered
by
azure
event
hubs.
A
A
Hubs
is
a
popular
real-time
events,
injection
and
distribution
services
built
for
scale,
and
that
built
for
skill
is
a
very
the
aspect
that
where
we
would
basically
discuss
things
in
a
lot
more
detail,
you
can,
of
course
now
with
this
feature
being
available
in
ga.
You
can
use
event
hub
instead
of
your
traditional
web
api
endpoint,
to
receive
change
notifications.
A
A
What
that
means
is
that,
let's
say
if
your
application
ends
up
in
a
certain
customer
tenant
where
the
change
notifications
are
extremely
large
in
nature
and
not,
and
you
don't
necessarily
have
the
compute
available
to
process
all
of
them
within
the
time
microsoft
graph
expects
you
to
do
so.
It
creates
issues
is
because
the
new
notifications
start
to
drop
in
this
case.
Redirecting
these
notifications
to
azure
event
hubs
allows
your
applications
to
process
notifications
at
its
own
base.
A
We
also
addressed
a
few
scenarios
where
this
requirement
of
publicly
exposing
a
url
or
an
endpoint
from
microsoft,
graph
to
call
was
not
acceptable
to
some
customers,
who
had
a
somewhat
different
or
or
more
on-premise
focused
security,
postures
temporizing.
This
is
a
very
common
complaint
that
we
had
received.
A
That
was
receiving
and
processing
notifications
from
microsoft
graph,
and
this
means
that
if
they
had
to
take
down
the
application
for
any
reason,
they
would
miss
notifications
in
that
period.
So
this
particular
scenario
also
helps
you
basically
dis,
connect
the
application
maintenance
from
availability
and
allows
you
to
update
your
application,
update
your
applications
and,
while
not
not
being
not
worrying
about
missing
any
change
notifications.
A
Similarly,
some
examples
of
high
throughput
scenarios
that
we
saw-
and
we
have
addressed
and
you
would
actually
find
it
quite
useful-
is
if
your
application
is
subscribing
to,
for
example,
a
large
set
of
resources,
which
means
that
you
will
get
a
large
set
of
notifications.
What
if
somebody
in
the
company
decided
that
they
will
write
a
powershell
script
to
update
you
know,
job
titles
of
all,
150
000
or
a
million
employees
in
an
organization?
A
Similarly,
applications
subscribing
to
resources
with
high
frequency,
like
group,
memberships
and
and
even
users
to
some
extent,
multi-tenant
applications
are
another
unique
set
of
applications
which
will
definitely
benefit
from
it.
So
those
of
you
who
know
who
have
developed
multi-tenant
applications,
you
will
realize
that,
as
your
application
makes
it
to
hundreds,
if
not
thousands,
of
tenants,
the
number
of
notifications
that
your
application
has
to
now
be
prepared
to
listen
to
grows
considerably,
including
a
wide
variety
of
scale
or
or
frequency
or
volume
that
your
application
now
has
to
expect.
A
You
will
definitely
find
this
feature
quite
useful
if
you
are
a
multi-tenant
app
developer
again
today.
This
change
delivery
reward
is
available
for
all
resources
that
support
change.
Notifications,
microsoft
graph
has
hundreds
of
entities,
but
not
all
entities
support
change
notification.
Today,
while
we
continue
to
work
to
enrich
the
number
of
entities
that
are
available
for
change
notifications,
all
of
these
entities
are
also
available
for
you
to
use
in
your
application,
if
you're
using
azure
event
hubs
today.
A
A
So
that
means
that
all
the
changes
that
happen
to
users
like
creation,
deletion,
operations,
modifier
and
and
groups
will
is
something
that
your
application
should
be
sent
a
notification
about,
because
you
are
interested
in
listening
about
them
and
processing
them
now
microsoft
graph
earlier
in
this
create
subscription,
you
will
provide
a
link
to
a
publicly
available
notification
url,
where
microsoft
graph
will
actually
send
you.
The
notifications
for
all
of
these
changes
today,
because
your
application
will
not
be
getting
a
the
notification
directly
from
graph.
A
What
happens
is
that
there
is
a
special
application
and
a
tenant
called
microsoft
graph
change
tracking.
This,
basically
would
send
the
notification
on
the
event
hubs
for
you.
So
the
way
it
comes
together
is
that
you
create
an
event
hub,
namespace
and
an
event
hub,
and
you
provide
the
connection
string
of
that
event
hub
in
as
a
secret
in
keyboard,
so
microsoft
graph
will
pull
out
this
connection.
String
connect
to
this
event
hub
and
place
the
notification
there.
A
At
this
point,
your
application,
the
way
whatever
you
have
chosen
as
the
as
the
manner
to
get
events
from
event
hub,
can
go
and
pull
these
events
according
in
the
in
the
manner
and
in
the
frequency
as
it
pleases.
So
this
is
how
the
whole
thing
comes
together,
and
this
is
where
I'm
going
to
take
a
pause
now
and
see.
If
we
have
any
questions
in
the
chat,
all
right,
yeah,
please
go
ahead
and
raise
your
hand
and
unmute
yourself.
If
you
wanted
as
well.
A
So
there
are
two
things
to
it.
So
multi-tenant
applications
are
a
thing
in
itself.
We
will
do
a
demo
for
you,
carlos
and
after
that.
Can
we
take
this
question
again.
Is
that
the
demo
was
able
to
help
you
out
or
not?
Is
that
okay
sure,
okay?
As
a
developer?
How
is
going
to
help
me?
It
depends
on
whether
you
have
change
notifications
being
used
in
your
applications
today.
A
The
reasons
we
had
to
build
it
as,
as
I
had
explained
a
bit
earlier,
is
that
let's
say
you
set
up
a
web
application
and
a
web
api
and
you
set
a
subscription
with
microsoft
graph
and
you
are
us
expecting
microsoft
graph
to
send
you
all
the
changes.
Let's
say
that
happens
in
the
user
site
of
a
tenant.
A
A
It
is
something
like
an
audit
log.
Yes,
you
can
use
it
like
an
audit
log.
Let's
say
if
you
are
interested
in
all
the
changes
in
users
and
groups,
you
can
definitely
use
change
notifications
to
log
them
on
what
changes
are
it
works
with
azure
id
groups?
Yes,
no,
it
does
not
change
any
any
numbers
or
limits
today,
ryan
that
you
can
subscribe
to.
A
A
B
Yes,
yes,
it
works
with
the
aed
groups,
so
we
have
all
the
all
the
resource,
all
the
resources,
all
the
workloads
are
enabled
in
in
azure
event,
hubs
as
well,
so
nothing.
I
think
I've
seen
ryan's
question
that
we
have
a
limit
of
one
1000
total
subscription
so
that
doesn't
this
doesn't
solve
that
limit.
We
are
still
going
to
to
to
retain
the
the
limit,
so
the
limit
still
applies.
A
Okay,
there
is
one
final
question
from
priyan,
which
is
that
it
supports
aad,
think
groups
or
security
groups.
It
supports
all
the
groups
that
are
available
usually
tonight.
Their
members
ship
cannot
can
be
synced
from
on-prem,
but
to
azure
ad
into
microsoft.
Graph
they're,
just
groups
available
in
an
azure
editor
today,
and
that's
that's
how
it
is
it's.
A
Something
that
the
the
microsoft
graph
discriminates
today
and
thank
you,
marco,
yes,
the
renewal
and
subscriptions
time
the
limits
are
differ
from
from
a
resource
to
the
various
resources.
One
of
the
great
things
about
microsoft
graph
is
that
it
basically
hides
or
abstracts
a
lot
of
these
various
other
older
apis
or
products
that
have
been
around
for
decades,
but
sometimes
it
also
means
that
some
of
these
older
products
have
their
own
ways
of
setting
their
limits
and
subscription
subscription
limits
and
eve
and
frequencies.
A
B
Okay,
so
just
pick
up
where
kalyan
left
thanks
karden
for
for
that
intro,
so
we
are
going
to
be
taking
you
through
how
you
will
be
creating
azure
event,
hubs
that
your
application
can
listen
to
for
notifications.
We
also
the
version
of
the
event.
The
event
that
we
are
using
requires
that
for
for
you
to
create
a
processor
or
rather
listener
onto
the
event
hub,
you
need
an
azure
storage.
B
So
we'll
take
you
through
how
you
can
you
can
create
that
in
a
few
steps
and
then
we'll
also
create
a
policy
and
access
policy
on
onto
the
azure
event
hub,
so
that
it
has
a
recent
capability
that
will
enable
you
to
to
access
the
notifications
as
and
when
they
they
come.
Okay,
some
some
steps
to
follow.
So
we
have.
B
It's
a
it's!
A
simple
console
application
that
that
we
can.
We
can
all
go
through
okay.
So
some
of
the
advantages
that
you
don't
you
don't
need
to
have
a
notification
url
installed
on
your
end.
Rather,
when
creating
the
subscription
you
will,
you
will
create,
you
will
give
the
subscription
notification
url,
the
azure
keyword,
url
I'll,
show
you
how
to
do
that
as
well,
when,
when
we'll
be
going
through
the
new
url,
the
way
the
url
looks
when
you,
when
you're,
when
you
are
subscribing
for
azure
event,
hubs.
B
B
So,
as
I
mentioned
earlier,
the
azure
cables
are
just
for
securing
the
connection
strings
for
for
the
event
hubs,
so
you'll
need
to
create
a
a
secret
that
will
will
store
the
key,
the
the
key
to
the
the
azure
key.
Here's
your
keyboard
id
and
something
else
that
that
will
do
is
is
is
add
the
the
event
up
connection
string
to
your
azure
keyboard,
okay
and
then
then
I'll
of
course
show
you
how
how
you
can
give
access
to
a
microsoft
graph
change
tracking
application
as
a
as
an
access
policy.
B
Okay,
let's
get
to
it.
This
is
how
the
new
url
will
look.
Traditionally,
it's
just
a
url.
Basically,
from
an
application
perspective,
you
can
host
a
web
service
on
your
end
and
that
web
service
is
what
you
will
you
will
give
to
to
a
subscription
so
that
whenever
there's
a
change,
our
hook,
application
will
be
able
to
send
notifications
to
your
endpoint.
B
But
there
are
downflows,
as
as
we
have
mentioned
earlier,
is,
for
instance,
what
happens
when
your
application
is
down.
Although
it's
a
powerful
key,
powerful
tool
that
we,
we
can
actually
notify
you
when
the
change
comes,
there
there's
a
dependency
whereby
you
must
have
a
url,
but
in
this
case
you
are,
you
url
looks
something
like
this.
B
So
you'll
have
the
azure
event
hub
as
the
first
key,
and
then
you
you'll
have
you'll,
get
you'll,
just
replace
azure
key
volts,
where
you
have
this
parenthesis,
you'll
just
replace
azure
keyword
with
a
key
vault
name
and
then
you'll
also
replace
the
secret
name.
So
remember
I
mentioned
earlier
that
you'll
have
a
secret
that
will
have
one
of
the
the
value
of
the
secret
will
be
the
azure
event
hub
connection
stream
and
then
you'll
also
use
the
tenant
id
domain
name.
So,
for
instance,
you
you,
your
is
example.com.
B
Probably
you'll
have
the
domain
name
there.
When
setting
up
okay
mention
this,
then
this
is
how
the
subscription
payload
will
look.
So
basically
in
in
this.
If
I
can
explain
it
just
notif,
it
just
shows
that
we
will
be
listening
in
for
any
updated
requests
or
deleted
requests.
So
there
are
there's
a
third
one
which
is
create,
but
for
this
payload
we
were
just
listening
for
the
two
and
then
the
notification
url.
So
we'll
show
you
how
a
sample
looks
like
in
in
the
presentation
and
then,
of
course,
the
resource.
B
So
we
look
at
at
users
for
this
one
and
then
the
expiry
date
and
time.
So
this
remains
so
we'll
have
the
the
expiry
date
date
and
time
there
and
then
reclaim
it.
That
will
help
you
identify
notifications
based
on
your
subscription
and
let's,
let's
get
to
do
it
so
I'll.
Just
take
you
through
the
first
step.
The
first
that
you
you
will
need
to
do
is
is
to
register
an
application.
B
B
B
Okay,
then,
you
can
also
look
at
application
permissions,
so
under
application
permissions
you
need
to
grant
some
permission.
So,
for
instance,
we
will
reading-
and
you
know,
and
and
probably
updating
users
from
our
application.
So
you
need
to
add
a
permission.
It's
a
delegated
permission
that
we
are
using
currently,
so
you
will
need.
So
all
you
need
to
do
is
just
go
to
add
permission.
B
Then
you
click
microsoft
graph
and
that
will
bring
you
here.
Where
you
choose
the
delegated
permissions.
You
can
search
so,
for
instance,
here
I'll
search
user
and
I
should
be
able
to
get
read
all
or
read
write.
So
I
may
I
can
pick
read,
write
for
instance,
and
with
that
I
I'll
the
next
step
is
just
to
give
to
grant
admin
consent
to
today
to
our
tenant
for
these
two
permissions,
so
that
will
create
the
we
will
create
the
application.
B
So
the
next
step
is
is
basically
you
you
it's
key
to
to
confirm
that
that
you've
granted
the
permission.
So
that's
that's
why
I
was
looking
at
this,
so
the
next
step
is
to
to
to
create
an
azure
event
hub.
So
if
you
go
to
to
the
event
hubs
page,
it's
easy
to
access
that
you
can
easily
come
here
and
and
just
type
in
on
the
search
and
and
you
can
select
event
hubs
so
once
you
do
that,
the
next
thing
is
just
to
come
and
and
click
add.
B
If
you
want
to
create
an
event
hub.
So
of
course
you'll
add
the
permissions
and
details,
and
then
this
is
basically
a
namespace.
We
are
creating
because
you
have
to
create
a
namespace.
Then
then
the
event
tab
itself.
So
I'll
just
do
something:
just
do
something
random.
It
will
clean
up
later
and
then
for
the
for
the
present
here.
You
you
can
select
standard
should
work,
then
you
create
so
once
you
create
that
you
should.
B
B
B
So
there's
some
bit
of
validation,
but
we
can
confirm
that
that
the
event
hub
namespace
was
created.
So
the
next
step
is
just
to
come
and
create
an
event
hub
under
the
namespace.
So
I'll.
Just
let
me
just
pick
up
this
and
just
say
so:
we're
going
to
do
a
couple
of
things.
So
this
creates
the
the
event
have
been.
Some
of
the
things
that
we
will
need
to
copy
includes
include
the
event
hub,
so
we'll
first
go
to
overview,
just
to
confirm
everything
looks
well
and
then
we
go
to
shared
policies.
B
B
And
then
you
give
it
both,
because
you
want
to
both.
You
know,
update
users
and
also
create
and
view
users
okay,
so
we
are
going
to
copy
the
connection
string.
So
when
you
copy
the
connection
string,
remember
this
is
the
connection
string
that
you're
going
to
add
into
your
azure
key
vaults.
So
that's
what
we'll
go
to
next.
I
just
wanted
to
come
here
at
this
storage,
just
to
confirm
that
this
created,
while
it
creates,
we
can
go
and
create
a
an
adjust
another
keyword.
B
B
So
when
you
go
to
the
resource
after
this
has
been
created,
the
next
thing
is
just
to
go
to
secrets
in
the
key
vaults
in
the
key
vault
that
you
have
created,
and
then
you,
you,
click
on,
generate
and
create.
So
with
that.
The
next
step
is
just
to
add
the
secret
name,
so
I'll
just
do
a
secret.
Okay.
Let
me
just
just
now.
B
B
So
as
as
I
mentioned
earlier,
we've
created
a
an
event
hub:
we've
created
a
storage
account,
so
under
the
storage
account
we
just
left
out.
We
just
left
with
one
thing
just
to
create
a
container,
so
the
container,
as
I
mentioned
earlier,
the
event
tabs
that
we're
using
requires
that
we
create
a
storage
account
with
a
container
that
the
event
app
will
use
to
to
for
connection
that
the
eventual
process
I
will
use
for
connection
so
just
adding
a
name
here
just
contain
and.
B
Yeah,
that
should
work
so
with
with
that.
The
next
step
is
simply
to
go
and
update
the
details
that
we've
got
so
we
have.
This
is
a
testing,
and
so
it's
okay,
the
credentials
are
okay,
so
we
have
the
event
up
connection
strings,
so
the
event
hub
connection
string
for
creating
the
subscription.
That's
that's
where
we
abstract
the
connection
string,
but
within
the
application
you
should
have
the
connection
string,
so
I've
I've
indicated
it
there.
We
have
the
event
hub
name,
okay,
and
we
have
the
storage
connection
string.
B
B
Okay,
so
under
the
access
keys,
I
forgot
to
mention
that
you'll
need
to
copy
the
storage
connection
string
that
we
will
use
in
our
application.
So
that
is
what
we
have
here,
and
then
we
have
the
container
name.
We
created
a
container
together
and
then
we
also
have
the
client
id
the
client
id
is
basically
the
application
id.
When
you
are
creating
this
application
under
overview,
you
should
be
able
to
see
the
client
id
so
with
that.
All
you
need
to
do
is
to
replace
the
details
that
that
we
have
here.
B
The
tenant
domain
is
basically
your
tenant,
the
tenant
domain
name.
So
you
can
replace
this
with
what
you
have
and
then
the
redirect
url
is
basically
http
local
lost,
as
we
added
in
earlier
and
then
the
notification
string,
as
I
mentioned,
it
will
be
used
for
creating
the
subscription.
So
this
is
also
important.
So
I'll
just
go
ahead
and
run
this
just
so,
you
can
see
how
it
runs,
so
it
will
request
for
consent,
consent.
B
Yeah
so
once
the
consent
is
granted,
then
the
next
step
is
that
it
has
already
connected
to
the
to
the
event
hub,
and
the
next
step
is
just
to
fetch
messages
and
all
the
users
that
are
in
the
in
our
tenant.
So
with
that,
I
think
you
should
be
able
to
configure
we.
We
can
share
the
we.
We
have
this
source
code
in
our
training
pack
and
and
hosted
in
in
github.
We
will
be
able
to
share
the
url
in
in
the
recording
yeah.
A
Fine,
thank
you,
george.
For
that
great
demo.
That
was
all
we
had
today
for
you
to
go
through,
and
if
you
have
any
questions,
please
use
the
chat
window.
If
you
will
can
raise
your
hands,
we
can
take
them
for
you.
In
the
time
we
have
remaining
yeah
stephen.
This
is
one
of
the
problems
that
we
solved
with
azure
event:
hubs
where
a
customer
side
issue
with
publicly
exposing
endpoints
on
the
internet,
so
you
should
definitely
give
it
a
try.
A
Paul
are
you?
Are
you
going
to
still
show
us
how
to
get
data
into
the
event
hub
in
the
first
place
in
the
demo
paul,
you
would
have
noticed
that
there
was
a
connection
string
that
we
had
created
and
placed
in
the
as
a
secret
in
the
keyboard,
so
that
has
the
connection
string
and
a
secret
to
write
data
into
event
hub.
A
A
B
D
B
D
B
A
Okay,
it
seems
like
we
have
answered
your
questions
again
feel
free
to
continue
to
use
this
chat
window.
If
you
have
more,
these
are
the
resources
that
are
provided
to
you.
These
are
all
the
links
that
you
need
to
get
everything
you
want
and
everything
we
have
published
on
this
particular
topic
and
I'm
going
to
copy
paste
just
this
as
well
and
yeah
stephen.
You
want
to
take
over
and
do
the
closing
for
us.