Merge pull request #16724 from MicrosoftDocs/main

Published main to live, Thursday 10:30 AM PST, 11/21

memdocs/intune/configuration/kernel-extensions-settings-macos.md

@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 04/15/2024
+ms.date: 09/23/2024
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -28,6 +28,11 @@ ms.collection:
 
 # macOS device settings to configure and use kernel and system extensions in Intune
 
+> [!IMPORTANT]
+> This template is deprecated in the August 2024 service release (2408). Existing policies continue to work. But, you can't create new policies using this template.
+>
+> Instead, use the settings catalog to create new policies that configure the System Extension payload. To learn more about the settings catalog, go to the [macOS settings catalog](settings-catalog.md).
+
 > [!NOTE]
 >
 > - [!INCLUDE [not-all-settings-are-documented](../includes/not-all-settings-are-documented.md)]

memdocs/intune/fundamentals/whats-new.md

@@ -159,6 +159,20 @@ The following settings have been deprecated by Apple and will be marked as depre
 
 ### Device management
 
+#### Windows 365 Link is now available in public preview<!-- 29267349 -->
+
+Windows 365 Link is the first Cloud PC device built by Microsoft to connect securely to Windows 365 in seconds, providing a responsive, high-fidelity Windows desktop experience in the Microsoft Cloud.
+
+Windows 365 Link runs a small Windows based OS called Windows CPC, and shows up in Intune alongside other managed Windows devices and Cloud PCs.  
+
+Also, Device actions, such as **Wipe**, **Restart**, and **Collect diagnostics** work similarly to other Windows devices.  As the OS is purpose built to directly connect to Windows 365, this results in only a fraction of Windows configuration policies being applicable, minimizing decision points.
+
+The process to configure and apply those applicable policies is simple and familiar because the process is the same as your other Windows devices.  Secondly, Windows 365 Link has no ability to store data locally, no local apps, no local admin users, and automatically keeps itself up to date.  
+
+This means several Intune features are not applicable including application and update management, along with scripts and remediations.
+
+Windows 365 Link is now available in public preview. For more information, see [Windows 365 Link—the first Cloud PC device for Windows 365.](https://aka.ms/Windows365LinkPublicPreview)
+
 #### Store macOS certificates in user keychain<!-- 7824255 -->  
 
 A new *deployment channel* setting in Microsoft Intune enables you to store macOS authentication certificates in the user keychain. This enhancement strengthens system security and improves the user experience by reducing certificate prompts. Prior to this change, Microsoft Intune automatically stored user and device certificates in the system keychain. The deployment channel setting is available in SCEP and PKCS certificate profiles for macOS, and in VPN, Wi-Fi, and wired network settings configuration profiles for macOS. For more information about the profiles and their new setting, see:  

windows-365/enterprise/connection-errors.md

@@ -122,6 +122,14 @@ Some other possible causes for Cloud PC connection failures include:
 
 **Possible solution**: Remote Credential Guard requires connectivity to the on-premises Active Directory Domain Controller on the client PC used to access the Cloud PC. This connection is only possible using a VPN solution. Using a KDC proxy isn't currently available for Windows 365.
 
+### Azure WireServer may be blocked
+
+Windows 365 Cloud PCs require access to Azure communication channels.
+
+Make sure that IP address 168.63.129.16 is reachable through any security software installed on the Cloud PC or gateway devices used in the vNET connected to your ANC.
+
+For more informationk, see [What is IP Address 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16).
+
 ## Other troubleshooting steps
 
 ### Move the Cloud PC to a new organizational unit (OU) with no group policies

windows-365/enterprise/whats-new.md

@@ -255,7 +255,7 @@ Uni-directional clipboard support for Cloud PCs has moved out of preview and is
 
 To help secure your Windows 365 environment, the inbound port 3389 is now closed by default.
 
-#### Windows 365 support for FAC mixed mode when MMR isn't enabled (preview)<!--50205898-->
+#### Windows 365 support for AVC mixed mode when MMR isn't enabled (preview)<!--50205898-->
 
 Windows 365 now supports AVC mixed mode when MMR is not enabled.