diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 00000000000..761368eb60e
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,41 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Mark stale issues and pull requests
+
+permissions:
+  issues: write
+  pull-requests: write
+  
+on:
+  schedule:
+  - cron: '0 */6 * * *'
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+  
+    steps:
+    - uses: actions/stale@v5
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        days-before-pr-stale: 120
+        days-before-pr-close: 130
+        stale-pr-label: 'inactive'
+        close-pr-label: 'auto-close'
+        exempt-pr-label: 'keep-open'
+        stale-pr-message: > 
+           This pull request has been inactive for 120 days. If you are finished with your changes, resolve any merge conflicts and/or validation warnings, and add a **#sign-off** comment. For instructions, see the [MSec Docs Self-Serve Playbook](https://aka.ms/MSecDocsSelfServePlaybook).
+           <br/>
+           <br/>If this PR is inactive for 10 more days it will be closed automatically. Thank you!
+           <br/>
+           <br/>If you have a question, post on the MSEC Documentation Excellence Program [Ask an Admin](https://teams.microsoft.com/l/channel/19%3A0cdb9988d02e4f78bef37d571686ec5b%40thread.tacv2/Ask%20an%20Admin?groupId=8b6faa31-5d02-4e94-90eb-f1944d5c40fd&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) Teams channel.      
+        close-pr-message: >
+           <br/>This pull request has been inactive for 130 days. At this time we're closing the PR.
+           <br/>
+           <br/>If you decide to continue working on your changes, you can reopen the PR and continue working. Thank you!
+           <br/>
+           <br/>If you have a question, post on the MSEC Documentation Excellence Program [Ask an Admin](https://teams.microsoft.com/l/channel/19%3A0cdb9988d02e4f78bef37d571686ec5b%40thread.tacv2/Ask%20an%20Admin?groupId=8b6faa31-5d02-4e94-90eb-f1944d5c40fd&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) Teams channel.
\ No newline at end of file
diff --git a/intune/device-management/actions/sync.md b/intune/device-management/actions/sync.md
index 694622f5ce7..1e05e3d0670 100644
--- a/intune/device-management/actions/sync.md
+++ b/intune/device-management/actions/sync.md
@@ -71,7 +71,25 @@ After selecting **Sync**, Intune initiates an on-demand synchronization across m
 You can track the progress of the sync action by selecting the **Device sync status** tab in the device overview pane.
 
 >[!NOTE]
-> The described sync behavior, including the **Device sync status** tab, applies only to Windows devices. To see the new device sync improvements, ensure that the 'Preview new device view' toggle is turned ON. This is at the top right of the Intune admin console screen.
+> The described sync behavior, including the **Device sync status** tab, applies only to Windows and iOS/iPadOS devices. To see the new device sync improvements, ensure that the 'Preview new device view' toggle is turned ON. This is at the top right of the Intune admin console screen.
+
+::: zone-end
+
+::: zone pivot="ios"
+
+## Sync behavior on iOS/iPadOS
+
+After selecting **Sync**, Intune initiates an on-demand synchronization across multiple workloads to help ensure the device reflects the latest admin intent as quickly as possible. This process includes, but isn't limited to:
+
+- Configuration policy processing
+- App detection and deployment state updates
+- Script and remediation processing
+- Other device management signals required to align device state with current assignments
+
+You can track the progress of the sync action by selecting the **Device sync status** tab in the device overview pane.
+
+>[!NOTE]
+> The described sync behavior, including the **Device sync status** tab, applies only to iOS/iPadOS and Windows devices. To see the new device sync improvements, ensure that the 'Preview new device view' toggle is turned ON. This is at the top right of the Intune admin console screen.
 
 ::: zone-end
 
diff --git a/intune/device-management/tools/management-extension-windows.md b/intune/device-management/tools/management-extension-windows.md
index b54d35772d8..1ab2e900209 100644
--- a/intune/device-management/tools/management-extension-windows.md
+++ b/intune/device-management/tools/management-extension-windows.md
@@ -101,7 +101,13 @@ On a Windows device with the IME installed, open **Company Portal**, select **Se
 Alternatively, open **Task Manager**, find the service **IntuneManagementExtension**, right-click, and select **Restart**. The `IntuneManagementExtension` service restarts immediately, initiating a check-in with Intune.
 
 > [!NOTE]
-> The **Sync** actions from either the **Settings** app or **Devices** in Microsoft Intune admin center initiate an MDM check-in but don't force an IME check-in.
+> The **Sync** actions from either the **Settings** app or **Devices** in Microsoft Intune admin center initiate an MDM check-in as well as an IME check-in. After selecting Sync, Intune initiates an on-demand synchronization across multiple workloads to help ensure the device reflects the latest admin intent as quickly as possible. This process includes, but isn't limited to:
+>- Configuration policy processing
+>- App detection and deployment state updates
+>- Script and remediation processing
+>- Other device management signals required to align device state with current assignments
+>  
+>You can track the progress of the sync action by selecting the **Device sync status** tab in the device overview pane.
 
 ### Intune management extension removal