Skip to content

Commit d518791

Browse files
committed
additional edits
1 parent f8c1cb0 commit d518791

2 files changed

Lines changed: 3 additions & 4 deletions

File tree

memdocs/intune/protect/endpoint-protection-windows-10.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
---
22
# required metadata
3-
title: Settings you can deploy with Intune to protect managed Windows devices
4-
description: On Windows 10 or Windows 11 devices, configure endpoint protection settings to enable Microsoft Defender features, including Application Guard, Firewall, SmartScreen, encryption and BitLocker, Exploit Guard, Application Control, Security Center, and security on local devices in Microsoft Intune.
5-
keywords:
3+
title: Windows 10/11 settings you can deploy with Microsoft Intune to protect managed Windows devices
4+
description: Use Microsoft Intune endpoint protection profiles to manage settings that help protect your enrolled Windows 10 and 11 devices.
65
author: brenduns
76
ms.author: brenduns
87
manager: dougeby

memdocs/intune/protect/software-updates-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Consider testing to assess the impact of OS updates on the app you are running i
8787
If you don't configure times to start or end, the configuration results in no restriction and updates can install at any time.
8888

8989
> [!NOTE]
90-
> You can configure settings in [Device Restrictions](../configuration/device-restrictions-ios.md#general) to hide an update from device users for a period of time on your supervised iOS/iPadOS devices. A restriction period can give you time to test an update before its visible to users to install. After the device restriction period expires, the update becomes visible to users. Users can then choose to install it, or your Software update policies might automatically install it soon after.
90+
> You can configure settings in [Device Restrictions](../configuration/device-restrictions-ios.md#general) to hide an update from device users for a period of time on your supervised iOS/iPadOS devices. A restriction period can give you time to test an update before it's visible to users to install. After the device restriction period expires, the update becomes visible to users. Users can then choose to install it, or your Software update policies might automatically install it soon after.
9191
>
9292
> When you use a device restriction to hide an update, review your software update policies to ensure they wont schedule the install of the update before that restriction period ends. Software update policies install updates based on their own schedule, regardless of the update being hidden or visible to the device user.
9393

0 commit comments

Comments
 (0)