Merge pull request #10067 from MicrosoftDocs/main

v-stsavell · web-flow · commit 041e92b97cd5 · 2023-03-06T12:41:28.000-06:00
Publish main to live on 3/6 @ 10:30 am
diff --git a/memdocs/intune/apps/android-deployment-scenarios-app-protection-work-profiles.md b/memdocs/intune/apps/android-deployment-scenarios-app-protection-work-profiles.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/app-protection-policy-settings-android.md b/memdocs/intune/apps/app-protection-policy-settings-android.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 08/15/2022
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -156,7 +156,7 @@ By default, several settings are provided with pre-configured values and actions
 |**SafetyNet device attestation** |App protection policies support some of Google Play Protect's APIs. This setting in particular configures [Google's SafetyNet Attestation](https://developer.android.com/training/safetynet/attestation) on end user devices to validate the integrity of those devices. Specify either **Basic integrity** or **Basic integrity and certified devices**. <p>**Basic integrity** tells you about the general integrity of the device. Rooted devices, emulators, virtual devices, and devices with signs of tampering fail basic integrity. **Basic integrity & certified devices** tells you about the compatibility of the device with Google's services. Only unmodified devices that have been certified by Google can pass this check.<p>If you select **SafetyNet device attestation** as required for conditional launch, you can specify that a hardware-backed key is used as the evaluation type. The presence of a hardware-backed key as the evaluation type will indicate greater integrity of a device. Devices that do not support hardware-backed keys will be blocked by the MAM policy if they are targeted with this setting. The hardware-backed key provides a more robust root detection in response to newer types of rooting tools and methods that cannot always be reliably detected by a software only solution. Within APP, hardware attestation will be enabled by setting **Required SafetyNet evaluation type** to **Hardware-backed key** once **SafetyNet device attestation** is configured. Hardware backed attestation leverages a hardware-based component which shipped with devices installed with Android 8.1 and later. Devices that were upgraded from an older version of Android to Android 8.1 are unlikely to have the hardware-based components necessary for hardware backed attestation. While this setting should be widely supported starting with devices that shipped with Android 8.1, Microsoft strongly recommends testing devices individually before enabling this policy setting broadly.<p>**Important:** Devices that do not support this evaluation type will be blocked or wiped based on the SafetyNet device attestation action. Organizations that would like to use this functionality will need to ensure users have supported devices. For more information on Google’s recommended devices, see [Android Enterprise Recommended requirements](https://www.android.com/enterprise/recommended/requirements/).<p>*Actions* include: <br><ul><li>**Warn** - The user sees a notification if the device does not meet Google's SafetyNet Attestation scan based on the value configured. This notification can be dismissed. </li></ul><ul><li>**Block access** - The user is blocked from access if the device does not meet Google's SafetyNet Attestation scan based on the value configured. </li></ul> <ul><li>**Wipe data** - The user account that is associated with the application is wiped from the device. </li></ul> </li></ul> For commonly asked questions related to this setting, see [Frequently asked questions about MAM and app protection](mam-faq.yml). |
 |**Require threat scan on apps** |App protection policies support some of Google Play Protect's APIs. This setting in particular ensures that Google's Verify Apps scan is turned on for end user devices. If configured, the end user will be blocked from access until they turn on Google's app scanning on their Android device. *Actions* include: <br><ul><li>**Warn** - The user sees a notification if Google's Verify Apps scan on the device is not turned on. This notification can be dismissed. </li></ul><ul><li>**Block access** - The user is blocked from access if Google's Verify Apps scan on the device is not turned on. </li></ul></li></ul> Results from Google's Verify Apps scan are surfaced in the **Potentially Harmful Apps** report in the console. |
 |**Min Company Portal version** |By using the **Min Company Portal version**, you can specify a specific minimum defined version of the Company Portal that is enforced on an end user device. This conditional launch setting allows you to set values to **Block access**, **Wipe data**, and **Warn** as possible actions when each value is not met. The possible formats for this value follow the pattern *[Major].[Minor]*, *[Major].[Minor].[Build]*, or *[Major].[Minor].[Build].[Revision]*. Given that some end users may not prefer a forced update of apps on the spot, the 'warn' option may be ideal when configuring this setting. The Google Play Store does a good job of only sending the delta bytes for app updates, but this can still be a large amount of data that the user may not want to utilize if they are on data at the time of the update. Forcing an update and thereby downloading an updated app could result in unexpected data charges at the time of the update. For more information, see [Android policy settings](app-protection-policies-access-actions.md#android-policy-settings). |
-|**Max Company Portal version age (days)** |You can set a maximum number of days as the age of the Company Portal (CP) version for Android devices. This setting ensures that end users are within a certain range of CP releases (in days). The value must be between 0 and 365 days. When the setting for the devices is not met, the action for this setting is triggered. Actions include **Block access**, **Wipe data**, or **Warn**. For related information, see [Android policy settings](app-protection-policies-access-actions.md#android-policy-settings). |
+|**Max Company Portal version age (days)** |You can set a maximum number of days as the age of the Company Portal (CP) version for Android devices. This setting ensures that end users are within a certain range of CP releases (in days). The value must be between 0 and 365 days. When the setting for the devices is not met, the action for this setting is triggered. Actions include **Block access**, **Wipe data**, or **Warn**. For related information, see [Android policy settings](app-protection-policies-access-actions.md#android-policy-settings). **Note:** The age of the Company Portal build is determined by [Google Play](https://developer.android.com/reference/com/google/android/play/core/appupdate/AppUpdateInfo#clientVersionStalenessDays) on the end user device. |
 |**Max allowed device threat level** |App protection policies can take advantage of the Intune-MTD connector. Specify a maximum threat level acceptable to use this app. Threats are determined by your chosen Mobile Threat Defense (MTD) vendor app on the end user device. Specify either *Secured*, *Low*, *Medium*, or *High*. *Secured* requires no threats on the device and is the most restrictive configurable value, while *High* essentially requires an active Intune-to-MTD connection. *Actions* include: <br><ul><li>**Block access** - The user will be blocked from access if the threat level determined by your chosen Mobile Threat Defense (MTD) vendor app on the end user device doesn't meet this requirement.</li></ul> <ul><li>**Wipe data** - The user account that is associated with the application is wiped from the device.</li></ul>For more information on using this setting, see [Enable the Mobile Threat Defense connector in Intune for unenrolled devices](../protect/mtd-enable-unenrolled-devices.md). |
 |**Require device lock** |This setting determines whether the Android device has a device PIN that meets the minimum password requirement. The App protection policy can take action if the device lock doesn’t meet the minimum password requirement.<p><p>**Values** include:<br><ul><li>**Low Complexity**</li><li>**Medium Complexity**</li><li>**High Complexity**</li></ul><p>This complexity value is targeted to Android 11+. For devices operating on Android 10 and earlier, setting a complexity value of low, medium, or high will default to the expected behavior for **Low Complexity**. For more information, see Google's developer documentation [getPasswordComplexity](https://developer.android.com/reference/android/app/admin/DevicePolicyManager#getPasswordComplexity%28%29), [PASSWORD_COMPLEXITY_LOW](https://developer.android.com/reference/android/app/admin/DevicePolicyManager#PASSWORD_COMPLEXITY_LOW), [PASSWORD_COMPLEXITY_MEDIUM](https://developer.android.com/reference/android/app/admin/DevicePolicyManager#PASSWORD_COMPLEXITY_MEDIUM), and [PASSWORD_COMPLEXITY_HIGH](https://developer.android.com/reference/android/app/admin/DevicePolicyManager#PASSWORD_COMPLEXITY_HIGH).<p>**Actions** include:<br><ul><li>**Warn** - The user sees a notification if the device lock doesn’t meet the minimum password requirement. The notification can be dismissed.</li><li>**Block access** - The user will be blocked from access if the device lock doesn’t meet the minimum password requirement.</li></ul><ul><li>**Wipe data** - The user account that is associated with the application is wiped from the device if the device lock doesn’t meet the minimum password requirement.</li></ul> |
 |**Primary MTD service** |If you have configured multiple Intune-MTD connectors, specify the primary MTD vendor app that should be used on the end user device.<p><p>**Values** include:<br><ul><li>**Microsoft Defender for Endpoint** - if the MTD connector is configured, specify Microsoft Defender for Endpoint will provide the device threat level information.</li><li>**Mobile Threat Defense (Non-Microsoft)** - if the MTD connector is configured, specify the non-Microsoft MTD will provide the device threat level information.</li></ul><p>You must configure the setting “Max allowed device threat level” to use this setting. <p> There are no **Actions** for this setting.|
diff --git a/memdocs/intune/apps/configure-microsoft-launcher.md b/memdocs/intune/apps/configure-microsoft-launcher.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/data-transfer-between-apps-manage-ios.md b/memdocs/intune/apps/data-transfer-between-apps-manage-ios.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/lob-apps-android.md b/memdocs/intune/apps/lob-apps-android.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/lob-apps-windows.md b/memdocs/intune/apps/lob-apps-windows.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/quickstart-create-assign-app-policy.md b/memdocs/intune/apps/quickstart-create-assign-app-policy.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/store-apps-android.md b/memdocs/intune/apps/store-apps-android.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/store-apps-company-portal-app.md b/memdocs/intune/apps/store-apps-company-portal-app.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/store-apps-company-portal-autopilot.md b/memdocs/intune/apps/store-apps-company-portal-autopilot.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/store-apps-ios.md b/memdocs/intune/apps/store-apps-ios.md
@@ -7,7 +7,7 @@ keywords: Intune
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/tutorial-configure-slack-enterprise-grid.md b/memdocs/intune/apps/tutorial-configure-slack-enterprise-grid.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: tutorial
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/vpp-apps.md b/memdocs/intune/apps/vpp-apps.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/vpp-ebooks-ios.md b/memdocs/intune/apps/vpp-ebooks-ios.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/apps/web-app.md b/memdocs/intune/apps/web-app.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
diff --git a/memdocs/intune/developer/app-sdk-get-started.md b/memdocs/intune/developer/app-sdk-get-started.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/app-sdk-xamarin.md b/memdocs/intune/developer/app-sdk-xamarin.md
@@ -7,7 +7,7 @@ keywords: sdk, Xamarin, intune
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/app-sdk.md b/memdocs/intune/developer/app-sdk.md
@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/app-wrapper-prepare-android.md b/memdocs/intune/developer/app-wrapper-prepare-android.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/01/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/app-wrapper-prepare-ios.md b/memdocs/intune/developer/app-wrapper-prepare-ios.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/apps-lob-app-versioning.md b/memdocs/intune/developer/apps-lob-app-versioning.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/apps-prepare-mobile-application-management.md b/memdocs/intune/developer/apps-prepare-mobile-application-management.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/01/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/data-warehouse-account-move.md b/memdocs/intune/developer/data-warehouse-account-move.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/intune-data-warehouse-collections.md b/memdocs/intune/developer/intune-data-warehouse-collections.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-api-url.md b/memdocs/intune/developer/reports-api-url.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-changelog.md b/memdocs/intune/developer/reports-changelog.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 02/01/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-nav-create-intune-reports.md b/memdocs/intune/developer/reports-nav-create-intune-reports.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-nav-intune-data-warehouse.md b/memdocs/intune/developer/reports-nav-intune-data-warehouse.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-proc-create-with-odata.md b/memdocs/intune/developer/reports-proc-create-with-odata.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-application.md b/memdocs/intune/developer/reports-ref-application.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 02/01/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-data-model.md b/memdocs/intune/developer/reports-ref-data-model.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-date.md b/memdocs/intune/developer/reports-ref-date.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-devices.md b/memdocs/intune/developer/reports-ref-devices.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-intunemanagementextension.md b/memdocs/intune/developer/reports-ref-intunemanagementextension.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-mobile-app-management.md b/memdocs/intune/developer/reports-ref-mobile-app-management.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-policy.md b/memdocs/intune/developer/reports-ref-policy.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-user-device.md b/memdocs/intune/developer/reports-ref-user-device.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-user-timeline.md b/memdocs/intune/developer/reports-ref-user-timeline.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/developer/reports-ref-user.md b/memdocs/intune/developer/reports-ref-user.md
@@ -7,7 +7,7 @@ keywords: Intune Data Warehouse
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
diff --git a/memdocs/intune/fundamentals/guided-scenarios-edge.md b/memdocs/intune/fundamentals/guided-scenarios-edge.md
@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
diff --git a/memdocs/intune/fundamentals/guided-scenarios-office-mobile.md b/memdocs/intune/fundamentals/guided-scenarios-office-mobile.md
@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
diff --git a/memdocs/intune/fundamentals/policy-sets.md b/memdocs/intune/fundamentals/policy-sets.md
@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
diff --git a/memdocs/intune/fundamentals/reports-export-graph-apis.md b/memdocs/intune/fundamentals/reports-export-graph-apis.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 03/06/2023
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
diff --git a/memdocs/intune/fundamentals/service-now-integration.md b/memdocs/intune/fundamentals/service-now-integration.md
diff --git a/memdocs/intune/fundamentals/whats-new.md b/memdocs/intune/fundamentals/whats-new.md
diff --git a/memdocs/intune/protect/app-modern-authentication-block.md b/memdocs/intune/protect/app-modern-authentication-block.md
