eBooks/eGuides

stores a lot of its data in Exchange mailboxes, so if an Exchange Mailbox is deleted then any Teams data residing in that mailbox is also deleted. Backup applications were never designed to act as eDiscovery tools. Even so, a good backup application not only has the potential to act as an eDiscovery tool. Its capabilities might even surpass those of the tools that are built into Microsoft 365. To show you what I mean, consider all of the things that normally happen as a part of the eDiscovery process. When an organization receives a mandate to produce certain documents, the first thing that it does is to use an eDiscovery interface to search for the requested documents. Once the search is complete, the organization will typically place those documents under legal hold to prevent them from being altered or deleted. The last step in the process is usually to export copies of the documents so that they can be shared with whoever requested them. Searching Data With that in mind, consider how a good backup application can perform these same tasks. Even though a backup application was never designed to act as an eDiscovery tool, a good backup application will likely include a search interface that allows an administrator to search for the data that has been backed up. As such, an administrator could conceivably use such an interface to perform eDiscovery within the context of a backup. Even if the native Microsoft 365 search interface is limited in its scope, a search tool that is integrated into a Microsoft 365 / Teams backup should be able to locate any data within the backup, even if that data is not something that would normally be surfaced by the native Microsoft 365 search tool. Of course, it isn't just administrators who sometimes need to locate data. A backup search interface can be useful to end

• Cover