Merging changes synced from https://github.com/MicrosoftDocs/memdocs-pr (branch live)

Author: Learn Build Service GitHub App

memdocs/intune/developer/app-sdk-android-phase5.md

@@ -509,6 +509,11 @@ Calling `protectForOID` with empty string for the identity parameter will tag th
 This operation will remove encryption from the file/directory if it was previously encrypted.
 When a selective wipe command is issued, the file/directory won't be deleted.
 
+> [!WARNING]
+> It is important to ensure that only files belonging to a particular identity become protected
+> with that identity. Otherwise, other identities may experience data loss when the owning identity
+> signs out, as files will be wiped and encryption key access will be lost.
+
 #### Displaying Protected File Content
 
 It is equally critical to have the correct identity set when file content is being *displayed* to prevent unauthorized users from viewing managed data.
@@ -597,6 +602,17 @@ An app can prevent these buffers becoming unreadable by calling `MAMDataProtecti
 It is also safe to call `protectForOID` during this notification, if you wish to preserve identity information.
 Encryption is guaranteed to be disabled during the notification and calling `protectForOID` in the handler won't encrypt data buffers.
 
+> [!WARNING]
+> Encryption operations should be avoided early in the app process. The SDK will perform encryption
+> initialization asynchronously as early as possible after app startup. However, if an app makes
+> an encryption request in app startup, it may be blocked until encryption initialization is
+> complete.
+
+> [!NOTE]
+> The Intune App SDK encryption API should be used only to encrypt data as required by Intune
+> policy. No protection will be applied to accounts that are not targeted with encryption policy
+> enabled, so it cannot be used as general-purpose encryption library.
+
 ### Content Providers
 
 A multi-identity app must also protect data shared through `ContentProvider`s to prevent inappropriately sharing managed content.

memdocs/intune/includes/intune-notices.md

@@ -4,14 +4,34 @@ description: include file
 author: dougeby  
 ms.service: microsoft-intune
 ms.topic: include
-ms.date: 03/13/2024
+ms.date: 10/30/2024
 ms.author: dougeby
 manager: dougeby
 ms.custom: include file
 ---
 
 These notices provide important information that can help you prepare for future Intune changes and features.
 
+### Update to the latest Intune App SDK and Intune App Wrapper for Android 15 support
+We've recently released new versions of the Intune App SDK and Intune App Wrapping Tool for Android to support Android 15. We recommend upgrading your app to the latest SDK or wrapper versions to ensure applications stay secure and run smoothly.
+ 
+#### How does this affect you or your users?
+
+If you have applications using the Intune App SDK or Intune App Wrapping Tool for Android, it's recommended that you update your app to the latest version to support Android 15.
+ 
+#### How can you prepare?
+
+If you choose to build apps targeting Android API 35, you'll need to adopt the new version of the Intune App SDK for Android (v11.0.0). If you’ve wrapped your app and are targeting API 34 you'll need to use the new version of the App wrapper (v1.0.4549.6).
+
+> [!NOTE]
+> As a reminder, while apps must update to the latest SDK if targeting Android 15, apps do not need to update the SDK to simply run on Android 15.
+
+You should also plan to update your documentation or developer guidance if applicable to include this change in support for the SDK.
+
+Here are the public repositories:
+- [Intune App SDK for Android](https://github.com/microsoftconnect/ms-intune-app-sdk-android)
+- [Intune App Wrapping Tool for Android](https://github.com/microsoftconnect/intune-app-wrapping-tool-android)
+
 ### Take Action: Update to the latest Intune App SDK for iOS and Intune App Wrapping Tool for iOS
 
 To support the upcoming release of iOS/iPadOS 18.1, update to the latest versions of the Intune App SDK and the Intune App Wrapping Tool to ensure applications stay secure and run smoothly. **Important:** If you don't update to the latest versions, some app protection policies may not apply to your app in certain scenarios. Review the following GitHub announcements for more details on the specific impact:

windows-365/enterprise/introduction-windows-365-government.md

@@ -45,7 +45,7 @@ For more information about Cloud PCs and Windows 365, see [What is Windows 365?]
 
 ## Features not yet supported Windows 365 Government
 
-The following features aren't yet supported for Windows 365 GCC or GCC High. 
+The following features aren't yet supported for Windows 365 GCC or GCC High.
 
 - Unified dashboard
 - Windows 365 Security baseline
@@ -68,6 +68,7 @@ The following features aren't yet supported for Windows 365 GCC or GCC High.
 - [Support for Omnissa Horizon clients and the Blast protocol](set-up-omnissa-horizon.md)
 - [Microsoft Purview Customer Key](purview-customer-key.md)
 - [HP Anyware for Windows 365](hp-anyware-set-up.md)
+- Bulk Troubleshoot action
 
 ## Next steps
 

windows-365/enterprise/whats-new.md

@@ -84,12 +84,9 @@ Azure network connections that meet either of the following conditions for more
 <!-- ########################## -->
 ## Week of October 21, 2024
 
-<!-- vvvvvvvvvvvvvvvvvvvvvv -->
-### Partners
-
-#### Use Citrix HDX Plus with Windows 365 Frontline<!--54445358-->
+#### Windows 365 support for AVC mixed mode when MMR isn't enabled (preview)<!--50205898-->
 
-You can now use Citrix HDX Plus with Windows 365 Frontline Cloud PCs.
+AVC Mixed Mode is now available in the default graphics profile. When MMR isn't enabled, AVC/h.264 is used to encode detected image content instead of the RemoteFX image encoder. This improves performance when encoding images relative to bitrate and framerate in network-constrained scenarios.
 
 <!-- ########################## -->
 ## Week of October 14, 2024