Use Outlook to export PST files for local Office 365 backup

Use Outlook to export PST files for a local Office 365 backup. The export creates a local copy of mail, contacts, calendar items, and tasks. A PST file is Outlook’s own data file. It can hold the mailbox data in one file that Outlook can open later.

The key point is simple. An export is a copy made at one moment. It is not a live backup. New mail that arrives after the export will not appear in that PST file. That small detail causes large confusion later. Email has a talent for making simple words sound optional.

I start with the account loaded in Outlook. The mailbox must be visible there before export begins. If Outlook has only part of the mailbox, the PST can only contain that part. Cached or offline data may also affect what is available, especially when the mailbox is large or the connection is slow.

For classic Outlook on Windows, the path is:

File > Open & Export > Import/Export

Then select Export to a file. Choose Outlook Data File (.pst). Select the Microsoft 365 account, not only the Inbox. Enable Include subfolders. That setting brings along folders such as Sent Items, Calendar, Contacts, Tasks, and custom folders.

Next, select a local folder and save the PST with a clear name. A name such as Office365-Mailbox-2026-03.pst is easier to understand later than backup-final-new2.pst. There is no prize for making the filename mysterious.

Outlook may ask about duplicate items when adding data to an existing PST. For a new export, saving to a new file keeps the result easier to check. If the PST already exists, the chosen duplicate setting can change the final contents. That choice deserves attention instead of a quick click.

The export may take time. Outlook can appear quiet while it works. The progress display is not always a perfect report of what has happened. The important result is the file itself and the data inside it.

A PST can include email, contacts, and calendar data. It can also include tasks and folder structure. It does not create a second Microsoft 365 mailbox. It creates a local Outlook Data File that can be opened or imported later.

That difference matters when checking the backup. A completed export message does not prove that every expected item is present. I treat the export as unfinished until the file opens and the main folders can be checked.

The check can stay simple:

• Open the PST in Outlook.
• Compare the folder list with the Microsoft 365 mailbox.
• Open recent and older messages.
• Check Sent Items and custom folders.
• Check contacts and calendar items.
• Look for missing nested folders.
• Confirm that the file size is sensible for the data being copied.

The word “sensible” matters here. A file size alone cannot prove that the backup is complete. A small mailbox may produce a small PST. A mailbox with large attachments may produce a much larger one. The contents still need a review.

The local file also needs basic care. Keep it on a drive with enough free space. Avoid working from a network location during export unless the setup supports it well. A lost connection can interrupt file writing. Saving first to a local drive gives Outlook a steadier target.

After the export, the PST should not live only on the same computer. A failed drive can take the mailbox copy with it. A second safe location gives the file a better chance of being useful when needed. That is practical backup hygiene, not a promise that every recovery will work.

A PST can also be protected with a password when Outlook creates it. That password helps control access to the file, but it does not replace safe storage. Password protection is not the same as encryption for every possible use. The exact behavior can vary by Outlook version and setup.

There is another limit. Microsoft 365 and Outlook change over time. New Outlook and classic Outlook do not always show the same tools or menu paths. Microsoft’s current instructions include export options in new Outlook, while many desktop export guides still describe classic Outlook. The available option depends on the Outlook version, account type, and organization settings.

The export also depends on mailbox access. If an account is not fully added to Outlook, or if folders have not finished syncing, the PST may not contain everything expected. Some organizations also control export features through account settings or policies. In those cases, the menu may be missing or behave differently.

For a normal mailbox that is visible in classic Outlook, the process is direct. Select the account root, include subfolders, save a PST, then inspect it. The hard part is usually not finding the menu. The hard part is checking the result with enough care.

This is where PST format knowledge helps. A PST is useful because Outlook can open it without turning every message into a separate file. It keeps mail in folders and carries related items such as contacts and calendar entries. That makes it a practical format for local Office 365 mailbox copies.

It is still a Microsoft Outlook format. Other mail programs may not open it directly. Moving the data to another mail system may require a separate import or conversion step. Requirements can change by application and version, so compatibility needs checking before a larger migration.

For readers working with 2PST tools, the same rule applies. A conversion tool may help move or recover PST data when Outlook cannot complete the job. That is a separate product capability from Outlook’s built-in export. The source file, destination format, mailbox size, and file condition all affect the result. No tool can promise success for every damaged or unusual file.

My technical judgment is plain: Outlook is a reasonable way to make a local PST copy of a Microsoft 365 mailbox. The export path is built into the desktop client, and the file can preserve the mailbox’s main folders and items. The export is only one point in the backup process, though. Opening and checking the PST is part of the work.

A local Office 365 backup is useful when the file can be found, opened, and understood. The safest process is therefore simple: export the account, include its subfolders, save the PST locally, keep another copy in a safe place, and check the contents. The result is a local snapshot, not a constantly updated archive.

That is the practical fix, and it also explains the format. The Migration Brief keeps the same promise: one practical fix, one file format explained, and one safer way to move your mail.