You can improve SharePoint without committing to a Copilot rollout. If the immediate problem is inappropriate access, unclear ownership, hard-to-find information, or an uncertain migration, begin with that business problem and a bounded written scope.
GlobalAdmins offers four SharePoint consulting starting points: a problem assessment, permissions and ownership repairs, an architecture and findability plan, and migration assessment and validation. The initial consultation checks fit. A professional assessment and any implementation are separately scoped work, with staffing, dates, fees, and acceptance agreed before delivery.
Which situation describes your team?
The scenarios below are examples of questions a buyer might bring, not customer case studies or promised results.
| Situation | Useful first scope | What the customer should be able to review |
|---|---|---|
| “We know SharePoint is a problem, but do not know where to start.” | A representative problem assessment | Observations, priorities, owners, and a proposed next boundary |
| “Sensitive content has broad access.” | Permissions and ownership review | Intended audience, observed access, proposed changes, approvals, and validation |
| “People who need content cannot open it.” | A bounded access investigation | Affected users and sites, intended access, findings, and approved correction checks |
| “Nobody can find the current document.” | Architecture and findability discovery | User tasks, content ownership, navigation and metadata decisions, and test criteria |
| “We have too many ownerless or inactive sites.” | Ownership and lifecycle assessment | Customer owners, review decisions, exceptions, and feasible governance options |
| “We need to move file shares or an on-premises SharePoint environment.” | Source-specific migration assessment | Inventory, supported tooling, identity mapping, dependencies, pilot, and acceptance plan |
| “The migration finished, but work is still broken.” | Post-migration exception and validation review | Available transfer evidence, user checks, unresolved items, and a feasible repair scope |
| “We may want Copilot later.” | The SharePoint scope that addresses today's blocker | A separate decision about whether readiness review or a controlled pilot is appropriate |
What a SharePoint assessment should deliver
Agree the sites, users, policies, and issues to sample. Record what was observed, its business impact, the accountable owner, and the next action. Distinguish evidence from a hypothesis that needs another check.
The handoff should make the next decision easier: approve selected repairs, commission an architecture plan, pilot a migration, gather missing evidence, or pause. It should also show what was not reviewed. An assessment does not silently include an unlimited cleanup or implementation project.
Microsoft's content management assessment documentation describes native reports for ownership, inactive sites, inheritance, and broad sharing. Where licensed and available, those reports can provide inputs. Consulting adds the agreed business boundary, customer decisions, approved changes, validation, and operating handoff; generating a report alone does not complete those responsibilities.
Architecture and repairs have different acceptance questions
An architecture engagement starts with the work people need to do. A proposed site, hub, navigation, or metadata design should be tested against representative user tasks. Use the architecture planning checklist to define the design and validation boundary.
A permissions repair starts with intended access and customer approval. Record the proposed change, its impact, the person who authorizes it, the result, and any exception that remains. Do not assume that everyone needs access just because one user cannot open a file. A security incident or active compromise needs its own incident-response process, not an ordinary architecture engagement.
Migration needs source-specific discovery
File shares, on-premises SharePoint, another cloud service, and a tenant-to-tenant move can have different tooling, identity, licensing, and validation requirements. They should not receive an interchangeable implementation promise.
Microsoft's Migration Manager overview describes supported migration paths and preparation. That is product guidance, not proof that a particular customization or workflow will move unchanged. GlobalAdmins confirms the source and feasible scope during discovery. Complex custom applications or tenant consolidation may require a separate specialist scope.
For a planned move, start with the migration readiness checklist. For a completed move, use the customer acceptance plan to separate job completion from usable content, correct access, and accepted exceptions. Recovery of every missing item is not guaranteed.
Copilot can remain a later decision
Standalone SharePoint work does not require a commitment to buy Copilot. Some advanced governance capabilities have separate prerequisites. Microsoft documents SharePoint Advanced Management licensing and access requirements, including a standalone add-on route. Confirm the actual tenant's licenses and roles before relying on a report or control; this guide is not a license quote or entitlement determination.
If the next question becomes what proposed Copilot users can reach, consider the Copilot Data Exposure Sprint. If that access boundary is understood and the question is workflow usefulness, consider the Secure Copilot Pilot. Neither step is automatic or required to make standalone SharePoint improvements useful.
Prepare the first conversation
Describe the business problem, approximate site or content scope, decision owner, and timing. Label unknowns rather than inventing a complete inventory. Do not send passwords, confidential documents, or sensitive tenant exports through the inquiry form.
Request a SharePoint consultation to choose the evidence and next scope your team needs. A request does not book a meeting or confirm a delivery date.