Merge pull request #16495 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/memdocs (branch main)

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

@@ -96,7 +96,7 @@ Microsoft hosts the applications in Microsoft storage accessible through `*.mana
 
 ### Is Microsoft providing security around any of the content provided in the Enterprise App Catalog?
 
-No. Microsoft makes no guarantee, express or implied, with respect to the security and compliance of the applications provided in the Enterprise App Catalog.
+Microsoft does not assert compliance or authorizations for apps distributed via Intune. Customers are responsible for ensuring that apps meet their requirements.
 
 ### What app installer types are in the Enterprise App Catalog?
 
@@ -110,6 +110,10 @@ At this time, Intune provides no running application detection.
 
 No SLA is currently available.
 
+### How many applications are in the catalog?
+
+The catalog has over 400+ available applications in the Enterprise App Catalog. More apps are available on an ongoing basis.
+
 ### How can working with the applications in Enterprise App Catalog be automated?
 
 Graph API is planned to be available soon.

memdocs/intune/apps/mamedge-1-mamca.md

@@ -102,7 +102,7 @@ In the previous steps, you implemented conditional access as a required app prot
     
     :::image type="content" alt-text="Device Platform - Conditional Access policy - Microsoft Intune admin center." source="./media/securing-data-edge-for-business/securing-data-edge-for-business59.png" lightbox="./media/securing-data-edge-for-business/securing-data-edge-for-business59.png":::
 
-7. Select **Grant** and select **Require device to be market as compliant.** This will provide access through desktop apps only for enrolled and compliant devices.
+7. Select **Grant** and select **Require device to be marked as compliant.** This will provide access through desktop apps only for enrolled and compliant devices.
 
     :::image type="content" alt-text="Grant - Conditional Access policy - Microsoft Intune admin center." source="./media/securing-data-edge-for-business/securing-data-edge-for-business60.png" lightbox="./media/securing-data-edge-for-business/securing-data-edge-for-business60.png":::
 

memdocs/intune/fundamentals/reports-export-graph-available-reports.md

@@ -860,6 +860,7 @@ The following table contains the possible output when calling the `AppInvAggrega
 | ApplicationShortVersion  |
 | ApplicationVersion  |
 | DeviceCount  |
+| Platform  |
 
 There are no filters for this report.
 
@@ -884,7 +885,19 @@ The following table contains the possible output when calling the `AppInvRawData
 |     EmailAddress  |
 |     UserName  |
 
-There are no filters for this report.
+You can filter the `AppInvRawData` report using the `eq` comparison operator on the following properties: 
+- ApplicationName
+- ApplicationPublisher
+- ApplicationShortVersion
+- ApplicationVersion
+- DeviceId
+- DeviceName
+- OSDescription
+- OSVersion
+- Platform
+- UserId
+- EmailAddress
+- UserName
 
 ## ChromeOSDevices report
 
@@ -941,7 +954,7 @@ You can check whether the ChromeOSDevices report has completed by using the Micr
 Use the output from the above call to determine the status of the ChromeOSDevices report. An example call will look similar to the following:
 `https://graph.microsoft.com/beta/deviceManagement/reports/exportJobs('ChromeOSDevices_1223a321-4bcd-5432-efg1-0hi9876h1234') `
 
-You can continue to run your call to check the status of the report. When the report shows a status of `complete`, you're report is ready to be downloaded.
+You can continue to run your call to check the status of the report. When the report shows a status of `complete`, your report is ready to be downloaded.
 
 ### Download the completed ChromeOSDevices report