SharePoint.
SharePoint is Microsoft's document management and collaboration platform, providing document libraries, metadata, permissions, versioning and workflow, integrated with the wider Microsoft 365 estate.
Where SharePoint fits on a long engagement.
SharePoint is where organisational documents actually live, and its value depends entirely on structure. Libraries with meaningful metadata support search and automated routing; libraries used as folder trees reproduce a shared drive with more steps and none of the benefits.
Permissions are where SharePoint estates become unmanageable. Inheritance broken at item level in thousands of places produces a permission model nobody can reason about, and answering who can see a document becomes genuinely difficult.
What an assigned team does with SharePoint.
Integration is usually the reason to work with it programmatically: pulling documents into other systems, automating filing, or driving approval processes from content.
That work sits inside ordinary development capacity rather than being a platform specialism, assigned under outsource software development services.
What we use SharePoint for.
- Metadata rather than folder trees Structure that supports search and routing instead of reproducing a shared drive.
- A permission model that can be reasoned about Inheritance preserved, so access is answerable.
- Document processes automated Filing and approvals driven from content rather than done by hand.
How SharePoint capacity is assigned.
Document platform work is assigned inside development capacity, with information structure treated as the determinant of whether the platform helps.
Tell us what your roadmap needs SharePoint for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.