Merge pull request #16372 from MicrosoftDocs/main

Publish main to live, Tuesday 3:30PM PDT, 10/15

autopilot/device-preparation/whats-new.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 manager: aaroncz
 ms.reviewer: jubaptis
-ms.date: 10/09/2024
+ms.date: 10/15/2024
 ms.collection:
   - M365-modern-desktop
   - tier2
@@ -37,11 +37,11 @@ Date added: *October 9, 2024*
 
 Admins can now download diagnostics logs for failed Autopilot device preparation deployments directly from the **Windows Autopilot device preparation deployment status** report. Logs are available for download in the **Device deployment details** when you select a failed deployment under the **Device** tab. Logs are automatically collected when an error occurs during deployment.
 
-## Windows Autopilot Device Preparation Support in Azure China 21Vianet
+## Windows Autopilot Device Preparation Support in Intune operated by 21Vianet in China
 
 Date added: *September 18, 2024*
 
-As part of the 2409 Intune release, we're announcing support for Windows Autopilot Device Preparation policy in the [Azure China 21Vianet](/mem/intune/fundamentals/china) cloud. Customers with tenants located in China can now provision devices and manage through Microsoft Intune. For an overview, see [Overview of Windows Autopilot device preparation](overview.md). For a tutorial on how to set up Windows Autopilot device preparation, see [Windows Autopilot device preparation scenarios](tutorial/scenarios.md).
+As part of the 2409 Intune release, we're announcing support for Windows Autopilot Device Preparation policy in [Intune operated by 21Vianet in China](/mem/intune/fundamentals/china) cloud. Customers with tenants located in China can now provision devices and manage through Microsoft Intune. For an overview, see [Overview of Windows Autopilot device preparation](overview.md). For a tutorial on how to set up Windows Autopilot device preparation, see [Windows Autopilot device preparation scenarios](tutorial/scenarios.md).
 
 <!-- MAXADO-9313795 / INADO-28687730 -->
 

memdocs/intune/fundamentals/android-os-project-supported-devices.md

@@ -7,7 +7,7 @@ keywords:
 author: Smritib17
 ms.author: smbhardwaj
 manager: dougeby
-ms.date: 09/23/2024
+ms.date: 10/15/2024
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -56,3 +56,5 @@ Before setting up Microsoft Intune for Android Open Source Project devices, ensu
 | Realwear| Navigator 500      | 1.1                | AR/VR Headset  |                    |
 | Lenovo| ThinkReality VRX     | VRX_user_S766001_2310192349_kona   | AR/VR Headset  |                   |
 | DigiLens Inc.| DigiLens ARGO    | DigiOS 2068 (B1.0001.2068)            | AR/VR Headset  |                    |
+| Vuzix     | M400   | M-Series Version 3.0.2    | AR/VR Headset  |                    |
+| Vuzix     | M4000   | M-Series Version 3.0.2   | AR/VR Headset  |                    |

windows-365/enterprise/whats-new.md

@@ -58,6 +58,15 @@ For more information about public preview items, see [Public preview in Windows
 <!-- ########################## -->
 ## Week of October 14, 2024
 
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Device security
+
+#### New Windows 365 IP subnet for RDP connectivity<!--53404845-->
+
+Core TCP-based RDP traffic for Cloud PC connections uses the *.wvd.microsoft.com wildcard fully qualified domain name (FQDN). The FQDN remains unchanged, but the underlying IP addresses associated with it will shortly be changed to a single subnet. This will simplify optimization of this traffic and reduce the need for future change management.
+
+For more information, see [Plan for change: New Windows 365 IP Subnet for RDP Connectivity](https://iridias.microsoft.com/messagecenter?id=894574) Message Center post.
+
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->
 ### Device management