SharePointVault ~/ ⌕ Search 404 pages, error messages, scripts…Ctrl K ★ Star
M↓ README.md◆ start-here
sharepoint-vault›start

Start here

Hundreds of notes are a lot to browse. These short lists pick the ones worth reading first.

Reading paths by role

  • Start here: SharePoint adminFor SharePoint Online admins and IT pros who run the tenant with PowerShell and the admin center. After this path you can inventory sites, audit permissions and sharing, keep big lists and search healthy, and find where storage goes.
  • Start here: SPFx developerFor developers who build SharePoint Framework web parts and extensions and ship them to the app catalog and Teams. After this path you can call SharePoint REST correctly, package and deploy without surprises, debug runtime errors and render list content safely.
  • Start here: Graph and REST from outside SharePointFor developers who call Microsoft Graph or SharePoint REST from scripts, services and Azure Functions rather than from a page in SharePoint. After this path you can pick the right API and permission model, write queries Graph accepts, retry safely and deploy a function app that stays up.

Top 10 lists

  • Top 10 throttling and limits trapsSharePoint and its neighbours enforce limits that stay invisible until a list grows or a loop speeds up. These ten cost the most time, from the 5,000 item threshold to 429 responses that quietly corrupt data.
  • Top 10 permissions and sharing trapsPermission mistakes in SharePoint rarely fail loudly: they either lock out the people who need access or leave content open to everyone. These ten are the ones that most often cost a day of investigation or a data exposure.
  • Top 10 SharePoint REST write trapsReads forgive a lot, writes do not: a wrong body, date or fallback can lose data while the response still says success. These ten write traps cost the most time to diagnose and the most data when missed.
  • Top 10 Microsoft Graph trapsMicrosoft Graph looks uniform, yet permissions, query options and mailbox rules differ by endpoint and licence. These ten traps cost the most time when building on Graph, whether from a script, a service or SPFx.
  • Top 10 search and KQL trapsSharePoint Search often answers HTTP 200 even when the query, the property or the index is wrong, so failures hide as empty or oversized results. These ten traps cost the most time for anyone building search, reports or RAG on top of it.