What Happens to Power Automate Flows and OneDrive Files When a User Leaves?
Question details
The user needs to know how to handle Power Automate flows, Power Apps, and shared OneDrive files when an employee leaves the organization to prevent data loss and automation failures.
- Product
- Power Automate, Power Apps, OneDrive
- Device & OS
- not provided
- Scenario
- An employee is retiring or leaving the company, requiring their digital assets, cloud files, and active workflow automations to be managed and transitioned before their account is permanently deleted.
- Observed behavior
- Without proper transition, automated flows will fail, custom apps will become inaccessible, and shared files stored in the user's personal OneDrive will be lost once the user's Microsoft 365 account is removed.
Ensure you have Microsoft 365 global administrator or SharePoint administrator privileges to access and reassign the departing user's workflows, apps, and OneDrive files.
Transfer Ownership of Flows, Apps, and OneDrive Files
Identify, document, and transfer the ownership of all critical automated flows and files before deleting the user's account.
To ensure business continuity, you must reassign ownership of the departing user's assets. If an account is deleted before reassignment, any Power Automate flows tied solely to that user will be disabled and shared OneDrive files will eventually be permanently deleted.
Review the departing user's Microsoft 365 account to identify all active Power Automate flows, published Power Apps, active service connections, and shared OneDrive files utilized by the team.
Navigate to the Power Automate and Power Apps admin centers. Add a service account or an active team member as a co-owner to the departing user's flows and apps. Update any specific data connections to use the new owner's credentials.
Access the user's personal OneDrive. Relocate critical business documents and shared files to a centralized SharePoint document library or a shared team OneDrive location to ensure uninterrupted access.
Monitor the reassigned flows and apps to confirm that all required automations continue to trigger and run successfully without depending on the departing user's account.
Looking for a Cost-Effective Office Solution for Your Team?
While managing user transitions and licenses in Microsoft 365, you might be exploring budget-friendly software alternatives. WPS Office provides a powerful, free office suite that is fully compatible with Microsoft Office file formats, ensuring your team can seamlessly edit and share documents without expensive subscriptions.
- 1. Download WPS Office: Visit the official WPS website to download and install the free WPS Office suite on your device.
- 2. Open Existing Documents: Easily open your existing .docx, .xlsx, and .pptx files directly in WPS Office without any format loss.
- 3. Collaborate and Save: Edit your files and save them in native Microsoft formats to share seamlessly with colleagues and clients.
Frequently Asked Questions
How long are a user's OneDrive files kept after their account is deleted?
By default, Microsoft 365 retains a deleted user's OneDrive files for 30 days. During this retention period, a designated manager or administrator can access the drive and move important files before they are permanently purged.
What happens if a Power Automate flow only has the departing user as the owner?
If the sole owner's account is deleted or disabled, the Power Automate flow will eventually be disabled and stop running. It is critical to add a co-owner or reassign the flow to a service account before the user leaves.
Can I restore a deleted user's Power Automate flow?
Yes, administrators can use PowerShell cmdlets or the Power Platform admin center to recover deleted flows within a specific retention window, typically up to 21 days after the deletion occurred.
Should I use a service account for company-wide automations?
Yes, it is highly recommended to use a dedicated, non-expiring service account rather than an individual employee's account for critical business flows. This prevents workflow disruptions when employees inevitably leave the company.
