Hello everyone, my name is Aakash and I'm from Microsoft product group.
And I'm really excited to announce the preview release of
SCOM managed instance.
Let's talk about what are the features and what the product is.
So, what is SCOM managed instance?
SCOM managed instance is nothing but a cloud alternative of SCOM,
the very successful enterprise Monitoring tool
which is part of System Center Data Center management suite of products.
We have a lot of existing SCOM customers
who have been looking to try the product in cloud or, you know, trying to have a similar kind of experience in cloud and SCOM Managed instance is a window to that.
It is a full feature parity with existing SCOM where you can go ahead and migrate all the 1P and 3P management packs
and all the existing SCOM constructs will work ‘as is’.
We also are presenting this product as a managed service. What that means is, whatever components that will be created in Azure will be managed by Microsoft.
And lastly,
the big takeaway for any existing SCOM customer is that we are going to help, we are going to provide
a seamless migration experience which will
help existing SCOM customers move their monitoring
experience into SCOM managed instance.
Having said that, what are the current customer pain points and what are the value props of SCOM managed instance?
The existing customer has a lot of infrastructure management of SCOM especially, and not only that, they also need to
manage the SQL side of things. With SCOM managed instance, all the components that will be created in Azure will be Microsoft managed.
Additionally,
the products related to SCOM, that is databases, agents,
all of these will be managed.
Since databases will be created in SQL managed instance, you hardly get to administer any of it.
Of course, for any other routine checks you may have to just jump into the SQL servers or SQL instance and manage them.
Having said that, right now,
we see a lot of customers who have invested heavily in management packs, custom management packs, self-developed, 3P or the existing Microsoft 1P MPs.
They are looking for an alternative of using management packs in cloud, right? Because they have traditionally worked with management packs which have a lot of customizations
and they wanna go ahead and use them in cloud.
With SCOM managed instance, we are helping existing SCOM customers migrate their management packs,
migrate all their custom configuration which are built into management packs, migrate into SCOM managed instance.
Lastly, for folks who want to go ahead and monitor
on-premise, as well as Azure,
SCOM managed instance will be a really great product to venture into.
With SCOM MI, you can
monitor whatever is in on premise and as well as in Azure VMs and Azure workloads, as long as there is line of sight.
Having said that, what exactly do you get in the current preview?
In the current view, when you create a SCOM managed instance
you get SCOM management servers created in Azure, which will be grouped
into one instance and with this comma as instance, you can go ahead and monitor anything in on premise or in Azure.
You can go ahead and manage the SCOM managed instance using Azure Portal right. To go ahead and create to use the Azure features, the permissions and all of it.
Having said that, we also make sure that it's not a huge learning curve for existing SCOM server admins.
What I'm trying to say is you can use an existing operations console, let's say from SCOM 2022 console
you can connect to the SCOM (Not SQL) managed instance so that all the administrative work, all the management pack
related work is done on the operations console, which is like a single screen for the SCOM admins.
Having said that, what are some of the prerequisites to deploy SCOM managed instance?
Let's jump into that. You need a line of sight to an existing Active Directory domain controller.
Since SCOM managed instance has SCOM servers which are joining to domain, we need to have the visibility to a domain controller.
To join this commenced instance to the domain. We need a domain account as well.
The next set of prerequisites are Azure managed identity, an IP address and FQDN to use it for Azure load balancer.
The best thing is Azure Load balancer does all the routing from the agent to the management server communication.
And as I mentioned earlier, the databases for SCOM managed instance are stored in SQL managed instance.
So, we need to have an existing SQL MI instance available in Azure.
And, lastly,
the GMSA and computer group should be created & available so that SCOM MI can use them.
So that's a quick intro of SCOM managed instance. In the next video, you can take a look on how we deploy a SCOM managed
instance in a matter of few minutes and also explore additional features that SCOM MI brings in.
Thank you