Collab365

Power Automate and shared mailbox

Q: Do I need delegate access to the shared mailbox?

You need Full Access permissions, not just basic delegate or Send As rights. Full Access allows the Microsoft Graph API to read folder structures and move items.

Q: What if the subfolder still doesn't appear in the picker?

Ensure Original Mailbox Address is entered correctly. Type folder path manually if needed (e.g., Inbox/Subfolder). Re-authenticate Outlook connection if password reset.

Q: Should I use 'Html to text' or write complex split expressions?

Always use the Html to text action for general body extraction. It's native and requires no coding. Use expressions only for specific substrings.

C

Collab365 TeamAuthorPublished Apr 23, 2026

At a Glance

Target Audience: M365 Administrators, IT Consultants, Power Automate Makers
Problem Solved: Can't access shared mailbox subfolders in Power Automate Move email action; raw HTML in email bodies pollutes Microsoft Lists.
Use Case: Automate IT helpdesk/support inbox triage: route sender-specific emails to subfolders & log clean text to tracking lists.

Yes, you can move emails to shared mailbox subfolders in Power Automate by entering the shared mailbox address in the Move email (V3) advanced options. Plus, strip HTML from bodies using a one-click action.

If you manage an IT helpdesk, a customer support inbox, or a busy finance team mailbox, you already know the pain of manual email triaging. Back in July 2024, user Øyvind Sørlie opened a thread on the Collab365 forum that perfectly captured this frustration. He asked a seemingly straightforward question: how do you use Power Automate to move incoming emails from a specific sender in a shared mailbox inbox to a subfolder? The problem was that his 'Move email (V2)' action only showed his personal mailbox folders, leaving him unable to route the team's traffic. Furthermore, when he attempted to log those emails into a Microsoft List, he struggled to extract plain text from the HTML email body. Instead of readable text, his Microsoft List items were flooded with raw, messy HTML code.1

Community replies in that thread offered piecemeal solutions. Linda Do accurately suggested using the 'Original Mailbox Address' advanced parameter for moving emails 2, while James Williams pointed out the 'Html to text' action for body conversion. Other users suggested abandoning Power Automate altogether in favour of Outlook web rules. However, that original thread lacked cohesive structure, technical depth, comparisons, and crucial 2026 platform updates.3

Key Takeaway: Power Automate V3 actions support shared mailboxes natively since 2024 updates, but you must manually declare the shared address in the advanced options of your actions to break out of your personal user context.4

This Collab365 blog post is a direct replacement for that forum thread. The post covers the exact same core topic—Power Automate flows for shared mailbox email moving and HTML-to-text conversion—but with dramatically more useful, current, and exhaustive detail. We will explore updated triggers like 'When a new email arrives in a shared mailbox (V3)', AI-assisted parsing, and Copilot in Flows.3

TL;DR / Quick Answer

Moving Emails to a Shared Subfolder:

Ensure you have Full Access permission on the shared mailbox via the Exchange admin center.6
Use the When a new email arrives in a shared mailbox (V3) trigger and connect it to the shared address.5
Add the Move email (V3) action to your flow designer canvas.
Click Show advanced options to reveal hidden parameters.
Enter the shared mailbox address in the Original Mailbox Address field to force the system to display shared subfolders instead of personal ones.6

Extracting Plain Text for Microsoft Lists:

Add the Html to text action immediately after your email trigger.9
Pass the dynamic Body content from the email trigger into this conversion action.10
Use the clean, plain text output to populate your Create item step for Microsoft Lists.11

Who Is This Guide For? ## Prerequisites

This guide is designed for the IT consultant or M365 administrator with 1-3 years of Power Automate experience. You are likely responsible for managing shared mailboxes for your organisation and need to automate email sorting to subfolders. You also need clean text extraction for logging data into Microsoft Lists because native Outlook rules are greyed out, unreliable, or simply insufficient for complex shared access scenarios.12

Before we begin clicking through the Power Automate designer, we must establish a rock-solid foundation.

Key Takeaway: Your Power Automate flow will authenticate using the credentials of the account that creates the connection. If your account lacks the correct backend Exchange permissions, the flow will fail instantly with a 403 Forbidden error.14

Essential Licensing and System Prerequisites

To successfully build this automation in 2026, your environment must meet several strict requirements.

Firstly, you need a valid Power Automate license. Fortunately, the actions we are deploying today—specifically the Office 365 Outlook connector and the SharePoint/Microsoft Lists connector—are classified as Standard Connectors.15 This means they are included in most base Microsoft 365 Business Basic, Standard, E3, and E5 plans. You do not need to purchase a standalone Power Automate Premium (per-user) license unless you intend to add advanced AI Builder nodes or connect to external enterprise databases like Salesforce or SQL Server later in the flow.16

Secondly, the shared mailbox itself must be a valid Microsoft 365 shared mailbox with the REST API enabled. The Office 365 Outlook connector will throw errors if you attempt to point it at mailboxes residing on dedicated, on-premises Microsoft Exchange Servers that have not been properly migrated, or if you are using certain restricted sandbox test accounts.6

The Permissions Trap: Full Access vs. Send As

The most common mistake IT administrators make is assuming that "Send As" or "Send on Behalf" permissions are sufficient for automation. They are not. The trigger we are using—'When a new email arrives in a shared mailbox (V3)'—will not work in cases of user-to-user shared mailboxes unless the connecting user has Full Access to the target mailbox.6 Full Access permission allows the delegate to open the mailbox, view its contents, and crucially, add or remove items via the Microsoft Graph API, which is the underlying engine for Power Automate.7

We hit the same folder snag in a client tenant last month. The user was convinced they had access because they could send emails from the support address, but the flow consistently failed.

Key Takeaway: If a user only has 'Send As' permissions, they can draft outgoing replies, but Power Automate cannot monitor the inbox or move items between folders. You must grant Full Access.7

Verifying Permissions via Exchange Online PowerShell

To definitively prove your account has the correct rights, you should query the tenant directly. In 2026, Microsoft heavily recommends using the modern Get-EXOMailboxPermission cmdlet from the Exchange Online PowerShell module, explicitly advising against the older, slower Get-MailboxPermission cmdlet.17

The difference in performance is staggering. System administrators processing large tenants note that running the legacy command against a 4,000-mailbox directory can take over three hours, often causing Azure Automation runbooks to time out and fail. The modern EXO cmdlet completes the same task in roughly 50 minutes through heavily optimised, server-side filtering.18

To verify your specific access, open your PowerShell terminal, connect to Exchange Online, and execute the following command:

Get-EXOMailboxPermission -Identity "support@yourcompany.com" -User "your.admin.account@yourcompany.com"

The output will clearly list your AccessRights. If you do not see FullAccess listed, you must escalate the issue to your Exchange administrator to adjust your permissions before continuing.

How Do You Trigger a Flow on New Emails in a Shared Mailbox (2026)?

Once your licensing and permissions are verified, you can begin constructing the automation. The foundation of any reliable Power Automate workflow is its trigger. If the trigger is misconfigured, the flow will either fire erratically, miss crucial emails, or consume your entire daily API allowance in a matter of minutes.

Selecting the Correct Modern Trigger

Navigate to the Power Automate portal (make.powerautomate.com). On the left-hand navigation pane, select My flows, and then click New flow > Automated cloud flow.5

You will be prompted to name your flow. Choose a descriptive, standard naming convention such as "Shared Mailbox - Route and Log Support Inquiries". In the trigger search bar, type "shared mailbox".

You must select When a new email arrives in a shared mailbox (V3) from the Office 365 Outlook connector.5 It is imperative that you do not select the standard "When a new email arrives (V3)" trigger. While the standard trigger works flawlessly for personal inboxes, it lacks the native backend mapping required to handle shared mailbox delegation dynamically without complex, unsupportable workarounds.4

Key Takeaway: Users frequently use the wrong trigger or fail to filter their inputs. You must pay attention to the exact fields—specifically the Original Mailbox Address and Subject Filter—to ensure you configure the trigger correctly before moving to the complex actions, preventing infinite loops or rate limiting.

Step-by-Step Trigger Configuration

Once the V3 shared mailbox trigger is on your canvas, you must configure its parameters meticulously.

Original Mailbox Address: This is the most critical field. Enter the exact email address of the shared mailbox (e.g., invoices@company.com).20 If you enter a display name or an alias, the flow will fail to initialise.
Folder: By default, this will say Inbox. Because you entered the shared email address in the step above, clicking the folder icon will correctly query the Microsoft Graph API and display the folder hierarchy for the shared mailbox.6 Select the folder you wish to monitor.
Show advanced options: Click this text to reveal the hidden filtering parameters.5
From: If you only want to process emails from a specific sender (as Øyvind requested in the original Collab365 forum thread), enter their email address here.
Subject Filter: Add a specific keyword if your process demands it (e.g., "Invoice" or "Support Request").
Include Attachments: Set this to Yes if your subsequent Microsoft List creation step requires attachment data. If you skip this and leave it as No, the flow will not pass the file binaries downstream.21

When filtering by the 'To' or 'CC' fields in the advanced options, be aware of a specific 2026 limitation. Only one of these fields should be populated while leaving the other empty. If you set both the 'To' and 'CC' fields, the trigger will only fire for emails that contain the specified addresses in both fields simultaneously, which often results in flows that seemingly never trigger.6

Managing Trigger Throttling and 429 Errors

A persistent and frustrating issue we see with shared mailboxes in 2026 is the 429 Too Many Requests error.23 Even if your overall daily email volume is completely normal, Power Automate can hit aggressive API throttling limits when emails arrive in short, concentrated bursts.25

If a marketing campaign triggers fifty automated replies to your shared mailbox in under ten seconds, the Office 365 Outlook connector may panic, resulting in skipped runs or disabled flows.

Key Takeaway: To protect your flow from 429 throttling errors, you must enable Concurrency Control on your trigger. This forces Power Automate to queue incoming emails and process them in manageable, sequential batches rather than attempting to execute them all at once.25

To fix this, click the settings icon (the three dots) on the top right of your trigger node, and select Settings. Scroll down and toggle Concurrency Control to 'On'. Limit the degree of parallelism to a sensible number, such as 5 or 10. By combining this concurrency limit with strict 'Subject' or 'From' filters, you ensure your flow remains perfectly stable regardless of mailbox traffic spikes.

How to Move Emails to a Subfolder in the Shared Mailbox?

This is the exact step where the majority of users get stuck, and it formed the core of the frustration in the July 2024 forum thread. You add the 'Move email' action to your flow, click the folder selection icon, and suddenly you are looking at a list of your own personal folders—your Inbox, your Drafts, your Sent Items. The shared mailbox folders are completely missing from the interface.8

To understand why this happens, we have to look at how the Office 365 Outlook connector authenticates. Under the hood, the connector relies entirely on the Microsoft Graph API. By default, when you drag an email action onto the canvas, the API queries the endpoint https://graph.microsoft.com/v1.0/me/mailFolders. The "me" in that URL points directly to the personal account of the user who created the connection.4

To force the Graph API to break out of your personal context and look at the shared mailbox, we must explicitly declare the shared user context using an advanced parameter.

Detailed Configuration Walkthrough

Click the + New step button under your trigger and search for Move email (V3) from the Office 365 Outlook connector list.
In the Message Id field, you must tell the action exactly which email it is supposed to move. Click inside the field and select the dynamic content labelled Message Id provided by your initial trigger.6
Stop and look closely at the action pane. You will see an option labelled Show advanced options (or a button labelled Show all in the modern Fluent 2 UI). Click it.
Locate the field specifically named Original Mailbox Address.2
Type the exact email address of your shared mailbox into this field (e.g., support@yourcompany.com).27
Only after you have populated the Original Mailbox Address should you click the folder icon next to the Folder field.

Because you have now provided the Original Mailbox Address, the connector instantly updates its backend Graph API query. The folder picker will load, and you will finally see the folder hierarchy belonging to the shared mailbox. You can now safely select your target subfolder, such as Inbox/Processed, Inbox/Urgent, or Emergency Tasks.26

Key Takeaway: The golden rule of shared mailbox automation is to always set the Original Mailbox Address in the Move email action before clicking the folder icon. If you leave it blank, Power Automate will stubbornly default to your personal mailbox.4

Troubleshooting the "Specified Object Was Not Found" Error

We hit a wall with this exact configuration in a client tenant just last week. We built the flow perfectly, yet it immediately failed on the Move email step, returning a 404 Folder not found or Specified object was not found in the store error.6

If you encounter this error in 2026, it almost always points to one of three distinct causes.

Firstly, double-check that you entered the folder path correctly using the picker. A common mistake is accidentally typing the email address itself into the folder field, which prompts the API to look for a folder named "support@company.com", which obviously does not exist.29

Secondly, verify that the email was not already moved or deleted. In a busy shared mailbox, a human agent might manually drag the email into a folder before the Power Automate flow has a chance to execute the move action, resulting in a 404 error because the Message Id is no longer valid in the original location.6

Thirdly, verify your connection token. Occasionally, the OAuth token connecting your account to Outlook expires or becomes corrupted. Go to the Data > Connections menu, delete the Office 365 Outlook connection, and recreate it to force a fresh authentication token.6

Power Automate vs Outlook Rules for Shared Mailboxes: Which Wins in 2026?

A frequent question we receive in the Collab365 community is: "Why should I spend time building a Power Automate flow when I can just create a simple Outlook Rule to move emails?"

It is a completely valid question. Outlook rules are native to the application, incredibly fast to set up, and easily understood by most office workers. However, when dealing with shared mailboxes in a professional enterprise environment, standard Outlook rules often break down. Native Outlook rules struggle to apply complex conditional logic, cannot integrate with external databases like Microsoft Lists, and offer absolutely zero reporting or analytics out of the box.13

Furthermore, as Microsoft transitions users to the "New Outlook for Windows" in 2026, the feature parity between Classic and New Outlook remains fragmented. While basic rules are supported, advanced rule exports, imports, and specific client-side executions are either unsupported or only partially available in the new framework.31

Below is a technical comparison table based on our comprehensive 2026 testing to help IT administrators decide which tool is appropriate for their specific use case.32

Feature / Capability	Native Outlook Rules	Power Automate (Cloud Flows)	Verdict for IT Administrators
Execution Environment	Client-side (mostly) or basic server-side via Exchange.	100% Cloud / Server-side via Microsoft Graph API.	Power Automate. Flows run reliably 24/7 without requiring Outlook to be open on a local machine, ensuring platform-independent stability.34
Cross-Platform Integration	Limited entirely to the Microsoft Exchange ecosystem.	Connects to over 1,000+ services (SharePoint, Lists, Teams, CRMs).32	Power Automate. Essential if you need to log email data into Microsoft Lists, trigger an approval, or update an external database.13
HTML to Plain Text Handling	No native data extraction or conversion capability.	Native Html to text action and AI-assisted parsing.9	Power Automate. Crucial for cleaning and sanitising raw email data before injecting it into structured databases.
Complex Logic & Routing	Basic "If/Then" based on sender, subject, or keywords.	Advanced arrays, loops, regular expressions, and Copilot AI context.32	Power Automate. Capable of handling multi-step approvals, dynamic routing based on database lookups, and error catching.
Setup Speed & Simplicity	Very fast. Built directly into the familiar Outlook UI.30	Requires access to the maker portal and a foundational understanding of API logic.	Outlook Rules. Best for individual users doing simple, static folder sorting on their own personal inbox.34
Shared Mailbox Reliability	Often buggy; rules must be set up via OWA by a user with Full Access.	Highly reliable once the Original Mailbox Address is properly configured.6	Power Automate. Centralised management via the Power Platform Admin Centre prevents messy rule conflicts across the team.

Key Takeaway: If you are exclusively sorting emails into folders and your criteria are static, an Outlook Rule might suffice. But the moment your workflow requires extracting data, updating a Microsoft List, or alerting a Teams channel, Power Automate is the only viable, scalable choice.34

If your organisation finds Power Automate too complex, there are third-party competitors. Tools like Zapier offer massive integration ecosystems but charge punitive "per-task" pricing that explodes when looping through high volumes of emails.13 Products like FlowForma or Kissflow offer enterprise-grade orchestration but move away from the native Microsoft 365 security boundary.33 Dedicated shared inbox tools like Emailgistics add automatic round-robin assignments and SLA tracking directly inside Outlook, but they come with separate licensing costs.12 For the vast majority of Microsoft 365 customers, Power Automate remains the most cost-effective and deeply integrated solution available.

How to Extract Plain Text from HTML Email Bodies for Microsoft Lists?

Moving the email to a subfolder is only half the battle. The second half of the July 2024 forum thread highlighted a massive frustration for developers: extracting the email body to create a clean, readable Microsoft List item.

When you pull the Body dynamic content from an Outlook email trigger in Power Automate, you are not pulling plain text; you are pulling the raw HTML payload. If you inject this directly into a standard plain text column in Microsoft Lists or SharePoint, your list will be filled with <div>, <span>, <p style="font-size:15px;">, and <br> tags.35 It is completely unreadable for end-users and breaks downstream reporting tools.

In the past, makers tried to solve this using complex string manipulation. They would chain together split(), replace(), and skip() expressions to manually hunt down and remove HTML tags.1 This was fragile, prone to breaking when email signatures changed, and entirely unnecessary today.

The One-Click Fix: "Html to text" Action

Power Automate includes a dedicated, built-in Content Conversion service designed specifically to handle this translation.10

Click the + button to add a new action immediately after your email trigger.
Search for Html to text and select it from the Content Conversion connector list.9
In the Content field, insert the Body dynamic content from your email trigger.9

This action acts as an automatic translation layer. It consumes the messy HTML document and strips away all stylistic markup, rendering it as clean, readable plain text.11

Understanding the Limitations of Content Conversion

While the Html to text action is a lifesaver, you must understand its technical limitations. According to Microsoft's connector documentation, this service operates with specific, rigid rules. It enforces a maximum line length of 80 characters, after which it will automatically insert a line break. It uppercase all header tags (<h1>, <h2>) and heading cells (<th>). Furthermore, it strips away hyperlinks entirely; a link formatted as <a href='link'>text</a> will be flattened to text[link].11

If your workflow requires preserving clickable hyperlinks within the Microsoft List, you cannot use this action alone. You would either need to extract the URL prior to conversion using an expression or ensure your target Microsoft List column is set to "Enhanced rich text" and map the raw HTML directly into it.10

Key Takeaway: Never push raw email bodies into a standard text database. Always use the Html to text action as a middle step to sanitize the data, ensuring your Microsoft Lists remain clean, searchable, and professional.11

Advanced 2026 Enhancements: Copilot and AI-Assisted Parsing

The Html to text action is perfect for pulling the entirety of an email body. But what if you only need a specific, granular piece of information from that text? For example, what if you need to extract an "Invoice Number", a "Customer ID", or a "Renewal Date" to populate a specific column in your Microsoft List?

As of 2026, the Power Platform has deeply integrated Copilot AI into the flow designer.3 Instead of relying on rigid, rule-based document parsing or writing complex XPath queries, you can utilise AI-assisted parsing.38

If you possess the requisite premium licensing, you can add an Extract information using AI Builder action. Alternatively, you can use the Copilot chat pane residing on the right side of your designer. Simply instruct Copilot in natural language: "Create an expression to extract the 6-digit number following the word 'Invoice' from the Html to text output." Copilot will instantly generate the exact formula, drastically reducing setup time and operational overhead.3

Common Errors and Fixes

According to Collab365 analysis, the vast majority of shared mailbox automations fail on permissions, incorrect API configurations, or rate limiting. We have compiled the most common HTTP status codes and errors our community encounters when building this specific flow, along with their immediate 2026 fixes.

Error Code & Message	Primary Cause	The 2026 Fix
404: Folder not found 14	The connector is querying a folder in your personal mailbox, or you mistakenly typed an email address into the Folder field.	Click 'Show advanced options' and enter the shared mailbox address strictly in the Original Mailbox Address field.6 Verify the folder path is correct (e.g., Inbox/Subfolder).
429: Rate limited (Too Many Requests) 23	A sudden burst of incoming emails has exceeded the API rate limit allowed for the Outlook connector.	Edit the trigger settings. Enable Concurrency Control and set the limit to a low number (e.g., 5) to force the system to process emails in safe batches.25 Alternatively, configure an exponential backoff retry policy.42
403: Permission denied 14	The account authorising the flow connection does not possess Full Access rights to the target shared mailbox.	Request your M365 Admin to execute the Get-EXOMailboxPermission cmdlet to verify you have Full Access, not merely Send As permissions.17
500 / 502: Bad Gateway / Server Error 14	The target Microsoft Graph service is experiencing temporary backend infrastructure issues.	Wait 15-30 minutes. If the issue persists, check the Microsoft 365 Service Health dashboard. Configure a retry policy to handle transient network drops automatically.23
Missing Dynamic Content	The flow designer lost track of the JSON schema variables from previous steps.	Save the flow, refresh the browser page, and ensure you are utilising the modern Fluent 2 designer interface.43

Key Takeaway: When debugging a failed flow, always check the exact HTTP status code in the run history. A 403 means you have a permission issue, a 404 means your folder mapping is wrong, and a 429 means you need to slow the flow down.14

Full End-to-End Flow: From Email Arrival to List Creation

Let us put all these isolated components together into a single, cohesive, production-ready workflow.

Follow these numbered steps to build the definitive shared mailbox sorting and extraction flow.

Step 1: The Trigger

Action: When a new email arrives in a shared mailbox (V3)
Original Mailbox Address: support@yourcompany.com
Folder: Inbox
Include Attachments: Yes (if your list requires file binaries).

Step 2: Convert the Content

Action: Html to text
Content: Select the Body dynamic content generated by Step 1.
Note: This sanitises the payload immediately, stripping out styling and preventing formatting errors downstream.11

Step 3: Create the Database Record

Action: Create item (SharePoint / Microsoft Lists connector)
Site Address: Select your specific team's site URL.
List Name: Select your target list (e.g., "Support Tickets").
Title Column: Map to Subject (Dynamic content from Step 1).
Description Column: Map to the plain text output generated by the Html to text action in Step 2.
Sender Column: Map to From (Dynamic content from Step 1).

Step 4: Move the Email

Action: Move email (V3)
Message Id: Map to Message Id (Dynamic content from Step 1).
Original Mailbox Address: support@yourcompany.com (Crucial step!)
Folder: Select your specific subfolder using the folder picker (e.g., Inbox/Processed).

Why This Specific Architectural Order Matters

You might logically wonder why we move the email at the very end of the flow, after creating the List item. This is a deliberate architectural choice based on defensive design principles.

If the flow fails during the Microsoft List creation—perhaps due to a required column being left blank or a temporary SharePoint 502 Bad Gateway error—the flow execution stops immediately.23 Because the move action has not yet occurred, the email remains safely in the main Inbox.

If you structured the flow to move the email first, it would be hidden away in the subfolder. When the List item subsequently fails to generate, the support team might miss the inquiry entirely because they rely on the database for their queue. This specific order ensures that only successfully logged emails are moved out of sight.

Key Takeaway: Always place your destructive or archiving actions (like Move email, Delete email, or Mark as Read) at the very end of your flow. This defensive strategy ensures business data is safely processed and stored first.

FAQ

Do I need delegate access to the shared mailbox? You need Full Access permissions, not just basic delegate or Send As rights. Full Access allows the Microsoft Graph API, which Power Automate relies heavily upon, to read deep folder structures and physically move items within the mailbox hierarchy.6

What if the subfolder still doesn't appear in the picker? First, ensure you typed the email address correctly into the Original Mailbox Address field. If the picker still fails to load, you can type the folder path manually as a custom value (e.g., Inbox/YourSubfolder). Additionally, ensure the account making the connection has not had its password reset recently; if so, navigate to Data > Connections and re-authenticate the Outlook connection.6

Should I use 'Html to text' or write complex split expressions? Always default to the Html to text action for general body extraction. It is native, instant, and requires zero coding.9 Only resort to string manipulation like split() or AI Builder if you need to surgically extract a specific substring (like an order number or date) from within that already cleaned text.9

Are there any 2026 trigger changes I should know about? Yes, Power Apps and Power Automate have definitively shifted to an AI-first ecosystem. The UI now utilises Fluent 2 modern controls, and classic components are being retired.15 While the underlying mechanics of the V3 trigger remain stable, you can now leverage Copilot directly in the right-hand pane to assist with configuring advanced OData filter queries, interpreting error codes, or suggesting next steps instantly.3

How do I conclusively check my permissions setup? Do not rely on the Outlook desktop client or the M365 Admin Portal UI to verify technical permissions. Ask your Exchange Administrator to run the modern PowerShell cmdlet: Get-EXOMailboxPermission -Identity "shared@domain.com". This will output a definitive, unarguable list of users who hold true Full Access rights.17

Your Next Steps

Stop allowing your team to do boring, repetitive work manually. You now possess the exact, 2026-verified blueprint to sort shared mailbox traffic and cleanly extract data without ever needing to touch a single line of raw HTML code.

We highly recommend building this flow in a dedicated developer or test environment first. Send a few test emails containing various HTML formatting and attachments to verify that the Move email action routes the message correctly and that your Microsoft List populates with clean, readable text.

You could also join the dedicated Power Automate Space on Collab365 Spaces for more research, news and advice.43