Skip to content

Commit 99e1cba

Browse files
authored
Merge branch 'main' into mde-content-freshness-updates
2 parents 7293b04 + ad3b1ec commit 99e1cba

File tree

3 files changed

+21
-16
lines changed

3 files changed

+21
-16
lines changed

defender-endpoint/ios-configure-features.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: conceptual
1515
ms.subservice: ios
1616
search.appverid: met150
17-
ms.date: 02/06/2025
17+
ms.date: 03/27/2025
1818
---
1919

2020
# 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
319319
> [!NOTE]
320320
> Defender for Endpoint on iOS supports creating custom indicators only for URLs and domains. IP based custom indicators aren't supported on iOS.
321321
>
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.
323323
>
324324
> For iOS, no alerts are generated in the Microsoft Defender portal when the URL or domain set in the indicator is accessed.
325325
@@ -427,6 +427,9 @@ Defender for Endpoint on iOS enables bulk tagging the mobile devices during onbo
427427

428428
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.
429429

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.
432+
430433
### Configure device tags using MDM
431434

432435
**For enrolled devices (MDM)**

defender-endpoint/microsoft-defender-endpoint-ios.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: ios
1717
search.appverid: met150
18-
ms.date: 03/21/2025
18+
ms.date: 03/27/2025
1919
---
2020

2121
# Microsoft Defender for Endpoint on iOS
@@ -44,10 +44,12 @@ ms.date: 03/21/2025
4444

4545
Intune Company Portal app can be downloaded from the [Apple App Store](https://apps.apple.com/us/app/intune-company-portal/id719171358).
4646

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).
5153

5254
- **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).
5355

@@ -78,7 +80,7 @@ ms.date: 03/21/2025
7880
- 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.
7981

8082
> [!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.
8284
8385
> [!NOTE]
8486
> - Microsoft Defender for Endpoint on iOS isn't supported on user-less or shared devices.
@@ -88,10 +90,7 @@ ms.date: 03/21/2025
8890
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).
8991

9092
- 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).
9594

9695
## Resources
9796

unified-secops-platform/mto-tenantgroups.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.collection:
1212
- highpri
1313
- tier1
1414
ms.topic: conceptual
15-
ms.date: 01/02/2025
15+
ms.date: 03/27/2025
1616
appliesto:
1717
- ✅ <a href="https://learn.microsoft.com/microsoft-365/security/defender/microsoft-365-defender" target="_blank">Microsoft Defender XDR</a>
1818
---
@@ -24,7 +24,7 @@ Content distribution helps you manage content at scale, across tenants in multit
2424
Distributing content in this manner, across tenants, enables you to organize tenants and content based on categories like business groups or location.
2525

2626
> [!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.
2828
2929
## Requirements
3030

@@ -41,7 +41,7 @@ The following table lists the requirements for content distribution in multitena
4141
To create a new tenant group:
4242

4343
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**.
4545

4646
:::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":::
4747

@@ -50,7 +50,7 @@ To create a new tenant group:
5050
:::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":::
5151

5252
> [!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.
5454
5555
4. In the **Custom detection rules** page, select **Add content** to add specific detection rules to your tenant group.
5656

@@ -82,6 +82,9 @@ Check the sync results under the **Last sync result** column. If the result is *
8282

8383
:::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":::
8484

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+
8588
## Syncing content among tenant groups
8689

8790
To sync content across tenant groups for the tenants you have permission for:

0 commit comments

Comments
 (0)