MC1423103 - Copilot Notebooks now supports Markdown (.md) files as grounding sources

Message Center

Summary

Copilot Notebooks now support Markdown (.md) files as reference sources, enabling grounding in technical docs without conversion. This feature, rolling out worldwide by early August 2026, requires no admin setup, respects existing permissions, and enhances Copilot’s response relevance using Markdown content. No user action is needed.

Last Updated

Jul 21, 2026

Published Jul 10, 2026

View version history

Service

Microsoft 365 apps

Tag

Updated message
New feature
User impact

More information

Updated July 20, 2026: We have updated the timeline. Thank you for your patience.

What and Why:

Microsoft is expanding Copilot Notebooks to support Markdown (.md) files as notebook reference sources. This enhancement enables users to ground Copilot conversations in technical documentation, README files, runbooks, wikis, and AI-generated Markdown content without converting files to other formats. By broadening the types of content that can be used as notebook references, Microsoft is helping organizations make better use of existing knowledge repositories and improve the quality and relevance of Copilot-generated responses.

Rollout Schedule:

  1. General Availability (Worldwide): Beginning end of July 2026 (previously mid-July); expected to complete by early August 2026 (previously late July)

Impact on Your Organization:

Who is affected:

  1. Users who have access to Copilot Notebooks.
  2. Teams that maintain knowledge assets in Markdown (.md) format.
  3. Organizations using Markdown-based documentation repositories such as technical runbooks, README files, and wiki exports.

Platforms/Services:

  1. Microsoft Copilot Notebooks
  2. Microsoft 365 Copilot
  3. Supported SharePoint and OneDrive locations

What will happen:

  1. Users will be able to add Markdown (.md) files as notebook reference sources.
  2. Copilot responses can use information contained within Markdown files as grounding content.
  3. Copilot can reference structural elements within Markdown documents.
  4. Existing Markdown-based documentation can be used without file conversion.
  5. Citations to source content continue to be available.
  6. The feature is enabled automatically.
  7. No admin configuration is required.
  8. Existing permissions and access controls continue to apply.

Action Required/Recommendations:

No action is required.

Recommended activities:

  1. Review internal guidance for users who maintain Markdown-based documentation.
  2. Communicate the update to Copilot Notebook users.
  3. Update adoption and training materials as appropriate.
  4. Validate documentation governance processes for Markdown repositories.

Compliance Considerations:

ConsiderationExplanation
Does the change alter how existing customer data is processed, stored, or accessed?Copilot Notebooks can now access and process Markdown (.md) files as grounding sources. This expands the types of content that Copilot can reference when generating responses.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Copilot can now reason over, cite, and generate responses based on information contained in Markdown documents, extending AI grounding capabilities to an additional file format.
Does the change provide end users any new way of interacting with generative AI?Users can add Markdown (.md) files directly to Copilot Notebooks and interact with Copilot using content from those files as grounding material.
Does the change allow a user to enable and disable the feature themselves?Users decide whether to include Markdown files as notebook references. The capability is available by default, but usage is controlled by the user when creating or editing notebooks.

Version history

2 versions tracked

Updated 1 time since Jul 10, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Jul 21, 2026 · 05:44 PMLatest · v2

    Changed: Body, Tags, End date

  2. Jul 10, 2026 · 10:45 PMOriginal · v1

    Changed: Initial version