Merge pull request #18705 from MicrosoftDocs/main

[AutoPublish] main to live - 09/18 15:29 PDT | 09/19 03:59 IST

Author: m365-skilling-repo-management[bot]

intune/intune-service/configuration/administrative-templates-import-custom.md

@@ -2,7 +2,7 @@
 # required metadata
 
 title: Import custom and third-party partner ADMX templates in Microsoft Intune
-description: You can add, upload, or import custom and third-party partner ADMX and ADML files in Microsoft Intune. When they're imported, create a device configuration profile and assign the profile to your Windows 10/11 devices.
+description: You can add, upload, or import custom and third-party partner ADMX and ADML files in Microsoft Intune. When they're imported, create a device configuration profile and assign the profile to your Windows 10/11 client devices.
 keywords:
 author: MandiOhlinger
 ms.author: mandia
@@ -34,15 +34,14 @@ You can import custom and third-party/partner ADMX and ADML templates into the I
 
 This feature applies to:
 
-- Windows 11
-- Windows 10
+- Windows
 
 This article shows you how to import custom ADMX and ADML files in the Intune admin center.
 
 > [!TIP]
 > The settings catalog has many settings natively built-in to Intune, including Google Chrome. For more information, go to:
 >
-> - [Use the settings catalog to configure settings on Windows, iOS/iPadOS, and macOS devices](settings-catalog.md)
+> - [Use the settings catalog to configure settings](settings-catalog.md)
 > - [Common tasks you can complete using the Settings Catalog](settings-catalog-common-features.md)
 
 ## What you need to know
@@ -147,7 +146,7 @@ When the import completes, your ADMX templates are shown in the list. You can al
 4. Select **Create**.
 5. In **Basics**, enter the following properties:
 
-    - **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is **ADMX: Mozilla Firefox for Windows 10/11 devices**.
+    - **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is **ADMX: Mozilla Firefox for Windows devices**.
     - **Description**: Enter a description for the profile. This setting is optional, but recommended.
 
 6. Select **Next**.
@@ -191,4 +190,4 @@ To update existing ADMX files that are imported, you have the following options:
 
 ## Related articles
 
-[Use the settings catalog to configure settings on Windows, iOS/iPadOS, and macOS devices](settings-catalog.md)
+[Use the settings catalog to configure settings](settings-catalog.md)

intune/intune-service/configuration/administrative-templates-windows.md

@@ -1,7 +1,7 @@
 ---
 # required metadata
 
-title: Use ADMX templates on Windows 10/11 devices in Microsoft Intune
+title: Use ADMX templates on Windows devices in Microsoft Intune
 description: Use Administrative templates in Microsoft Intune to create groups of settings for Windows 10/11 client devices. Use these settings in a device configuration profile. You can control Office programs, Microsoft Edge, access OneDrive, use remote desktop, enable Auto-Play, set power management settings, use HTTP printing, control user sign-in, and change the event log size.
 keywords:
 author: MandiOhlinger
@@ -31,7 +31,7 @@ ms.collection:
 - msec-ai-copilot
 ---
 
-# Use Windows 10/11 templates to configure group policy settings in Microsoft Intune
+# Use Windows templates to configure group policy settings in Microsoft Intune
 
 > [!IMPORTANT]
 > Starting with the December 2412 release, you can't create new Administrative Templates policies from the **Templates** > **Administrative Templates** profile type in the Intune admin center. To create ADMX template profiles, use the **[settings catalog](settings-catalog.md)**. For more information on this change, see [Windows device configuration policies migrating to unified settings platform in Intune](https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-windows-device-configuration-policies-migrating-to/ba-p/4189665).
@@ -43,8 +43,7 @@ ms.collection:
 
 This feature applies to:
 
-- Windows 11
-- Windows 10
+- Windows
 
 The Intune templates are 100-percent cloud-based, are built in to Intune (no downloading), and don't require any customizations, including using OMA-URI. They offer a straight-forward way to find and configure the settings you want:
 
@@ -62,7 +61,7 @@ This article describes the steps to create a template for Windows client devices
 
 ## Before you begin
 
-- Some of these settings are available starting with Windows 10 version 1709 (RS2/build 15063). Some settings aren't included in all Windows editions. For the best experience, we recommend Windows 10 Enterprise version 1903 (19H1/build 18362) or newer.
+- Some settings aren't included in all Windows editions. For the best experience, we recommend using the Windows Enterprise edition.
 
 - The Windows settings use the [Windows policy CSPs](/windows/client-management/mdm/policy-configuration-service-provider#policies-supported-by-group-policy-and-admx-backed-policies). The CSPs work on different editions of Windows, such as Home, Professional, Enterprise, and so on. To see if a CSP works on a specific edition, go to [Windows policy CSPs](/windows/client-management/mdm/policy-configuration-service-provider#policies-supported-by-group-policy-and-admx-backed-policies).
 
@@ -94,7 +93,7 @@ This article describes the steps to create a template for Windows client devices
 4. Select **Create**.
 5. In **Basics**, enter the following properties:
 
-    - **Name**: Name your profiles so you can easily identify them later. For example, a good profile name is *ADMX: Windows 10/11 admin template that configures xyz settings in Microsoft Edge*.
+    - **Name**: Name your profiles so you can easily identify them later. For example, a good profile name is **ADMX: Configures xyz settings in Microsoft Edge**.
     - **Description**: This setting is optional but recommended.
 
 6. Select **Next**.

intune/intune-service/configuration/bios-configuration.md

@@ -40,8 +40,7 @@ For example, you want to prevent end users from reimaging the device and getting
 
 This feature applies to:
 
-- Windows 11
-- Windows 10
+- Windows
 - Dell devices
 
 This article includes more information on the configuration file and Win32 app, and shows you how to create the **BIOS configuration and other settings** policy in Intune.

intune/intune-service/configuration/custom-profile-hololens.md

@@ -36,7 +36,7 @@ Using Windows PowerShell and Microsoft Intune, you can use the WDAC CSP to allow
 This feature applies to:
 
 - HoloLens 2 devices running Windows Holographic for Business
-- Windows 10/11
+- Windows
 
 The WDAC CSP is based on the [Windows Defender Application Control (WDAC) feature](/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control). You can also [use multiple WDAC policies](/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies).
 

intune/intune-service/configuration/custom-settings-configure.md

@@ -37,7 +37,7 @@ This feature applies to:
 - Android device administrator
 - iOS/iPadOS
 - macOS
-- Windows 10/11
+- Windows
 
 [!INCLUDE [android_device_administrator_support](../includes/android-device-administrator-support.md)]
 
@@ -75,7 +75,7 @@ This article shows you how to create a custom device configuration profile in In
     - [Android device administrator](custom-settings-android.md)
     - [iOS/iPadOS](custom-settings-ios.md)
     - [macOS](custom-settings-macos.md)
-    - [Windows 10/11](custom-settings-windows-10.md)
+    - [Windows](custom-settings-windows-10.md)
     - [Windows Holographic for Business](custom-settings-windows-holographic.md)
 
 8. Select **Next**.

intune/intune-service/configuration/custom-settings-windows-10.md

@@ -1,7 +1,7 @@
 ---
 # required metadata
 
-title: Add custom settings for Windows 10/11 devices in Microsoft Intune
+title: Add custom settings for Windows devices in Microsoft Intune
 description: Add or create a custom profile to use the OMA-URI settings for devices running Windows 10/11 client in Microsoft Intune. Use a custom profile to add custom settings.
 keywords:
 author: MandiOhlinger
@@ -41,8 +41,7 @@ These settings are added to a device configuration profile in Intune, and then a
 
 This feature applies to:
 
-- Windows 11
-- Windows 10
+- Windows
 
 Windows client custom profiles use Open Mobile Alliance Uniform Resource Identifier (OMA-URI) settings to configure different features. These settings are typically used by mobile device manufacturers to control features on the device.
 

intune/intune-service/configuration/custom-settings-windows-holographic.md

@@ -1,7 +1,7 @@
 ---
 # required metadata
 
-title: Custom settings - Windows Holographic for Business devices - Microsoft Intune | Microsoft Docs
+title: Custom settings - Windows Holographic for Business devices
 description: Add or create a custom profile to use the OMA-URI settings for devices running Windows Holographic for Business in Microsoft Intune, including Microsoft HoloLens. You can set AllowFastReconnect, AllowVPN, AllowUpdateService, UpdateServiceURL, RequireUpdatesApproval, ApprovedUpdates, and ApplicationLaunchRestrictions policy configuration service provider (CSP) settings.
 keywords:
 author: MandiOhlinger
@@ -34,7 +34,7 @@ Using Microsoft Intune, you can add or create custom settings for your Windows H
 This article applies to:
 
 - Windows Holographic for Business
-- Windows 10/11
+- Windows
 
 Windows Holographic for Business custom profiles use Open Mobile Alliance Uniform Resource Identifier (OMA-URI) settings to configure different features. These settings are typically used by mobile device manufacturers to control features on the device.
 

intune/intune-service/configuration/device-firmware-configuration-interface-windows-settings.md

@@ -1,8 +1,8 @@
 ---
 # required metadata
 
-title: Device firmware configuration interface settings for Windows 10/11 in Microsoft Intune
-description: See a list of all the DFCI profile settings and their descriptions on Windows 10/11 client devices. Use these settings in a configuration profile to control UEFI firmware layer features using Microsoft Intune policy. You can manage the CPU, built-in hardware, and boot options on Windows 10/11 client devices using Microsoft Intune.
+title: Device firmware configuration interface settings for Windows devices
+description: See a list of all the DFCI profile settings and their descriptions on Windows 10/11 client devices. Use these settings in a configuration profile to control UEFI firmware layer features using Microsoft Intune policy. You can manage the CPU, built-in hardware, and boot options on client devices using Microsoft Intune.
 keywords:
 author: MandiOhlinger
 ms.author: mandia
@@ -34,8 +34,7 @@ This article lists and describes the DFCI profile settings you can control on Wi
 
 These settings apply to:
 
-- Windows 11 on supported UEFI
-- Windows 10 RS5 (1809) and later on supported UEFI
+- Windows on supported UEFI
 
 These settings are added to a device configuration profile in Intune, and then assigned or deployed to your Windows client devices.
 
@@ -228,7 +227,7 @@ We recommend you configure the **Radios (Bluetooth, Wi-Fi, NFC, etc.)** category
 
 ## Related articles
 
-- For other technical details on each setting and what editions of Windows are supported, go to [Windows 10/11 Policy CSP Reference](/windows/client-management/mdm/policy-configuration-service-provider).
+- For other technical details on each setting and what editions of Windows are supported, go to [Windows Policy CSP Reference](/windows/client-management/mdm/policy-configuration-service-provider).
 
 - [Use DFCI profiles on Windows devices in Microsoft Intune](device-firmware-configuration-interface-windows.md).
 

intune/intune-service/configuration/device-firmware-configuration-interface-windows.md

@@ -38,8 +38,7 @@ In Intune, use this feature to control BIOS settings. Typically, firmware is mor
 
 This feature applies to:
 
-- Windows 11 on supported UEFI
-- Windows 10 RS5 (1809) and later on supported UEFI
+- Windows on supported UEFI
 
 For example, you use Windows client devices in a secure environment, and want to disable the camera. You can disable the camera at the firmware-layer, so it doesn't matter what the end user does. Reinstalling the OS or wiping the computer won't turn the camera back on. In another example, lock down the boot options to prevent users from booting up another OS, or an older version of Windows that doesn't have the same security features.
 

intune/intune-service/configuration/device-profile-create.md

@@ -137,7 +137,7 @@ Each template is a logical group of settings grouped together, like Email, VPN,
 
 ---
 
-For example, if you select **Windows 10 and later** for the platform, your options look similar to the following profile:
+For example, if you select Windows for the platform, your options look similar to the following profile:
 
 :::image type="content" source="./media/device-profile-create/windows-create-device-profile.png" alt-text="Screenshot that shows how to create a Windows device configuration policy and profile in Microsoft Intune.":::
 
@@ -151,31 +151,30 @@ For more information about scope tags, and what you can do, go to [Use RBAC and
 
 Applies to:
 
-- Windows 11
-- Windows 10
+- Windows
 
-Applicability rules allow administrators to target devices in a group that meet specific criteria. For example, you create a device restrictions profile that applies to the **All Windows 10/11 devices** group. And, you only want the profile assigned to devices running Windows Enterprise.
+Applicability rules allow administrators to target devices in a group that meet specific criteria. For example, you create a device restrictions profile that applies to the **All Windows devices** group. And, you only want the profile assigned to devices running Windows Enterprise.
 
 To do this task, create an **applicability rule**. These rules are great for the following scenarios:
 
-- You use Windows 10 Education (EDU). At Bellows College, you want to target all Windows 10 EDU devices between RS3 and RS4.
-- You want to target all users in Human Resources at Contoso, but only want Windows 10 Professional or Enterprise devices.
+- At Bellows College, you want to target all Windows devices running Windows 11, version 24H2.
+- You want to target all users in Human Resources at Contoso, but only want Windows Professional or Enterprise devices.
 
 To approach these scenarios, you:
 
-- Create a devices group that includes all devices at Bellows College. In the profile, add an applicability rule so it applies if the OS minimum version is `16299` and the maximum version is `17134`. Assign this profile to the Bellows College devices group.
+- Create a devices group that includes all devices at Bellows College. In the profile, add an applicability rule so it applies if the OS minimum version is `10.0.26100` and the maximum version is `10.0.26200`. Assign this profile to the Bellows College devices group.
 
   When the profile is assigned, it applies to devices between the minimum and maximum versions you enter. For devices that aren't between the minimum and maximum versions you enter, their status shows as **Not applicable**.
 
-- Create a users group that includes all users in Human Resources (HR) at Contoso. In the profile, add an applicability rule so it applies to devices running Windows 10 Professional or Enterprise. Assign this profile to the HR users group.
+- Create a users group that includes all users in Human Resources (HR) at Contoso. In the profile, add an applicability rule so it applies to devices running Windows Professional or Enterprise. Assign this profile to the HR users group.
 
-  When the profile is assigned, it applies to devices running Windows 10 Professional or Enterprise. For devices that aren't running these editions, their status shows as **Not applicable**.
+  When the profile is assigned, it applies to devices running Windows Professional or Enterprise. For devices that aren't running these editions, their status shows as **Not applicable**.
 
-- If there are two profiles with the exact same settings, then the profile without an applicability rule is applied. 
+- If there are two profiles with the exact same settings, then the profile without an applicability rule is applied.
 
-  For example, ProfileA targets the Windows 10 devices group, enables BitLocker, and doesn't have an applicability rule. ProfileB targets the same Windows 10 devices group, enables BitLocker, and has an applicability rule to only apply the profile to Windows 10 Enterprise.
+  For example, ProfileA targets the Windows devices group, enables BitLocker, and doesn't have an applicability rule. ProfileB targets the same Windows devices group, enables BitLocker, and has an applicability rule to only apply the profile to the Windows Enterprise edition.
 
-  When both profiles are assigned, ProfileA is applied because it doesn't have an applicability rule. 
+  When both profiles are assigned, ProfileA is applied because it doesn't have an applicability rule.
 
 When you assign the profile to the groups, the applicability rules act as a filter, and only target the devices that meet your criteria.
 
@@ -185,7 +184,7 @@ Use the following steps to create an applicability rule.
 
 1. In your policy, select **Applicability Rules**. You can choose the **Rule**, and **Property**:
 
-    :::image type="content" source="./media/device-profile-create/applicability-rules.png" alt-text="Screenshot that shows how to add an applicability rule to a Windows 10 device configuration profile in Microsoft Intune." lightbox="./media/device-profile-create/applicability-rules.png":::
+    :::image type="content" source="./media/device-profile-create/applicability-rules.png" alt-text="Screenshot that shows how to add an applicability rule to a Windows device configuration profile in Microsoft Intune." lightbox="./media/device-profile-create/applicability-rules.png":::
 
 2. In **Rule**, choose if you want to include or exclude users or groups. Your options:
 
@@ -218,7 +217,7 @@ When creating profiles, consider the following recommendations:
   Some configuration profile examples include:
 
   **Profile name**: OneDrive configuration profile for all Windows users  
-  **Profile description**: OneDrive profile that includes the minimum and base settings for all Windows 10 users. Created by `[email protected]` to prevent users from sharing organizational data to personal OneDrive accounts.
+  **Profile description**: OneDrive profile that includes the minimum and base settings for all Windows users. Created by `[email protected]` to prevent users from sharing organizational data to personal OneDrive accounts.
 
   **Profile name**: VPN profile for all iOS/iPadOS users  
   **Profile description**: VPN profile that includes the minimum and base settings for all iOS/iPadOS users to connect to Contoso VPN. Created by `[email protected]` so users automatically authenticate to VPN, instead of prompting users for their username and password.