Merge pull request #16116 from MicrosoftDocs/main

Publish main to live, Wednesday 3:30PM PDT, 09/11

memdocs/intune/apps/apps-add-enterprise-app.md

@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 01/08/2024
+ms.date: 09/11/2024
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -208,7 +208,7 @@ The **Rules format** provides the following options:
    The Intune agent checks the results from the script. It reads the values written by the script to the STDOUT stream, the standard error (STDERR) stream, and the exit code. If the script exits with a nonzero value, the script fails and the application detection status isn't installed. If the exit code is zero and STDOUT has data, the application detection status is installed. 
 
    > [!NOTE]
-   > We recommend encoding your script as UTF-8. When the script exits with the value of **0**, the script execution was successful. The second output channel indicates that the app was detected. STDOUT data indicates that the app was found on the client. We don't look for a particular string from STDOUT.
+   > We recommend encoding your script as UTF-8 BOM. When the script exits with the value of **0**, the script execution was successful. The second output channel indicates that the app was detected. STDOUT data indicates that the app was found on the client. We don't look for a particular string from STDOUT.
 
 When you add the app to Intune, the version of your Windows catalog app (Win32) is displayed in the Microsoft Intune admin center. The app version is provided in the **All apps** list, where you can filter by Windows catalog app (Win32) and select the optional **version** column. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps** > **All apps** > **Columns** > **Version** to display the app version in the app list.
 

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

@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 08/08/2024
+ms.date: 09/11/2024
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -247,7 +247,7 @@ On the **Detection rules** pane, configure the rules to detect the presence of t
    The Intune agent checks the results from the script. It reads the values written by the script to the STDOUT stream, the standard error (STDERR) stream, and the exit code. If the script exits with a nonzero value, the script fails and the application detection status isn't installed. If the exit code is zero and STDOUT has data, the application detection status is installed. 
 
    > [!NOTE]
-   > We recommend encoding your script as UTF-8. When the script exits with the value of **0**, the script execution was successful. The second output channel indicates that the app was detected. STDOUT data indicates that the app was found on the client. We don't look for a particular string from STDOUT.
+   > We recommend encoding your script as UTF-8 BOM. When the script exits with the value of **0**, the script execution was successful. The second output channel indicates that the app was detected. STDOUT data indicates that the app was found on the client. We don't look for a particular string from STDOUT.
 
 The version of your Win32 app is displayed in the Microsoft Intune admin center. The app version is provided in the **All apps** list, where you can filter by Win32 apps and select the optional **version** column. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps** > **All apps** > **Columns** > **Version** to display the app version in the app list.
 

memdocs/intune/includes/app-protection-framework-level3.md

@@ -53,5 +53,5 @@ Level 3 is the data protection configuration recommended as a standard for organ
 | Device conditions  |       Max   OS version  |          *Format: Major.Minor.Build <br>Example:   15.0* / Block access |          iOS/iPadOS        | Microsoft recommends configuring   the maximum iOS/iPadOS major version to ensure beta or unsupported versions of the operating system aren't used. See   [Apple security updates](https://support.apple.com/en-us/HT201222) for Apple's latest recommendations |
 | Device conditions  |       Max   OS version  |          *Format: Major.Minor<br>   Example: 22631.* / Block access   |          Windows        | Microsoft recommends configuring   the maximum Windows major version to ensure beta or unsupported versions of the operating system aren't used. |
 | Device conditions  |       Samsung Knox device attestation  | Wipe data |          Android        | Microsoft recommends configuring the **Samsung Knox device attestation** setting to **Wipe data** to ensure the org data is removed if the device doesn't meet Samsung's Knox hardware-based verification of device health.  This setting verifies all Intune MAM client responses to the Intune service were sent from a healthy device.  <p> This setting will apply to all devices targeted.  To apply this setting only to Samsung devices, you can use "Managed apps" assignment filters.  For more information on assignment filters, see [Use filters when assigning your apps, policies, and profiles in Microsoft Intune](/mem/intune/fundamentals/filters).|
-| App conditions | Offline grace period | 30 / Wipe data (days) | iOS/iPadOS, Android, Windows | |
+| App conditions | Offline grace period | 30 / Block access (days) | iOS/iPadOS, Android, Windows | |
 

memdocs/intune/remote-actions/collect-diagnostics.md

@@ -93,12 +93,12 @@ The *Collect diagnostics* remote action is supported for:
 - Devices that are online and able to communicate with the service during diagnostics
 
 > [!NOTE]
-> For diagnostics to be able to upload successfully from the client, make sure that the following URLs are not blocked on the network:
-> `lgmsapeweu.blob.core.windows.net`
-> `lgmsapewus2.blob.core.windows.net`
-> `lgmsapesea.blob.core.windows.net`
-> `lgmsapeaus.blob.core.windows.net`
-> `lgmsapeind.blob.core.windows.net`
+> For diagnostics to be able to upload successfully from the client, make sure that the URL for your region is not blocked on the network:
+> - `Europe - lgmsapeweu.blob.core.windows.net`
+> - `Americas - lgmsapewus2.blob.core.windows.net`
+> - `East Asia - lgmsapesea.blob.core.windows.net`
+> - `Australia - lgmsapeaus.blob.core.windows.net`
+> - `India - lgmsapeind.blob.core.windows.net`
 
 
 ### Collect diagnostics