Skip to content

Commit 3b9cca1

Browse files
committed
Merge branch 'main' into release-win365-gcc
2 parents 60c0025 + 4b2629c commit 3b9cca1

9 files changed

Lines changed: 89 additions & 56 deletions

memdocs/autopilot/known-issues.md

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,14 @@
11
---
22
title: Windows Autopilot known issues
33
description: Inform yourself about known issues that may occur during Windows Autopilot deployment.
4-
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
5-
ms.prod: w10
6-
ms.mktglfcycl: deploy
4+
ms.prod: windows-client
5+
ms.technology: itpro-deploy
76
ms.localizationpriority: medium
8-
ms.sitesec: library
9-
ms.pagetype: deploy
10-
audience: itpro
117
author: aczechowski
128
ms.author: aaroncz
139
ms.reviewer: jubaptis
1410
manager: dougeby
15-
ms.date: 05/18/2022
11+
ms.date: 09/21/2022
1612
ms.collection: M365-modern-desktop
1713
ms.topic: troubleshooting
1814
---
@@ -28,6 +24,14 @@ This article describes known issues that can often be resolved by configuration
2824

2925
## Known issues
3026

27+
### Autopilot deployment report shows "failure" status on a successful deployment
28+
29+
The Autopilot deployment report (preview) will show a failed status for any device that experiences an initial deployment failure. For subsequent deployment attempts, using the **Try again** or **Continue to desktop** options, it won't update the deployment state in the report. If the user resets the device, it will show as a new deployment row in the report with the previous attempt remaining as failed.
30+
31+
### Autopilot deployment report doesn't show deployed device
32+
33+
Autopilot deployments that take longer than one hour may display an incomplete deployment status in the deployment report. If the device successfully enrolls but doesn't complete provisioning after more than one hour, the device status may not be updated in the report.
34+
3135
### Autopilot profile not being applied when assigned
3236

3337
In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
@@ -62,9 +66,11 @@ When you attempt an Autopilot reset, you see the following message: _Autopilot r
6266

6367
When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. This behavior is by design. It makes sure that all devices that you register with Autopilot go through the Autopilot experience. If you don't want the device to go through an Autopilot deployment, remove the Autopilot registration.
6468

65-
### White screen during HAADJ deployment
69+
### White screen during hybrid Azure AD joined deployment
70+
71+
There's a UI bug on Autopilot hybrid Azure AD joined deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
6672

67-
There's a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
73+
This issue was resolved in September 2022.
6874

6975
### Virtual machine failing at "Preparing your device for mobile management"
7076

memdocs/intune/apps/app-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Intune offers a range of capabilities to help you get the apps you need on the d
7474
| Apps from a store | Yes | Yes | No | Yes |
7575
| Update apps | Yes | Yes | No | Yes |
7676

77-
<sup>1</sup> Consider using [Windows Information Protection](../protect/windows-information-protection-configure.md) to protect apps on devices that run Windows 10/11.<br>
77+
<sup>1</sup> Consider using [Microsoft Purview Information Protection](/microsoft-365/compliance/information-protection) and [Microsoft Purview Data Loss Prevention](/microsoft-365/compliance/dlp-learn-about-dlp). Microsoft Purview simplifies the configuration set-up and provides an advanced set of capabilities. <br>
7878
<sup>2</sup> Applies to devices managed by Intune only.<br>
7979
<sup>3</sup> Intune supports available apps from Managed Google Play store on Android Enterprise devices.<br>
8080
<sup>4</sup> Intune does not provide installing a shortcut to an app as a web link on standard Android Enterprise devices. However, Web link support is provided for [multi-app dedicated Android Enterprise devices](../configuration/device-restrictions-android-for-work.md#device-experience).<br>

memdocs/intune/fundamentals/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ The **All devices** option is now available for [compliance policy](../protect/c
216216
When you include the *All devices* group you can then exclude individual groups of devices to further refine the assignment scope.
217217

218218
#### Trend Micro – New mobile threat defense partner<!-- 11017779 -->
219-
You can now use [Trend Micro Mobile Security](../protect/trend-micro-mobile-threat-defense-connector.md) as an integrated mobile threat defense (MTD) partner with Intune. By configuring the Trend MTD connector in Intune, you can control mobile device access to corporate resources using conditional access that's based on risk assessment.
219+
You can now use [Trend Micro Mobile Security as a Service](../protect/trend-micro-mobile-threat-defense-connector.md) as an integrated mobile threat defense (MTD) partner with Intune. By configuring the Trend MTD connector in Intune, you can control mobile device access to corporate resources using conditional access that's based on risk assessment.
220220

221221
For more information, see:
222222
- [Mobile threat defense integration with Intune](../protect/mobile-threat-defense.md)

memdocs/intune/protect/mobile-threat-defense.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,6 @@ Learn how to protect access to company resource based on device, network, and ap
109109
- [Pradeo](pradeo-mobile-threat-defense-connector.md)
110110
- [Sophos Mobile](sophos-mtd-connector.md)
111111
- [Symantec Endpoint Protection Mobile](skycure-mobile-threat-defense-connector.md)
112-
- [Trend Micro Mobile Security](trend-micro-mobile-threat-defense-connector.md)
112+
- [Trend Micro Mobile Security as a Service](trend-micro-mobile-threat-defense-connector.md)
113113
- [Wandera Mobile Threat Defense](wandera-mtd-connector.md)
114114
- [Zimperium](zimperium-mobile-threat-defense-connector.md)

memdocs/intune/protect/mtd-apps-ios-app-configuration-policy-add-assign.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,9 +157,9 @@ Use the same Azure AD account previously configured in the [Symantec Endpoint Pr
157157

158158
Create the iOS app configuration policy as described in the [using iOS app configuration policy](../apps/app-configuration-policies-use-ios.md) article. For more information, see [Sophos Intercept X for Mobile iOS - Available managed settings](https://community.sophos.com/kb/133963) in the Sophos knowledge base.
159159

160-
### Trend Micro Mobile Security app configuration policy
160+
### Trend Micro Mobile Security as a Service app configuration policy
161161

162-
See the instructions for [using Microsoft Intune app configuration policies for iOS](../apps/app-configuration-policies-use-ios.md) to add the Trend Micro Mobile Security app configuration policy.
162+
See the instructions for [using Microsoft Intune app configuration policies for iOS](../apps/app-configuration-policies-use-ios.md) to add the Trend Micro Mobile Security as a Service app configuration policy.
163163

164164
### Wandera app configuration policy
165165

memdocs/intune/protect/trend-micro-mobile-threat-defense-connector.md

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
# required metadata
33

4-
title: Trend Micro Mobile connector with Intune
4+
title: Trend Micro Mobile Security as a Service connector with Intune
55
titleSuffix: Intune on Azure
66
description: Set up the Trend Micro Mobile Threat Defense connector with Intune.
77
keywords:
@@ -29,11 +29,16 @@ search.appverid: MET150
2929
ms.collection: M365-identity-device-management
3030
---
3131

32-
# Use Trend Micro Mobile Security with Intune
32+
# Use Trend Micro Mobile Security as a Service with Microsoft Intune
3333

34-
Control mobile device access to corporate resources using Conditional Access based on risk assessment conducted by Trend Micro Mobile Security, a mobile threat defense (MTD) solution that integrates with Microsoft Intune. Risk is assessed based on telemetry collected from devices running the Trend Micro Mobile Agent app.
34+
Control mobile device access to corporate resources using Conditional Access based on risk assessment conducted by Trend Micro Mobile Security as a Service, a mobile threat defense (MTD) solution that integrates with Microsoft Intune. Risk is assessed based on telemetry collected from devices protected by the Trend Micro Mobile Security as a Service, including:
3535

36-
You can configure Conditional Access policies based on a Trend Micro risk assessment, enabled through Intune device compliance policies for enrolled devices. You can set up your policies to allow or block noncompliant devices from accessing corporate resources based on detected threats.
36+
- Malicious apps installed
37+
- Malicious network behavior and profiles
38+
- Operating system vulnerabilities
39+
- Device misconfiguration
40+
41+
You can configure Conditional Access policies based on Trend Micro Mobile Security as a Service’s risk assessment, enabled through Intune device compliance policies for enrolled devices. You can set up your policies to allow or block noncompliant devices from accessing corporate resources based on detected threats.
3742

3843
For more information about how to integrate Trend Micro with Microsoft Intune, see [Integration with Microsoft Endpoint Manager (Intune)](http://docs.trendmicro.com/en-us/enterprise/trend-micro-vision-one/mobile-security/getting-started-with_003/integration-with-int.aspx) in the [Trend Micro Mobile Security documentation](https://docs.trendmicro.com/en-us/enterprise/trend-micro-vision-one/mobile-security.aspx).
3944

@@ -53,11 +58,11 @@ For more information about how to integrate Trend Micro with Microsoft Intune, s
5358

5459
## How do Intune and the Trend Micro MTD connector help protect your company resources?
5560

56-
The Trend Micro Mobile Agent app for Android and iOS/iPadOS captures file system, network stack, device, and application telemetry where available, then sends the telemetry data to the *Mobile Security* cloud service to assess the device's risk for mobile threats.
61+
The Trend Micro Mobile Security as a Service mobile agent app for Android and iOS/iPadOS captures file system, network stack, device, and application telemetry where available, then sends the telemetry data to Trend Micro Mobile Security as a Service to assess the device's risk for mobile threats.
5762

58-
- **Support for enrolled devices** - Intune device compliance policy includes a rule for MTD, which can use risk assessment information from Trend Micro. When the MTD rule is enabled, Intune evaluates device compliance with the policy that you enabled. If the device is found noncompliant, users are blocked access to corporate resources, such as Exchange Online and SharePoint Online. Users also receive guidance from the Trend Micro Mobile Agent app installed on their devices to resolve the issue and regain access to corporate resources. To support using Trend Micro with enrolled devices:
63+
- **Support for enrolled devices** - Intune device compliance policy includes a rule for MTD, which can use risk assessment information from Trend Micro. When the MTD rule is enabled, Intune evaluates device compliance with the policy that you enabled. If the device is found noncompliant, users are blocked access to corporate resources, such as Exchange Online and SharePoint Online. Users also receive guidance from the Trend Micro Mobile Security as a Service mobile agent app installed on their devices to resolve the issue and regain access to corporate resources. To support using Trend Micro with enrolled devices:
5964

60-
- [Add MTD apps to devices](../protect/mtd-apps-ios-app-configuration-policy-add-assign.md)
65+
- [Add MTD apps to devices](../protect/mtd-apps-ios-app-configuration-policy-add-assign.md) (This is done automatically when setting up Trend Micro Mobile Security as a Service integration)
6166
- [Create a device compliance policy that supports MTD](../protect/mtd-device-compliance-policy-create.md)
6267
- [Enable the MTD connector in Intune](../protect/mtd-connector-enable.md)
6368

@@ -107,7 +112,7 @@ Detect threats like **Man-in-the-middle** in network and prevent synchronization
107112

108113
## Next steps
109114

110-
- [Integrate Trend Micro with Intune](../protect/trend-micro-mtd-connector-integration.md)
111-
- [Set up Trend Micro Mobile Agent app](../protect/mtd-apps-ios-app-configuration-policy-add-assign.md)
112-
- [Create Trend Micro device compliance policy](../protect/mtd-device-compliance-policy-create.md)
113-
- [Enable Trend Micro Mobile Security MTD connector](../protect/mtd-connector-enable.md)
115+
- [Integrate Trend Micro Mobile Security as a Service with Intune](../protect/trend-micro-mtd-connector-integration.md)
116+
- [Set up Trend Micro Mobile Security as a Service mobile agent app](../protect/mtd-apps-ios-app-configuration-policy-add-assign.md)
117+
- [Create Trend Micro Mobile Security as a Service device compliance policy](../protect/mtd-device-compliance-policy-create.md)
118+
- [Enable Trend Micro Mobile Security as a Service MTD connector](../protect/mtd-connector-enable.md)

0 commit comments

Comments
 (0)