OpenText VIM and SAP Insights.
Helping future-focused leaders navigate what’s next:
Microsoft 365 Backup is not your retention policy
Microsoft 365 Backup restores sites and mailboxes to a point in time, on a clock apart from Purview retention. Records owners should know what it keeps.
Retention policies that archive: what Copilot stops seeing in SharePoint
Retention policies can soon archive SharePoint files. They stay under retention and in eDiscovery, but drop out of Copilot. Choose the archive clock with care.
Copilot Studio agents: decide which SharePoint sites they may read
Power Platform admins can now limit which SharePoint sites Copilot Studio agents read, and post the rules where makers build. The site list is a records call.
Default library labels in SharePoint now reach the files already there
Default sensitivity labels on SharePoint libraries used to skip older files. A Purview policy now labels them, ten sites at a time. Pick the order with care.
SharePoint version history limits: decide the restore window before the trim
SharePoint keeps 500 versions per file by default. Changing that, or trimming old versions, is a records decision, and trimmed versions skip the recycle bin.
Every guest in Microsoft 365 needs a sponsor and an end date
Guest accounts outlive the projects that created them. Give every Microsoft 365 guest a named sponsor and a clock that ends access unless someone renews it.
Oversharing in SharePoint: who answers the site access review
SharePoint can now list every item shared with your whole company. Fixing it falls to site owners through access reviews, so brief them before the first email.
Who may build a flow that touches a business record?
Any licensed user can build in the Power Platform default environment. Decide where flows touching business records live, and who owns them, before they spread.
Microsoft 365 Archive is a records decision with a storage meter attached
Microsoft 365 Archive moves SharePoint content to a cold tier in the tenant. Price is the easy part; who decides what goes cold, and who wakes it, is harder.
Purview labels as records discipline on the tenant you already license
Purview works when the policy comes first: a short file plan, a named records owner, and the labeling G5 already includes. Copilot readiness follows from it.
SharePoint search after the move: tuning, ownership, and when to build
SharePoint search drifts after launch. Name a search owner, read failed queries, fix with bookmarks and acronyms first, and build custom web parts sparingly.
Rebuild, don't lift: moving an old intranet to a SharePoint Online hub
Moving an old intranet to SharePoint Online? Rebuild, don't copy: inventory content, leave the rest behind, name site owners, and cut over without dead links.
AI readiness on Microsoft 365: finish the intranet on G5 first
Finish the Microsoft 365 intranet on the G5 you already own before optional AI. Treat Copilot-era features as reversible when the organization is ready.
SharePoint Online findability without expensive redesign theater
SharePoint Online findability usually fails from weak information architecture and not a missing redesign. Fix hubs, labels, and search before expensive theater.
Access model first: intranet success is who can see what
Intranet success starts with who can see what: Entra groups, RBAC, and permission-respecting SharePoint—not greyed-out links that still leak titles today.