Copilot Studio Announced #179

Add an extract node to a Copilot Studio workflow

Extract document data for later workflow steps

An extract node in Copilot Studio workflows lets makers pull document data into later workflow steps. Feature-specific availability and rollout dates are not stated.

Key points

  • The node extracts named values from documents.
  • The node also extracts tables.
  • Document examples include invoices, contracts, and financial statements.

What to do

Identify workflows where later steps need values or tables from documents. Check feature availability and licensing before planning adoption. Tell makers that the extracted data can be used by later workflow steps.

Timeline

  1. October 2026 In Microsoft’s monthly deck
Speaker notes

The extract node connects document processing with later steps in a Copilot Studio workflow. It handles both named values and tables, rather than just one type of extracted data. Invoices, contracts, and financial statements are the examples Microsoft gives. The September 2026 heading is a summary-list label, not a feature-specific rollout date. Availability, licensing, and admin controls are not specified.

Sources and links

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.