OneDrive for Business storage quotas do not update for large departments: Fix Guide

When you manage OneDrive for Business storage quotas for a large department, you might notice that the assigned quota does not reflect correctly in the OneDrive admin center or user OneDrive pages. This delay or failure to update typically occurs because of propagation limits in Microsoft 365 or because the quota change was applied to a group that exceeds the service’s immediate processing capacity. This article explains why storage quota updates can stall for large departments and provides a step-by-step fix to force the update. You will also learn how to verify the change and what to do if the quota still does not appear correctly.

Why OneDrive Storage Quota Updates Fail for Large Departments

When you change a storage quota for a user or a group in the Microsoft 365 admin center, the change must propagate to the SharePoint Online service that hosts OneDrive sites. For a single user or a small group, this propagation usually completes within minutes. For a large department — typically more than 500 users — the service applies the change in batches. If the batch size exceeds the service’s internal limit, the update may appear to succeed in the admin panel but never reach the underlying OneDrive site.

Another common cause is that the quota change was applied to a security group or distribution list that contains nested groups. SharePoint Online does not recursively process nested groups for storage quota updates. Only direct members of the group receive the new quota, while indirect members remain on the old limit. This mismatch creates the illusion that the update failed for the entire department.

Finally, the OneDrive admin center’s storage quota field may cache the previous value for up to 24 hours. Even if the underlying site received the new quota, the admin center display may not refresh until the cache expires. This caching behavior is by design and can cause confusion.

Steps to Force OneDrive Storage Quota Updates for Large Departments

Use the following methods in order. The first method uses the admin center and works for individual users. The second method uses PowerShell and is required for bulk updates to large groups.

Method 1: Update Quota for a Single User via SharePoint Admin Center

1. Open the SharePoint admin center
   Sign in to the Microsoft 365 admin center at admin.microsoft.com. In the left navigation, select Admin centers and then SharePoint.
2. Locate the user’s OneDrive site
   In the SharePoint admin center, select Active sites from the left menu. In the search box, type the user’s full name or email address. The OneDrive site URL typically follows the pattern https://yourtenant-my.sharepoint.com/personal/user_domain_com.
3. Open site settings
   Click the site URL to open the site details panel. In the panel, select the Settings tab.
4. Change the storage limit
   Under Storage limit, select Edit. Enter the new quota in megabytes. For example, 1 terabyte is 1048576 MB. Click Save.
5. Verify the quota
   Wait 5 minutes. Open the user’s OneDrive by navigating to https://yourtenant-my.sharepoint.com/personal/user_domain_com. Click the gear icon, select OneDrive settings, and then Storage. Confirm the displayed quota matches what you set.

Method 2: Bulk Update Quota for a Large Department Using PowerShell

1. Install and connect to SharePoint Online PowerShell
   Open Windows PowerShell as an administrator. Run Install-Module -Name Microsoft.Online.SharePoint.PowerShell if not already installed. Then run Connect-SPOService -Url https://yourtenant-admin.sharepoint.com and sign in with a SharePoint admin account.
2. Get all OneDrive sites for the department
   If your department users are in a specific security group, export the group members first. Use Get-SPOSite -IncludePersonalSite $true -Filter "Url -like '-my.sharepoint.com/personal/'" to list all OneDrive sites. Filter the list by user property or by comparing against a CSV of department users.
3. Apply the new quota to each site
   Run the following cmdlet for each site:
   Set-SPOSite -Identity -StorageQuotaWarningLevel -StorageQuota
   Replace with the full OneDrive site URL and with the new limit in megabytes. For example:
   Set-SPOSite -Identity https://contoso-my.sharepoint.com/personal/john_contoso_com -StorageQuotaWarningLevel 512000 -StorageQuota 1048576
4. Run the cmdlet in a loop for all users
   Use a foreach loop to apply the quota to every site in your filtered list. Example:
   foreach ($site in $sites) { Set-SPOSite -Identity $site.Url -StorageQuotaWarningLevel 512000 -StorageQuota 1048576 }
   This process bypasses batch propagation delays and updates each site directly.
5. Verify the bulk update
   Run Get-SPOSite -Identity | fl StorageQuota, StorageQuotaWarningLevel for a sample of users. The output should show the new values immediately.

If OneDrive Storage Quota Still Does Not Update After the Fix

Quota reverts to the old value after a few hours

This indicates that a group policy or a central storage quota setting is overriding your manual change. Check the Microsoft 365 admin center under Billing > Licenses to ensure the user has the correct license that includes the desired storage. Also check the SharePoint admin center under Policies > Storage for a tenant-wide storage limit that may cap individual quotas.

PowerShell returns an error: “Site does not exist”

The user’s OneDrive site may not have been provisioned yet. A user must sign in to OneDrive at least once to create the site. Ask the user to visit onedrive.com and sign in with their work account. After the site is created, rerun the PowerShell cmdlet.

Admin center shows the old quota but user sees the new quota

This is the caching behavior described earlier. The admin center cache can take up to 24 hours to refresh. The user’s actual storage limit is correct. You can clear your browser cache or use a private browser window to force the admin center to fetch fresh data.

SharePoint Admin Center vs PowerShell for Quota Updates: Key Differences

Item	SharePoint Admin Center	PowerShell (Set-SPOSite)
Propagation speed	Batch processing; can take hours for large groups	Immediate for each site processed
Support for bulk updates	Only single user or small group via UI	Supports loops and CSV imports for any number of users
Nested group handling	Does not process nested group members	No group dependency; you target specific site URLs
Error reporting	Minimal; success message may not reflect actual propagation	Explicit error messages for missing sites or permission issues
Caching delay	Admin center may cache old value up to 24 hours	No caching; Get-SPOSite returns live data

The SharePoint admin center is adequate for single-user quota changes where immediate feedback is not critical. For large departments or when nested groups are involved, PowerShell provides direct control and immediate verification. Use PowerShell whenever you need to update more than 50 users at once or when the admin center fails to propagate the change.

Now you can diagnose why OneDrive storage quota updates stall for large departments and apply the correct fix using either the SharePoint admin center for individual users or PowerShell for bulk updates. After applying the fix, verify the quota using the user’s OneDrive settings page or the Get-SPOSite cmdlet. As an advanced tip, combine the Set-SPOSite cmdlet with a scheduled Azure Automation runbook to enforce storage quotas for new users automatically, preventing future propagation delays.