Skip to content

Commit 9d83bcd

Browse files
committed
replaced the content
1 parent ea4f8eb commit 9d83bcd

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/update-manager/guidance-migration-azure.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Patching guidance overview for Microsoft Configuration Manager to A
44
author: snehasudhirG
55
ms.service: azure-update-manager
66
ms.topic: conceptual
7-
ms.date: 04/18/2024
7+
ms.date: 04/19/2024
88
ms.author: sudhirsneha
99
---
1010

@@ -58,7 +58,9 @@ As a first step in MCM user's journey towards Azure Update Manager, you need to
5858

5959
### Overview of current MCM setup
6060

61-
If you have WSUS server configured as part of the initial setup as MCM client uses WSUS server to scan for first-party updates. Third party updates content is published to this WSUS server as well. Azure Update Manager has the capability to scan and install updates from WSUS and we recommend leveraging the WSUS server configured as part of MCM setup to make Azure Update Manager work along with MCM.
61+
MCM client uses WSUS server to scan for first-party updates, therefore you have WSUS server configured as part of the initial setup.
62+
63+
Third-party updates content is published to this WSUS server as well. Azure Update Manager has the capability of scanning & installing updates from WSUS, so we would leverage the WSUS server configured as part of MCM setup to make Azure Update Manager work along with MCM.
6264

6365
### First party updates
6466

0 commit comments

Comments
 (0)