>> Welcome to your new episode of the Azure Enablement Show.
Today, we're going to have a look at
the hybrid and multicloud scenario. So stay tuned.
[MUSIC].
Welcome back. My name is Thomas,
and I'm here with Lior,
and we are going to discuss the hybrid and multicloud scenario.
But before we actually going to do that,
I want to ask Lior,
why is hybrid and multicloud so important?
>> Yeah. Thomas, thanks for having me.
Always a pleasure talking to you.
Hybrid and multicloud is a very interesting space.
When we started the Azure journey a few years back,
we always said that Azure was born with hybrid in mind.
The fact that it's becoming some mainstream to have
in a hybrid environment or a hybrid architecture,
this tells you how important it is.
Because the reality is that customers are not just
looking to deploy things in one Cloud or another,
but also have their own premises assets that they currently own.
So hybrid really becomes
the de facto standard for a lot of organizations
just because of the fact that is just a reality of their business.
That's why hybrid is so important in the context
of this conversation and where businesses are at.
>> Yeah, absolutely. I remember when Hybrid was
just about networking and connecting
your own premises to the Cloud.
But now we have obviously way more to offer,
such as Azure Stack and Azure Arc and can you tell us a little bit
more about our Azure Hybrid offering and especially Azure Arc?
>> Yeah. You touched a very important point.
Because in the past it was really
about just the network connectivity.
It was enough for you to have a site to site VPN or express route,
and you would be able to tell that,
"Hey, I have a hybrid environment."
But we all know the reality is not like that today.
What we have is multiple solutions that we
created in the spirit of making hybrid real.
Obviously, Azure Arc is being the de facto strategy when it comes
to the hybrid motion that we are trying to lead with.
Azure Arc is really about stretching our control thing.
It really provides a solution that is software based.
If you're thinking about Azure Resource Manager,
that's what we always say.
That's the operating system of Azure.
What we're trying to do is we're trying to
stretch it to outside of Azure.
That means that we're able to bring resources or
IP assets like servers or Kubernetes clusters that
are deployed outside of Azure and bring those as
first class citizens inside Azure Resource Manager or being able
to deploy our own services like segmented instance Postgres at
services functions and the list goes on into
Kubernetes clusters that are deployed outside of Azure.
It's really a bi directional thing,
and that's where Azure plays
a critical role to enable that technology.
>> It's absolutely gained, especially because we are
meeting customers where they are,
and we are helping them by
building different solutions and offering them to them.
We are going to talk about the hyper, the multicloud scenario.
But before we then go into that,
for those who don't know,
can you tell us a little bit more what a scenario is?
>> Yeah. A scenario is really a bundling
of information if you want to think about it that way.
What we're doing with this type of scenario is we are taking
all the best practices, the battle-tested recommendations,
consideration that you need to take into account and
bringing those into a very organized set of documentations.
It can be a part of
the well architected framework or Microsoft Learn or Azure Docs,
but really, it's about bringing everything
together into one place and create a scenario.
A scenario is designed to take you by
the hand in a very organized fashion to make sure
that you are thinking about your architecture in
the way that we consider to be best practice.
Now obviously, best practice is
a term that can be relevant to you,
but not relevant to someone else.
What we're trying to do,
we're trying to all these documentations and bundling.
We're trying to a lot of the times to find that common ground,
making sure that the recommendations
and considerations that you need
to take under account are somewhat generic in a way.
It will apply to most customers.
But these documentations and
critical design areas that we created are
really about giving you that bit of tested recommendations.
That's what scenario is all about.
>> All right, it's absolutely awesome to have
all these information in one place,
depending on the scenario,
makes it super easy to discover
all the different sources and tools you have available.
We have one for hybrid and multicloud. What does that include?
>> Yeah. Like we mentioned,
hybrid started a few years back,
hybrid started with the notion of just connectivity.
But as technology evolves and customer needs
became more mature in the sense of Cloud,
the hybrid era also started for real.
That means that customers are really
leveraging assets that are on premises
alongside with their Cloud assets that might have
multiple Cloud providers that they are working with
or multiple infrastructure types that they have on premises.
The hybrid and multicloud scenario is really about
bringing Azure Arc to the center of this conversation,
and we're doing that by creating multiple critical design areas.
As you can see in the illustration that I'm showing you,
this critical design areas are designed to give you-all the layers
of architecture that you want to think about
when you are designing in Azure Arc environment.
We are coming up with Azure Arc enabled
servers landings on accelerator.
That accelerator takes all the critical design areas and
take you by the hand on each and every
one of those providing you with reference,
architectures, considerations, recommendation and
eventually some next steps for you to take on
a consideration as you go by and design this type of stuff.
The hybrid and multicloud scenario
brings Azure Arc into the center,
into the architecture and into the way you're thinking
about your hybrid implementations in your organization.
>> This is awesome stuff and again,
absolutely like to see them.
You mentioned the Azure Arc enabled
server landing zone accelerator.
Can you tell us a little bit more what that is and how
customers can leverage that to be successful with this?
>> Yes. You know Thomas,
we're talking to a lot of customers
and those Azure Arc enabled service customers.
One thing that always comes up is they're asking us,
how should I do this the right way?
Also, how should I do this at scale?
Because on-boarding 10 Azure Arc enabled servers, that's easy.
Sure, you can have an automated way to do that,
or you can do that manually.
But at the end of the day,
it's only 10 resources that you enabling.
But what happened when you are talking to
an enterprise that has 5,000 servers,
how do you go by an approach this type of architecture?
The running on accelerator for Azure Arc enabled
servers takes all the critical design areas that you want to
think about and basically shows
you what are the things that are related between one another.
You can talk about identity management,
for example, and how does that really fits
into the governance and compliance conversation?
You can talk about network topology and again,
how does that fit two automation conversation?
Eventually, how do you think about
it from cost and billing perspective?
Now all these areas are really
bundled together in what we called critical design areas.
We have seven of those for this Azure Landing zone accelerator,
and we want to make sure
that customer have all the knowledge that they
need in order for them to actually
start with Azure Arc enabled servers the right way.
>> Well, that's exciting, and again,
I can completely understand,
because especially if you talk to
a customer who is just on a journey to the Cloud,
obviously these learnings on accelerators are absolutely
great to help them to build all
this and for the hybrid and multicloud.
I completely see that as well because as you mentioned before,
we see a lot of enterprise and
organizations being in multicloud and hybrid scenario.
Obviously, this is going to be interesting
to a lot of our customers.
How can they try this out?
>> Yes. To answer that,
we really want to think about why didn't we call this accelerator?
The reason that we call this accelerator
was because Azure Arc is unique.
Azure Arc resources and specifically Azure Arc enabled servers in
this case can leave in any landing zone that may be.
If you're familiar with the landing zone concept coming
from us Azure Arc really complement that.
But once you onboard those servers into Azure,
they can leave in any landing zone because they can be
essentially part of any application that may be.
In order for you to actually go buy and try
that without the sandbox automation that we created,
you actually need to have resources that are or IP assets that are
deployed outside of Azure and onboard those into Azure.
What we did, we created
a sandbox reference automation or implementation.
That sandbox automation is powered by
the Jumpstart project and this is part of our box.
With that flavor that you see right here,
which is a new flavor that we are
creating is the IT Pro's flavors.
The IT Pro flavors will bring Azure like enabled servers in
a simulated way into
your Azure subscription in a single resource group,
but will also deploy
all the unified operations capabilities that you
need in order for you to actually start
looking at the value proposition of Azure Arc enabled servers.
Once you were done with those Azure Arc enabled
servers that were on-boarding for you, that's okay.
You can go delete those resources.
But the unified operation management layer,
that's actually something that you can
leverage for your production workloads.
The log analytics workspace,
the Cloud Defender Integration Monitor,
tagging all that stuff can be relevant for
workloads that will come after you are
done with your sandbox implementation.
What we're doing with our box for IT Pros,
we're giving you everything in a single resource group
in order for actually to go and try this stuff out.
>> It was fantastic.
I love to like because it really speeds up the processes,
how customers can try out the value proposition.
How they can make use of
Microsoft Defender for Cloud
and many of other services, as you just mentioned.
I'm excited to try this out,
and I'm sure a lot of viewers are also excited.
Where do I go to try this out?
>> You simply go to the hybrid and multicloud scenario
and you're going to find the Landing Zone Accelerator homepage.
You're going to see all the capabilities and
mapping to each and every one of the critical design areas.
Also eventually, once you are done
with the critical design areas and you feel that,
now it's time for me to actually try stuff out,
you can go into the sandbox automation
and actually go and deploy Auerbach's for IT Pros.
>> Awesome. Thank you very much,
Lior and thank you very much for everyone watching.
Don't forget, check out a.k.a.ms/adopt.
[MUSIC].