You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/ios-configure-features.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: conceptual
15
15
ms.subservice: ios
16
16
search.appverid: met150
17
-
ms.date: 02/06/2025
17
+
ms.date: 03/27/2025
18
18
---
19
19
20
20
# Configure Microsoft Defender for Endpoint on iOS features
@@ -319,7 +319,7 @@ Defender for Endpoint on iOS enables admins to configure custom indicators on iO
319
319
> [!NOTE]
320
320
> Defender for Endpoint on iOS supports creating custom indicators only for URLs and domains. IP based custom indicators aren't supported on iOS.
321
321
>
322
-
> IP `245.245.0.1` is an internal Defender IP and should not be included in custom indicators by customers to avoid any functionality issues.
322
+
> IP `245.245.0.1` is an internal Defender IP and shouldn't be included in custom indicators by customers to avoid any functionality issues.
323
323
>
324
324
> For iOS, no alerts are generated in the Microsoft Defender portal when the URL or domain set in the indicator is accessed.
325
325
@@ -427,6 +427,9 @@ Defender for Endpoint on iOS enables bulk tagging the mobile devices during onbo
427
427
428
428
This configuration is available for both the enrolled (MDM) devices and unenrolled (MAM) devices. Admins can use the following steps to configure the Device tags.
429
429
430
+
> [!NOTE]
431
+
> Configuring more than one device tags from Intune isn't supported as only one device tag reflects when configured. However, multiple device tags can be added manually in the XDR portal.
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-endpoint-ios.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: ios
17
17
search.appverid: met150
18
-
ms.date: 03/21/2025
18
+
ms.date: 03/27/2025
19
19
---
20
20
21
21
# Microsoft Defender for Endpoint on iOS
@@ -44,10 +44,12 @@ ms.date: 03/21/2025
44
44
45
45
Intune Company Portal app can be downloaded from the [Apple App Store](https://apps.apple.com/us/app/intune-company-portal/id719171358).
46
46
47
-
> [!NOTE]
48
-
> Apple doesn't allow redirecting users to download other apps from the app store so this step needs to be done by the user before onboarding to Microsoft Defender for Endpoint app.
49
-
50
-
Devices are registered with Microsoft Entra ID. This configuration requires the end user to be signed in through [Microsoft Authenticator app](https://apps.apple.com/app/microsoft-authenticator/id983156458).
47
+
> [!NOTE]
48
+
> Apple doesn't permit redirecting users to download other apps (Company Portal/Authenticator) from the App Store. Therefore, users need to complete this step themselves before onboarding to the Microsoft Defender for Endpoint app.
49
+
> Due to iOS platform restrictions, the MDE app allows onboarding without device registration, enabling MDE protections but leaving the device invisible on the security portal. For enrolled scenarios (MDM), the Company Portal or Authenticator app handles registration. For unenrolled scenarios (MAM), this is managed via the Authenticator app.
50
+
> If a user has a valid MDE license and is registered in the Authenticator App or Company Portal App, signing in to the Defender App allows the device appear in the Defender Portal.
51
+
52
+
Devices are registered with Microsoft Entra ID. This configuration requires the end user to be signed in through [Microsoft Authenticator app](https://apps.apple.com/app/microsoft-authenticator/id983156458).
51
53
52
54
-**For unenrolled devices**: Devices are registered with Microsoft Entra ID. This requires the end user to be signed in through [Microsoft Authenticator app](https://apps.apple.com/app/microsoft-authenticator/id983156458).
53
55
@@ -78,7 +80,7 @@ ms.date: 03/21/2025
78
80
- The device should be either enrolled with the [Intune Company Portal app](https://apps.apple.com/us/app/intune-company-portal/id719171358) or is registered with Microsoft Entra ID through [Microsoft Authenticator](https://apps.apple.com/app/microsoft-authenticator/id983156458) with the same account to seamlessly onboard the device.
79
81
80
82
> [!IMPORTANT]
81
-
> Microsoft Defender for Endpoint is ending support for devices running iOS/iPadOS 15 on January 31, 2025. Moving forward, only devices running iOS/iPadOS 16 and later are supported.
83
+
> Microsoft Defender for Endpoint is ending support for devices running iOS/iPadOS 15 on January 31, 2025. Only devices running iOS/iPadOS 16 and later are supported.
82
84
83
85
> [!NOTE]
84
86
> - Microsoft Defender for Endpoint on iOS isn't supported on user-less or shared devices.
@@ -88,10 +90,7 @@ ms.date: 03/21/2025
88
90
Deployment of Microsoft Defender for Endpoint on iOS can be done via Microsoft Intune and both supervised and unsupervised devices are supported. End-users can also directly install the app from the [Apple app store](https://aka.ms/mdatpiosappstore).
89
91
90
92
- For information on deploying on enrolled devices through Microsoft Configuration Manager or Intune, see [Deploy Microsoft Defender for Endpoint on iOS](ios-install.md).
91
-
- For information on using Defender for Endpoint in app protection policy (MAM), see [Configure app protection policy to include Defender for Endpoint risk signals (MAM)](ios-install-unmanaged.md)
92
-
93
-
> [!NOTE]
94
-
> If a user has a valid MDE license and is registered in the Authenticator App or Company Portal App, and signs in to the Defender App, the device appears in the Defender Portal.
93
+
- For information on using Defender for Endpoint in app protection policy (MAM), see [Configure app protection policy to include Defender for Endpoint risk signals (MAM)](ios-install-unmanaged.md).
@@ -24,7 +24,7 @@ Content distribution helps you manage content at scale, across tenants in multit
24
24
Distributing content in this manner, across tenants, enables you to organize tenants and content based on categories like business groups or location.
25
25
26
26
> [!NOTE]
27
-
> Multitenant management currently supports adding custom detection rules to a tenant group. Additional content types will be added in the future.
27
+
> Multitenant management currently supports adding custom detection rules to a tenant group. Additional content types will be added in the future.
28
28
29
29
## Requirements
30
30
@@ -41,7 +41,7 @@ The following table lists the requirements for content distribution in multitena
41
41
To create a new tenant group:
42
42
43
43
1. Go to the [Tenant groups page](https://mto.security.microsoft.com/tenantgroups) in multitenant management in Microsoft Defender XDR.
44
-
2. Select **Create tenant group**. In the **Tenants** page, select **Add tenant** to see a list of available tenants that you can add to your tenant group. Choose the tenants you want to add to the tenant group, then select **Add**.:
44
+
2. Select **Create tenant group**. In the **Tenants** page, select **Add tenant** to see a list of available tenants that you can add to your tenant group. Choose the tenants you want to add to the tenant group, then select **Add**.
45
45
46
46
:::image type="content" source="media/mto-tenantgroups/mto-add-tenants-small.png" alt-text="Screenshot of the tenant group creation wizard." lightbox="media/mto-tenantgroups/mto-add-tenants.png":::
47
47
@@ -50,7 +50,7 @@ To create a new tenant group:
50
50
:::image type="content" source="media/mto-tenantgroups/mto-add-content-small.png" alt-text="Screenshot of content selection wizard." lightbox="media/mto-tenantgroups/mto-add-content.png":::
51
51
52
52
> [!NOTE]
53
-
> The content type selection is currently limited to adding custom detection rules to a tenant group. Adding other content types will be available in the future.
53
+
> The content type selection is currently limited to adding custom detection rules to a tenant group.
54
54
55
55
4. In the **Custom detection rules** page, select **Add content** to add specific detection rules to your tenant group.
56
56
@@ -82,6 +82,9 @@ Check the sync results under the **Last sync result** column. If the result is *
82
82
83
83
:::image type="content" source="media/mto-tenantgroups/mto-sync-results-small.png" alt-text="Screenshot of sync results side pane." lightbox="media/mto-tenantgroups/mto-sync-results.png":::
84
84
85
+
> [!NOTE]
86
+
> The maximum number of published items per publish operation is 9,500. Published items are calculated as the number of tenants multiplied by the number of templates. For example, if you publish 10 tenant groups with 10 target tenants and 95 content templates, then the published items equals to 9,500.
87
+
85
88
## Syncing content among tenant groups
86
89
87
90
To sync content across tenant groups for the tenants you have permission for:
0 commit comments