Microsoft 365 security center and exporting mailbox data to PST

Microsoft 365 security & compliance center and exporting to PST

Requirements

There are two sets of requirements you need to meet in order to access the new Microsoft 365 security and compliance center: license and permission.

The minimum required license for an organization is Microsoft 365 E3 subscription.

For a user to be able to access the new centers, they need to have at least one of the following roles assigned:

  • Global Administrator – Able to access both compliance and security centers.
  • Compliance Administrator or Compliance Data Administrator – Will be able to access Microsoft 365 compliance center
  • Security Administrator, Security Operator or Security Reader – are the roles required to access the Microsoft 365 security center.

What is new in Microsoft 365 security and compliance center?

The new Microsoft 365 security and compliance center has been announced to be generally available on April 22nd, 2019. This new platform consists of two separate entities – one devoted to security, the second – to compliance. Mind that new features are added frequently. Judging from this Microsoft article, the ultimate goal is to move all functionalities and solutions from the Office 365 security and compliance center to the new platform and to retire the old platform.

At the moment, many options redirect the user to the old Admin Center. For example, you will not find Content Search here and to run such a search, you need to go to the old Office 365 security & compliance center. Hunting and eDiscovery-related options also have not yet been migrated.

How to export Office 365 mailbox data in Microsoft 365 security center?

Office 365 is a great email platform in which security is one of the top priorities. That being said, it is still wise to be prepared for the worst-case scenario. That is why most security-concerned organizations look for a way to back up their mailbox data to another location. Local backup copies stored in a safe location allow you to access your data independently of any service providers. PST files, despite all their (numerous) flaws, have an advantage of being supported by various email clients.

Let’s put aside the irony of using an advanced security-related feature for a backup workaround which uses an outdated and hardly a reliable file format (PST).

If you choose to access content search straight from the Microsoft 365 admin center, you have two options:

From this point, simply follow the steps from How to export Office 365 mailboxes to PST using eDiscovery.

I cannot stress it enough, the method described above is a backup workaround, not a good and reliable backup solution. It will let you restore, at the very least, some lost data in case of a disaster. Keep in mind, though, that PST files are more fit for archiving, than for backup & restore purposes. And PST file corruption is not just a buzzword – it is a problem you might face each time you export or access a PST file. It is worth to take a good look at what this PST workaround might get you into before actually deploying it.

If you are looking for a reliable Office 365 and SharePoint backup & restore solution, take a look at CodeTwo Backup for Office 365.

How is a third-party tool better than PST files?

You might wonder how a third-party backup solution might be better than good old PST files, which, after all, have been used for ages. Here is a list of the most important advantages:

Granular backup and restore – a good backup solution is identified by how it performs when you actually need it. In other words: can you efficiently search through backup copies? And what about restoring? When it comes to PST files, the only way to search through them is to perform a PST import into Outlook. This allows you to search through a single PST file at a time. On the other hand, CodeTwo Backup for Office 365 lets you hunt for specific files in the whole backup database and restore single items or folders into the location of your choosing. You can restore items into their original location, or to another mailbox, even if it is in another Office 365 tenant.

Incremental backup – PST export is quite straightforward – by default, it performs a 1-1 backup. And while it is possible to limit exported items by date, this method has a side-effect of creating even more PST files to handle. CodeTwo Backup for Office 365 has the clear advantage of creating an incremental backup. You can set this tool up to run periodically to add only the new and modified items to the backup database.

Automation & Reliability – Export to PST through the Microsoft 365 security center is a manual, UI-based task. Since there are no out-of-the-box scripts to export the results of a content search, there is no easy way to schedule the task either. The common problem of PST corruption usually comes up when you actually need to restore some items. CodeTwo Backup for Office 365 can be scheduled to run backup processes in cycles, adding only the new and modified items to the backup copies. Why CodeTwo Backup for Office 365 is a secure solution.

For a more detailed description, take a look at the program’s features and its examples of use.

Tools for Exchange Server

Recommended articles

All you need to know about sensitivity labels in Microsoft 365

All you need to know about sensitivity labels in Microsoft 365

Learn how to use sensitivity labels to secure documents and emails as they travel across your Microsoft 365 organization and beyond.
How to migrate from Exchange Server 2016/2019 to Microsoft 365

How to migrate from Exchange Server 2016/2019 to Microsoft 365

Migrating Exchange data to the cloud is not rocket science – explore your options and launch the migration stress-free. As you may already know, Exchange Server 2016 and 2019 have reached end of life and are no longer officially supported by Microsoft. If your organization still uses either of these platforms to manage email, contacts, calendars, and tasks, keep in mind that: Your environment may become vulnerable to newly discovered security threats – Microsoft will no longer provide security updates for Exchange 2016 and 2019 (unless you’ve enrolled in the Extended Security Update program, which ends in October 2026). Your emails may get blocked – Microsoft has started to throttle and block emails sent from unsupported Exchange Server versions to Exchange Online (as I covered in this article). That said, migrating to a supported platform is now the only viable long-term option for keeping your organization’s email environment secure, supported, and fully operational. If your organization wants or needs to keep things on‑premises (and continue using Microsoft’s solutions for that), upgrading to Exchange Server Subscription Edition (SE) is the only path forward. But given Microsoft’s clear preference for its cloud services – evident in the faster rollout of new features and the many security capabilities available exclusively in Microsoft 365 (Office 365) – now is a great time to leave your on‑prem environment behind and migrate to Exchange Online as part of Microsoft 365. While switching over to a new platform might seem like a rough ride, I’ll show you some easy ways to follow when migrating mailboxes from Exchange Server 2016/2019 to Microsoft 365. How to prepare for email migration to Microsoft 365 Before you start the migration process, you need to make sure your environment is ready for the move. For this purpose, you can use this guide in the Microsoft 365 admin center – it will help you connect your organization to Microsoft 365 and integrate your existing user accounts with Microsoft Entra ID. Microsoft also recommends completing the steps below: Set up an SPF record to determine valid email sources for your organization’s Microsoft 365 domain. Set up the Exchange Online Protection service as a means of protection against spam and malware. If you’re behind on updates, make sure to install the latest Cumulative Update (CU). And here is my quick, less obvious Microsoft 365 migration checklist: Verify if your software will work in Microsoft 365 (especially when it comes to server software). Microsoft 365 migration might be the time you learn that there is crucial legacy software that half the company uses and which is hard to replace. Encourage the whole company to clean up projects. It’s much easier to do this before the migration and start fresh. Gather as much information about your on‑premises environment as possible. For example, you might need to recreate access roles and permissions from scratch in the cloud or set up mail flow rules. Without prior research, it will be much more difficult. Verify if you need to migrate service accounts. There can be a lot of them on‑premises and in most cases, you won’t need them after the move. Review mailbox size limits in Exchange Online before migration to see which licenses you’ll need and whic
How to connect and remotely manage Microsoft 365 with PowerShell

How to connect and remotely manage Microsoft 365 with PowerShell

Microsoft 365 web interface was designed to make it easier to manage your tenant right down to its administrative bowels. On the one hand it really is quick and simple to navigate, on the other it definitely lacks some advanced configuration options so loved by sysadmins. Luckily there is the mighty PowerShell coming to the rescue! You should already know its potential, which can also be utilized in Microsoft 365. Find out how.

Comments

  1. avatar
    Castle Interactive LLC says:

    Wow, this article sheds light on a crucial aspect of Microsoft 365 security that many might overlook. The detailed explanation on leveraging the security center and exporting mailbox data to PST is invaluable. It’s commendable how you’ve simplified a potentially complex process, making it accessible for users at all levels. Kudos to the author for sharing such informative content!

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.