Merge pull request #7146 from MicrosoftDocs/revert-7051-revert-7022-erikre-rel2203-13155022

erikre-OOB2203-13155022a

Author: PRMerger12

memdocs/intune/apps/lob-apps-macos-dmg.md

@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 02/17/2022
+ms.date: 03/14/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -96,6 +96,9 @@ You can use detection rules to choose how an app installation is detected on a m
 
 **Ignore app version**: Select **Yes** to install the app if the app is not already installed on the device. This will only look for the presence of the app bundle ID. For apps that have an auto-update mechanism, select **Yes**. Select **No** to install the app when it is not already installed on the device, or if the deploying app's version number does not match the version that's already installed on the device.
 
+> [!NOTE]
+> To **Uninstall** group assignments, consider the **Ignore app version** setting. When **Ignore app version** is set to **No**, the app bundle ID and version number must match to remove the app. When **Ignore app version** is set to **Yes**, only the app bundle ID must match to remove the app.
+
 **Included apps**: Provide the apps that are contained in the uploaded file. Included app bundle IDs and build numbers are used for detecting and monitoring app installation status of the uploaded file. Included apps list should only contain the application(s) installed by the uploaded file in **Applications** folder on Macs. Any other type of file that is not an application or an application that is not installed to **Applications** folder should be excluded from the **Included apps** list. If **Included apps** list contains files that are not applications or if all the listed apps are not installed, app installation status does not report success.
 
 > [!NOTE]
@@ -107,9 +110,9 @@ You can use detection rules to choose how an app installation is detected on a m
 > 
 >   Then, run the following:
 > 
->   ```defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleVersion```
+>   ```defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleShortVersionString```
 >
-> - Alternatively, the `CFBundleIdentifier` and `CFBundleVersion` can be found under the ```<app_name>.app/Contents/Info.plist``` file of a mounted DMG file on a Mac.
+> - Alternatively, the `CFBundleIdentifier` and `CFBundleShortVersionString` can be found under the ```<app_name>.app/Contents/Info.plist``` file of a mounted DMG file on a Mac.
 
 ## Step 4 – Select scope tags (optional)
 
@@ -119,7 +122,14 @@ You can use scope tags to determine who can see client app information in Intune
 
 ## Step 5 - Assignments
 
-1. Select the **Required group assignments** for the app. For more information, see [Add groups to organize users and devices](../fundamentals/groups-add.md) and [Assign apps to groups with Microsoft Intune](../apps/apps-deploy.md).
+You can select the **Required** or **Uninstall** group assignments for the app. For more information, see [Add groups to organize users and devices](../fundamentals/groups-add.md) and [Assign apps to groups with Microsoft Intune](../apps/apps-deploy.md).
+
+> [!NOTE]
+> A macOS app deployed using Intune agent will not automatically be removed from the device when the device is retired. The app and data it contains will remain on the device. It is recommended that the app is removed prior to retiring the device.
+
+1. For the specific app, select an assignment type:
+  - **Required**: The app is installed to `/Applications/` directory on devices in the selected groups.
+  - **Uninstall**: The app is uninstalled from `/Applications/` directory on devices in the selected groups.
 2. Click **Next** to display the **Review + create** page.
 
 ## Step 6 – Review + create
@@ -141,16 +151,16 @@ The app you have created appears in the apps list where you can assign it to the
 
 ## Known issues
 
-- **"Uninstall" and "Available for enrolled devices" assignment types are not available**: only "Required" assignment type is currently supported. 
-- **"Collect logs" action is unavailable during preview**: log collection feature on macOS apps (DMG) is unavailable during preview. 
-- **Errors might not show details during preview**: some errors you encounter may only show "Failed" status with an error code and not provide additional details.
+- **"Available for enrolled devices" assignment type is not available**: Only **Required** and **Uninstall** assignment types are currently supported. 
+- **"Collect logs" action is unavailable during preview**: Log collection feature on macOS apps (DMG) is unavailable during preview. 
+- **Errors might not show details during preview**: Some errors you encounter may only show "Failed" status with an error code and not provide additional details.
 - **App upgrade fails to install**: Updating an app that has the same bundle ID as an existing app in Applications folder fails to install. 
 - **DMG apps report once after deployment**: Assigned DMG apps report back on initial deployment only. These apps will not report back again during preview.
 - **Some DMG apps may display a warning to end-users on launch**: Apps downloaded from the internet and deployed using Intune may show a warning to end-users when launched. End-users can click "Open" on the dialog to continue opening the app.
 
   ![DMG apps may display a warning to end-users on launch](./media/lob-apps-macos-dmg/lob-apps-macos-dmg-01.png)
 
-- **Some app icons may not display immediately after installation**: some app icons may take some time after installation to start displaying on the installed device.
+- **Some app icons may not display immediately after installation**: Some app icons may take some time after installation to start displaying on the installed device.
 - **Monitoring reports only show error code**: failed app installations only show an error code in "device status" monitoring reports. To show error details, refresh the browser window or refer to the table in the Troubleshooting section.