Forum Discussion
OneDrive site locked NoAccess for 1 month - Ticket #2605040040008376 - No resolution
- Jun 16, 2026
After six weeks, we have successfully regained access to the departed user's archived OneDrive account and recovered the shared folder.
The unlicensed OneDrive account, archived due to Microsoft's own enforcement policies, combined with a retention policy deadlock, was ultimately resolved by enabling Microsoft 365 Archive billing and submitting a reactivation request (After setting up a Pay as you Go subscription). This solution was not identified or communicated to us until very late in the process, despite being documented in Microsoft's own support articles.
While we are relieved and grateful that the issue has been resolved, we feel it is important to provide honest and constructive feedback to Microsoft on the overall support experience for quality assurance purposes:
- Improve frontline support training on unlicensed OneDrive archival scenarios
- Establish clear escalation timelines. It is inconceivable that cases go more than a week without tangible technical progress
- Proactively notify administrators of the real status facts related to the case, for instance, when OneDrive accounts are approaching archival due to unlicensed status
- Consider waiving reactivation fees for cases where archival occurs during an active support engagement
We remain committed Microsoft 365 customers and appreciate the eventual resolution of this issue. However, we strongly encourage Microsoft to review this case as an example of where the support process fell short of the service levels expected by a paying enterprise customer.
We hope this feedback helps improve the experience for other customers facing similar issues in the future.
Hi nardila,
This sounds like it may be stuck somewhere on the Microsoft side rather than being a normal SharePoint admin issue.
What stands out to me is that Set-SPOSite -LockState Unlock completes successfully, but the site remains in a "No Access" state. If the command succeeds but nothing actually changes, I'd suspect there's still some compliance or retention-related process holding the site.
I'd be interested to know what Get-SPOSite currently reports for the lock state and whether the retention policy exclusion has had enough time to fully propagate.
Given that you've already been working with support for over a month, I would ask whether the case has been escalated to the SharePoint Online engineering team. This doesn't sound like a standard administrative lock.
Hopefully someone who's dealt with a similar retention-policy scenario can chime in.
Good luck.