What is a one sentence summary of your feature request?
Request to Add a File Type for Applying Block and Detection Policies to MIP-Encrypted Documents
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
We would like to request the addition of a file type so that MIP-encrypted M365 documents can be recognized as a distinct file format, allowing them to be included in the block and detection policy targets.
Currently, MIP-encrypted M365 documents are classified as Unidentified file types. As a result, when this category is configured for blocking or logging, other unnecessary garbage data is also blocked or recorded, causing an excessive increase in log volume and operational inconvenience.
How do you currently solve the challenges you have by not having this feature?
Currently, since M365 MIP-encrypted documents do not have a specific file type, we are also selecting the Unidentified file type to block and log them together.
I am sorry for the delayed response, I’ve just returned from my holiday vacation.
We will review your request and get back with a response as soon as possible.
Our team is still looking into this request and for a better technical analysis we kindly ask you to provide some examples of MIP encrypted files. Could you please attach the samples here so our development team can use them in this way?
The file is encrypted with MIP, so it can only be accessed using authorized accounts.
At the moment, the customer using MIP is unable to add additional authorized accounts. As an alternative, they have asked whether it would be possible to provide remote access to a PC where the MIP-protected document can be viewed.