I am implementing a Zero Touch device swap solution in an Intune environment, with the goal of significantly improving the first sign-in user experience. Current situation At the moment, users: Run a PowerShell script on the old device to back up Outlook-related data to OneDrive Then manually run the script again on the new device to restore the data The script currently handles: Outlook profile registry (HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles) Signatures Word building blocks / text modules Drive mappings Target solution I want to convert this into a single PSADT-based Win32 app (Intune) with a clean and guided flow: Mode 1 – Backup (old device): Detect user context Store backup in OneDrive (user folder) Save device identifier (e.g. computer name or ID) Mode 2 – Restore (new device, first sign-in): Detect that backup already exists Restore all settings automatically Apply additional setup steps (e.g. mappings, taskbar, etc.) Key challenges I want to solve: Reliable mechanism to differentiate old vs new device Clean mode handling (backup vs restore) inside PSADT Ensure everything runs in user context (Intune Win32 app) Proper logging and error handling (PSADT standard) What I need from you Refactor my existing script into a clean PSADT structure Implement the backup/restore logic in a robust way Design a reliable detection mechanism Make it production-ready for Intune deployment I can provide my current script and environment details. Would you be able to support with this? Thanks a lot in advance, Ruben