Moving SCOM MI docs to new home

Author: PriskeyJeronika-MS

articles/azure-monitor/scom-manage-instance/connect-managed-instance-ops-console.md

@@ -0,0 +1,36 @@
+---
+ms.assetid: 
+title: Connect the Azure Monitor SCOM Managed Instance to Operations console
+description: This article describes how to connect the Azure Monitor SCOM Managed Instance to Operations console.
+author: PriskeyJeronika-MS
+ms.author: v-gjeronika
+manager: jsuri
+ms.date: 05/22/2024
+ms.service: azure-monitor
+ms.subservice: operations-manager-managed-instance
+ms.topic: how-to
+---
+
+# Connect the Azure Monitor SCOM Managed Instance to Operations console
+
+Azure Monitor SCOM Managed Instance is compatible with [System Center Operations Manager 2022](https://www.microsoft.com/download/details.aspx?id=104038).
+
+After you create the SCOM Managed Instance in Azure, connect the instance to Operations console to configure the workloads and monitor.
+
+## Connect SCOM Managed Instance to Operations console
+
+Follow the below steps to connect a SCOM Managed Instance to Operations console:
+
+1. **Identify server to install Ops Console**: Identify a server where you want to install the Operations console. 
+     >[!Note]
+     >Don't perform this on a SCOM Managed Instance VM; do it on a separate VM. The VM needs to be a Windows Server. This server can be on-premises or on Azure.
+     >- If the VM/machine is on-premises, set the NSG rules and firewall rules on the SCOM Managed Instance VNet and on the on-premises network where the VM/machine is located to ensure specified essential port (5724) is reachable.
+     >- If the VM/machine is in Azure, set the NSG rules and firewall rules on the SCOM Managed Instance VNet and on the Virtual network (VNET) where the VM/machine is located to ensure specified essential port (5724) is reachable.
+1. **Install the Ops Console**: From the [executable file](https://go.microsoft.com/fwlink/?linkid=2212475), install the Operations console and follow the installation wizard to successfully install the Operations console.
+1. **Connect SCOM Managed Instance to Ops Console**: Sign in to the Operations console and select **Connect To Server**. Add the DNS name displayed at SCOM Managed Instance > **Overview** > **Properties** > **Load Balancer**.
+
+## Next step
+
+[Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md)
+
+

articles/azure-monitor/scom-manage-instance/create-reports-power-bi.md

@@ -0,0 +1,64 @@
+---
+ms.assetid: 
+title: Create reports on Power BI
+description: This article describes how to create reports on Power BI for Azure Monitor SCOM Managed Instance.
+author: PriskeyJeronika-MS
+ms.author: v-gjeronika
+manager: jsuri
+ms.date: 05/24/2024
+ms.custom: UpdateFrequency.5, engagement-fy24
+ms.service: system-center
+ms.subservice: operations-manager-managed-instance
+ms.topic: how-to
+---
+
+# Create reports on Power BI
+
+This article describes how to create reports on Power BI for Azure Monitor SCOM Managed Instance.
+
+> [!VIDEO https://www.youtube.com/embed/MG5kGoe1zj0?start=215]
+
+## Prerequisites
+
+- Azure Active Directory based authentication: 
+
+    1. [Create an Azure Active Directory group](/azure/active-directory/roles/groups-create-eligible) for the users to whom you want to provide permissions to read data from the SQL Managed Instance through this Power BI report. 
+
+    2. Create login credentials for the Azure Active Directory group in the SQL Managed Instance, which adds the user principal of the group in the SQL Managed Instance. To create a login, see [Create Login (Transact-SQL)](/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current&preserve-view=true).
+            :::image type="Create login" source="media/operations-manager-managed-instance-create-reports-on-power-bi/create-login.png" alt-text="Screenshot showing create login option.":::
+    3. Provide **db_datareader** permission to the Login on Data warehouse database.
+            :::image type="Login properties" source="media/operations-manager-managed-instance-create-reports-on-power-bi/login-properties.png" alt-text="Screenshot showing login properties.":::
+    4. [Download the supported SSMS](/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16&preserve-view=true) and add login to SSMS.
+    5. In the network security group of the subnet where the Azure SQL Managed Instance is hosted, create an NSG rule to allow public endpoint traffic on port number 3342. For more information about how to configure public endpoint, see [Configure public endpoint](/azure/azure-sql/managed-instance/public-endpoint-configure?view=azuresql&preserve-view=true).
+            :::image type="Destination port range" source="media/operations-manager-managed-instance-create-reports-on-power-bi/destination-port-range.png" alt-text="Screenshot showing destination port range.":::
+- SQL based authentication: 
+
+    - You need the username and password of the SQL Managed Instance.
+
+## Create reports through public endpoint of SQL MI
+
+1. Sign in to the [Azure portal](https://portal.azure.com/) and search for SCOM Managed Instance.
+1. On the **Overview** page, under **Reports**, select **Power BI**. You have three options on the Power BI page.
+    1. **Prerequisite**: Allows you to manage endpoints.
+    1. **Configure and install Power BI**: Allows you to install and configure the SCOM Managed Instance dashboard in Power BI.
+    1. **View Power BI dashboard**: Allows you to visualize the SCOM Managed Instance dashboard in Power BI after the configuration.
+1. Review the **Prerequisites** to ensure Public endpoint of SQL MI is enabled. You'll notice the Database Host URL and Database name are displayed.
+     :::image type="Public endpoints" source="media/operations-manager-managed-instance-create-reports-on-power-bi/public-endpoints.png" alt-text="Screenshot showing public endpoints.":::
+1. Select **Configure Dashboard**, **Powerbi.com** opens in a new browser. Select **Get it now** to install **Microsoft SCOM managed instance reports** Power BI app in your workspace. 
+     :::image type="Power BI app" source="media/operations-manager-managed-instance-create-reports-on-power-bi/power-bi-app.png" alt-text="Screenshot showing Power BI app.":::
+1. The app displays sample data. You can edit the parameter values **Data-Warehouse DB host URL** and **Data-Warehouse Name**.
+     >[!Note]
+     >To update the parameters, go to **Settings** of the dataset, and edit the parameters or select **Connect your data** in the banner.
+         :::image type="Connect your data" source="media/operations-manager-managed-instance-create-reports-on-power-bi/connect-your-data.png" alt-text="Screenshot showing Connect your data option.":::
+1. After you enter the parameters, select any one of the following authentication methods: 
+    - SQL username and password-based method 
+    - Azure Active Directory-based method 
+    
+    The dataset and reports will be refreshed. 
+
+     >[!Note]
+     >To view Power BI reports of multiple SCOM Managed Instances, **Microsoft SCOM managed instance reports** app must be installed individually in a different Power BI workspace.
+
+## Next steps
+
+[Connect the Azure Monitor SCOM Managed Instance to Ops console](connect-managed-instance-ops-console.md).

articles/azure-monitor/scom-manage-instance/dashboards-on-azure-managed-grafana.md

@@ -0,0 +1,59 @@
+---
+ms.assetid: 
+title: Dashboards on Azure Managed Grafana
+description: This article describes how to create a SCOM Managed Instance dashboard on Azure Managed Grafana.
+author: PriskeyJeronika-MS
+ms.author: v-gjeronika
+manager: jsuri
+ms.date: 05/22/2024
+ms.service: azure-monitor
+ms.subservice: operations-manager-managed-instance
+ms.topic: how-to
+---
+
+# Dashboards on Azure Managed Grafana
+
+Azure Managed Grafana (AMG) is a data visualization platform, built on top of the Grafana software by Grafana Labs. Grafana helps you bring together metrics, logs, and traces into a single user interface.
+
+Azure Managed Grafana is optimized for the Azure environment and works seamlessly, providing the following integration features:
+
+- Built-in support for [Azure Monitor](/azure/azure-monitor/) and [Azure Data Explorer](/azure/data-explorer/).
+- User authentication and access control using Microsoft Entra identities.
+- Direct import of existing charts from the Azure portal.
+
+This article describes how to create a SCOM Managed Instance dashboard on Azure Managed Grafana.
+
+## Steps to create a SCOM Managed Instance dashboard on Azure Managed Grafana
+
+To create a SCOM Managed Instance dashboard on Azure Managed Grafana, follow these steps:
+
+### Get started with Azure Managed Grafana (AMG)
+
+1. Create or reuse an Azure Managed Grafana (AMG) with a version 10 on the Azure portal. To create an AMG instance, follow [these steps](/azure/managed-grafana/quickstart-managed-grafana-portal).
+2. Enable System assigned managed identity on the AMG instance.
+
+     :::image type="Permissions" source="media/dashboards-on-azure-managed-grafana/grafana-permissions.png" alt-text="Screenshot of grafana permissions.":::
+3. Browse to SQL managed instance where SCOM Managed Instance databases are created. Note the SQL managed instance public endpoints and the Database name.
+
+### Assign Permissions
+
+1. On the AMG instance, provide **Grafana Admin** permissions to the users who need access to create dashboards.
+      >[!NOTE]
+      >After you set up a dashboard, assign **Grafana Editor** user permission to view, edit and create additional dashboards.
+1. Grant permissions to the System managed identity of the Grafana instance on the SQL managed instance database by downloading and running the [PowerShell script](https://go.microsoft.com/fwlink/?linkid=2252607). This script creates a SQL user for Azure Managed Grafana identity.
+1. The script accepts details of **Azure Managed Grafana Instance name**, **SCOM MI instance name**, SQL managed instance **Public endpoint** and **Server admin login** credentials of SQL managed instance.
+
+### Configure Data source on AMG
+
+1. Browse to the AMG portal by selecting the AMG instance endpoint.
+2. Navigate to **Connections** > **Data sources** and add a data source of type **Microsoft SQL Server**.
+3. On the **Settings** page, enter the Database endpoint URL in the **Host** field.
+4. Enter the Database name (noted above) in **Database** field.
+5. Use **Azure Managed Identity** as the authentication method.
+6. Select **Save and test**.
+
+### Import SCOM Managed Instance dashboards in AMG instance
+
+1. Navigate to AMG instance endpoint > **Dashboards** > **New** > **Import** > **Import via grafana.com** > **Enter 19919** and select **Import**.
+2. Browse to the imported dashboards.
+3. On the top of the dashboard, choose the created Data source and the respective database in the dashboard settings.

articles/azure-monitor/scom-manage-instance/patch-scom-managed-instance.md

@@ -0,0 +1,93 @@
+---
+ms.assetid: 
+title: Patch Azure Monitor SCOM Managed Instance
+description: This article provides information on how to patch your Azure Monitor SCOM Managed Instance.
+author: PriskeyJeronika-MS
+ms.author: v-gjeronika
+manager: jsuri
+ms.date: 05/22/2024
+ms.service: azure-monitor
+ms.subservice: operations-manager-managed-instance
+ms.topic: how-to
+---
+
+# Patch Azure Monitor SCOM Managed Instance
+
+Azure Monitor SCOM Managed Instance offers a convenient patching experience compared to on-premises System Center Operations Manager.
+
+Following are the key highlights:
+
+- No update rollup in SCOM Managed Instance. A patch is released as and when there are significant fixes and updates made to the product. They're released at a frequency of as often as two weeks or two months.
+- Patching is quick and convenient and happens at the click of a button.
+- All newer patches are backward compatible with the older versions. 
+
+This article provides information on how to patch your SCOM Managed Instance.
+
+## Pre-Patching checklist
+
+Before you proceed with the patching process, complete the following prechecks to ensure a successful patching operation:
+
+1. **SQL managed instance status**: Verify that the SQL managed instance is operational and running, and not in a shutdown state.
+
+2. **Management server health**: Confirm the health of existing Management Servers.
+
+3. **Domain credentials verification**: Validate the status of the domain credentials used in the key vault. If the credentials have expired, update the password to ensure they're active and functional.
+
+4. **NAT Gateway association**: Ensure that the NAT Gateway is still associated with the subnet and hasn't been removed.
+
+5. **VNET connectivity requirements**: Ensure that VNet to VNet communication is allowed to enable communication between the newly added managed servers and the existing ones. Additionally, verify that the connectivity from the VNet to the SQL managed instance and Domain Controller is operational.
+
+## Patch SCOM Managed Instance
+
+To patch SCOM Managed Instance, follow these steps:
+
+1. Sign in to the [Azure portal](https://portal.azure.com/) and search for **SCOM Managed Instance**.
+1. On the **Overview** page, under **Configuration**, select **Patching**.
+1. On the **Patching** page, you see the status of the updates available for your instance.
+
+     :::image type="Patching" source="media/patch-scom-managed-instance/scom-mi-patching.png" alt-text="Screenshot of Patching.":::
+
+1. Select **Update instance** to update your instance.
+
+     :::image type="Update Instance" source="media/patch-scom-managed-instance/update-instance.png" alt-text="Screenshot of Update Instance.":::
+ 
+It takes 30 mins to 1 hour to successfully update the instance.
+
+ :::image type="Instance updated" source="media/patch-scom-managed-instance/instance-updated.png" alt-text="Screenshot of Instance updated.":::
+
+>[!NOTE]
+>To run custom configurations in your SCOM Managed Instance management servers, see [Customizations on Azure Monitor SCOM managed instance management servers](customizations-on-scom-managed-instance-management-servers.md).
+
+
+## Troubleshoot patching issues
+
+### Issue: In rare cases, after patching, stale Management Servers are visible on console
+
+**Cause**: Occurs if a patching operation has left an inconsistent state after completion.
+
+**Resolution**: Microsoft Azure Virtual Machine Scale Sets is used to provision the management servers for SCOM Managed Instances. To remove the stale management server from the system, follow these steps:
+
+1. Access the Azure Virtual Machine Scale Sets and log in to one of the management servers for the SCOM Managed Instance.
+
+2. Launch PowerShell in administrative mode and navigate to the following directory.
+
+    `C:\Packages\Plugins\Microsoft.Azure.SCOMMIServer.ScomServerForWindows\<version>\bin\troubleshooter`
+
+    >[!Note]
+    >To find the version, go to `C:\Packages\Plugins\Microsoft.Azure.SCOMMIServer.ScomServerForWindows` and review all available versions and then select the latest one.
+
+3. Execute the following script:
+
+    ```powershell
+    .\RemoveStaleManagementServers.ps1 
+    ```
+
+    The script is interactive and prompts you for the FQDN of the stale server.  
+
+4. Provide the accurate FQDN of the stale management server you wish to remove.
+
+    For example, FQDN: SCOMMI2000001.contoso.com.
+
+## Next steps
+
+[Connect the Azure Monitor SCOM Managed Instance to Ops console](connect-managed-instance-ops-console.md)