>> Learn about directly connected mode for
Azure Arc-enabled data services this week on Data Exposed.
[MUSIC]
>> Hi. I'm Anna Hoffman and welcome
to this episode of Data Exposed.
Today I'm joined by Lior.
Lior we are so excited to have you on the show again.
But for those who haven't seen you before can you
tell us a little bit about what you do.
>> Sure, Anna. Thanks for the invite always a pleasure.
My name is Lior Kamrat and I'm
the Worldwide Technical Strategy Lead
for everything that is Azure Hybrid in Microsoft.
My job basically is to make our field and customers
awesome with Azure Arc by creating a lot of technical content,
demos, and many other things.
>> Awesome, I love it. Make our customers awesome seems like
a good job title but also a pretty broad scope.
Today we're going to be talking about like we mentioned Azure Arc.
I wanted to start by asking you was
there something specific or something
new that you want to talk about today?
>> Yeah sure. Last month during Ignite we
announced the new directly connected mode general availability
for Azure Arc-enabled data services.
We've been waiting with this announcement for
a while and I'm happy that we finally got
this out the door and that's actually a critical piece when it
comes to customer adoption for Azure Arc-enabled data services.
>> Awesome, cool. This is directly connected mode.
Can you tell us either a little bit about this or
are there other modes that we should be
aware of before we go deeper in it?
>> Yeah. In order to understand what is directly connected mode,
you need to take one step back which is
why I wanted to share with you
this illustration that I have so we can talk about it.
With Azure Arc-enabled data services you
basically have two connectivity mode.
You have a disconnected mode or indirectly
connected and you also have directly connected.
Now to explain what does that mean,
we'll need to take a step back and really
understand the notion of what is
Azure Arc-enabled data services with the context
of how does that really integrate with our own API?
Azure Arc-enabled data services really offering you to
deploy our own managed data services
outside of Azure using Kubernetes as
the fundamental building block
when it comes to deploying these services.
Now when you are deploying
these services you basically have two options;
you can either deploy these services in
indirectly connected mode which means
that you'll be able to deploy
it in a SQL managed instance or
PostgreSQL Hyperscale but once you're done with the deployment,
those services will not have
basically an ongoing connection
with our APIs or Azure Resource Manager.
With connected mode or directly connected mode,
this is really the premise of Azure Arc-enabled
data services because it means that this services
that you just deployed are natively now part and integrated in
Azure Resource Manager and in
our own APIs and brings a lot of goodies with it.
>> Got it. So is it safe to
assume that the only way to get all the bells and
whistles associated with Azure Arc-enabled data services
is by using directly connected mode?
>> It's a great question. When we're talking
to customers and we are asking them
what is the use case that they're looking
for with regards to Azure Arc-enabled data services,
a lot of the time they're talking to us on data sovereignty.
With data sovereignty when it comes to this use case,
what we wanted to assure customers is they will be able to deploy
the data services again on
a Kubernetes cluster that they maintain,
they own and they control the compliance and
the governance as the security for these Kubernetes clusters.
But the data itself that is
deployed as part of the process of deploying data services
using Azure Arc is actually
still on-premise or in a multi-Cloud environment.
That doesn't leave that side of the deployment.
The only thing that gets hooked
into Azure Resource Manager is metadata.
Directly connected mode brings all these bells and
whistles because of those APIs integrations and when we
were saying bells and whistles we're
really talking about enterprise
great capabilities like billing management,
scaling, security,
compliance and all that Jazz.
Yeah, you can say
that with directly connected mode you are actually
getting the full blown benefits
when it comes to Azure Arc-enabled data services.
>> Got it. You talked to us a little bit about
the scenarios for each type of mode.
Are there other scenarios or use
cases that would be good to mention here?
>> I think with Azure Arc-enabled data services,
it's really about creating
this unified operations when it
comes to how do you go buy and manage those data services?
Our customers really love SQL Managed Instance
on Azure or PostgreSQL Hyperscale and what we wanted to do
with Azure Arc-enabled data services
is to bring the same unified experience.
If you're a customer that's looking to modernize the way
that you are working with your data assets
either on-premises or in
a multi-Cloud environment what you can do is you can actually
use those Azure Arc-enabled data services
but not changing the tool set that you are using.
If you look at the illustration right on the top-left,
you actually have the user interfaces.
You can see that these user interfaces
are no different than the one that you're going to use by
using SQL Managed Instance or Postgres on
a standard Azure deployment or a regular Azure deployment.
With Azure Arc-enabled data services you're getting
the same experience so another great use case is to
keep your unifying operations intact so
you don't have to re-skill people,
you don't have to go through a lot
of hurdles in order for you to get to a point that
you actually have either SQL or Postgres
deployed on-premises or you are in a multi-Cloud environment.
>> Awesome, cool. Just looking
at this illustration that you have,
I have a random question that you might be able to help me with;
if I wanted to run
indirectly connected or disconnected mode somewhere else as
opposed to on-prem or
HCI or something like that like [inaudible] can I do that?
Or do I still have the option or is there
only one option if I go somewhere else?
>> As long as you have a Kubernetes cluster that is supported by
our validation program for
Kubernetes cluster as just part of Azure Arc, you're good to go.
You can deploy Azure Arc-enabled data services on
any Kubernetes cluster that may be as long as it's CNCF
certified and is part of
our validation program and obviously we're
going to share some links to make
sure that customers and
people are aware of that validation program and
know what is it that we are
talking about when we're saying the validation program.
>> Awesome, cool. That's great to
hear and we'll put those links in the description for our viewers.
Final thing like how do you get started with this thing,
it seems especially from his illustration there's a lot going on.
>> In this illustration really designed to
show the elements that
are part of Azure Arc-enabled data services.
To maybe explain how to get started,
I wanted to connect the dots here.
What you're seeing right here in the Azure portal you're seeing
a resource group that was actually created as part of ArcBox.
ArcBox you and I,
we talked about it in the past,
it's part of the Jumpstart project.
ArcBox is really our way to provide
a product that includes everything that is Azure Arc in
one resource group and has
everything that you need to have in order for you to
start and get going with
Azure Arc-enabled data services or
the Azure Arc technologies that we have to offer.
That resource group that you're seeing right here is part of it.
Let's do a bit of filtering here and choose the things that are
actually relevant for Azure Arc-enabled data services.
I'll choose the Data controller,
I'll choose PostgreSQL,
we'll take the Kubernetes cluster,
we'll take the custom location and also let's go for
the SQL Managed Instance and then we'll do a bit of
filtering to get that cleaner look here.
What you're seeing here are actually
the relevant Azure Arc data services resources
that we deployed as part of the automation.
These resources are deployed in a way that is
directly connected mode so you can get
all the bells and whistles that we were talking about.
In order for you to get started with that,
again we talked about it.
That's part of the Jumpstart project.
The Jumpstart project as of today
is also supporting the latest release
of Azure Arc-enabled data services
the November release that we had last month,
which again include
the directly connected mode supportability
in general availability.
The individual scenarios that you
have as part of the Jumpstart project for
Azure Arc-enabled data services or if you prefer to
deploy ArcBox as a fully opinionated deployment,
all of these are already included
with all these goodies baked into.
You can just go ahead to the Jumpstart project,
go to the Data Services scenarios or
ArcBox and get going with this easily.
>> Awesome. That's great to hear.
Thanks so much Lior and I love the Azure Arc Jumpstart program.
It just makes sense to have
an easy way to get started especially for
folks maybe new to any of
the things involved because there are several components.
Any final tips or advice for folks?
I know you already gave a lot of tips and tricks,
but any final advice for folks
as they're just getting started with this?
>> Yeah, we have great learning models created
by our friends Buck and Bob as part of MSLearn.
These learning models are focusing on
Azure Arc-enabled data services.
There are a few blog post that we created as part of
the tech community that we
have for Azure Arc so a lot of great content there.
Really if you'll go into the YouTube channel for
Jumpstart project or into
the Jumpstart project itself and obviously Microsoft Docs,
you will get a lot of that knowledge
already so I highly recommend go and check those out.
>> Awesome. Thanks so much Lior.
To our viewers,
we'll put links in the description to
all the great things that Lior talked about
today whether it's more information
about directly connected mode,
more information about Azure Arc Jumpstart,
the Microsoft Learn modules,
or the YouTube channels will have all in our description.
If you like this video go ahead give it a like,
leave us a comment and let us know what you think and we
hope to see you next time on Data Exposed.
[MUSIC]