Skip to content

Commit 485a8d9

Browse files
authored
Update group-policy-analytics-migrate.md
1 parent b00689e commit 485a8d9

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

memdocs/intune/configuration/group-policy-analytics-migrate.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: MandiOhlinger
88

99
ms.author: mandia
1010
manager: dougeby
11-
ms.date: 06/21/2022
11+
ms.date: 06/29/2022
1212
ms.topic: how-to
1313
ms.service: microsoft-intune
1414
ms.subservice: configuration
@@ -126,6 +126,12 @@ The **Migrate** feature takes the parsed data from the imported Group Policy obj
126126

127127
When you create the Settings Catalog profile, any settings that can be included in the profile will be included. There can be some differences with the imported settings and the settings in Settings Catalog.
128128

129+
- **Some settings have a better configuration experience in Endpoint Security**
130+
131+
If your imported Group Policy object contains AppLocker settings or Firewall rule settings, these are better configured in Endpoint Security rather than in the Settings Catalog. Learn more about [firewall policy in Endpoint Security](https://docs.microsoft.com/en-us/mem/intune/protect/endpoint-security-firewall-policy) and [application control policy in Endpoint Security](https://docs.microsoft.com/en-us/mem/intune/protect/endpoint-security-asr-policy).
132+
133+
You will see a grayed out checkbox to migrate these settings to Settings Catalog; however, they are supported in Endpoint Security.
134+
129135
- **Some settings don't migrate exactly, and may use a different setting**
130136

131137
In some scenarios, some GPO settings won't migrate to the exact same setting in the Settings Catalog. Intune will show an alternate setting that has a similar effect.

0 commit comments

Comments
 (0)