Skip to content

Commit edad01f

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into WN8764312
2 parents 5b3ecad + 2b07057 commit edad01f

33 files changed

Lines changed: 3003 additions & 3233 deletions

memdocs/autopilot/add-devices.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,13 @@
11
---
22
title: Manually register devices with Windows Autopilot
33
description: Learn how to manually add devices to Windows Autopilot.
4-
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
54
ms.prod: w10
6-
ms.mktglfcycl: deploy
75
ms.localizationpriority: medium
8-
ms.sitesec: library
9-
ms.pagetype: deploy
10-
audience: itpro
116
author: aczechowski
127
ms.author: aaroncz
138
ms.reviewer: jubaptis
149
manager: dougeby
15-
ms.date: 08/05/2021
10+
ms.date: 06/03/2022
1611
ms.topic: how-to
1712
ms.collection:
1813
- M365-modern-desktop
@@ -166,7 +161,8 @@ Keep these other requirements for the CSV file in mind:
166161
- You can use only ANSI-format text files (not Unicode).
167162
- Headers are case-sensitive.
168163

169-
Because of these requirements, editing an Excel file and saving it as .csv will not generate a usable file for importing into the Intune portal.
164+
> [!IMPORTANT]
165+
> Use a plain-text editor with this CSV file, like Notepad. Don't use Microsoft Excel. Because of the requirements, editing an Excel file and saving it as `.csv` won't generate a usable file for importing to Intune.
170166
171167
When you upload a CSV file to assign a user, make sure that you assign valid User Principal Names (UPNs). If you assign an invalid UPN (that is, an incorrect username), your device might be inaccessible until you remove the invalid assignment.
172168

memdocs/intune/enrollment/macos-enroll.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Intune supports the following enrollment methods for company-owned macOS devices
6969
## Bootstrap tokens (preview)
7070

7171
> [!IMPORTANT]
72-
> This feature is in [public preview](../fundamentals/public-preview.md). It is not available in GCC High and government cloud tenants.
72+
> This feature is in [public preview](../fundamentals/public-preview.md).
7373
7474
Intune supports the use of bootstrap tokens on enrolled Macs running macOS 10.15 or later. Bootstrap tokens grant volume ownership status to local user and guest accounts, so that non-admin users can approve important operations that an admin would otherwise need to do. Operations such as:
7575

memdocs/intune/enrollment/windows-bulk-enroll.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,9 @@ Azure AD users are standard users on these devices and receive assigned Intune p
7070
6. Select **Enroll in Azure AD**, enter a **Bulk Token Expiry** date, and then select **Get Bulk Token**. The token validity period is 180 days.
7171
![Screenshot of account management in the Windows Configuration Designer app](./media/windows-bulk-enroll/bulk-enroll-account.png)
7272

73+
> [!NOTE]
74+
> Once a provisioning package is created, it can be revoked before its expiration by removing the associated package_{GUID} user account from Azure AD.
75+
7376
7. Provide your Azure AD credentials to get a bulk token.
7477
![Screenshot of signing in to the Windows Configuration Designer app](./media/windows-bulk-enroll/bulk-enroll-cred.png)
7578

memdocs/intune/enrollment/windows-enrollment-status.md

Lines changed: 102 additions & 68 deletions
Large diffs are not rendered by default.

memdocs/intune/fundamentals/in-development.md

Lines changed: 655 additions & 135 deletions
Large diffs are not rendered by default.

memdocs/intune/fundamentals/supported-devices-browsers.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@ Intune supports devices running the following operating systems (OS):
4444
* Android
4545
* Windows
4646
* macOS
47-
* Linux
4847

4948
[!INCLUDE [mdm-supported-devices](../includes/mdm-supported-devices.md)]
5049

memdocs/intune/protect/advanced-threat-protection-configure.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords: configure, manage, capabilities, attack surface reduction, next-genera
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 05/23/2022
10+
ms.date: 06/06/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -40,6 +40,8 @@ Use the information and procedures in this article to configure integration of M
4040

4141
Before starting, your environment must meet the [prerequisites](../protect/advanced-threat-protection.md#prerequisites) to use Microsoft Defender for Endpoint with Intune.
4242

43+
In addition to managing settings for Microsoft Defender for Endpoint on devices you manage with Intune, you can manage Defender for Endpoint security configurations on devices that aren’t enrolled with Intune. This scenario is called *Security Management for Microsoft Defender for Endpoint* and requires configuring the *Allow Microsoft Defender for Endpoint to enforce Endpoint Security Configurations* toggle to *On*. For more information, see [MDE Security Configuration Management](../protect/mde-security-integration.md).
44+
4345
## Enable Microsoft Defender for Endpoint in Intune
4446

4547
The first step you take is to set up the service-to-service connection between Intune and Microsoft Defender for Endpoint. Set up requires administrative access to both the Microsoft Defender Security Center, and to Intune.
@@ -52,7 +54,7 @@ You only need to enable Microsoft Defender for Endpoint a single time per tenant
5254

5355
2. Select **Endpoint security** > **Microsoft Defender for Endpoint**, and then select **Open the Microsoft Defender for Endpoint admin console**.
5456

55-
This opens the **Microsoft 365 Defender** portal at *security.microsoft.com*, which [replaces the use of the previous portal](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide) at *securitycenter.windows.com*.
57+
This opens the **Microsoft 365 Defender** portal at *security.microsoft.com*, which [replaces the use of the previous portal](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide&preserve-view=true) at *securitycenter.windows.com*.
5658

5759
> [!TIP]
5860
> If the **Connection status** at the top of the page is already set to **Enabled**, the connection to Intune has already been made, and the admin center displays different UI than in the following screen shot. In this event, you can use the link **Open the Microsoft Defender for Endpoint admin console** to open the Microsoft Defender Security Center and use the guidance in the following step to confirm that the **Microsoft Intune connection** is set to **On**.

memdocs/intune/protect/antivirus-microsoft-defender-settings-windows-tenant-attach.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,7 @@ Learn more
327327

328328
- **Allow users to view full History results**
329329
> [!NOTE]
330-
> This is a legacy setting that only applies to versions of Windows prior to Windows 10 version 1703. User of this setting with a current operating system has no effect. This setting is scheduled for removal from this policy. For more information, see **-DisablePrivacyMode** in [Set-MpPreference](/powershell/module/defender/set-mppreference?view=windowsserver2022-ps) in the Windows PowerShell documentation.
330+
> This is a legacy setting that only applies to versions of Windows prior to Windows 10 version 1703. User of this setting with a current operating system has no effect. This setting is scheduled for removal from this policy. For more information, see **-DisablePrivacyMode** in [Set-MpPreference](/powershell/module/defender/set-mppreference?view=windowsserver2022-ps&preserve-view=true) in the Windows PowerShell documentation.
331331
332332
- **Not Configured** (*default*)
333333
- **Yes**

memdocs/intune/protect/atp-manage-vulnerabilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ Following is an example workflow for an application. This same general workflow
9494

9595
## Work with security tasks
9696

97-
Before you can work with security tasks, they must be created from within the Defender Security Center. For information on using the Microsoft Defender Security Center to create security tasks, see [Remediate vulnerabilities with threat and vulnerability management](/microsoft-365/security/defender-endpoint/tvm-remediation?view=o365-worldwide#request-remediation) in the Defender for Endpoint documentation.
97+
Before you can work with security tasks, they must be created from within the Defender Security Center. For information on using the Microsoft Defender Security Center to create security tasks, see [Remediate vulnerabilities with threat and vulnerability management](/microsoft-365/security/defender-endpoint/tvm-remediation?view=o365-worldwide&preserve-view=true#request-remediation) in the Defender for Endpoint documentation.
9898

9999
To manage security tasks:
100100

memdocs/intune/protect/checkpoint-sandblast-mobile-mobile-threat-defense-connector.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ You can configure Conditional Access policies based on Check Point Harmony Mobil
4040
4141
## Supported platforms
4242

43-
- **Android 4.1 and later**
43+
- **Android 8 and later**
4444

45-
- **iOS 8 and later**
45+
- **iOS 12 and later**
4646

4747
## Pre-requisites
4848

0 commit comments

Comments
 (0)