"Clear everything off of SharePoint you don't need, we're running out of room."
"The shared drive is full, we're going to purge everything not in one of the special directories. See the list."
AFS, as used at my university in the 00s, nicely reduced this problem by greatly expanding the amount of storage capacity available. It also helped speed up access to data by moving it to the system you were working on (assuming it was also an AFS node and not your personal device, in which case it was exactly like accessing a remote disk). It also helped with the "SharePoint is down again because even though we're a multibillion dollar corporation we're too cheap to hire real IT staff and Bob the Build Engineer tasked with keeping it up is on vacation." Local copies of data remained accessible.
In some ways it was self-fulfilling - corporate offices didn't use it, so there wasn't a great ecosystem, so corporate offices did not use it.
There were a handful of vendors, all with drawbacks. On a large network, AFS, or particular cells or filesystems could get into a weird state. It was not like Solaris NFS where most senior sysadmins understood the filesystem error states.
You want to feel you are putting data into something safe, permanent and always accessible, and AFS never felt like that in corporate environments I was in.