Microsoft Entra Suite Tech Accelerator
Aug 14 2024, 07:00 AM - 09:30 AM (PDT)
Microsoft Tech Community

Azure Information Protection (AIP) Scanner_ Guidance for November 2023 and beyond

Copper Contributor



We are currently in process of testing the AIP Scanner to point towards on premises Nasuni file shares. We can get the scanner to work against a test folder but we are still having some obstacles. We have an open ticket with MS Engineering to help troubleshoot further (hopefully this week even).


The main questions I have at this moment are:


  • Is it STILL advisable to have the scanner hooked up to a Log Analytics workspace in Azure to have it display results?
  • If not, will the scanner results show up in Compliance Portal?
    • If they do show up in Content Explorer, currently that shows only OneDrive, Outlook, SharePoint, and Teams. Our on-premises files shares would need to be differentiated somehow for searching and reporting purposes through the GUI.

I know this is a lot but looking forward to hopefully getting some further guidance. 


Thanks and God Bless!

Luke Fisher


P.S. This was a helpful walkthrough from 2 years ago.... E04 - AIP Scanner - Microsoft Purview Customer Experience Engineering (CxE)

2 Replies



Hi Luke! Thank you for posting your question here.


First, I hope your ticket is resolved soon, feel free to add some of those obstacles here as well, if you'd like.


Second, if you configured the Azure Analytics connection in the past, I do not believe there is a need to remove it but do note that the Azure side has been completely retired. Most recommendations would be to leverage activity explorer, which will show the movement/label changes/DLP policy matches/violations against the repo's you've targeted with the scanner, as well as using the auto-generated csv file, located at the below location, for a custom, org-specific power bi configuration.






Thanks Mike-- so once configured to point towards on our on premises file shares, Activity Explorer can be used to drill down to the correct Target Path? And on top of that we can leverage some custom-built Power BI reports out of the CSV files?

I think we will go that route instead of a Log Analytics workspace.