Skip to content

Commit c4ba6d9

Browse files
committed
Merge branch 'release-intune-2204' of https://github.com/microsoftdocs/memdocs-pr into erikre-rel2204-14191454b
2 parents 8c546e9 + 6208f92 commit c4ba6d9

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

memdocs/intune/enrollment/ios-ipados-supervised-device-security-configurations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ To simplify the table below, only configured settings are listed. Undocumented d
8282

8383
## Supervised enhanced security (Level 2)
8484

85-
Level 2 is the recommended configuration for personal devices where users access more sensitive information. These devices are a natural target in enterprises today. These settings don't assume a large staff of highly skilled security personnel. Therefore, they should be accessible to most enterprise organizations. This configuration is applicable to most mobile users accessing work or school data on a device.
85+
Level 2 is the recommended configuration for supervised devices where users access more sensitive information. These devices are a natural target in enterprises today. These settings don't assume a large staff of highly skilled security personnel. Therefore, they should be accessible to most enterprise organizations. This configuration is applicable to most mobile users accessing work or school data on a device.
8686

8787
This configuration expands upon the configuration in Level 1 by enacting data transfer controls and blocking access to USB devices.
8888

memdocs/intune/protect/mde-security-integration.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 04/20/2022
10+
ms.date: 04/21/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -68,15 +68,15 @@ Devices that are using this flow will be unable to be deleted from the Microsoft
6868

6969
### Unable to enable the Security Management for Microsoft Defender for Endpoint workload in Endpoint Security
7070

71-
Most initial provisioning flows are completed typically and created by an Administrator of both services. There are some scenarios where Role-based Administration is used to customize the permissions of administrators. Today, those delegated the *Endpoint Security Manager* role may not have the necessary permissions to enable this feature. We will address this in a future release.
71+
Most initial provisioning flows are typically completed by an Administrator of both services (such as a Global Administrator). There are some scenarios where Role-based Administration is used to customize the permissions of administrators. Today, those delegated the *Endpoint Security Manager* role may not have the necessary permissions to enable this feature. We will address this in a future release.
7272

7373
### Co-existence with Microsoft Endpoint Configuration Manager
7474

7575
When using Configuration Manager, the best path for management of security policy is using the [Configuration Manager tenant attach](../../configmgr/tenant-attach/endpoint-security-get-started.md). In some environments it may be desired to use Security Management for Microsoft Defender for Endpoint. When using Security Management for Microsoft Defender for Endpoint with Configuration Manager, endpoint security policy should be isolated to a single control plane. Controlling policy through both channels will create the opportunity for conflicts and undesired results.
7676

7777
### Active Directory joined devices
7878

79-
Devices that are joined to Active Directory will use their **existing infrastructure** to complete Hybrid Azure Active Directory join. While the Defender for Endpoint component will start this process, the join action uses your Federation provider or Azure Active Directory Connect (AAD Connect) to complete the join. Review [Plan your hybrid Azure Active Directory join implementation](/azure/active-directory/devices/hybrid-azuread-join-plan) to learn more about configuring your environment.
79+
Devices that are joined to Active Directory will use their **existing infrastructure** to complete the Hybrid Azure Active Directory join process. While the Defender for Endpoint component will start this process, the join action uses your Federation provider or Azure Active Directory Connect (AAD Connect) to complete the join. Review [Plan your hybrid Azure Active Directory join implementation](/azure/active-directory/devices/hybrid-azuread-join-plan) to learn more about configuring your environment.
8080

8181
To troubleshoot Azure Active Directory onboarding issues, see [Troubleshoot Security Configuration Management Azure Active Directory onboarding issues](/microsoft-365/security/defender-endpoint/troubleshoot-security-config-mgt).
8282

0 commit comments

Comments
 (0)