One drive is an insanely poorly implemented solution to a problem nobody really had.
For enterprise companies, ones I've worked in at least, they will auto sync the users folder /c/Users/(name) with one drive, but there is some weird alternative they have to set on the windows system to actually use a workspace for the user.
So when I'm on site somewhere, and have no access to a network that's safe, I can't access files that are in my documents folder, pictures or desktop.. when I never asked OneDrive to lift and shift my days off my machine.
I've had the guys turn off one drive explicitly on my machine several times but it keeps reactivating itself as soon as I sign back into the AD.
They can't figure it out, I can't trust it, and the company pays for it.
The best thing you can do with an enterprise Onedrive is having long long file and folder names. The moment it exceeds 255 characters, the software application dies. I am ready to hear easier fixes but so far this worked:
- Rename the offending folder from the web
- Unlink the folder from the user's machine
- Delete the existing onedrive folder
- Relink and resync
The best part is, the web side of onedrive has practically unlimited length, the windows part has. As long as you don't sync, you don't experience anything but god forbid if you try to do it.
Also do not get me started on "Add a shortcut/Sync" debate. All in all, onedrive feels like a system that works but will feed you to the wolves the moment it hiccups. But on the enterprise side that's the only game in town so... we suffer altogether.
I’ve seen a lot of people have issues with git, because this is going on in the background and they don’t realize it.
They’ll change branches, then OneDrive sees files are missing, so it starts pulling them back down. It makes a mess.
Any new hire we get, we need to make sure to explicitly tell them not to keep their code in a folder managed by OneDrive, but they never listen. They speak up about a month later, complaining about weird issues.
On my last laptop refresh I also had to manually enable the sync. It didn’t just happen. I knew if I used the local folders that would eventually stop working and things would get lost.
I’ve also seen a lot of confusion from people who save something to their desktop, and it’s not there… because they didn’t save it to their OneDrive desktop. This is always fun to explain.
OneDrive is also now our backup, but they only sync 3 folders from the home directory. If your work has you using other folders, good luck and enjoy your data loss. I setup a scheduled job to backup some of my other key files to OneDrive, but that was quite annoying. I’m sure I’m in the minority.
The enterprise enables all this stuff, but never actually tells anyone. They think it will “just work”, but it creates a confusing mess that every employee eventually has to figure out.
The whole thing is a cobbled together bodge over SharePoint as a backend. I wouldn't ever trust my company data with that dogwater product.
Back when I had to work with it I found a bug that could cause folders to become un-synced without you realising, meaning changes would not be tracked and cause merge-conflicts when it was fixed.
Managed to use our Gold partner tickets to raise the issue with the product team, they flat out refused to fix the issue even knowing it was a bug. This was back in 2020 or so, I wonder if they ever fixed that bug. It's pretty simple to reproduce:
1. - Sync a nested subfolder from Sharepoint
2. - Sync the parent folder
3. - Note that the folder synced in 1. is not longer being tracked (no checkmark)
4. - Normal users will now go to folder 1. by default and have no idea none of their changes are no longer being tracked now that it's being synced within folder 2.
The university I attend uses SharePoint, classroom and moodle for various courses.
SharePoint is by far the worst piece of software I've ever used. Like, there's no mental model to be done, not intuitive, not working, files disappear from time to time, and I could go on for hours
Somehow finding the Frontpage HTML editors down at the bottom makes it feel slightly better. At least it bring a fond memory while navigating our corporate Sharepoint horrorfest.
And as someone who worked and still works in IT support, users will not save to network drives, their machine will crash and files will be lost.
YES, you can do GPO redirect desktop etc to network drive but needs a VPN and sync is also slow.
OneDrive has solved this, like it or not.
>So when I'm on site somewhere, and have no access to a network that's safe, I can't access files that are in my documents folder, pictures or desktop.. when I never asked OneDrive to lift and shift my days off my machine.
Probably enterprise config. Standard OneDrive office 365 enterprise with SharePoint can absolutely work over the "normal internet", you don't need a "network that's safe" whatever that means. VPN? Anyway the big office 365 win was it will work over the normal internet without running /owa open on your exchange server.
>And as someone who worked and still works in IT support, users will not save to network drives, their machine will crash and files will be lost. [...] OneDrive has solved this, like it or not.
In my previous job there was an app(by Dell EMC I think) that would run every day at lunch and backup all your user document folders to some company network drive. You could then view all your backup files in the webUI.
So network backup feels like a solved problem for decades now.
However, cloud is more than just a backup solution.
Come on, a problem nobody really had? I wholeheartedly disagree. Data loss and the orthogonal problem of lacking free space on computers is/was a massive problem at enterprise scale and OneDrive, for all its many shortcomings, is well and truly into good-enough territory to cover the 80% case. I'd go so far as to argue that the scenario you've described is by far the less frequent one. And if it frustrates you, you're afforded the ability to designate files and entire folders to be kept downloaded at all times anyway.
Data loss and storage is always a challenge, that's why companies will have network drives, network storage that's not strongly coupled with your account acess. OneDrive doesn't solve the problem in a clean way. It adds an extra layer of brittleness.
Network storage does not handle the online/offline switching as transparently as OneDrive (or other cloud storage).
For large enterprises that old architecture you refer to means long lead times on network and storage outage notifications, and huge fallout if an outage window is blown.
And if the building network goes down, or if your storage servers are located off site because you’re too big for one building and the commercial internet goes down, etc etc
But it doesn’t have to be OneDrive. There are many other options. I run ownCloud 10 for my personal files. If I were a small to medium business, I would look hard at OCIS.
Network drives mean no local retention and no real good answer for Windows+Mac+Android+iOS clients to remotely access the files. It also doesn't solve sharing those files externally with granular permissions.
All of these kinds things need protection against data loss and centralized control+management, not just the user folder alone.
F OneDrive. They locked me out without any explanation and without any notificaiton, ended my subscription and I lost valuable photos forever. Stay away from it if you are looking for storage for any reason.
Indeed, they are probably one of the worst cloud "storage" services ever to exist.
I also lost data on their platform. Not sure why anyone would like to still use them. This follows a pattern of Microsoft mishandling their user's data. They even routinely delete code hosted on their servers when they shutdown services without handling the migration well.
I'm building a digital document archive organizer platform that relies on users' own local machine storage and their cloud storage, and the only provider I trust to support are s3-compatible storage and Google drive (much as I'm wary of Google, Gdrive is reliable). Dropbox, Box, etc are also ok, but the storage is kind of expensive.
There's always an excuse, or perhaps someone who actually went through it might be aware of the process and limitations better than your surface level assumptions?
I don't want to imagine how much mess they have in their backend, given that most Microsoft 365 products rely on SharePoint in one way or another. And then, sometimes you get a "peek" of what's happening behind the scenes (spurious folders, random files appearing, hidden libraries, etc...).
Whenever I was forced to interact with OneDrive, I couldn't help imagining the proverbial digital duct tape holding everything together behind the scenes.
It comes up with a scenario where it could be a problem ( license removal ), and then it generates why a license might get removed ( "cost-saving" ).
It's not a person thinking, so there's no real thought to whether it is really a likely scenario, it's just something that sounds plausible.
I read too many blogs, I've come to spot these phrases that trip a feeling of, "Wait, do people really do that?".
You'll still have someone along in the comments to suggest that this article isn't AI slop, and that people really do remove individual one-drive licenses from active people in an organisation to cut costs, that this is just "edited" by AI, etc.
But it's slop from start to finish. Or in LLM speak, "The slop is real".
Related story: I recently watched a new video by a well-known YouTuber whom I was subscribed to for years. Something was off with the video: the script sounded like LLM slop. It sounded as if the author provided some bullet points on the main content of the script, and then let the LLM "expand" on it, with its typical, overly verbose, mode-collapsed LLM style. Then the YouTuber seems to have added some light edits to the script himself because it did sound real occasionally.
This was just after a few minutes of video and I didn't finish watching it. At a quick glance, I didn't see anybody else pointing this out in the comments. Disappointing.
How can I be so certain about LLM usage after just a few minutes? It's both the fact that it sounded like slop, and the fact that I intuitively know his real writing style from past years, and it simply sounded very different this time.
An article about OneDrive being substantially LLM written is sort of okay (who cares about OneDrive by some Office365 blog), but if people you thought you like resort to these methods I feel betrayed.
I had something similar happen where someone linked a blog article, I thought it sounded like slop, especially since they were posting 2-3 articles a day, but I wasn't sure so I checked their back catalogue.
I then saw they've always written like that, and always posted 2-3 articles a day, so I figured they're prolific and LLMs copied their style.
Then I read their first post again, and realised I should check the wayback machine.
Sure enough, they had gone through their entire post history, and had rewritten it with an LLM, to make it less obvious when they started using them.
Now, this was always a bit of a junk site, a knock-off Boing Boing, but it seems incredible to me that someone would replace their original posts with AI gen.
Surely it destroys any reputation you might have?
A site they've been running for nearly 20 years, overwritten by slop.
Damn this is horrible. So the author chose to waste everyone's time by expanding with cow manure. I generally don't read much articles online anymore since they are all likely to contain slop unless authored by known non-slop users.
Data is on pragmatic lockout after 3 months, not 12.
For years, enterprises have been conditioned to lean into OneDrive and forget about it. Indeed, that dark pattern is a festering disease across consumer Windows.
Retention and legal holds: Data can still be deleted even if a retention policy or legal hold is in place, unless licensing or billing is restored first. Do not rely on holds alone to protect unlicensed data.
Surprising it doesn't automatically move into an admin or company lawyer's drive so it can be dealt with rather then a few notifications which will probably be missed and the data permanently deleted.
In an enterprise environment onedrive is perfectly fine. Yet so many developers think they're to good for it. They save their things outside of onedrive and low and behold they lose data. Its so dumb and im yet to hear a good reason why they couldnt have used onedrive.
If you start uploading data to your cloud without my clear consent, I already see a very big problem with your product.
If you even substitute the directories in my computer (a standard that was untouched for the last 20 years) in a way to force my stuff into your cloud, then there’s a much bigger problem.
Managers who approved this should be thrown out of the company because this is clearly how NOT to make a product.
You can find multiple comments on past OneDrive posts from people who are/were at Microsoft with frankly terrifying stories of them losing their own or customer data. They all said the same thing: Do not use or trust OneDrive.
IIRC one of the funnier examples was users, their managers, and so on all the way up the chain (perhaps including HR and Legal) being let go resulting in there being no user to transfer the ownership/access to so it was simply deleted.
Don’t put your data in onedrive at all. We’ve experienced multiple cases of data loss which were definitely either implementation bugs or files simply being unreadable or lost.
This will have a huge impact on a lot of organisations, for example those that have a communal SharePoint, or shared document page: files shared from ex-employees for critical documentation is going to break.
Arguably, this situation is already broken right now. If an organization can't be bothered to use their tools (Sharepoint and the wider O365 ecosystem) correctly, it's entirely on them.
AFAIK Sharepoint doesn't have these limitations. The idea is that in companies OneDrive should not be used for permanent stuff. Which is strange, to be granted, but after all using OneDrive for company documents basically means they are being shared out of some personal space that doesn't belong anywhere.
Do you see "personal" and something that looks like your name in the path? That's your personal onedrive, like your home directory on a unix system.
See "sites" in the URL? That's a sharepoint site (AKA teams "shared" folder).
The former disappears (after a year) when the user license is removed. The latter is not associated with an individual user, so even if everyone in a team leaves the company it isn't just automatically removed.
Following was wrong and had been edited:
The non-business personal onedrive was a box.com/dropbox/g-drive competitor. Microsoft moved its backend to Sharepoint at some time. (Onedrive for business used Sharepoint from the get-go). The integration of the personal drive, even though it's a descendent from the 'for business' product, is still quite unintuitive in my opinion.
And if they haven't migrated the ownership of the OneDrive to another user's account in 12 months (such as cascading the drive up to the next manager to pull out whatever docs)... what kind of other bad IT and managerial practices are in use?
The worst managerial practice is to use OneDrive for company work purposes. For anybody else than the original creator these docs are nowhere to be found unless you know the shared URL.
Don't use Microsoft OneDrive. They mine your data and share it with the US government. And - as the International Criminal Court staff has recently discovered - they will cut you off from your data if they, or the US government, decide they don't like you.
One drive is an insanely poorly implemented solution to a problem nobody really had.
For enterprise companies, ones I've worked in at least, they will auto sync the users folder /c/Users/(name) with one drive, but there is some weird alternative they have to set on the windows system to actually use a workspace for the user.
So when I'm on site somewhere, and have no access to a network that's safe, I can't access files that are in my documents folder, pictures or desktop.. when I never asked OneDrive to lift and shift my days off my machine.
I've had the guys turn off one drive explicitly on my machine several times but it keeps reactivating itself as soon as I sign back into the AD.
They can't figure it out, I can't trust it, and the company pays for it.
The best thing you can do with an enterprise Onedrive is having long long file and folder names. The moment it exceeds 255 characters, the software application dies. I am ready to hear easier fixes but so far this worked:
- Rename the offending folder from the web
- Unlink the folder from the user's machine
- Delete the existing onedrive folder
- Relink and resync
The best part is, the web side of onedrive has practically unlimited length, the windows part has. As long as you don't sync, you don't experience anything but god forbid if you try to do it.
Also do not get me started on "Add a shortcut/Sync" debate. All in all, onedrive feels like a system that works but will feed you to the wolves the moment it hiccups. But on the enterprise side that's the only game in town so... we suffer altogether.
You can change that setting in Windows so that it no longer has a 255 character limit.
I’ve seen a lot of people have issues with git, because this is going on in the background and they don’t realize it.
They’ll change branches, then OneDrive sees files are missing, so it starts pulling them back down. It makes a mess.
Any new hire we get, we need to make sure to explicitly tell them not to keep their code in a folder managed by OneDrive, but they never listen. They speak up about a month later, complaining about weird issues.
On my last laptop refresh I also had to manually enable the sync. It didn’t just happen. I knew if I used the local folders that would eventually stop working and things would get lost.
I’ve also seen a lot of confusion from people who save something to their desktop, and it’s not there… because they didn’t save it to their OneDrive desktop. This is always fun to explain.
OneDrive is also now our backup, but they only sync 3 folders from the home directory. If your work has you using other folders, good luck and enjoy your data loss. I setup a scheduled job to backup some of my other key files to OneDrive, but that was quite annoying. I’m sure I’m in the minority.
The enterprise enables all this stuff, but never actually tells anyone. They think it will “just work”, but it creates a confusing mess that every employee eventually has to figure out.
I keep my code in OneDrive. I probably have hundreds of repos cloned and active. Been going like this since like 2018 or so.
I’ve never had problems except for warnings about deleting lots of filed when I git branch or checkout or whatever.
I would expect onedrive not to pull down files after a checkout because from a file io, it’s deleting and copying in new files, right?
>One drive is an insanely poorly implemented solution to a problem nobody really had.
I highly doubt that the need to steal as much data and media from people to train AI was a problem nobody really had.
I'd guess it is more about making companies paying more and higher subs than training data.
Standard sub gives 1TB per user.
Laptop drives are still 256 or 512GB in office work.
No real need to pay for "higher subs"
You are conflating private OneDrive with enterprise Office 365 Sharepoint based solution.
Also that came out 10-13 years ago... way before AI. Why are people on this site such midwits?
I guess because the general hatred of Microsoft interferes with people's ability to think logically.
Downloads folder to the rescue, hallelujah!
The whole thing is a cobbled together bodge over SharePoint as a backend. I wouldn't ever trust my company data with that dogwater product.
Back when I had to work with it I found a bug that could cause folders to become un-synced without you realising, meaning changes would not be tracked and cause merge-conflicts when it was fixed.
Managed to use our Gold partner tickets to raise the issue with the product team, they flat out refused to fix the issue even knowing it was a bug. This was back in 2020 or so, I wonder if they ever fixed that bug. It's pretty simple to reproduce:
1. - Sync a nested subfolder from Sharepoint
2. - Sync the parent folder
3. - Note that the folder synced in 1. is not longer being tracked (no checkmark)
4. - Normal users will now go to folder 1. by default and have no idea none of their changes are no longer being tracked now that it's being synced within folder 2.
The university I attend uses SharePoint, classroom and moodle for various courses.
SharePoint is by far the worst piece of software I've ever used. Like, there's no mental model to be done, not intuitive, not working, files disappear from time to time, and I could go on for hours
Isn't sharepoint itself a cobbled together on top of Microsoft Exchange mailboxes?
Plus some WebDAV hacks via the MS Frontpage HTML editor! Truly great software engineering and design.
So it's MS products all the way down.
Somehow finding the Frontpage HTML editors down at the bottom makes it feel slightly better. At least it bring a fond memory while navigating our corporate Sharepoint horrorfest.
Plus the sync results in so many errors and duplicates even on a personal drive with one machine that it is not fit for purpose.
And as someone who worked and still works in IT support, users will not save to network drives, their machine will crash and files will be lost.
YES, you can do GPO redirect desktop etc to network drive but needs a VPN and sync is also slow.
OneDrive has solved this, like it or not.
>So when I'm on site somewhere, and have no access to a network that's safe, I can't access files that are in my documents folder, pictures or desktop.. when I never asked OneDrive to lift and shift my days off my machine.
Probably enterprise config. Standard OneDrive office 365 enterprise with SharePoint can absolutely work over the "normal internet", you don't need a "network that's safe" whatever that means. VPN? Anyway the big office 365 win was it will work over the normal internet without running /owa open on your exchange server.
>And as someone who worked and still works in IT support, users will not save to network drives, their machine will crash and files will be lost. [...] OneDrive has solved this, like it or not.
In my previous job there was an app(by Dell EMC I think) that would run every day at lunch and backup all your user document folders to some company network drive. You could then view all your backup files in the webUI.
So network backup feels like a solved problem for decades now.
However, cloud is more than just a backup solution.
Come on, a problem nobody really had? I wholeheartedly disagree. Data loss and the orthogonal problem of lacking free space on computers is/was a massive problem at enterprise scale and OneDrive, for all its many shortcomings, is well and truly into good-enough territory to cover the 80% case. I'd go so far as to argue that the scenario you've described is by far the less frequent one. And if it frustrates you, you're afforded the ability to designate files and entire folders to be kept downloaded at all times anyway.
Data loss and storage is always a challenge, that's why companies will have network drives, network storage that's not strongly coupled with your account acess. OneDrive doesn't solve the problem in a clean way. It adds an extra layer of brittleness.
Network storage does not handle the online/offline switching as transparently as OneDrive (or other cloud storage).
For large enterprises that old architecture you refer to means long lead times on network and storage outage notifications, and huge fallout if an outage window is blown.
And if the building network goes down, or if your storage servers are located off site because you’re too big for one building and the commercial internet goes down, etc etc
But it doesn’t have to be OneDrive. There are many other options. I run ownCloud 10 for my personal files. If I were a small to medium business, I would look hard at OCIS.
Network drives mean no local retention and no real good answer for Windows+Mac+Android+iOS clients to remotely access the files. It also doesn't solve sharing those files externally with granular permissions.
All of these kinds things need protection against data loss and centralized control+management, not just the user folder alone.
Sure. And you wouldn't need phishing protections if users had brains. But then you run into real users so hand-holding solutions start to make sense.
And as someone who worked and still works in IT support, users will not save to network drives, their machine will crash and files will be lost.
YES, you can do GPO redirect desktop etc to network drive but needs a VPN and sync is also slow.
OneDrive has solved this, like it or not.
Seems to me that if you want to experience data loss, Sharepoint is going to cover your needs just fine.
[dead]
F OneDrive. They locked me out without any explanation and without any notificaiton, ended my subscription and I lost valuable photos forever. Stay away from it if you are looking for storage for any reason.
Indeed, they are probably one of the worst cloud "storage" services ever to exist.
I also lost data on their platform. Not sure why anyone would like to still use them. This follows a pattern of Microsoft mishandling their user's data. They even routinely delete code hosted on their servers when they shutdown services without handling the migration well.
I'm building a digital document archive organizer platform that relies on users' own local machine storage and their cloud storage, and the only provider I trust to support are s3-compatible storage and Google drive (much as I'm wary of Google, Gdrive is reliable). Dropbox, Box, etc are also ok, but the storage is kind of expensive.
I would never support OneDrive.
Data request. Or just sue them.
You make it sound way simpler than it is. Their ToS are probably written in a way they are fully protected in cases like this.
[flagged]
There's always an excuse, or perhaps someone who actually went through it might be aware of the process and limitations better than your surface level assumptions?
‘Just sue a trillion dollar company’ does sound pretty easy.
[flagged]
This sounds very reasonable. If you stop paying then they stop serving you. Am I missing something?
The whole OneDrive ecosystem is scary as hell.
I don't want to imagine how much mess they have in their backend, given that most Microsoft 365 products rely on SharePoint in one way or another. And then, sometimes you get a "peek" of what's happening behind the scenes (spurious folders, random files appearing, hidden libraries, etc...).
Whenever I was forced to interact with OneDrive, I couldn't help imagining the proverbial digital duct tape holding everything together behind the scenes.
SharePoint/ OneDrive suck, but this policy change seems sane. What's crazy if anything is that they didn't have this policy before.
> Let me paint a familiar picture. Someone leaves your organisation, or a licence gets removed as part of a cost-saving exercise.
That's a rather weird way of phrasing it. It almost suggested that you shouldn't audit your license needs.
Other than this was always the case, it's hard to see why data stored in a close account wouldn't get deleted.
It's LLM phraseology.
It comes up with a scenario where it could be a problem ( license removal ), and then it generates why a license might get removed ( "cost-saving" ).
It's not a person thinking, so there's no real thought to whether it is really a likely scenario, it's just something that sounds plausible.
I read too many blogs, I've come to spot these phrases that trip a feeling of, "Wait, do people really do that?".
You'll still have someone along in the comments to suggest that this article isn't AI slop, and that people really do remove individual one-drive licenses from active people in an organisation to cut costs, that this is just "edited" by AI, etc.
But it's slop from start to finish. Or in LLM speak, "The slop is real".
Related story: I recently watched a new video by a well-known YouTuber whom I was subscribed to for years. Something was off with the video: the script sounded like LLM slop. It sounded as if the author provided some bullet points on the main content of the script, and then let the LLM "expand" on it, with its typical, overly verbose, mode-collapsed LLM style. Then the YouTuber seems to have added some light edits to the script himself because it did sound real occasionally.
This was just after a few minutes of video and I didn't finish watching it. At a quick glance, I didn't see anybody else pointing this out in the comments. Disappointing.
How can I be so certain about LLM usage after just a few minutes? It's both the fact that it sounded like slop, and the fact that I intuitively know his real writing style from past years, and it simply sounded very different this time.
An article about OneDrive being substantially LLM written is sort of okay (who cares about OneDrive by some Office365 blog), but if people you thought you like resort to these methods I feel betrayed.
I had something similar happen where someone linked a blog article, I thought it sounded like slop, especially since they were posting 2-3 articles a day, but I wasn't sure so I checked their back catalogue.
I then saw they've always written like that, and always posted 2-3 articles a day, so I figured they're prolific and LLMs copied their style.
Then I read their first post again, and realised I should check the wayback machine.
Sure enough, they had gone through their entire post history, and had rewritten it with an LLM, to make it less obvious when they started using them.
Now, this was always a bit of a junk site, a knock-off Boing Boing, but it seems incredible to me that someone would replace their original posts with AI gen.
Surely it destroys any reputation you might have?
A site they've been running for nearly 20 years, overwritten by slop.
Compare:
Original: https://web.archive.org/web/20191017113113/https://www.geeky...
Rewritten slop: https://www.geeky-gadgets.com/metal-detecting-sandals/
Damn this is horrible. So the author chose to waste everyone's time by expanding with cow manure. I generally don't read much articles online anymore since they are all likely to contain slop unless authored by known non-slop users.
Also the deletion will kick in after 12 months
> Day 1: licence removed or user deleted: The clock starts. The OneDrive account is now unlicensed and the retention countdown begins.
> Day 60: read-only mode: No more edits.
So yeah if you spend 12 months without realizing you might need the data of someone who left then I think that's on you
Data is on pragmatic lockout after 3 months, not 12.
For years, enterprises have been conditioned to lean into OneDrive and forget about it. Indeed, that dark pattern is a festering disease across consumer Windows.
This is classic Microsoft long rug pull.
> Someone leaves your organisation
https://learn.microsoft.com/en-us/sharepoint/retention-and-d...
"By default, when a user is deleted, the user's manager is automatically given access to the user's OneDrive"
Seems like it should be enough time to firesale the data out you need as a manager.
Retention and legal holds: Data can still be deleted even if a retention policy or legal hold is in place, unless licensing or billing is restored first. Do not rely on holds alone to protect unlicensed data.
Surprising it doesn't automatically move into an admin or company lawyer's drive so it can be dealt with rather then a few notifications which will probably be missed and the data permanently deleted.
Don’t worry, you have ~30 days, that should be enough for you to audit your entire org. /s
That number has no connection to the actual system.
In an enterprise environment onedrive is perfectly fine. Yet so many developers think they're to good for it. They save their things outside of onedrive and low and behold they lose data. Its so dumb and im yet to hear a good reason why they couldnt have used onedrive.
That happened to me many yeas ago with Dropbox.
I had all my old android's phone gallery there and many years ago. I tried getting them and they were all removed. All my memories removed.
If you start uploading data to your cloud without my clear consent, I already see a very big problem with your product.
If you even substitute the directories in my computer (a standard that was untouched for the last 20 years) in a way to force my stuff into your cloud, then there’s a much bigger problem.
Managers who approved this should be thrown out of the company because this is clearly how NOT to make a product.
Microsoft had the idea that PCs are like phones.
Google/Apple sync everything in the background so Microsoft wanted to do it as well.
You can find multiple comments on past OneDrive posts from people who are/were at Microsoft with frankly terrifying stories of them losing their own or customer data. They all said the same thing: Do not use or trust OneDrive.
IIRC one of the funnier examples was users, their managers, and so on all the way up the chain (perhaps including HR and Legal) being let go resulting in there being no user to transfer the ownership/access to so it was simply deleted.
I'm really confused by the article. What the hell does unlicensed mean? Does unlicensed means free (as in free personal onedrive accounts)?
Don’t put your data in onedrive at all. We’ve experienced multiple cases of data loss which were definitely either implementation bugs or files simply being unreadable or lost.
Pretty fair... if you don't pay, the data doesn't stay
I'm not against getting help from AI when writing, but at least take some time to make sure it's not place-filler slop.
AI;DR: Starting from early July 2026, all associated data will be deleted 12 Months after a user license is removed.
Nah, this is just slop.
Took me 10 seconds to find this better link: https://mc.merill.net/message/MC1381110
This will have a huge impact on a lot of organisations, for example those that have a communal SharePoint, or shared document page: files shared from ex-employees for critical documentation is going to break.
Arguably, this situation is already broken right now. If an organization can't be bothered to use their tools (Sharepoint and the wider O365 ecosystem) correctly, it's entirely on them.
Organization employees use tools in a way that is practical for them. In microsoft case, it often means "incorrectly" and that is on Microsoft too.
AFAIK Sharepoint doesn't have these limitations. The idea is that in companies OneDrive should not be used for permanent stuff. Which is strange, to be granted, but after all using OneDrive for company documents basically means they are being shared out of some personal space that doesn't belong anywhere.
>shared out of some personal space that doesn't belong anywhere
Do you care explaining this better?
(moreover, to this day I still can't understand the difference between SharePoint and OneDrive -- if there's any)
Do you see "personal" and something that looks like your name in the path? That's your personal onedrive, like your home directory on a unix system.
See "sites" in the URL? That's a sharepoint site (AKA teams "shared" folder).
The former disappears (after a year) when the user license is removed. The latter is not associated with an individual user, so even if everyone in a team leaves the company it isn't just automatically removed.
Following was wrong and had been edited: The non-business personal onedrive was a box.com/dropbox/g-drive competitor. Microsoft moved its backend to Sharepoint at some time. (Onedrive for business used Sharepoint from the get-go). The integration of the personal drive, even though it's a descendent from the 'for business' product, is still quite unintuitive in my opinion.
Odfb has always had a SharePoint backend. Used to be called MySites and carried no relation to the consumer product you’re confusing it with.
Exactly this!
And if they haven't migrated the ownership of the OneDrive to another user's account in 12 months (such as cascading the drive up to the next manager to pull out whatever docs)... what kind of other bad IT and managerial practices are in use?
The worst managerial practice is to use OneDrive for company work purposes. For anybody else than the original creator these docs are nowhere to be found unless you know the shared URL.
This will cause some major headaches.
OneDrive itself should have expired years ago.
Joke of a company
"Your OneDrive data..."
No, it's not my OneDrive data. What an infuriatingly click-bait title.
It's OneDrive data for individaul user accounts at organisations that are unlicensed (probably, as the article says, for people that have left).
I'm also unsure what they wanted Microsoft to do. Just store data that apparently doesn't belong to anyone anymore forever?
Don't use Microsoft OneDrive. They mine your data and share it with the US government. And - as the International Criminal Court staff has recently discovered - they will cut you off from your data if they, or the US government, decide they don't like you.
[dead]
I wonder why FTP is not enough?