OneDrive for Business Read-Only Issue – What You Need to Know
As of February 25, 2025, at 5:25 PM CST, Microsoft identified a service degradation affecting OneDrive for Business (Issue ID: OD1017081). Users encountered their OneDrive content in a read-only state, accompanied by the error message: “You can’t edit your files because your license to use OneDrive ended over a month ago.”
User Impact
This issue prevents users from editing their OneDrive for Business content, limiting them to read-only access.

Details
The problem arises when the ownership of a OneDrive account is assigned to a group or service account, which is not a supported configuration. Additionally, a recent policy enforcement rollout caused some newly licensed users to be mistakenly recognized as unlicensed, leading to read-only access.
Mitigation Steps
Update OneDrive Configurations: Admins should ensure that each OneDrive account’s owner (primary site collection administrator) is correctly assigned to the individual user, not to a service or group account. Detailed instructions are available here:
Optional Workaround: Admins can remove the read-only lock using PowerShell by following the guidance provided here: Note that the read-only notification will persist until full mitigation is achieved, but no archiving actions will occur during this period.
Scope of Impact
This issue affects a subset of users recently configured in unsupported scenarios or those who have recently been licensed.
Preliminary Root Cause
A recent policy enforcement interacted negatively with certain configurations within organizations, particularly when OneDrive ownership was assigned to groups or service accounts. This enforcement also led to some newly licensed users being misidentified as unlicensed, resulting in read-only access.
Current Status
As of February 28, 2025, at 7:41 PM CST, Microsoft has deployed a permanent fix, expected to be fully implemented by Monday, March 3, 2025. Additionally, targeted rollouts providing immediate relief for the secondary issue are 93% complete.
Next Update
The next update is scheduled for Monday, March 3, 2025, at 1:00 PM CST.
Microsoft Updates
-
Mar 3, 2025, 1:39 PM CST
We've completed deploying the permanent fix to the affected infrastructure, and after a period of monitoring, we've determined impact is now resolved.
-
Feb 28, 2025, 7:41 PM CST
We’ve successfully deployed the permanent fix and anticipate it will be completed by Monday, March 3, 2025. Additionally, the targeted rollouts intended to provide immediate relief for the second scenario are currently 93 percent complete.
-
Feb 28, 2025, 11:53 AM CST
We've initiated the targeted rollouts for immediate relief for the second scenario, which are currently 50 percent complete. In addition, we've completed development for our permanent fix which is undergoing deployment with an expected completion date of Monday, March 3, 2025.
-
Feb 27, 2025, 7:02 PM CST
We're continuing to validate our interim fix for scenario 2 and are in the process of initiating our first wave of targeted rollouts. In parallel, we're developing and testing our permanent fix which will address this issue for all users. We'll aim to establish an estimated time to deploy the fix in our next scheduled update.
-
Feb 27, 2025, 4:56 PM CST
We've developed a fix to address scenario 2, in which newly licensed accounts aren't registering in our internal systems as expected, and we're performing internal validations before applying it more broadly. We expect that this process will begin by our next scheduled update. In parallel, we're continuing to monitor responses confirming resolution from users who received our fix for scenario 1, which addressed the unsupported configuration we outlined in our last communication.
-
Feb 27, 2025, 12:35 PM CST
We've investigated further and determined that your users may experience impact behavior due to several scenarios, which require separate mitigations. Scenario 1 - Users may be in a read-only state due to account ownership being moved from an individual to a group, which is an unsupported state. This state can be mitigated by following the instructions outlined in the 'More info' section of this communication. If you've followed these steps then, while the banner informing users that they're in a read-only state remains, users can edit content as expected. The fix we've been tracking has also been specifically targeting this scenario, and we've fixed approximately 93 percent of accounts in this state. These accounts will no longer see the read-only banner. Scenario 2 - Users may be in a read-only state due to issues registering licenses for accounts that were recently licensed. Since accounts are perceived as unlicensed, users are put in a read-only state. This issue was introduced when we reverted a portion of code in an attempt to remediate the first scenario, and we're working to develop a remediation strategy to address this secondary impact.
-
Feb 26, 2025, 6:06 PM CST
We've confirmed with some sample affected users that our change successfully provides relief, and we're in the process of applying it more broadly. We anticipate that our fix will complete and remediate the issue by our next scheduled communications update.
-
Feb 26, 2025, 2:23 PM CST
We've collected a preliminary list of accounts in unsupported states and we're validating our change, which will be applied to these accounts to alleviate impact by reversing the policy enforcement rollout. This alleviation is temporary, as the configuration our policy rollout interacted negatively with is an unsupported scenario. Please refer to https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive to ensure account ownership is properly configured to prevent future impact. We'll aim to provide an estimated timeline to resolution in our next scheduled update.
-
Feb 26, 2025, 1:53 AM CST
Our rollback of read-only sites is progressing as expected in a thorough and secure pace for our previously identified use cases. While we continue our mitigation efforts, we strongly recommend admins to take prompt action and perform the self-mitigation steps outlined in our “More Info” section as our changes may not address every unique configuration of OneDrive owners who have been changed from the correct Entra ID owner. We’ll continue rollbacks and provide another update on Wednesday, February 26, 2025 at 4:00 PM CST
-
Feb 25, 2025, 11:24 PM CST
We’re continuing our rollback to remove affected users and sites from the read-only state that they are in. In addition, we’ve expanded our initial use case scenarios to include other potential scenarios that may result in similar impact. Interim, admins should change their configurations from unsupported states as described in the more info section.
-
Feb 25, 2025, 10:39 PM CST
We’re analyzing and expanding additional use case scenarios where this read-only issue can affect users to ensure they're included in our mitigation efforts. This quick update is designed to give the latest information on this issue.
-
Feb 25, 2025, 9:45 PM CST
We’ve confirmed the cause of this issue was as a result of a recent policy change in our enforcement of unlicensed OneDrive user accounts, which uncovered unsupported instances of users being removed as admins from their own OneDrive accounts and further resulting in read-only status. We’ve paused the rollout of this enforcement change to prevent new users from entering this bad state or being archived and are working on rolling back affected users, which we anticipate completing within the next week. In addition, we’ve provided links with instructions in the more info section if you would like to manually revert the read-only state and resolve these unsupported states within your organization more quickly.
-
Feb 25, 2025, 5:39 PM CST
We received reports of an issue where some users' OneDrive for Business content is in read-only mode and an error states "You can't edit your files because your license to use OneDrive ended over a month ago." We're reviewing these reports to determine our next steps.