logo
search
Others

How to Fix Power Automate CC Field Error with Multiple SharePoint Emails

WPS EditorWPS Editor Oct 1, 2026 868 views

Question details

The user needs to correctly pass a multi-value SharePoint email field into a Power Automate email action without triggering an invalid address format error.

Fixing Power Automate CC Field Errors with Multiple SharePoint Email Addresses
Product
Microsoft Power Automate
Device & OS
not provided
Scenario
Automating email delivery through a flow using multiple CC addresses sourced directly from a SharePoint list.
Observed behavior
The flow fails at the email action because multiple email addresses are passed as a single comma-separated value, which the action rejects as an invalid email string.
Before you start

Ensure you have edit permissions for the Power Automate flow and verify that the source SharePoint list column allows multiple selections.

Solution 1Recommended

Convert Multi-Value Output Using Data Operations

Extract the email addresses from the SharePoint array and join them into a valid semicolon-separated string that email connectors require.

Power Automate reads multi-value SharePoint fields as an array of objects. When pushed directly into an email field, it forces the array into an unreadable format. Using 'Select' and 'Join' data operations parses this array perfectly.

1
Add a Select operation

In your flow, add a 'Select' data operation just before the email action. Set the 'From' field to your SharePoint multi-value CC field.

2
Map the email values

In the 'Map' field of the Select action, choose the dynamic 'Email' content that corresponds to your SharePoint multi-value field.

3
Add a Join operation

Insert a 'Join' data operation below the Select action. Set the 'From' input to the 'Output' of the Select action, and type a semicolon (;) in the 'Join with' field.

4
Update the email action

Open your 'Send an email' action, navigate to the CC field, and replace the raw SharePoint data with the output from the Join operation.

Convert Multi-Value Output Using Data Operations
Correct Delimiters: Most email connectors in Power Automate (like Office 365 Outlook) strictly require semicolons (;) instead of commas to separate multiple email recipients.
Free Microsoft Office alternative

Enhance Your Daily Workflow with WPS Office

While resolving Microsoft ecosystem integration issues, consider using WPS Office for your local document management. It provides a lightweight, highly compatible, and free alternative to Microsoft Office for all your word processing, spreadsheet, and presentation needs.

  1. 1. Download the software: Visit the official WPS Office website and click the download button for your specific operating system.
  2. 2. Install WPS Office: Run the downloaded installer and follow the quick setup wizard to complete the installation.
  3. 3. Open existing documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Word, Excel, and PowerPoint files.
Fully compatible with Microsoft Office formats like .docx, .xlsx, and .pptx.Lightweight installation ensures fast startup and smooth operation.Familiar tabbed user interface requires zero learning curve.Built-in PDF editing tools for seamless document management.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Power Automate interpret my SharePoint CC field as a single comma-separated string?

SharePoint multi-value fields are retrieved by Power Automate as complex array objects. When you place an array directly into a text input like an email CC field, Power Automate flattens it into a single JSON-formatted string, causing validation errors.

Can I use commas to separate multiple email addresses in Power Automate email connectors?

Generally, no. Connectors like Office 365 Outlook require semicolons (;) to delimit multiple email addresses. Using commas will result in an invalid recipient format error.

Where should I go for advanced Power Automate troubleshooting?

For highly specific connector errors or complex flow logic issues, posting detailed screenshots and error logs to the official Microsoft Power Automate Community is recommended for expert assistance.