Skip to content

Commit 9bcff9b

Browse files
authored
Merge pull request #6551 from MicrosoftDocs/main
1/14/2021 PM Publish
2 parents 576fb94 + f0fdda2 commit 9bcff9b

5 files changed

Lines changed: 23 additions & 7 deletions

File tree

memdocs/configmgr/protect/deploy-use/endpoint-protection-site-role.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,9 @@ The endpoint protection point requires the following Windows Server features:
3131

3232
- .NET Framework 3.5
3333

34-
- Windows Defender features (Windows Server 2016 or later)<!-- SCCMDocs#2120 -->
34+
- Windows Defender feature (Windows Server 2016)<!-- SCCMDocs#2120 -->
35+
- Windows Defender Antivirus feature (Windows Server 2019)
36+
- Microsoft Defender Antivirus feature (Windows Server 2022 or later)
3537

3638
For more information, see [Site and site system prerequisites](../../core/plan-design/configs/site-and-site-system-prerequisites.md).
3739

memdocs/configmgr/sum/deploy-use/office-365-dashboard.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,9 @@ After verifying you have the [prerequisites](#prerequisites), use the following
214214

215215
Generate a pilot recommendation from a limiting collection at the click of a button. As soon as the action is launched, a background task starts calculating your pilot collection. Your limiting collection must contain at least one device with an Office version that isn't Office 365 Apps.
216216

217+
> [!NOTE]
218+
> The **All Desktop and Server Clients (Office Pilot)** collection is managed by Configuration Manager. Manual changes aren't supported. If you delete or edit this collection, the pilot deployment won't work. <!--12610779-->
219+
217220
### Recommended pilot devices
218221

219222
**Recommended pilot devices** are a minimal set of devices representing all installed add-ins across the limiting collection you used when generating the pilot. Drill down to get a list of these devices. Then use the details to exclude any devices from the pilot if needed. If all of your add-ins are already on Microsoft 365 Apps devices, then devices with those add-ins won't be included in the calculation. This also means it's possible that you won't get any results in your pilot collection since all of your add-ins have been seen on devices where Microsoft 365 Apps is installed.

memdocs/configmgr/sum/get-started/software-update-point-ssl.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Tutorial - Configure Windows Server Update Services (WSUS) servers
55
author: mestew
66
ms.author: mstewart
77
manager: dougeby
8-
ms.date: 04/05/2021
8+
ms.date: 01/14/2022
99
ms.topic: tutorial
1010
ms.prod: configuration-manager
1111
ms.technology: configmgr-sum
@@ -289,11 +289,13 @@ Starting in Configuration Manager 2103, you can further increase the security of
289289
- Configuration Manager version 2103
290290
- Ensure your WSUS servers and software update points are configured to use TLS/SSL
291291
- Add the certificates for your WSUS servers to the new `WindowsServerUpdateServices` certificate store on your clients
292+
- When using certificate pinning with a cloud management gateway (CMG), the `WindowsServerUpdateServices` store needs the CMG certificate. If clients switch from internet to VPN both the CMG and WSUS server certificates are needed in the `WindowsServerUpdateServices` store. <!--12590425-->
292293

293294
> [!Note]
294295
> Software update scans for devices will continue to run successfully using the default value of **Yes** for the **Enforce TLS certificate pinning for Windows Update client for detecting updates** client setting. This includes scans over both HTTP and HTTPS. The certificate pinning doesn't take effect until a certificate is in the client's `WindowsServerUpdateServices` store and the WSUS server is configured to use TLS/SSL.
295296
296297

298+
297299
### Enable or disable TLS certificate pinning for devices scanning HTTPS-configured WSUS servers
298300

299301
1. From the Configuration Manager console, go to **Administration** > **Client Settings**.
@@ -306,4 +308,4 @@ Starting in Configuration Manager 2103, you can further increase the security of
306308

307309
## Next steps
308310

309-
[Deploy software updates](../deploy-use/deploy-software-updates.md)
311+
[Deploy software updates](../deploy-use/deploy-software-updates.md)

memdocs/intune/apps/apps-add-office365.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
author: Erikre
99
ms.author: erikre
1010
manager: dougeby
11-
ms.date: 12/16/2021
11+
ms.date: 01/14/2021
1212
ms.topic: how-to
1313
ms.service: microsoft-intune
1414
ms.subservice: apps
@@ -47,6 +47,8 @@ Before you can assign, monitor, configure, or protect apps, you must add them to
4747

4848
> [!IMPORTANT]
4949
> If there are .msi Office apps on the end-user device, you must use the **Remove MSI** feature to safely uninstall these apps. Otherwise, the Intune delivered Microsoft 365 apps will fail to install.
50+
>
51+
> Multiple required or available app assignments are not additive. A later app assignment will overwrite pre-existing installed app assignments.
5052
5153
- Devices to which you deploy these apps must be running the Windows 10 Creators Update or later.
5254
- Intune supports adding Office apps from the Microsoft 365 Apps suite only.

memdocs/intune/fundamentals/monitor-audit-logs.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
ms.author: dougeby
88
author: dougeby
99
manager: dougeby
10-
ms.date: 02/04/2021
10+
ms.date: 01/14/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: fundamentals
@@ -56,6 +56,8 @@ You can review audit logs in the monitoring group for each Intune workload:
5656
4. Select **Apply**.
5757
5. Select an item in the list to see the activity details.
5858

59+
For related information about audit logs, see [Addition information](../fundamentals/monitor-audit-logs.md#additional-information).
60+
5961
## Route logs to Azure Monitor
6062

6163
Audit logs and operational logs can also be routed to Azure Monitor. In **Tenant administration** > **Audit logs**, select **Export**:
@@ -76,6 +78,11 @@ For details on using the graph API to get up to one year of audit events, see [L
7678

7779
## Next steps
7880

79-
[Send log data to storage, event hubs, or log analytics](review-logs-using-azure-monitor.md).
81+
- [Send log data to storage, event hubs, or log analytics](review-logs-using-azure-monitor.md)
82+
- [Review client app protection logs](../apps/app-protection-policy-settings-log.md)
83+
84+
## Additional information
8085

81-
[Review client app protection logs](../apps/app-protection-policy-settings-log.md).
86+
- [Data storage and processing in Intune](../protect/privacy-data-store-process.md)
87+
- [Use audit logs throughout Intune](../fundamentals/review-logs-using-azure-monitor.md#use-audit-logs-throughout-intune)
88+
- [Audit, export, or delete personal data in Intune](../protect/privacy-data-audit-export-delete.md)

0 commit comments

Comments
 (0)