Security Policy Errors

Fix Exchange Admin Center Freezing When Removing Quarantined Mobile Device

Steve KSteve K Oct 14, 2026 868 views

Question details

Administrators cannot remove a quarantined mobile device because the Exchange admin center interface freezes on the Saving screen.

Fix Exchange Admin Center Freezing When Removing Quarantined Mobile Device
Product
Microsoft Exchange Online
Device & OS
not provided
Scenario
Attempting to remove a quarantined mobile device from the Exchange admin center interface.
Observed behavior
The interface becomes stuck on the Saving prompt and freezes, leaving the mobile device in a quarantined state across multiple administrator accounts.
Before you start

Ensure you are logged in with Global Administrator or Exchange Administrator credentials and verify that your Microsoft 365 tenant is not currently experiencing active service degradation.

Solution 1Recommended

Verify RBAC Permissions and Device Configurations

Check your Exchange Online RBAC permissions and ensure there are no conflicting Intune access policies causing the interface to freeze.

The freezing issue typically stems from insufficient administrative permissions or conflicting mobile device access policies that prevent the Exchange Admin Center from saving the new device state.

1
Check RBAC permissions

Sign in to the Exchange Admin Center and navigate to the roles or permissions section to ensure your administrator account has the required Exchange Online Role-Based Access Control (RBAC) permissions to manage mobile devices.

2
Review Intune device policies

Access the Microsoft Intune admin center and review your device compliance and conditional access policies to verify there are no conflicting rules keeping the device quarantined.

3
Contact Microsoft Support

If permissions and policies are correct but the interface still freezes on Saving, collect diagnostic logs and submit a support ticket to Microsoft Support for backend assistance.

Verify RBAC Permissions and Device Configurations
Microsoft 365 Defender Portal Limitation: Do not use the Microsoft 365 Defender quarantine portal (security.microsoft.com/quarantine) for this issue. It is intended for managing quarantined email messages and files, not mobile-device access.
Free Microsoft Office alternative

Discover WPS Office for Seamless Business Productivity

While resolving Microsoft Exchange administration issues, consider optimizing your team's document workflows with WPS Office. It provides a lightweight, cost-effective, and highly compatible alternative to Microsoft Office for all your everyday document needs.

  1. 1. Download the software: Visit the official WPS Office website and download the installer for Windows, Mac, or Linux.
  2. 2. Install WPS Office: Run the setup file and follow the straightforward on-screen instructions to complete the installation.
  3. 3. Open and edit files: Launch WPS Office to easily create new documents or open your existing Microsoft Office files without formatting loss.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight application size ensures smooth performance on a wide range of devices.Familiar tabbed user interface minimizes training time and ensures seamless user migration.Includes powerful built-in PDF editing and conversion tools.
QA img-9

Frequently Asked Questions

Why does the Exchange Admin Center freeze on the Saving screen?

This freezing behavior usually happens when there are conflicting mobile device access policies between Exchange and Intune, or when the admin account lacks the specific RBAC permissions required to process the device state change.

Can I remove a quarantined mobile device using the Microsoft 365 Defender portal?

No. The Microsoft 365 Defender quarantine portal is designed exclusively for handling quarantined messages and files. Mobile device management must be done via the Exchange Admin Center or Intune.

What should I do if multiple administrators experience this freezing issue?

If multiple administrators with the correct RBAC permissions face the same issue, it suggests a tenant-level backend problem. You should collect network diagnostic logs (like a HAR file) from your browser and escalate the issue to Microsoft Support.