Merge pull request #276562 from PriskeyJeronika-MS/release-scommi

v-ccolin · web-flow · commit ca57a5edc023 · 2024-05-30T08:40:46.000+01:00
More edits
diff --git a/articles/azure-monitor/scom-manage-instance/create-operations-manager-managed-instance.md b/articles/azure-monitor/scom-manage-instance/create-operations-manager-managed-instance.md
@@ -96,8 +96,6 @@ To create a SCOM Managed Instance, follow these steps:
 
            The subnet can have existing resources in it. However, don't choose the subnet that houses the SQL managed instance because it won't contain enough IP addresses to house the SCOM Managed Instance components.
 
-           >[!NOTE]
-           >Make sure to associate a NAT gateway with a chosen subnet. The presence of a NAT gateway is necessary for SCOM Managed Instance to retrieve the components required for both installation and auto upgrade scenarios.
     - **SCOM managed instance interface**:
         - **Static IP**: Enter the static IP for the load balancer. This IP should be in the selected subnet range for SCOM Managed Instance. Ensure that the IP is in the IPv4 format, and create it in your routing table.
         - **DNS name**: Enter the DNS name that you attached to the static IP from the preceding step. The DNS name is mapped to the static IP that's previously defined.
@@ -127,12 +125,14 @@ To create a SCOM Managed Instance, follow these steps:
 1. Under **Review + create**, review all the inputs given so far, and then select **Create**. Your deployment is created on Azure. Creation of a SCOM Managed Instance takes up to an hour.
 
     >[!NOTE]
-    >If the deployment fails, delete the instance and all the associated resources, and then create the instance again.
+    >If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./common-questions.md#other-queries).
 
 1. After the deployment is finished, select **Go to resource**.
 
    On the instance page, you can view some of the essential details and instructions for post-deployment steps and reporting bugs.
 
-## Next step
+## Next steps
 
-[Create a user-assigned identity](create-user-assigned-identity.md).
+- [Troubleshoot commonly encountered errors while validating input parameters](troubleshooting-input-parameters-scom-managed-instance.md)
+- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md)
+- [Azure Monitor SCOM Managed Instance frequently asked questions](common-questions.md)
diff --git a/articles/azure-monitor/scom-manage-instance/create-separate-subnet-in-vnet.md b/articles/azure-monitor/scom-manage-instance/create-separate-subnet-in-vnet.md
@@ -22,7 +22,7 @@ This article describes how to create a separate subnet in a virtual network for
 
 For more information on how to create a virtual network, see [Quickstart: Use the Azure portal to create a virtual network](/azure/virtual-network/quick-create-portal).
 
-After a SCOM Managed Instance subnet is created, we need a NAT gateway for outbound internet access from the SCOM Managed Instance subnet. Edit the subnet to add a NAT gateway. In Azure, add a NAT gateway to the subnet where the SCOM Managed Instance is created. A NAT gateway is needed for outbound internet access from the SCOM Managed Instance subnet. For more information, see [What is Virtual Network NAT?](/azure/virtual-network/nat-gateway/nat-overview).
+After a SCOM Managed Instance subnet is created, we need a NAT gateway for outbound internet access from the SCOM Managed Instance subnet. Edit the subnet to add a NAT gateway. In Azure, add a NAT gateway to the subnet where the SCOM managed instance is created. A NAT gateway is needed for outbound internet access from the SCOM Managed Instance subnet. For more information, see [What is Virtual Network NAT?](/azure/virtual-network/nat-gateway/nat-overview).
 
 >[!NOTE]
 >The SCOM Managed Instance requires outbound Internet access for communication with dependent endpoints. We recommend to use a NAT Gateway for this purpose. However, if there is an already established outbound internet access through a firewall, you can skip the creation of a NAT Gateway.
diff --git a/articles/azure-monitor/scom-manage-instance/create-user-assigned-identity.md b/articles/azure-monitor/scom-manage-instance/create-user-assigned-identity.md
@@ -109,3 +109,7 @@ To grant permission on the key vault that you created in [step 4](create-key-vau
     :::image type="Principal tab" source="media/create-user-assigned-identity/principal.png" alt-text="Screenshot that shows the Principal tab.":::
 
 1. Select **Next** > **Create**.
+
+## Next steps
+
+- [Create a gMSA account](create-group-managed-service-account.md)
diff --git a/articles/azure-monitor/scom-manage-instance/customizations-on-scom-managed-instance-management-servers.md b/articles/azure-monitor/scom-manage-instance/customizations-on-scom-managed-instance-management-servers.md
@@ -48,6 +48,6 @@ If the script runs successfully, deployment gets successful and displays **Deplo
 
 If there's an error in the script, you see **An error occurred during deployment. Please check the above logs for debugging** message.
 
-## Next step
+## Next steps
 
-[Register the Azure Monitor SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md)
+[Create a SCOM Managed Instance](create-operations-manager-managed-instance.md).
diff --git a/articles/azure-monitor/scom-manage-instance/index.yml b/articles/azure-monitor/scom-manage-instance/index.yml
@@ -33,4 +33,24 @@ landingContent:
         links:
           - text: Migrate from Operations Manager on-premises to SCOM Managed Instance
             url: migrate-to-operations-manager-managed-instance.md
-     
+      - linkListType: how-to-guide
+        links:
+          - text: Create SCOM Managed Instance
+            url: create-operations-manager-managed-instance.md
+
+  - title: Visualize monitoring data
+    linkLists:
+      - linkListType: how-to-guide
+        links:  
+          - text: Create reports on Power BI
+            url: create-reports-power-bi.md
+          - text: Dashboards on Azure Managed Grafana
+            url: dashboards-on-azure-managed-grafana.md
+  - title: Troubleshooting
+    linkLists:
+      - linkListType: how-to-guide
+        links:  
+          - text: Troubleshoot issues with Azure Monitor SCOM Managed Instance
+            url: troubleshoot-scom-managed-instance.md
+          - text: Troubleshoot commonly encountered errors while validating input parameters
+            url: troubleshooting-input-parameters-scom-managed-instance.md
diff --git a/articles/azure-monitor/scom-manage-instance/migrate-to-operations-manager-managed-instance.md b/articles/azure-monitor/scom-manage-instance/migrate-to-operations-manager-managed-instance.md
@@ -17,7 +17,7 @@ This quickstart provides the process of migration from Operations Manager on-pre
 
 ## Prerequisites
 
-1. Verify that your current Operations Manager agent version is supported to be multi-homed with SCOM Managed Instance.  
+1. Verify that your current Operations Manager agent version is supported to multi-homed with SCOM Managed Instance.  
 
     >[!Note]
     >Agent versions 2022 and 2019 are supported.
@@ -219,3 +219,7 @@ To migrate from System Center Operations Manager agent to SCOM Managed Instance,
 - Agent mapping and configuration
 - Gateways 
 - Custom and 3P Solutions 
+
+## Next steps
+
+[Create a SCOM Managed Instance on Azure](create-operations-manager-managed-instance.md).
diff --git a/articles/azure-monitor/scom-manage-instance/monitor-health-scom-managed-instance.md b/articles/azure-monitor/scom-manage-instance/monitor-health-scom-managed-instance.md
@@ -27,8 +27,6 @@ For more information, see [Azure Resource Health overview](/azure/service-health
 
 To troubleshoot the problems in your service, see the following:
 
+- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](./troubleshoot-scom-managed-instance.md).
+- [Troubleshoot commonly encountered errors while validating input parameters](./troubleshooting-input-parameters-scom-managed-instance.md).
 - Use the [troubleshooting tool](https://portal.azure.com/#view/Microsoft_Azure_Support/TroubleshootV2Blade/assetId/%2Fsubscriptions%2F5a87dd7e-200a-4e94-8cd6-a9461de63755%2FresourceGroups%2Fsaipwus2rg1%2Fproviders%2FMicrosoft.Scom%2FmanagedInstances%2Fsaipscom1) to get recommended solutions.
-
-## Next step
-
-[Tutorial: Create an instance of Azure Monitor SCOM Managed Instance](tutorial-create-scom-managed-instance.md).
diff --git a/articles/azure-monitor/scom-manage-instance/overview.md b/articles/azure-monitor/scom-manage-instance/overview.md
@@ -62,7 +62,7 @@ The following table highlights the key differences between System Center Operati
 |Manageability of monitoring infrastructure|Availability, Reliability, and Fault-Tolerance|Customer responsibility. No HA or BCDR promised by the product.|Instance-level availability and tolerance.|
 |Manageability of monitoring infrastructure|Optimization and Scaling|Customer responsibility and heavy infrastructure.|Manually initiated from the portal at the click of a button.|
 |Workload monitoring|Reuse of System Center Operations Manager management packs|All agent-based management packs are supported.|All agent-based management packs are supported.|
-|Workload monitoring|Monitoring non-domain workloads|Supported via gateway servers.|Via gateway servers for off-Azure endpoints and via managed identity for Azure endpoints.|
+|Workload monitoring|Monitoring non-domain workloads|Supported via gateway servers.|Via gateway servers for off-Azure endpoints and via managed identify for Azure endpoints.|
 |Workload monitoring|Monitoring Arc and multicloud workloads|Arc is not supported. Availability of Azure management pack.|Azure-based, Arc connected, and on-premises workloads.|
 |Log collection and analysis|Query and analysis of observability data|Querying is possible.|Maintained in SQL managed instance. <br/> <br/> A first-class ability to channel data into the log analytics workspace to maintain a central data plane.
 |Alerting|Real-time alerts for infra and apps|Alerting through System Center Operations Manager Ops console.|Integrated alerting with Azure Monitor.|
@@ -71,6 +71,8 @@ The following table highlights the key differences between System Center Operati
 
 ## Architecture
 
+:::image type="SCOM Managed Instance architecture" source="media/operations-manager-managed-instance-overview/architecture.png" alt-text="Screenshot showing architecture.":::
+
 A SCOM Managed Instance consists of two parts:
    - A Microsoft-managed part
    - A customer-managed part
@@ -96,3 +98,21 @@ In customer subscription, SCOM Managed Instance, creates a Virtual Machine Scale
 
 Operations Manager Management server and monitored agents are connected through ER/VPN. Agents establish session with Operations Manager Management server using the Kerberos authentication, where Operations Manager Virtual Machine Scale Sets VMs are joined to the AD domain of the monitored agents. 
 
+## Next steps
+
+  To create SCOM Managed Instance, follow these steps:
+
+   - [Step 1. Register the SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md).
+   - [Step 2. Create separate subnet in a VNet](create-separate-subnet-in-vnet.md).
+   - [Step 3. Create a SQL Managed Instance](create-sql-managed-instance.md).
+   - [Step 4. Create a Key vault](create-key-vault.md).
+   - [Step 5. Create a user assigned identity](create-user-assigned-identity.md).
+   - [Step 6. Create a computer group and gMSA account](create-group-managed-service-account.md).
+   - [Step 7. Store domain credentials in Key vault](store-domain-credentials-key-vault.md).
+   - [Step 8. Create a static IP](create-static-ip.md).
+   - [Step 9. Configure the network firewall](configure-network-firewall.md).
+   - [Step 10. Verify Azure and internal GPO policies](verify-azure-internal-group-policy-object-policies.md).
+   - [Step 11. SCOM Managed Instance self-verification of steps](self-verification-steps.md).
+   - [Step 12. Create a SCOM Managed Instance](create-operations-manager-managed-instance.md).
+
+[Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md).
diff --git a/articles/azure-monitor/scom-manage-instance/query-scom-managed-instance-data-on-grafana.md b/articles/azure-monitor/scom-manage-instance/query-scom-managed-instance-data-on-grafana.md
@@ -191,4 +191,4 @@ SELECT PD.TimeSampled
 
 ## Next steps
 
-[Patch Azure Monitor SCOM Managed Instance](patch-scom-managed-instance.md)
+[Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md).
diff --git a/articles/azure-monitor/scom-manage-instance/tutorial-create-scom-managed-instance.md b/articles/azure-monitor/scom-manage-instance/tutorial-create-scom-managed-instance.md
@@ -36,6 +36,22 @@ This tutorial describes how to create an instance of the service (a SCOM Managed
 - West US 2
 - West US 3
 
+## Prerequisites
+
+Before you create a SCOM Managed Instance, follow these steps:
+
+- [Step 1. Register the SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md).
+- [Step 2. Create separate subnet in a VNet](create-separate-subnet-in-vnet.md).
+- [Step 3. Create a SQL Managed Instance](create-sql-managed-instance.md).
+- [Step 4. Create a Key vault](create-key-vault.md).
+- [Step 5. Create a user assigned identity](create-user-assigned-identity.md).
+- [Step 6. Create a computer group and gMSA account](create-group-managed-service-account.md).
+- [Step 7. Store domain credentials in Key vault](store-domain-credentials-key-vault.md).
+- [Step 8. Create a static IP](create-static-ip.md).
+- [Step 9. Configure the network firewall](configure-network-firewall.md).
+- [Step 10. Verify Azure and internal GPO policies](verify-azure-internal-group-policy-object-policies.md).
+- [Step 11. SCOM Managed Instance self-verification of steps](self-verification-steps.md).
+
 ## Create a SCOM Managed Instance
 
 To create a SCOM Managed Instance, follow these steps:
@@ -96,8 +112,6 @@ To create a SCOM Managed Instance, follow these steps:
 
            The subnet can have existing resources in it. However, don't choose the subnet that houses the SQL managed instance because it won't contain enough IP addresses to house the SCOM Managed Instance components.
 
-           >[!NOTE]
-           >Make sure to associate a NAT gateway with a chosen subnet. The presence of a NAT gateway is necessary for SCOM Managed Instance to retrieve the components required for both installation and auto upgrade scenarios.
     - **SCOM managed instance interface**:
         - **Static IP**: Enter the static IP for the load balancer. This IP should be in the selected subnet range for SCOM Managed Instance. Ensure that the IP is in the IPv4 format, and create it in your routing table.
         - **DNS name**: Enter the DNS name that you attached to the static IP from the preceding step. The DNS name is mapped to the static IP that's previously defined.
@@ -127,9 +141,14 @@ To create a SCOM Managed Instance, follow these steps:
 1. Under **Review + create**, review all the inputs given so far, and then select **Create**. Your deployment is created on Azure. Creation of a SCOM Managed Instance takes up to an hour.
 
     >[!NOTE]
-    >If the deployment fails, delete the instance and all the associated resources, and then create the instance again. 
+    >If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./common-questions.md#other-queries).
 
 1. After the deployment is finished, select **Go to resource**.
 
    On the instance page, you can view some of the essential details and instructions for post-deployment steps and reporting bugs.
 
+## Next steps
+
+- [Troubleshoot commonly encountered errors while validating input parameters](troubleshooting-input-parameters-scom-managed-instance.md)
+- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md)
+- [Azure Monitor SCOM Managed Instance frequently asked questions](common-questions.md)
diff --git a/articles/azure-monitor/scom-manage-instance/whats-new-scom-managed-instance.md b/articles/azure-monitor/scom-manage-instance/whats-new-scom-managed-instance.md
@@ -17,11 +17,11 @@ This article provides details of what's new in each version of Azure Monitor SCO
 
 ## Version 1.0.100
 
-- Bug fix in prepatch/prescale validations.
+- Bug fix in pre-patch/pre-scale validations.
 
 ## Version 1.0.99
 
-- Enhanced checks for domain connectivity to handle multiple domain controllers during onboarding, prepatching, and prescaling validations.
+- Enhanced checks for domain connectivity to handle multiple domain controllers during onboarding, pre-patching, and pre-scaling validations.
 
 ## Version 1.0.98
 
@@ -39,11 +39,11 @@ This article provides details of what's new in each version of Azure Monitor SCO
 
 ## Version 1.0.96
 
-- Prepatch validation bug fix for machines that have unresolved accounts in the admin group.
+- Pre-patch validation bug fix for machines that have unresolved accounts in the admin group.
 
 ## Version 1.0.95
 
-- Enhance onboarding/prepatching/prescaling validations to check the connectivity to required endpoints.
+- Enhance onboarding/pre-patching/pre-scaling validations to check the connectivity to required endpoints as described in [firewall requirements](configure-network-firewall.md#firewall-requirements).
 
 ## Version 1.0.94
 
@@ -57,7 +57,7 @@ This article provides details of what's new in each version of Azure Monitor SCO
 
 ## Version 1.0.91
 
-- **Implemented prepatching validations**: Conducted essential checks before initiating the patching operation, ensuring optimal conditions for existing management servers, verifying SQL connectivity, confirming active directory accessibility, and validating the accuracy of domain account credentials.
+- **Implemented pre-patching validations**: Conducted essential checks before initiating the patching operation, ensuring optimal conditions for existing management servers, verifying SQL connectivity, confirming active directory accessibility, and validating the accuracy of domain account credentials.
 
 - Bug fix to handle the concurrency in extension installation.
 
@@ -89,4 +89,4 @@ This article provides details of what's new in each version of Azure Monitor SCO
 
 ## Next steps
 
-[Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md).
+[Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md)

Original file line number	Diff line number	Diff line change
`@@ -191,4 +191,4 @@ SELECT PD.TimeSampled`
`191`	`191`
`192`	`192`	`## Next steps`
`193`	`193`
`194`		`-[Patch Azure Monitor SCOM Managed Instance](patch-scom-managed-instance.md)`
	`194`	`+[Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md).`