Skip to content

Commit 49b1e2a

Browse files
Merge pull request #16523 from Brenduns/content-fresh-november
November Content engagment efforts
2 parents b60c8ce + 79d6e56 commit 49b1e2a

File tree

1 file changed

+13
-7
lines changed

1 file changed

+13
-7
lines changed

memdocs/intune/protect/mtd-connector-enable.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
author: brenduns
99
ms.author: brenduns
1010
manager: dougeby
11-
ms.date: 07/09/2024
11+
ms.date: 11/05/2024
1212
ms.topic: how-to
1313
ms.service: microsoft-intune
1414
ms.subservice: protect
@@ -33,25 +33,31 @@ ms.collection:
3333

3434
# Enable the Mobile Threat Defense connector in Intune
3535

36-
During Mobile Threat Defense (MTD) setup, you should have created a policy for classifying threats in your Mobile Threat Defense partner console and created a related device compliance policy in Microsoft Intune. If you already configured the Intune connector in the MTD partner console, you can now enable the MTD connection for your MTD partner application.
36+
Microsoft Intune can integrate data from a Mobile Threat Defense (MTD) partner for use by device compliance policies and device Conditional Access rules. You can use this information to help protect corporate resources like Exchange and SharePoint, by blocking access from compromised mobile devices.
37+
38+
After you [setup your MTD Partner](../protect/mobile-threat-defense.md#mobile-threat-defense-partners) and configure the Intune connector in the MTD partner console, you can then enable the MTD connection for that MTD partner application from within the Intune admin center.
3739

3840
Applies to:
3941

4042
- All [Intune Mobile Threat Defense partners](../protect/mobile-threat-defense.md#mobile-threat-defense-partners).
4143

44+
## Required role-based access control permissions
45+
46+
To successfully enable the Mobile Threat Defense connector, you must use an account that is assigned [Role-based access control](../fundamentals/role-based-access-control.md) (RBAC) permissions equivalent to the *Endpoint Security Manager* built-in admin role for Intune. If you use a custom role, ensure it includes the *Read* and *Modify* rights for the Intune *Mobile Threat Defense* permission.
47+
4248
## To enable the Mobile Threat Defense connector
4349

4450
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
4551

46-
2. Select **Tenant administration** > **Connectors and tokens** > **Mobile Threat Defense**. To set up an integration with a third-party Mobile Threat Defense vendor, your account must be assigned the *Endpoint Security Manager* built-in admin role for Intune, or be assigned a custom role that includes the *Read* and *Modify* rights for the Intune *Mobile Threat Defense* permission.
52+
2. Select **Tenant administration** > **Connectors and tokens** > **Mobile Threat Defense**.
4753

4854
3. On the **Mobile Threat Defense** pane, select **Add**.
4955

5056
4. For **Mobile Threat Defense connector to setup**, select your MTD partner solution from the drop-down list.
5157

52-
> [!NOTE]
53-
>
54-
> As of the August 2023 Intune service release (2308), classic Conditional Access (CA) policies are no longer created for the **Microsoft Defender for Endpoint** connector. As of April 2024 Intune service release (2404), classic CA policies are no longer needed for 3rd party **Mobile Threat Defense** connectors either. If your tenant has a classic CA policy that was previously created for integration with Microsoft Defender for Endpoint or 3rd party Mobile Threat Defense connectors, it can be deleted.
58+
> [!NOTE]
59+
>
60+
> As of the August 2023 Intune service release (2308), classic Conditional Access (CA) policies are no longer created for the **Microsoft Defender for Endpoint** connector. As of April 2024 Intune service release (2404), classic CA policies are no longer needed for 3rd party **Mobile Threat Defense** connectors either. If your tenant has a classic CA policy that was previously created for integration with Microsoft Defender for Endpoint or 3rd party Mobile Threat Defense connectors, it can be deleted.
5561
5662
5. Enable the toggle options according to your organization's requirements. The toggle options that are visible can vary depending on the MTD partner. For example, the following image shows the available options that are available for Symantec Endpoint Protection:
5763

@@ -114,4 +120,4 @@ To learn more about using Mobile Threat Defense connectors for Intune App Protec
114120
115121
## Next steps
116122

117-
- [Create Mobile Threat Defense (MTD) device compliance policy with Intune](mtd-device-compliance-policy-create.md).
123+
- [Create Mobile Threat Defense (MTD) device compliance policy with Intune](mtd-device-compliance-policy-create.md)

0 commit comments

Comments
 (0)