The official specifications are listed in the docs here but at least 4 cores and 8GB RAM is required (more is highly recommended) and at least 10GB of free storage space for temporary files (again, more = better).At least one Server (Physical or Virtual) capable of running the AIP scanner.However, before production deployment we recommend that you read through the official documentation at to ensure that you will not run into any issues. We will walk you through the whole process so that it is as painless as possible. Now, this may seem like a lot of things, but don't worry. Configuring AIP Azure Log Analytics (Optional).Create Azure AD applications for service authentication.Cloud service account (creation or sync).To configure the scanner, there are a few steps you need to follow: Once the data is discovered, the AIP scanner(s) can aggregate the findings and display them in Analytics reports so you can begin visualizing your data risk and see recommendations for setting up protection rules based on the content. The AIP scanner allows you to scan your on premises data repositories against the standard Office 365 sensitive information types and custom types you build with keywords or regular expressions. In this article, we will walk you through the discovery of sensitive data and show you options to classify and protect that data. Managing this data the way you manage other corporate resources is a daunting but achievable task using tools that you likely already own. Most modern organizations have terabytes (or petabytes) of unstructured data sitting in their on-premises data repositories and SharePoint libraries. If you would like to deploy the Unified Labeling version, please see. NOTE : This version of the blog is based on the AIP Classic version of the AIP scanner.

Microsoft safety scanner not working