Merge pull request #277 from FehseCorp/scommidocs

Scommidocs

content/management/scom-mi/agents.md

@@ -1,5 +1,8 @@
 # SCOM MI Agents
 
+
+#### [Previous](setup.md) | [Home](readme.md) | [Next](newfeatures.md)
+
 Azure Monitor SCOM Managed Instance provides a cloud-based alternative for Operations Manager users providing monitoring continuity for cloud and on-premises environments across the cloud adoption journey.
 
 [Monitor Azure and Off-Azure Virtual machines with Azure Monitor SCOM Managed Instance](https://learn.microsoft.com/en-us/system-center/scom/monitor-off-azure-vm-with-scom-managed-instance?view=sc-om-)
@@ -35,3 +38,5 @@ Note:
 - Currently, multi-homing for gateway servers isn't supported.
 - Arc-enabled Gateways require line of sight to region.workloadnexus.azure.com on port 443.
 - Initial authentication is performed by a managed identity, then certificates are used to manage Managed Gateways by Microsoft.
+
+#### [Previous](setup.md) | [Home](readme.md) | [Next](newfeatures.md)

content/management/scom-mi/intro.md

@@ -16,9 +16,9 @@ SCOM MI is a new deployment option for System Center Operations Manager (SCOM) t
 
 SCOM Managed Instance has all the capabilities of System Center Operations Manager on-premises in a cloud-native way.
 
-The following table highlights the key differences between System Center Operations Manager on-premises and SCOM Managed Instance:
+Comparison of SCOM on-premises with SCOM Managed Instance:
 
-![alt text](ComparisonTable.png)
+<https://learn.microsoft.com/en-us/system-center/scom/operations-manager-managed-instance-overview?view=sc-om-2022#comparison-of-system-center-operations-manager-on-premises-with-scom-managed-instance>
 
 ## Pricing and Benefits
 

content/management/scom-mi/migration.md

@@ -2,13 +2,17 @@
 
 ### [Previous](newfeatures.md) | [Home](readme.md)
 
-The process is technically simple, but it requires a lot of planning and testing. The migration process is not reversible, so it is important to plan and test the migration process before you start.
+The process is technically simple, but it requires planning and testing. It is a multi-step process and can be gradually implemented.
+
 It consists of the following steps:
 
 - Exporting Management Packs from the source management group
 - Importing Management Packs to the target management group
 
 ## Migrate to Operations Manager managed instance
-https://learn.microsoft.com/en-us/system-center/scom/migrate-to-operations-manager-managed-instance?view=sc-om-2022&tabs=mp-overrides
+
+<https://learn.microsoft.com/en-us/system-center/scom/migrate-to-operations-manager-managed-instance?view=sc-om-2022&tabs=mp-overrides>
 
 ### [Previous](newfeatures.md) | [Home](readme.md)
+
+[Kevin Holman's SCOM Management MP](https://kevinholman.com/2017/05/09/scom-management-mp-making-a-scom-admins-life-a-little-easier/)

content/management/scom-mi/newfeatures.md

@@ -2,29 +2,49 @@
 
 ### [Previous](setup.md) | [Home](readme.md) | [Next](migration.md)
 
-## Management
+# Features
 
-- Infrastructure
-- Gateway servers
+### SCOM Managed Instance functionality allows you to:
 
-![alt text](image-2.png)
+- Configure an E2E System Center Operations Manager setup (SCOM Managed Instance) on Azure.
+- Manage (view, delete) your SCOM Managed Instance in Azure.
+Connect to your SCOM Managed Instance using the System Center Operations Manager Ops console.
+- Monitor workloads (wherever they're located) using the Ops, and while using your existing management packs.
+- Incur zero database maintenance (Ops database and Data warehouse database) because of the offloading of database management to SQL Managed Instance (SQL MI).
+- Scale your instance immediately without the need to add/delete physical servers.
+- View your SCOM Managed Instance reports in Power BI.
+- Patch your instance in one click with the latest bug fixes and features.
+
+## New Features
+
+### Manage
+
+- [Monitored Resources (preview)](https://learn.microsoft.com/en-us/system-center/scom/monitor-arc-enabled-vm-with-scom-managed-instance?view=sc-om-2022)
+
+- [Managed Gateways (preview)]()
 
-## Workbooks
+### Monitoring
 
-- Alerts
-- 
-## Grafana Integration
+- [Configure Log Analytics for Azure Monitor](https://learn.microsoft.com/en-us/system-center/scom/configure-log-analytics-for-scom-managed-instance?view=sc-om-2022)
+
+- [SCOM Alerts in Azure Monitor](https://learn.microsoft.com/en-us/system-center/scom/view-operations-manager-alerts-azure-monitor?view=sc-om-2022)
+
+- [Logs (preview)](https://learn.microsoft.com/en-us/system-center/scom/configure-log-analytics-for-scom-managed-instance?view=sc-om-2022#view-logs)
+
+![alt text](image-2.png)
 
+- [Workbooks (preview)]()
 
+### Dashboards and Reporting
 
-## Log Analytics
+- [Create PowerBI Reports](https://learn.microsoft.com/en-us/system-center/scom/operations-manager-managed-instance-create-reports-on-power-bi?view=sc-om-2022)
 
-![alt text](image-3.png)
+- [Microsoft SCOM Managed Instance Reports](https://appsource.microsoft.com/en-us/product/power-bi/microsoftcorporation1664440972680.9c257347-1dd6-4440-ab56-4392609cd1c8)
 
-https://learn.microsoft.com/en-us/system-center/scom/configure-log-analytics-for-scom-managed-instance?view=sc-om-2022
+- [Grafana Dashboards](https://learn.microsoft.com/en-us/system-center/scom/dashboards-on-azure-managed-grafana?view=sc-om-2022)
 
-## Power BI
+- [Query SCOM MI from Grafana Dashboards](https://learn.microsoft.com/en-us/system-center/scom/query-scom-managed-instance-data-on-grafana?view=sc-om-2022)
 
-https://learn.microsoft.com/en-us/system-center/scom/configure
+Note: Grafana is still in preview
 
 ### [Previous](setup.md) | [Home](readme.md) | [Next](migration.md)

content/management/scom-mi/readme.md

@@ -14,6 +14,10 @@
 
 In this session you will learn more about SCOM MI. The engineering team will cover details of the setup steps, the migration process and how to leverage the improvements made to SCOM when running as a managed instance in Azure.
 
+### Audience
+
+This session is most useful for IT administrators and architects responsible for managing SCOM or considering moving to SCOM MI.
+
 ## Agenda
 
 ### [Introduction to SCOM Managed Insance](intro.md)
@@ -24,42 +28,29 @@ What is SCOM MI and how does it differ from SCOM?
 
 Let's start with the business requirements and the setup process.
 
-### [Features](Features.md)
-
-What features does SCOM MI offer and how to leverage them?
-
-What are the features that are not available in SCOM MI?
-
 ### [Agents](agents.md)
 
 How to deploy agents via SCOM MI
 
 - Automatically
 - Manually
 
-### [Migration](migration.md)
-
-Migrating to SCOM MI.
+### [Features](newfeatures.md)
 
-### Audience
-
-This session is most useful for IT administrators and architects responsible for managing SCOM. While this session does introduce technical concepts, no special knowledge is required other than a general familiarity with the Azure Portal.
+What features does SCOM MI offer and how to leverage them?
 
-### Goals
+What are the features that are not available in SCOM MI?
 
-In this session you will review the following topics:
+### [Migration](migration.md)
 
-- SCOM MI Setup
-- Migrating to SCOM MI
-- Leveraging the new features of SCOM MI
+Migrating to SCOM MI.
 
 ### Additional learning resources
 
-[SCOM MI](https://docs.microsoft.com/en-us/azure/azure-monitor/insights/scom-mi-overview)
+[SCOM MI](https://learn.microsoft.com/en-us/azure/azure-monitor/vm/scom-managed-instance-overview)
 
 [About Operations Manager](https://learn.microsoft.com/en-us/system-center/scom/welcome?view=sc-om-2022)
 
 [SCOM MI FAQ](https://learn.microsoft.com/en-us/system-center/scom/faq?view=sc-om-2022)
 
 [SCOM MI Pricing](https://azure.microsoft.com/en-us/pricing/details/monitor/)
-

content/management/scom-mi/setup.md

@@ -4,37 +4,36 @@
 
 ## Pre-requisites
 
-### Network requirements
+### Setup Process
 
-![alt text](image-1.png)
+![alt text](image-4.png)
 
-Step 1. Register the SCOM Managed Instance resource provider
+[Step 1. Register the SCOM Managed Instance resource provider](https://learn.microsoft.com/en-us/system-center/scom/register-scom-managed-instance-resource-provider?view=sc-om-2022)
 
-Step 2. Create separate subnet in a VNet
+[Step 2. Create separate subnet in a VNet](https://learn.microsoft.com/en-us/system-center/scom/create-separate-subnet-in-vnet?view=sc-om-2022)
 
-Step 3. Create a SQL MI
+[Step 3. Create a SQL MI](https://learn.microsoft.com/en-us/system-center/scom/create-sql-managed-instance?view=sc-om-2022)
 
-Step 4. Create a Key vault
+[Step 4. Create a Key vault](https://learn.microsoft.com/en-us/system-center/scom/create-key-vault?view=sc-om-2022)
 
-Step 5. Create a user assigned identity
+[Step 5. Create a user assigned identity](https://learn.microsoft.com/en-us/system-center/scom/create-user-assigned-identity?view=sc-om-2022)
 
-Step 6. Create a computer group and gMSA account
+[Step 6. Create a computer group and gMSA account](https://learn.microsoft.com/en-us/system-center/scom/create-gmsa-account?view=sc-om-2022)
 
-Step 7. Store domain credentials in Key vault
+[Step 7. Store domain credentials in Key vault](https://learn.microsoft.com/en-us/system-center/scom/store-domain-credentials-in-key-vault?view=sc-om-2022)
 
-Step 8. Create a static IP
+[Step 8. Create a static IP](https://learn.microsoft.com/en-us/system-center/scom/create-static-ip?view=sc-om-2022)
 
-Step 9. Configure the network firewall
+[Step 9. Configure the network firewall](https://learn.microsoft.com/en-us/system-center/scom/configure-network-firewall?view=sc-om-2022)
 
-Step 10. Verify Azure and internal GPO policies
+[Step 10. Verify Azure and internal GPO policies](https://learn.microsoft.com/en-us/system-center/scom/verify-azure-and-internal-gpo-policies?view=sc-om-2022)
 
-Step 11. SCOM Managed Instance self-verification of steps
+[Step 11. SCOM Managed Instance self-verification of steps](https://learn.microsoft.com/en-us/system-center/scom/scom-managed-instance-self-verification-of-steps?view=sc-om-2022)
 
-Step 12. Create a SCOM Managed Instance
+Step 12. Create a SCOM Managed Instance!
 
-- SCOM MI requires a virtual network in Azure. This virtual network must have a gateway subnet and a virtual network gateway. The gateway subnet must be at least /29 and the virtual network gateway must be a VPN gateway.
 - The virtual network must have a DNS server configured. This DNS server must be able to resolve the SCOM MI domain name.
 
-[Setup Docs](https://learn.microsoft.com/en-us/system-center/scom/tutorial-create-scom-managed-instance?view=sc-om-2022)
+#### [Previous](intro.md) | [Home](readme.md) | [Next](agents.md)
 
-#### [Previous](intro.md) | [Home](readme.md) | [Next](newfeatures.md)
+[Setup Docs](https://learn.microsoft.com/en-us/system-center/scom/tutorial-create-scom-managed-instance?view=sc-om-2022)