Microsoft has begun rolling out a much-requested capability for Microsoft 365 Copilot Notebooks: the ability to add Outlook emails as explicit references. The feature, tracked as Roadmap ID 564910, entered preview in June 2026 and is slated for general availability in July 2026. It lets users select specific email messages and add them to a Copilot Notebook, where they can serve as grounding material for AI-generated summaries, analyses, drafts, and answers.

What Actually Changed

Until now, Copilot Notebooks could reference files stored in OneDrive, SharePoint, meetings, Copilot Pages, and other content types—but not emails. The new integration adds Outlook messages as a first-class reference category. When you create or edit a notebook, you can browse, search, and pick individual emails from your mailbox (or a shared/delegated mailbox, provided you have the right permissions) and pin them into the notebook alongside the other source material.

Microsoft’s documentation makes it clear that this is not an open-ended inbox search for Copilot. The notebook only uses the references you deliberately add. That means no automatic ingestion of your entire email history; you curate which threads become part of the project’s AI context. Once added, the messages behave like any other reference—they stay current as underlying content changes, and Copilot can cite them in its responses.

The roadmap entry frames the feature as a way to bring “email conversations, decisions, and working context directly into the notebook experience.” Practically, that means a notebook for a product launch, an account review, or an executive decision brief can now include the email thread where a stakeholder approved a budget, a customer clarified a requirement, or a team debated a timeline change.

What It Means for You

The impact varies depending on how you work, but the common thread is richer project context with less manual reconstruction.

For knowledge workers and decision-makers

If you regularly prepare briefings, status reports, or decision logs, you likely spend time piecing together information from documents, meetings, and email chains. Copilot Notebooks with email references can dramatically reduce that toil. You assemble the formal artifacts—the project plan, the spreadsheet, the presentation deck—and then add the handful of emails that contain the actual reasoning behind the changes. Ask Copilot to draft an executive summary, and it can now weigh the board-approved strategy against the follow-up thread where a key executive added a condition.

For sales, account, and customer-success teams

Client-facing professionals often receive requirements, caveats, or approvals via email that never make it into the CRM or SOW. By adding those messages to a customer-specific notebook, a team can generate more accurate account reviews, renewal strategy documents, and meeting briefs. The important word is “selected.” You don’t dump every exchange; you choose the messages that document decisions, commitments, and exceptions.

For product and engineering leads

Technical projects generate a lot of decision-making in email—design choices, dependency clarifications, risk assessments. A notebook that combines the approved specification, the latest sprint notes, and the email where the architect confirmed a trade-off becomes a powerful tool for creating release readiness docs or onboarding new team members. It is not a replacement for an architecture decision record, but it is a practical safety net when formal records lag behind the conversations.

These areas can benefit from the feature but must exercise extra caution. Email threads often contain nuance, negotiation positions, and sensitive information that may not be reflected in final contracts. Copilot can accelerate draft preparation, but any output must be rigorously reviewed against the original messages. The notebook’s scoped grounding is a governance advantage—you control exactly which emails the AI sees—but the ultimate accountability for accuracy rests with the human reviewer.

How We Got Here

Microsoft 365 Copilot Notebooks were designed from the start to be curated workspaces, not open-ended search engines. Microsoft explicitly states that Copilot does not access your entire OneDrive, email, or Teams chats when you use a notebook; it grounds answers only in the references you provide. This “scoped grounding” model is both a strength and a deliberate constraint.

Earlier reference types—Word documents, PowerPoint decks, Excel workbooks, PDFs, meeting notes, and Copilot Pages—covered the formal outputs of work. But they left a blind spot: the reasoning, negotiation, and informal decision-making that happens in email. Microsoft 365 Copilot already supported referencing emails in Copilot Chat, where the system could surface relevant messages based on signals like mentions, flags, and sender similarity. But those were one-off prompts, not persistent project context. Roadmap ID 564910 closes that gap by making selected email content a reusable part of a notebook’s corpus.

The timing aligns with a broader shift in enterprise AI: moving from “ask any question across all your data” to “build a bounded, accountable context for a specific task.” Adding email to the mix makes the notebook more representative of how real work actually gets done—across multiple apps, with critical context often buried in a reply-all chain.

What to Do Now

If you have access to Microsoft 365 Copilot and the Outlook email references feature (preview or general availability), here’s how to start using it effectively.

1. Define the notebook’s purpose narrowly

Avoid creating a generic “Project X” notebook. Instead, tie it to a specific decision, deliverable, or review cycle. Examples:
- “Q3 executive decision brief for Project Aurora”
- “Contoso renewal: customer requirements and risks”
- “Windows 11 deployment: regional readiness review”

A clear scope makes it easier to decide which emails belong.

2. Add authoritative files first

Start with the formal sources that represent the agreed-upon plan:
- Approved project charter or brief
- Latest roadmap or timeline
- Budget spreadsheet or forecast
- Customer statement of work
- Meeting notes or decision log

This establishes the baseline against which email content will be weighed.

3. Curate emails ruthlessly

Only add messages that fill a genuine gap in the formal record. Prioritize emails containing:
- Final approvals or rejections
- Confirmed dates, owners, or deliverables
- Customer feedback that changes scope
- Technical constraints or dependencies
- Clear explanations for why a decision changed

Avoid adding long threads with stale information or irrelevant discussion. If a later reply supersedes earlier text, consider adding only the decisive message and noting that in your prompt.

4. Give Copilot explicit instructions

Notebooks support custom instructions about tone, format, and how to weight sources. For email-heavy notebooks, useful guardrails include:
- “Treat the approved project plan as the primary authority unless a later email explicitly changes it.”
- “Separate confirmed decisions from suggestions and unanswered questions.”
- “List conflicting dates or commitments rather than choosing one.”
- “Cite the specific email source when presenting a fact drawn from correspondence.”

These rules turn vague requests into structured analytical tasks.

5. Review before sharing or acting

Copilot can draft quickly, but it cannot assume accountability. Before you use an output, check:
- Chronology: Is the AI relying on the latest message, not an outdated reply?
- Authority: Did the sender have the authority to make that commitment?
- Scope: Does the email apply to the entire project or just one workstream?
- Tone: Has an informal exploration been presented as a final decision?
- Confidentiality: Does the draft expose information not appropriate for the intended audience?

6. Handle sharing with care

Microsoft warns that sharing a notebook can also share access to the files and emails inside it, provided you have the permissions to grant that access. Treat email references as sensitive project material. Before sharing broadly:
- Confirm you have the right to share each included message.
- Remove any emails that are not essential for the notebook’s purpose.
- Consider creating an internal-only version and a heavily curated shareable version.

Shared and delegated mailboxes add another layer: ensure your organization’s access controls, retention policies, and sensitivity labels are aligned before treating those conversations as reusable AI reference material.

Outlook

Email references in Copilot Notebooks mark a meaningful step toward making AI work assistants that understand not just documents, but the conversations that shape them. Microsoft’s roadmap suggests this is part of a broader effort to bring all Microsoft 365 content types into the notebook experience. In the near term, expect more refinement of reference management and possibly tighter integration with Outlook rules or sensitivity labeling.

The feature’s real power will be realized not by dumping entire inboxes into AI, but by disciplined curation—building small, clean, well-governed working sets that capture the reasoning behind the work. For organizations already deep in the Microsoft 365 ecosystem on Windows, that turns Copilot Notebooks from a note-taking space into a genuine project intelligence layer.