Export a Shared Mailbox in Microsoft 365 to PST or Excel

Last updated August 2026

Try it now: extract email data to Excel, CSV, or JSON

Convert your email files
No install

Connect a mailbox to pull .eml/.msg in bulk, or paste a raw email to test the converter now.

or paste an email to test
Output format
Columns to extract
Extract your own custom fields
Popular:

Create a free account to download. No credit card required.

The short answer

A Microsoft 365 shared mailbox has no password of its own, so you export it through an account that holds Full Access permission on it. In classic Outlook for Windows that is File > Open & Export > Import/Export > Export to a file, choosing PST for an archive or CSV for a spreadsheet. Administrators who need a defensible copy use Content Search in Microsoft Purview, which also outputs PST. New Outlook and Outlook on the web have no Import/Export wizard at all. If what you actually want is the data rather than the mail, connect the shared mailbox and export the folder straight to Excel.

Shared mailboxes are where the awkward requests live. Purchasing, dispatch, accounts, support, careers: the address everyone in a team can see, nobody personally owns, and which quietly accumulates several years of the only record of how something was agreed. Then somebody asks for it. An auditor wants the correspondence on a supplier. Legal wants a preserved copy before a matter opens. A new ops manager wants to know how many requests came in last quarter and how quickly they were handled. Those three requests need three different files, and picking the wrong one is how an afternoon disappears.

Why a shared mailbox is not just another mailbox

A shared mailbox in Microsoft 365 is a mailbox without a user behind it. It normally carries no license and no sign in credentials, which is the whole point: you give people Full Access permission instead of handing round a password. That design decision is also the reason the usual export advice half works. You cannot open a browser, sign in as [email protected], and click export, because there is nothing to sign in as. Everything you do has to be done through an account that has been granted rights over it, or through an administrative tool that works at the tenant level.

There is a second constraint people run into later. New-MailboxExportRequest, the PowerShell cmdlet that so many older guides reach for, belongs to on-premises Exchange. It is not available in Exchange Online, so a script written against an in-house Exchange server will not survive the move to Microsoft 365. The tenant-level equivalent is Content Search, covered below.

Method 1: the classic Outlook Import/Export wizard

This is the route most people want, and it works well when the shared mailbox is properly attached to your Outlook profile.

  1. Confirm you have Full Access permission on the shared mailbox. An administrator grants this in the Microsoft 365 admin center.
  2. Open classic Outlook for Windows and wait for auto-mapping to add the mailbox to the folder list. This is not instant and can take a while to appear after the permission is granted.
  3. Go to File > Open & Export > Import/Export.
  4. Choose Export to a file, then pick Outlook Data File (.pst) for a full archive or Comma Separated Values for a spreadsheet.
  5. Select the shared mailbox folder you want, tick Include subfolders if you need the whole tree, and save the file somewhere the rest of the team can reach.

Why is my shared mailbox not showing in the Import/Export wizard?

Almost always because it is not really in your profile yet. Auto-mapping adds a shared mailbox to Outlook as a secondary folder tree, and the export wizard can only see mailboxes that are properly attached. If the permission was granted minutes ago, give it time and restart Outlook. If it still does not appear, add it by hand: File > Account Settings > Account Settings > Change > More Settings > Advanced > Add, and type the shared mailbox name. It then shows in the wizard alongside your own.

Can you export a shared mailbox to PST?

Yes, through an account with Full Access permission, using classic Outlook for Windows and the Import/Export wizard. The PST preserves the mail as mail: folder structure, attachments, formatting and read state. It is the right choice when the requirement is preservation. It is the wrong choice when somebody wanted a list, because a PST only opens in Outlook.

Method 2: Content Search in Microsoft Purview, the administrator route

When the request is legal, regulatory or an internal investigation, the export needs to be defensible rather than convenient, and it should not depend on one employee's laptop. That is what Content Search is for.

An administrator adds their account to the eDiscovery Manager role group in the Microsoft Purview compliance portal, creates a new content search scoped to the shared mailbox, optionally narrows it by date range, sender or keyword, runs it, and exports the results. The output is a PST plus a results manifest, which is the part that matters for an audit trail: you can show what was searched, when, and what came back.

Two practical notes. The export runs as a background job on Microsoft's side, so a large mailbox takes real time rather than finishing while you watch. And exporting other people's correspondence is a decision with policy implications, so get the request in writing before you run it, even when you technically have the rights.

Method 3: new Outlook and Outlook on the web

Here is where a lot of guides quietly go out of date. New Outlook for Windows and Outlook on the web were rebuilt without the File tab, and Microsoft has not carried the Import/Export wizard across. There is no CSV export of a folder and no PST export of a shared mailbox from that interface.

What exists instead is a personal mailbox export: Settings > General > Privacy and data > Export mailbox, which queues a job, states that it can take up to 48 hours, and emails a link to a .pst. That covers your own mailbox, not a shared one you merely have rights over. If new Outlook is what your organization has standardized on, your options for a shared mailbox are Content Search, installing classic Outlook alongside it, or connecting the mailbox to a tool that does the export for you.

Method 4: connect the shared mailbox and export the folder to Excel

The three methods above all optimize for preserving mail. If the request was really about the contents, they leave you doing the actual work by hand. A PST tells you nothing until you reopen it in Outlook and start reading. A CSV export from the wizard gives you Subject, Body, From, To and Cc, which sounds right until you notice that the entire message body arrives in one cell, tables flattened into a run of text, and attachments dropped altogether.

The other route is to treat the shared mailbox as a data source. Connect it with Microsoft sign in, or over IMAP with a host, username and app password, choose the folder, and take the result as a spreadsheet. Each message becomes a row with its date, sender, recipients and subject, and the body is parsed instead of dumped: name the fields you care about, such as po_number, invoice_total or ticket_ref, and they come back as their own columns across every sender layout in the folder. Messages built as HTML tables, which is most automated business mail, return one spreadsheet row per table row. The export Outlook emails to Excel page covers the setup, and the IMAP email parser page has the host and port settings for mailboxes outside Microsoft 365.

Two honest limits, since they decide whether this fits your request. It does not produce a PST, so it is not a substitute for a preservation copy. And it parses the message body, its HTML tables and the attachment filenames, but not the data sealed inside an attached PDF or workbook, which needs a document extraction step of its own. If your goal is neither archiving nor analysis but simply finding one message somewhere across every mailbox and file the company holds, that is a different problem again, and an enterprise search layer across your work apps answers it better than any export will.

PST, CSV or a parsed spreadsheet: which one does your request need

What you were asked forThe right outputHow to get it
Preserve the mailbox before an account closesPSTClassic Outlook Import/Export, or Content Search for a defensible copy
A legal hold or audit requestPST plus a results manifestContent Search in Microsoft Purview, run by an administrator
A list of what arrived, from whom and whenSpreadsheetClassic Outlook CSV export, or connect the mailbox and export the folder
The numbers inside the messagesSpreadsheet with named columnsParse the folder into fields; the wizard cannot break out the body
Line items out of order or remittance mailOne row per line itemParse the HTML tables; a CSV export flattens them into text

Questions that come up every time

How do I export a shared mailbox without a license?

You do not license the shared mailbox. You grant Full Access permission to a licensed user and export through that user's Outlook profile, or you export at the tenant level with Content Search. Microsoft does require a license on a shared mailbox once it exceeds the free storage allowance or when you put it on litigation hold, so check that before you plan a long retention.

Do I need admin rights to export a shared mailbox?

Not for the Outlook route. Full Access permission on the mailbox is enough, and a manager can request that for you. You do need administrative rights for Content Search, specifically membership of the eDiscovery Manager role group, which is deliberately restricted because the tool can read any mailbox in the tenant.

How long does a Microsoft 365 mailbox export take?

An Outlook Import/Export run happens on your machine and finishes in minutes for a normal folder, longer for years of mail with attachments. Microsoft's own built-in mailbox export runs as a queued background job and is documented as potentially taking up to 48 hours. Content Search exports similarly run server side and scale with the size of the result set.

Can I export just one folder or a date range?

Yes in every method, and you should. The Import/Export wizard exports the folder you select, with subfolders optional. Content Search takes a date range and keyword conditions. Parsing a mailbox works the same way: point it at one folder for one quarter rather than the whole tree. Narrower exports finish faster, are easier to check, and avoid handing over correspondence nobody asked for.

What happens to attachments?

A PST keeps them inside the archive. A CSV export from the wizard drops them entirely, which surprises people who assumed the file names would at least be listed. A parsed export records each attachment by filename, type and size next to its message, so you keep the audit trail of what was attached even though the contents of those files are a separate extraction job.

Can I automate this so it runs every month?

The wizard cannot be scheduled, which is why so many teams end up with a VBA macro nobody wants to own. The VBA route for Outlook to Excel is worth reading if you want to understand the tradeoff. A connected mailbox is the simpler answer: set the folder and the fields once, and every new message lands in the same columns, so pulling the current month is a download rather than a project.

Before you export anything

A shared mailbox usually contains other people's correspondence, sometimes customer data, occasionally regulated data. Three questions save trouble later. Who asked for this, and is it in writing? What is the narrowest scope that answers the question, one folder and one quarter rather than everything? And where will the file live once it exists, given that a PST or a spreadsheet of a purchasing inbox sitting on a laptop is a data incident waiting for a lost laptop.

Once that is settled, the mechanics are straightforward. Preserve with PST, prove with Content Search, and analyze with a spreadsheet. If it is the third one you actually need, connect the mailbox and pull the folder into columns rather than exporting everything and cleaning it up afterwards. The extract data from Outlook emails page walks through naming the fields, and you can test the shape on a single message with the tool at the top of this page before you connect anything.