Email Archiving in Power Automate: One Outlook Message Becomes One Compressed PDF/A File in SharePoint with PDF4me

PDF4me Create PdfA is a Power Automate action that rewrites a PDF to the ISO 19005 archival standard. Placed at the end of an Outlook flow that converts the message body, converts every attachment, and merges them, it turns email archiving into a single compressed PDF/A file that SharePoint stores permanently.

Search for email archiving and page one sells you storage. Proofpoint, Mimecast, Barracuda, GoDaddy, every one of them answers the question "where will the mail live and for how long". Not one of them answers the question that actually decides whether an archive is worth keeping: what format is it in? A mailbox export is only readable while something can still open it. This flow treats archiving as a format problem first and a storage problem second, which is the opposite order to everyone on that results page.

Why-Based Q&A​

What You'll Get​

Input: an Outlook email with one or more attachments. Output: a single compressed PDF/A-2b file in SharePoint containing the message body as page one followed by every attachment in order.

The message that triggers the flow: a short body and one PDF attachment.

EmailArchive.pdf, written by the flow account, about a minute after the mail arrived.

What You Need​

The Flow at a Glance​

1. When a new email arrives (V3) (Outlook trigger) with attachments included.
2. Initialize variable email, type Array.
3. Convert to PDF (PDF4me Connect) on the HTML message body.
4. Append to array variable pushing the converted body.
5. Apply to each over the trigger's Attachments.
6. Convert to PDF 2 on each attachment's contentBytes.
7. Append to array variable 2 pushing each converted attachment.
8. Merge multiple PDF files into a single PDF file (PDF4me Connect).
9. PDF - Compress with Optimize Profile Web.
10. PDF - Create PdfA with Compliance PdfA2b.
11. Create file (SharePoint) into /Shared Documents/EmailArchive.

Complete flow overview​

Four document operations at ten to eleven seconds each dominate the run. Budget about fifty-six seconds for a message with one attachment, and roughly ten seconds more for each extra attachment.

Step 1: How do you trigger a flow on incoming Outlook mail?​

Flow so far: nothing yet, this is the trigger.

The trigger decides what gets archived, so it is worth being deliberate here. Two of its advanced parameters do the real work.

1. Create an Automated cloud flow and pick Office 365 Outlook > When a new email arrives (V3).
2. Open Advanced parameters and configure:
   • To: [email protected]
   • Include Attachments: Yes
   • Importance: Any
   • Only with Attachments: Yes
   • Folder: Inbox

Outlook trigger configuration​

Include Attachments is the one people miss. Leave it off and the loop still runs, but every attachment arrives with empty content.

Step 2: Why does the flow need an array variable?​

Flow so far: Outlook trigger.

The number of attachments is not known until the message arrives, so the flow needs somewhere to accumulate an unknown number of PDFs while preserving their order.

1. Add Variables > Initialize variable.
2. Configure:
   • Name: email
   • Type: Array
   • Value: leave empty

Initialize variable configuration​

Value stays empty. The body gets appended next, before the loop, which is what puts it on page one.

Step 3: How do you convert an email body to PDF?​

Flow so far: Outlook trigger plus Initialize variable.

The Outlook trigger hands over the message body as HTML. PDF4me Convert to PDF renders it, which is why the File Name carries an .html extension even though a PDF comes back.

1. Add Convert to PDF from the PDF4me Connect connection.
2. Configure:
   • Content: the Body token, which resolves to triggerOutputs()?['body/body']
   • File Name: email-body.html

Convert to PDF configuration​

The extension in File Name tells the converter what it is being handed. It is HTML going in, so email-body.html is correct even though the output is a PDF.

Step 4: How do you put the message body on page one?​

Flow so far: Outlook trigger, Initialize variable, Convert to PDF.

Order in the merged document is simply the order things enter the array. Appending the body here, before the loop, is the entire mechanism that keeps it first.

1. Add Variables > Append to array variable.
2. Configure:
   • Name: email
   • Value: the File Content token from Convert to PDF, which resolves to body('Convert_to_PDF')

Append to array variable configuration​

Value must be the File Content token, which is body('Convert_to_PDF'). Anything else here is the single most common reason Merge fails later.

Step 5: How do you convert every email attachment to PDF?​

Flow so far: Outlook trigger, Initialize variable, Convert to PDF, Append to array variable.

One loop over the attachment collection, two actions inside it. That is the whole pattern, and it does not change as the attachment count grows.

1. Add Control > Apply to each.
2. Select an output from previous steps: the Attachments token, which resolves to triggerBody()?['Attachments'].

Apply to each configuration​

Two actions inside the loop, and that stays true for one attachment or twenty.

Now add the first action inside the loop.

3. Add Convert to PDF (PDF4me Connect) inside the loop. Power Automate names it Convert to PDF 2.
4. Configure:
   • File Content: the expression base64ToBinary(items('Apply_to_each')?['contentBytes'])
   • File Name: the name token from the attachment

Outlook hands attachments over base64 encoded. base64ToBinary is what turns contentBytes back into a file the converter can read.

Then the second action inside the loop.

5. Add Append to array variable inside the loop, named Append to array variable 2.
6. Configure:
   • Name: email
   • Value: the File Content token from Convert to PDF 2, which resolves to body('Convert_to_PDF_2')

Same array, same pattern as step 4. Each pass through the loop adds one more page range to the eventual archive.

The two loop expressions​

base64ToBinary and items() both come from the Workflow Definition Language function reference, which is the authoritative list of what an expression field will accept.

Step 6: How do you merge an unknown number of PDFs into one?​

Flow so far: everything through the Apply to each loop.

By the time the loop finishes, the email array holds the body PDF followed by every attachment PDF. Merge takes the whole array in a single call.

1. Add Merge multiple PDF files into a single PDF file from PDF4me Connect, after the loop.
2. Configure:
   • docContent: @variables('email')
   • Output File Name: EmailArchive.pdf

The code view makes the shape unambiguous:

{
  "type": "OpenApiConnection",
  "inputs": {
    "parameters": {
      "body/docContent": "@variables('email')",
      "body/document/Name": "EmailArchive.pdf"
    },
    "host": {
      "apiId": "/providers/Microsoft.PowerApps/apis/shared_pdf4meconnect",
      "connection": "shared_pdf4meconnect",
      "operationId": "Merge_V1"
    }
  },
  "runAfter": {
    "Apply_to_each": [
      "Succeeded"
    ]
  }
}

Merge action code view​

runAfter Apply_to_each Succeeded is what guarantees the merge waits for every attachment to finish converting.

Step 7: How do you make an email archive compliant with PDF/A?​

Flow so far: everything through Merge.

Two actions, in this order, from the PDF4me PDF connection. The order is not cosmetic.

1. Add PDF - Compress.
   • File Content: the merged file content
   • File Name: the headers/FileName token carried through from the previous action
   • Optimize Profile: Web
2. Add PDF - Create PdfA.
   • File Content: the compressed file content
   • File Name: the headers/FileName token
   • Compliance: PdfA2b
   • Allow Upgrade: Yes
   • Allow Downgrade: Yes

Compress and Create PdfA parameters​

Compress runs on the merged document, before anything is certified.

Create PdfA is the last action to touch the document, which is exactly where it belongs.

Step 8: Where does the finished archive get stored?​

Flow so far: everything through Create PdfA.

The last action writes the certified file into SharePoint.

1. Add SharePoint > Create file.
2. Configure:
   • Site Address: PDF4me Sharepoints - https://ynoox1.sharepoint.com/sites/PDF4meSharepoints
   • Folder Path: /Shared Documents/EmailArchive
   • File Name: EmailArchive.pdf
   • File Content: the File Content token from PDF - Create PdfA, which resolves to body('PDF_-_Create_PdfA')

SharePoint Create file configuration​

File Content resolves to body('PDF_-_Create_PdfA'). Take it from Compress instead and you get a valid PDF that is not an archive.

Run the flow and verify​

Send a test message to the monitored address with at least one attachment, then check three things rather than one.

1. The run history. All eleven actions green, with the Apply to each showing the right iteration count. The captured run shows 1 of 1 for a single-attachment email.
2. The SharePoint folder. EmailArchive.pdf present in /Shared Documents/EmailArchive, with Modified By showing the flow's account.
3. The file itself. This is the step people skip. Open the document properties and confirm the PDF/A declaration is really there.

The archive produced by the captured run is 32,088 bytes across two pages: the message body on page one, the attachment on page two. Its embedded XMP metadata declares pdfaid:part as 2 and pdfaid:conformance as B, which is what PDF/A-2b looks like from the inside. If your own output opens fine but carries no such declaration, the Create file action is almost certainly reading from the wrong upstream action.

Common Variations You Can Add Without Rebuilding​

How this compares to the usual approaches​

The distinction that matters: the first three answer where the mail lives. Only the last one answers whether it will still render correctly when the software that made it is gone.

Common questions​

What is email archiving?​

Email archiving is the practice of capturing messages into a separate, durable store so they survive mailbox cleanup, staff departures, and retention deadlines. Most products define it as a storage problem: copy the mail somewhere safe and index it so it can be searched.

That definition is incomplete. An archive is only useful if it can still be opened, and a mail item is tied to the system that holds it. Converting the message and its attachments to a fixed document format is what turns a copy into a record.

How does email archiving work?​

Traditionally, a journaling appliance sits beside the mail server and receives a copy of everything, storing it in a proprietary repository with its own search interface.

This flow works differently. A trigger fires on arrival, the body and attachments are converted to PDF, merged into one document in order, compressed, and converted to PDF/A-2b before being written to SharePoint. There is no appliance and no proprietary store, and the output is a file anyone can open without your software.

How to archive emails to SharePoint?​

Point an Office 365 Outlook trigger at the mailbox, do the document work in the flow, and finish with SharePoint Create file pointed at the destination folder. That is the shape of it.

The thing worth getting right is what you write. Saving a .msg or .eml into a document library is technically archiving to SharePoint, but the result is a mail item that needs a mail client. A PDF/A file is a document that SharePoint can index, preview, and apply a retention label to like any other.

Can you save emails in SharePoint?​

Yes, in several ways, and they are not equivalent. You can drag a message from Outlook into a synced library, use "Save to OneDrive" on an individual mail, or automate it with Power Automate as this flow does.

The manual routes save the message in its native form, so attachments stay embedded inside a file only a mail client can open. The automated route lets you decide the output format, which is the reason to prefer it when the purpose is retention rather than convenience.

What are the email archiving best practices?​

Four hold up regardless of the tool. Archive on arrival rather than on a schedule, so nothing depends on someone remembering. Keep the body and its attachments together, because separating them destroys the context that made the message evidence. Use a format with a specification behind it, which in practice means PDF/A. And give every archived item a unique name, since an archive that overwrites yesterday's file is a single document with extra steps.

The flow here follows the first three by construction. The fourth is the one thing you must change from the captured configuration before going live.

Troubleshooting​

Related reading​

This post covers the archival format end of email automation. Three neighbouring walkthroughs cover the adjacent pieces:

• Convert the email body and every attachment into one consolidated PDF covers the merge pattern itself in more detail, storing to Dropbox.
• Turn every inbound email into an audit-ready PDF archive takes the same seven actions from a records-management angle.
• PDF archiving in Power Automate with an unattended SharePoint folder applies the compress and PDF/A pair to documents that are already in SharePoint, with no email involved.

Next Steps​

Storage decides where your email lives. Format decides whether anyone can still read it. This flow settles the second question, which is the one nobody on the first page of results is asking.