You can start a Copilot consulting conversation with the decision your team faces, an approximate environment size, the sponsor, and the timing. You do not need to send passwords, customer documents, or confidential tenant exports in an initial inquiry.
GlobalAdmins uses written intake to identify the question and prepare a human discovery conversation. A consultation request does not book a meeting or confirm an engagement. The actual participants, availability, scope, and next step are agreed separately.
Explain the business decision
Describe what your team needs to decide: whether to enable Copilot for a group, review sharing before expansion, test a workflow, or understand low adoption. State the consequence of waiting and any known deadline without assuming it creates an emergency delivery commitment.
A useful example is: “We need to decide whether our proposed pilot group can use two document workflows, but site ownership and broad sharing are unclear.” That gives discovery a purpose without disclosing the documents themselves.
Give approximate scope
| Bring to discovery | Why it matters |
|---|---|
| Approximate employee and proposed user counts | Identifies the rollout and participant boundary |
| Approximate SharePoint site count and relevant OneDrive policies | Helps bound an access review |
| Current Copilot stage | Separates preparation, pilot, and adoption questions |
| Two candidate workflows, if known | Gives a pilot or value review a testable purpose |
| Known access or reporting dependencies | Makes prerequisites visible before a proposal |
Estimates are acceptable for the first discussion. Label unknowns as unknown instead of inventing a complete inventory. A later scoped review may establish a more precise boundary.
Identify the people who own the decisions
Bring a sponsor who can explain the outcome, a Microsoft 365 or SharePoint owner who understands the environment, and a security reviewer when access is part of the decision. These may be different people. Identify who can approve changes and who will accept the findings.
GlobalAdmins confirms the actual human discovery and delivery participants before scheduling or committing to work. A shared inbox is a contact route, not evidence that a particular consultant or time slot is available.
Separate the possible engagement paths
The readiness assessment reviews a bounded access and sharing question. The Secure Copilot Pilot evaluates selected users and workflows. The adoption engagement measures use and two workflow outcomes after access exists. Our assessment-versus-pilot guide explains the different decision boundaries.
You do not need to choose the package name before making contact. Explain the decision first; discovery determines the fit and any prerequisites.
What belongs in the written proposal
Before delivery, agree the deliverables, exclusions, customer responsibilities, evidence handling, access process, acceptance criteria, staffing, timing, fee, and payment milestones. Scope changes need their own approval. A generic public timeline is a planning boundary, not a confirmed start date for your environment.
Microsoft's deployment governance guidance provides technical context for a governed rollout. Your actual controls and licensing still need confirmation during scoping.
Describe your consulting request. Keep the initial message to the decision, approximate scope, sponsor, and timing; use an agreed private process for any evidence needed later.