Hello everyone. My name is Aakash and I'm a product manager at Microsoft.
And in this video, we are going to briefly recap the prerequisites needed to create a new Azure monitor SCOM managed instance
We will also showcase on how to discover and manage an existing SCOM managed instances.
And lastly, how to quickly deploy a new SCOM managed Instance.
For SCOM managed instance,
we need to have Line of sight with an existing domain controller since it is dependent on Active Directory.
While it is having a line of sight, we also need a domain account so that you can join SCOM managed instance to the Active Directory.
Thirdly, an Azure managed identity is required which is going to replace all the traditional SCOM service accounts
and this will be used to access the SQL managed instance databases.
Next, we also require an IP address and an FQDN address for the Azure load balancer.
which is going to load balance, all the communication between agent and SCOM managed instance
SQL managed instance, is another requirement where the databases of the SCOM managed instance will be hosted.
And lastly, the GMSA account and a computer group is required to go ahead and provision a scrimmaged instance.
Having said that, let's quickly jump into Azure portal.
On the Azure portal, you can search for SCOM instance right from the top search bar menu.
Then, you can also click on more services and then go ahead
and filter the services for SCOM managed instance.
There are multiple ways to jump in. click on this SCOM managed instance from here. When you open the homepage,
you can view all the existing instances created, create a new instance and look for the prerequisites information page.
Let's quickly look at the existing instances created.
Over here
There are multiple instances created and each instance is technically a SCOM management group which you can create for multiple purposes.
Now that we've seen and that all the instances, let's create one.
When you go create a SCOM managed instance, you need to import all those prerequisites that we talked about earlier,
like the subscription name, resource groups, and of course you need to key in the SCOM name.
Having said that, in preview version, you can deploy managed instance in couple of regions which is West Europe and West US.
We will be adding multiple more regions as the product evolves.
We then go ahead and key in the domain name the DNS server name,and then the OU path which is optional
And then, we key in the domain account details which is stored in Azure keyvault. Lastly, the Azure hybrid benefit (AHB) in preview version, you can proceed to using No.
The reason is this will be applicable when the product goes GA.
Having said that, we next jump into the networking details. Over here we key in the virtual network it needs to be part of,
the subnet that it needs to be part of, and then the static IP and the DNS name which will be used for Azure load balancer.
And then, we go ahead and key in the GMSA details, which is the computer group and GMSA account
and lastly the SQL database or the SQL instance name to which
SCOM MI I will deploy its databases and the manager entity to which
has access to the SQL managed instance.
You can optionally create tags. You click on Next, which will go ahead and validate all the inputs
such as the subnet and VNET matching, the IP address and the DNS assigned,
Once you're done with the validation you click on Create.
That's it.
all the
All the hard work that a SCOM admin puts to create a SCOM on premise
for about 2-3 days is done in a matter of few minutes.
Having said that, let me show you how existing SCOM managed instance will look like.
Over here, I've created a new SCOM managed instance called Contoso MI.
You view all the information that you keyed in during the prerequisite stage.
and then, you can navigate around to see the existing properties.
In the next video we will talk about the features the SCOM managed instance provides. Thank you very much.