Skip to content

Commit 359bc9f

Browse files
committed
update
1 parent 765361a commit 359bc9f

File tree

2 files changed

+7
-10
lines changed

2 files changed

+7
-10
lines changed

articles/azure-monitor/azure-monitor-operations-manager.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,23 @@
11
---
2-
title: Azure Monitor for existing Operations Manager customers
2+
title: Migrate from SCOM to Azure Monitor
33
description: Guidance for existing users of Operations Manager to transition monitoring of certain workloads to Azure Monitor as part of a transition to the cloud.
44
ms.topic: conceptual
55
author: bwren
66
ms.author: bwren
7-
ms.date: 04/05/2022
7+
ms.date: 03/16/2023
88
ms.reviewer: bwren
99

1010
---
1111

12-
# Azure Monitor for existing Operations Manager customers
13-
This article provides guidance for customers who currently use [System Center Operations Manager](/system-center/scom/welcome) and are planning a transition to cloud based monitoring with [Azure Monitor](overview.md) as they migrate business applications and other resources into Azure. It assumes that your ultimate goal is a full transition into the cloud, replacing as much Operations Manager functionality as possible with Azure Monitor, without compromising your business and IT operational requirements.
12+
# Migrate from SCOM to Azure Monitor
13+
This article provides guidance for customers who currently use [System Center Operations Manager (SCOM)](/system-center/scom/welcome) and are planning a transition to cloud based monitoring with [Azure Monitor](overview.md) as they migrate business applications and other resources into Azure. It assumes that your ultimate goal is a full transition into the cloud, replacing as much Operations Manager functionality as possible with Azure Monitor, without compromising your business and IT operational requirements.
1414

1515
> [!IMPORTANT]
1616
> There is a cost to implementing several Azure Monitor features described here, so you should evaluate their value before deploying across your entire environment. See [Cost optimization and Azure Monitor](best-practices-cost.md) for strategies for reducing your cost for Azure Monitor.
1717
18-
## Prerequisites
19-
This article assumes that you already use [Operations Manager](/system-center/scom) and at least have a basic understanding of [Azure Monitor](overview.md). For a complete comparison between the two, see [Cloud monitoring guide: Monitoring platforms overview](/azure/cloud-adoption-framework/manage/monitor/platform-overview). That article details specific feature differences between to the two to help you understand some of the recommendations made here.
20-
2118

2219
## General strategy
23-
Your migration will instead constitute a [standard Azure Monitor implementation](best-practices.md) while you continue to use Operations Manager. As you customize Azure Monitor to meet your requirements for different applications and components and as it gains more features, then you can start to retire different management packs and agents in Operations Manager.
20+
Your migration will typically include a [standard Azure Monitor implementation](best-practices.md) while you continue to use Operations Manager. As you customize Azure Monitor to meet your requirements for different applications and components and as it gains more features, then you can start to retire different management packs and agents in Operations Manager.
2421

2522
> [!IMPORTANT]
2623
> [Azure Monitor SCOM Managed Instance (preview)](vm/scom-managed-instance-overview.md) is now in public preview. This allows you to move your existing SCOM environment into the Azure portal with Azure Monitor while continuing to use the same management packs. The rest of the recommendations in this article still apply as you migrate your monitoring logic into Azure Monitor.

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,6 @@ items:
6868
href: vm/monitor-virtual-machine-analyze.md
6969
- name: Create alerts
7070
href: vm/monitor-virtual-machine-alerts.md
71-
- name: Migrate management pack logic
72-
href: vm/monitor-virtual-machine-management-packs.md
7371
- name: Monitor Azure Monitor
7472
href: monitor-azure-monitor.md
7573
- name: Samples
@@ -555,6 +553,8 @@ items:
555553
items:
556554
- name: Migrate from Operations Manager
557555
href: azure-monitor-operations-manager.md
556+
- name: Migrate management pack logic
557+
href: vm/monitor-virtual-machine-management-packs.md
558558
- name: SCOM Managed Instance (preview)
559559
href: vm/scom-managed-instance-overview.md
560560
- name: Connect Operations Manager

0 commit comments

Comments
 (0)