Power Apps: Restore Deleted Canvas App

Key insights

• Video summary: This how-to video demonstrates step-by-step recovery for a deleted Power Apps canvas app, showing hands-on fixes when an app is accidentally removed and explaining the main recovery tools available.
  
• Key concept — soft deletion and retention: Deleted canvas apps go to a recoverable state for up to 28 days (varies by environment). After that window the app may be permanently removed, so act quickly to recover deleted items.
  
• Quick restore via the Recycle Bin: Sign in to make.powerapps.com, open Solutions, click the Recycle Bin, find the app, and choose Restore. This is the fastest method for makers and does not require admin tools.
  
• Admin recovery with PowerShell: Install the Microsoft.PowerApps.Administration.PowerShell module, run Add-PowerAppsAccount to sign in, list deleted apps with Get-AdminDeletedPowerAppsList -EnvironmentName 'YourEnvironmentName', then restore by app GUID using Get-AdminRecoverDeletedPowerApp -AppName 'AppGUID' -EnvironmentName 'YourEnvironmentName'. Use admin rights and replace placeholders with your values.
  
• Command-line option — Power Apps CLI: Authenticate with pa login, list deleted apps, and run pa restore app --guid 'AppGUID'. The CLI is scriptable for batch or automated restores and integrates well with developer workflows.
  
• Backups, versions and post-restore checks: If you use Azure backups, restore from the Recovery Services vault or recover app versions from the maker portal when available. After restoring, reconnect any connectors, test the app, and verify permissions and environment settings before returning it to users.
  

Summary of the Video

In a recent YouTube tutorial, Shane Young [MVP] walks viewers through how to restore a deleted Power Apps Canvas app, focusing primarily on a practical PowerShell solution. He presents a calm, step-by-step approach that shows the exact commands and menu clicks needed to find and recover an app after accidental deletion. Moreover, the video highlights several alternative methods, such as using the in-portal Recycle Bin, the Power Apps CLI, and environment backups, so viewers can choose the approach that fits their situation.

What the Demonstration Covers

First, Shane explains the typical lifecycle of a deleted app and why many deletions are recoverable because of soft-delete retention policies. Then, he demonstrates installing the required PowerShell modules, authenticating to the tenant, listing deleted apps, and issuing the recovery command that targets the app by its GUID. Finally, he reviews the restored app in the maker portal and points out the need to reconnect connectors and reassign owners where necessary.

Methods and Their Tradeoffs

The video compares straightforward in-portal recovery against command-line and backup-based approaches, making the tradeoffs clear. For instance, using the Recycle Bin is easy and fast for non-admin makers, but it only works if the app still appears in the portal and the user has the right permissions. Conversely, PowerShell and the CLI give admins precise, scriptable control and can handle bulk restores or cross-environment operations, yet they require more technical skill and appropriate rights.

Shane also explains that restoring from an environment-level backup, such as through an Azure Recovery Services vault, can recover more than a single app but comes with more overhead and potential downtime. Therefore, teams must weigh the convenience of a simple restore against the complexity and cost of broader environment restores, especially when only a single app is affected. In addition, some environments enforce shorter retention windows, which increases the risk of permanent loss if organizations do not act promptly.

Step-by-Step PowerShell Walkthrough

In the central portion of the tutorial, Shane demonstrates the precise PowerShell sequence: installing the administration module, authenticating with Add-PowerAppsAccount, listing deleted apps with Get-AdminDeletedPowerAppsList, and finally restoring with Get-AdminRecoverDeletedPowerApp using the app's unique GUID. He encourages viewers to capture the environment name and app identifier in advance, because mistyped names can lead to failed commands or the wrong target being restored. Furthermore, he shows how to verify the restoration in the portal and how to handle prompts to reconnect connectors and reauthorize services.

Shane also calls attention to common errors, such as missing modules, expired sessions, or insufficient privileges, and he demonstrates simple fixes like reinstalling modules or reauthenticating. Importantly, he highlights that restoring an app may not fully restore connector credentials or environment-specific settings, so testers should always validate functionality after recovery. These practical checks reduce the chance of surprises when the app goes back into production.

Practical Challenges and Risks

The video does not downplay real-world constraints: retained apps persist only for the retention window, which is typically 28 days but can be shorter in some environments, and after that apps become permanently deleted. Moreover, restoring apps across environments can lead to configuration mismatches, broken connections, or missing data if the target environment lacks the same resources. Thus, administrators must plan for consistent environment configuration and consider staging restores before applying changes in production.

Another challenge Shane addresses is permission management: recovering some apps requires tenant or environment admin rights, so organizations should carefully assign delete and restore privileges. Additionally, automated restores and bulk operations speed recovery but increase the risk of accidentally overwriting a current app if identifiers are confused, which makes careful validation and safeguards essential.

Best Practices and Recommendations

Drawing on the video’s advice, organizations should combine simple safeguards with technical controls to reduce recovery time and risk. For example, teams can regularly export and version apps, keep app GUID records, enable scheduled backups where available, and restrict delete permissions to minimize accidental removals. In addition, documenting a tested recovery runbook and training at least one staff member in the PowerShell and CLI methods will speed response when incidents occur.

Finally, Shane’s tutorial emphasizes that calm, methodical action often resolves a deleted-app emergency, and that PowerShell offers a reliable path to recovery when the portal is insufficient. Consequently, the video will help both makers and admins adopt practical habits and technical steps that lower the risk of permanent data or app loss while improving organizational readiness.

Keywords

restore deleted Power Apps canvas app, recover deleted Power Apps app, restore Power Apps app step by step, recover canvas app from recycle bin Power Apps, undelete Power Apps canvas app tutorial, restore app version in Power Apps, Power Apps recycle bin restore guide, step by step restore deleted canvas app Power Apps