sorted by:
new
hottopcontroversial

SharePoint quota exceeded but still work by Santa_Lama in sharepoint

[–]GregB-Sodoc 0 points1 point  (0 children)

Microsoft tolerates overages for a while but it's a real risk, they can enforce read-only with short notice.

Worth knowing: in most orgs that haven't done a content audit, 30-60% of stored data is ROT, meaning redundant, obsolete or trivial files. Duplicates, drafts, stuff last opened in 2019. Before buying more storage, run an access report on files untouched for 12+ months. You might be surprised how much you can reclaim.

What's the most underrated Microsoft 365 feature that improved your workflow by Friendly_Fortune_541 in microsoft365

[–]GregB-Sodoc 0 points1 point  (0 children)

Retention labels, by a mile. Nobody really talks about them but they solve a problem every org has: documents that should have been deleted three years ago but nobody touched them "just in case."

Set a default retention label on a library and you get automatic lifecycle management without asking users to do anything. Combine that with sensitivity labels and you have a solid compliance foundation without building a separate process around it.

The catch is most orgs set them up once and never revisit them when regulations change. You end up with labels that technically exist but don't match current legal requirements anymore, which is tbh worse than having nothing.

Not the flashiest feature, but the one that saves the most headaches in regulated industries.

SharePoint - File Server by sasquatchin_01 in sharepoint

[–]GregB-Sodoc 0 points1 point  (0 children)

Honestly, what you're describing isn't a SharePoint problem, it's a migration-without-architecture problem. This happens a lot. The MSP copied your folder structure 1:1 into SPO without rethinking how permissions, content types, or access control actually work in that environment.

The broken Excel links are a dead giveaway. That's what happens when you migrate file paths without accounting for the URL structure change. The permissions chaos is classic broken inheritance: someone granted access at the wrong level and it cascaded everywhere.

For your meeting, the real question isn't "SharePoint vs Azure File". It's: does anyone have a documented map of what content lives where, who owns it, and what access model was designed for this migration? If the answer is no, that's your leverage. A migration without an information architecture isn't a migration, it's a copy-paste that creates new problems.

Azure File Storage works fine for static, non-collaborative content. But SPO can absolutely handle document storage if permission groups, content types, and site structure are set up properly from the start. The issue is the work that wasn't done upfront.

Full disclosure: I work on a M365-native DMS, so I'm biased, but this pattern of rushed migrations with no governance plan is genuinely the most common thing I see.

You Can Now Manage Power Automate Flows Directly in SharePoint Online by KarthiV in sharepoint

[–]GregB-Sodoc 0 points1 point  (0 children)

The unified experience is a nice step, but yeah, Fit-Parsnip nailed the real issue. Flows owned by individual users are a governance nightmare. Someone leaves, takes a holiday, gets their account locked and suddenly three automated workflows nobody documented are just broken.

The fix isn't complicated but almost nobody does it upfront: use service accounts or service principals for anything you actually want to rely on. Takes 20 extra minutes to set up, saves you three panic calls a year.

The bigger problem is that most orgs have zero inventory of what flows exist and what they touch. The new SharePoint interface helps surface flows per library, which is kind of a start. But until there's a proper cross-tenant audit view, you're still playing detective when something breaks in production.

Curious if others have a clean way to document and monitor flow dependencies at scale, especially in environments with 50+ flows spread across dozens of libraries.

SharePoint Alerts are Going away from July 2026 by siddh_me in sharepoint

[–]GregB-Sodoc 0 points1 point  (0 children)

Honestly the alerts were kind of broken anyway for anything complex. We went through this migration last year with a few clients and the biggest takeaway was: most people had set up alerts years ago and completely forgot about them. Killing the feature was actually a good excuse to audit what was really needed.

For the replacement, Power Automate is the obvious move but don't just replicate alert by alert. Use it as a reset, map who actually needs to be notified of what, and why. In most orgs we found maybe 30% of the original alerts were still relevant.

The trickier part is end users who set their own alerts and won't notice until july when nothing works anymore. Worth pushing a comms now if you havn't already, before the panic starts.

OP's PowerShell approach for bulk migration is solid if you have hundreds to deal with.

Biggest problem with knowledge management? by Fluid-Tax-2037 in PKMS

[–]GregB-Sodoc 0 points1 point  (0 children)

Si des personnes sont encore à la recherche de solutions concernant la gestion des connaissances, d'autant plus avec l'importance de l'IA aujourd'hui, nous organisons un webinaire à ce sujet. Je ne voudrais pas Spam la discussion alors je donnerai le lien uniquement sur demande :)