6.1 Creating a New Document from a Prompt
Key Takeaways
- Microsoft Copilot in Word provides two core authoring modes: blank-canvas generation from comprehensive natural language prompts and grounded generation referencing up to 3 enterprise source files via the '/' command.
- Grounded document creation preserves organizational context, corporate terminology, and factual accuracy by extracting content directly from SharePoint or OneDrive stored documents.
- The on-canvas 'Draft with Copilot' dialog enables rapid iterative refinement, allowing users to regenerate, modify prompts, or discard candidate drafts before accepting them into the document canvas.
- In-line transformation features—including 'Rewrite with Copilot', tone adjustments (Professional, Casual, Concise), and length controls—allow targeted section-level polishing without altering unaffected text.
- The 'Visualize as a Table' feature automatically parses unstructured narrative paragraphs or bulleted lists into formatted, editable Word tables with distinct categorical column headers.
6.1 Creating a New Document from a Prompt
Quick Answer: Microsoft 365 Copilot in Word offers two fundamental document drafting paths: blank-canvas generation driven entirely by natural language prompt instructions (specifying goal, persona, audience, structure, and tone), and source-grounded generation referencing up to three existing files using the
/reference command. Once text is generated, professionals can perform granular, in-line modifications—including Rewrite with Copilot, tone adjustments (Professional, Casual, Concise), section expansion or condensation, and instant conversion to formatted tables via Visualize as a Table.
In modern enterprise workflows, document authoring is rarely a one-time generative event. Business professionals frequently transition between creating original proposals from raw ideation, synthesizing formal client deliverables grounded in existing project charters, and refining dense technical prose to match executive standards. Mastering Microsoft 365 Copilot in Word requires understanding both initial document generation mechanics and subsequent in-line transformation workflows.
1. Document Creation Modes in Microsoft Word
When launching Microsoft Word with a Copilot license, users encounter the Draft with Copilot interface directly on the blank canvas. Word supports two distinct generation paradigms:
┌─────────────────────────────────────────────────────────────────────────────┐
│ WORD COPILOT DRAFTING PARADIGMS │
├──────────────────────────────────────┬──────────────────────────────────────┤
│ BLANK-CANVAS GENERATION │ SOURCE-GROUNDED GENERATION │
│ │ │
│ User Prompt Instructions │ User Prompt + '/' Source Files │
│ [Role + Goal + Audience + Tone] │ [Charter.docx, Transcript.docx] │
│ │ │ │ │
│ ▼ │ ▼ │
│ Copilot Orchestration Engine │ Microsoft Graph Retrieval (RAG) │
│ │ │ │ │
│ ▼ │ ▼ │
│ Azure OpenAI Foundation Model │ Azure OpenAI Grounded Synthesis │
│ │ │ │ │
│ ▼ │ ▼ │
│ Original Structured Document Draft │ Factual, Cited Enterprise Output │
└──────────────────────────────────────┴──────────────────────────────────────┘
Blank-Canvas Generation (Prompt-Driven Drafting)
Blank-canvas generation creates completely new documents based exclusively on the prompt instructions supplied by the user. Because Copilot does not have an attached file to anchor its facts, the user must provide explicit structural and stylistic guardrails.
- Ideal Use Cases: Brainstorming campaign strategies, drafting standard business policies, outlining initial project frameworks, or authoring customer communication templates.
- Essential Prompt Parameters:
- Persona & Role: "Acting as a Senior Enterprise Change Management Consultant..."
- Target Audience: "Drafted for plant managers and frontline logistics staff..."
- Structural Blueprint: "Include an Executive Summary, a 4-phase Implementation Timeline, and a Risk Mitigation Matrix."
- Tone & Register: "Maintain an authoritative, actionable, and formal business tone."
2. On-Canvas Dialog vs. Copilot Side Pane in Word
Microsoft Word provides two distinct user interfaces for interacting with Copilot. Understanding when to use each interface is critical for operational efficiency and Exam AB-730 questions.
┌─────────────────────────────────────────────────────────────────────────────┐
│ ON-CANVAS DIALOG VS. COPILOT SIDE PANE │
├──────────────────────────────────────┬──────────────────────────────────────┤
│ ON-CANVAS "DRAFT WITH COPILOT" │ COPILOT SIDE PANE │
│ │ │
│ • Appears directly in document body │ • Persistent right-hand task pane │
│ • Activated on blank lines or │ • Activated via Ribbon 'Copilot' │
│ via the left margin icon │ button │
│ • Designed for: Text generation, │ • Designed for: Q&A about the doc, │
│ section drafting, and rewriting │ summarizing, cross-file research │
│ • Output directly enters canvas │ • Output stays in pane until copied │
└──────────────────────────────────────┴──────────────────────────────────────┘
The Review and Acceptance Lifecycle
When Copilot finishes generating text via the on-canvas dialog, the content is rendered in a temporary preview state. The user is presented with four critical controls before the text is permanently merged into the document:
- Keep it: Accepts the generated draft, applying Word's active stylesheet and merging the text into the document body.
- Regenerate: Re-runs the prompt to generate an alternative variation of the content.
- Edit Prompt / Adjust: Allows the user to modify prompt parameters (e.g., "Make the third paragraph shorter and add a bulleted list of deliverables") without starting over.
- Discard (Trash Icon): Deletes the draft entirely, leaving the document in its previous state.
3. Prompt Engineering for Document Generation: GCSE in Action
To achieve consistent, production-grade output in Microsoft Word, business professionals must apply the GCSE Framework (Goal, Context, Source, Expectations):
+-------------------------------------------------------------------------+
| WORD PROMPT SPECIFICATION BREAKDOWN |
+-------------------------------------------------------------------------+
| [GOAL] -> "Draft a formal 3-page Commercial Project Proposal..." |
| [CONTEXT] -> "...for the Chief Technology Officer of Fabrikam, |
| addressing our cloud infrastructure migration." |
| [SOURCE] -> "...grounded strictly in /Project_Charter_2026.docx |
| and /Fabrikam_Discovery_Call_Transcript.docx." |
| [EXPECTATIONS]-> "Structure with: Executive Summary, Proposed Solution, |
| Milestone Table, and SLA Commitments. Maintain a |
| formal, confident tone. Do not invent pricing terms." |
+-------------------------------------------------------------------------+
Step-by-Step Prompt Refinement Workflow
| Iteration Step | User Prompt Input | Result & Operational Rationale |
|---|---|---|
| Step 1: Initial Draft | "Draft a project brief for Fabrikam based on /Charter.docx." | Generates a generic 2-page overview; lacks specific SLA commitments and executive tone. |
| Step 2: Structural Refinement | "Rewrite to include four distinct sections: Executive Summary, Architecture Overview, Implementation Milestones, and Risk Management." | Re-organizes text into clear headings; adds professional hierarchy. |
| Step 3: Tabular Formatting | (Highlighting Milestones) "Visualize as a table with columns: Phase, Deliverable, Target Date, and Responsible Owner." | Converts bulleted narrative into an actionable, structured project tracking grid. |
| Step 4: Tone Polishing | (Highlighting Executive Summary) "Rewrite in a Concise and Professional tone, keeping total length under 150 words." | Sharpens value proposition and removes wordy transitions for C-suite readability. |
4. Realistic Business Scenario: Generating an Enterprise Bid Proposal
Business Context
Maria is a Senior Solutions Architect at Contoso Cloud Services. She must prepare a formal 5-page Statement of Work (SOW) for a prospective banking client, Woodgrove Financial. The source materials consist of an internal technical architecture specification (/Woodgrove_TechSpec.docx) and a recorded client discovery session transcript (/Discovery_Meeting_Transcript.docx).
Execution Process
- Canvas Initialization: Maria opens a blank Word document formatted with Contoso's official corporate typography and margins.
- Prompt Submission: In the "Draft with Copilot" dialog, Maria inputs:
"Draft a formal Statement of Work for Woodgrove Financial. Acting as the Lead Cloud Architect, synthesize the technical requirements and project scope. Ground the document strictly in
/Woodgrove_TechSpec.docxand/Discovery_Meeting_Transcript.docx. Include the following sections: (1) Business Objectives, (2) Hybrid Cloud Architecture, (3) Migration Phases, and (4) Compliance Guardrails. Maintain a professional, authoritative tone. Do not introduce speculative hardware costs not listed in the technical specification." - Review & Iterative Edit: Copilot streams the 4-section draft. Maria reviews the Migration Phases section, highlights the paragraph describing cutover timelines, and clicks Visualize as a Table to produce a 4-column deployment schedule.
- Acceptance: Satisfied with the structured output, Maria clicks Keep it, committing the AI-generated SOW into her document canvas.
5. Exam Tips & Governance Warnings
[!IMPORTANT] Core Principles for Exam AB-730
- Reference Limits: Word Copilot allows referencing up to 3 files simultaneously in a single generation prompt.
- Sensitivity Label Inheritance: When Copilot generates a document grounded in a source file marked Confidential, the newly generated Word document automatically inherits the most restrictive sensitivity label applied to the source files via Microsoft Purview.
- Active Document Stylesheet: Text generated via Copilot automatically inherits the existing Word template's typography, header styles, and paragraph spacing, ensuring corporate design consistency.
- Human Accountability: Generated text must always be reviewed by a subject matter expert. Copilot is an authoring accelerator, not an autonomous legal or technical signatory.
A business analyst needs to draft a customer project brief in Microsoft Word. What is the primary operational difference between using the on-canvas 'Draft with Copilot' dialog versus using the Copilot Side Pane?
A proposal manager attempts to ground a new Word document in an existing technical specification using the '/' reference command. However, the target document does not appear in the file picker. What is the most likely cause of this issue?