Skip to content
  • There are no suggestions because the search field is empty.

Uninstall Foxit PDF Editor Cloud in SharePoint

Explains how to uninstall the Foxit PDF Editor Cloud app from Microsoft SharePoint.

Answer

Summary

This article describes how to remove the Foxit PDF Editor Cloud for SharePoint app from an individual site or from the entire tenant, depending on how it was originally deployed.

 

 

Prerequisites

  • Site Owner role (to remove the app from a specific site)
  • SharePoint Administrator role (to remove the app from the entire tenant)
  • Foxit PDF Editor Cloud for SharePoint previously deployed to your environment

 

Important: The removal method available to you depends on how the app was originally deployed. If an administrator used "Enable this app and add it to all sites," site owners cannot remove the app from Site Contents — only tenant-level removal by an administrator will work.

 

 

1. Removing the App from a Specific Site

Audience: Site Owners

Follow these steps to remove the Foxit PDF Editor Cloud app from a single SharePoint site. This option is only available if the administrator originally selected "Only enable this app" during deployment.

 

  1. Go to the SharePoint site — Navigate to the site from which you want to remove the app.
  2. Open Site Contents — Click Settings (the gear icon in the top-right corner), then select Site contents.
  1. Locate the app — Find the entry named Foxit PDF Editor Cloud in the list of installed apps.
  2. Remove the app — Click the ... (ellipsis) next to the Foxit PDF Editor Cloud entry and select Remove from the menu. Confirm the action when prompted.




 

  1. Delete from Recycle Bin (Required) — To fully remove the app and prevent it from being restored, navigate to the site's Recycle Bin and permanently delete the Foxit PDF Editor Cloud entry. Without this step, the app may reappear if the Recycle Bin is restored.

 

Note: Expected Result: The Open with Foxit PDF Editor option will no longer appear in document library menus on this site. Changes may take a few minutes to propagate.

 

2. Removing the App from the Entire Tenant

Audience: SharePoint Administrators

Follow these steps to completely remove the Foxit PDF Editor Cloud app from your Microsoft 365 tenant. This will remove the app from all sites where it is currently deployed.

 

Important: This action affects all users across all sites in your tenant. Verify with your organization before proceeding.

 

  1. Open SharePoint Admin Center — Navigate to your SharePoint Admin Center at admin.microsoft.com > SharePoint.
  2. Navigate to App Catalog — Go to More features > App Catalog > Apps for SharePoint.
  3. Locate the app — Find Foxit PDF Editor Cloud for SharePoint in the list.
  4. Delete the app — Select the app, click Delete, and confirm the action. This removes the package from the tenant App Catalog and uninstalls it from all sites.

 

Note: Expected Result: The Foxit PDF Editor Cloud app will be removed from all SharePoint sites in your tenant. The Open with Foxit PDF Editor option will no longer appear for any users. This process may take up to 30 minutes to propagate across all sites.

 

Troubleshooting

 

"Remove" option is not available in Site Contents

  • The administrator likely deployed the app using "Enable this app and add it to all sites." In this case, only a SharePoint Administrator can remove it at the tenant level. Follow the steps in Section 2 above.

 

App reappears after removal from Site Contents

  • The app entry was not deleted from the Recycle Bin. Complete Step 5 in Section 1 to permanently delete the app from the Recycle Bin.
  • If the app was deployed tenant-wide, it will continue to reinstall. Contact your SharePoint Administrator to remove it at the tenant level.

 

App still appears for users after tenant-level deletion

  • Tenant-wide propagation can take up to 30 minutes. Ask users to refresh their browser (Ctrl+Shift+R or Cmd+Shift+R).
  • If the issue persists after 30 minutes, contact Microsoft Support, as this may be a CDN caching issue.

 

Related Articles