Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community
SOLVED

AIP Tracking and Revocation

Copper Contributor
We are working with AIP tracking and revocation. When a file is accessed outside the organization it is not being logged in the tracking portal. Is the behaviour normal? Thanks
11 Replies

Well, depends. Generally speaking files must be "registered" with the tracking portal by selecting the corresponding option in the client. It does not happen automatically for all files.

@Vasil Michev  we have E3 + EMS licenses, so do we still need E5 for track and Revoke?

 

I have heard that MS is going to launch a new portal for track and revoke. So by any chance would it available by enterprises with E3+EMS

@James Escober 

@thesmilingguruYou need to have minimum of EMS E3 license for tracking and revocation

*** For classic AIP client only ***

 

Only files that have protection applied (i.e. the AIP label used to classify the file includes an RMS template to control access and usage) will show up in the Track & Revoke portal.

Files that are labelled without protection are not tracked because when they are accessed, no authentication happens with Azure RMS so no access attempts can be logged.

 

(Unified labelling client does not support track & revoke.)

@markwarnes - I'm still unsure as to why Unified Labeling doesn't support Track and Revoke? Basically, Microsoft Information Protection (...Unified Labeling) is technically "a step up" from AIP, but this handy feature is no longer included.

 

Do you have any ideas or can you point me in the direction of why this is, and if it ever will, or what will replace Track and Revoke? I simply can't find much info on why this is.

 

Cheers, Joe

 @markwarnes - As mentioned by @Joe McGiven Corban, the track and revoke feature was a great feature and one of the selling points for AIP internally. Now that Classic client is no longer going to be supported, is there a roadmap for including this feature in UL. 

Thanks, 

best response confirmed by Rafael Dominguez (Microsoft)
Solution

@cpsecurity@Joe McGiven Corban - As far as I can tell, the classic "Track & Revoke" functionality that is curently available with the classic AIP client is not coming to the unified labelling (UL) client at any point on the roadmap.

 

The approach that you should probably be taking now is to make use of central reporting to check for user activities on labelled documents.

 

From the AIP documentation (https://docs.microsoft.com/en-us/azure/information-protection/rms-client/use-client#compare-the-labe...) :

 

"The document tracking site that's supported by the classic client isn't supported by the unified labeling client. However, without the need to first register the document for tracking, administrators can use central reporting to identify whether protected documents are accessed from Windows computers, and whether access was granted or denied."

 

This basically means the the UL client on Windows computers will report activity to the configured Log Analytics workspace when a protected document has been accessed. It's not the same as the dedicated T&R portal but it does offer opportunities to alert on particular document access (either through alerts on the analytics workspace or through monitoring using Azure Sentinel if linked up).

 

@Rafael Dominguez wrote a series of blogs about creating a custom AIP tracking portal that uses the central reporting data -(https://techcommunity.microsoft.com/t5/azure-information-protection/how-to-build-a-custom-aip-tracki.... Definitely worth a look if you've not seen them already.

 

That said, there is a limitation currently - only the UL and classic clients on Windows devices can report their activity to the central reporting workspace. That means native AIP functionality in Office applications and any activity from MacOS, iOS and Android does not get reported. I'm hoping this is one of the gaps of functionality between the native and UL clients that is going to be closed in the near future.

Hi,

I would like restart this discussion, because I am testing last AIP Client 2.9.116 and I would like to understand if "Track & Revoke" option is available in clients or not?

According this article this option was added in 2.9.111.0: https://docs.microsoft.com/en-us/azure/information-protection/rms-client/unifiedlabelingclient-versi...

Nevertheless, I installed version 2.9.116 and I can't see this option in my label bar (https://docs.microsoft.com/en-us/azure/information-protection/rms-client/revoke-access-user).

Thanks.

I have the same problem @Andre_Silva 

Until know I don't have any new update about my question, but I hope have a answer soon.
The option does not comes by default. It will show up only when you apply a label that has custom permission specified in the label settings..
1 best response

Accepted Solutions
best response confirmed by Rafael Dominguez (Microsoft)
Solution

@cpsecurity@Joe McGiven Corban - As far as I can tell, the classic "Track & Revoke" functionality that is curently available with the classic AIP client is not coming to the unified labelling (UL) client at any point on the roadmap.

 

The approach that you should probably be taking now is to make use of central reporting to check for user activities on labelled documents.

 

From the AIP documentation (https://docs.microsoft.com/en-us/azure/information-protection/rms-client/use-client#compare-the-labe...) :

 

"The document tracking site that's supported by the classic client isn't supported by the unified labeling client. However, without the need to first register the document for tracking, administrators can use central reporting to identify whether protected documents are accessed from Windows computers, and whether access was granted or denied."

 

This basically means the the UL client on Windows computers will report activity to the configured Log Analytics workspace when a protected document has been accessed. It's not the same as the dedicated T&R portal but it does offer opportunities to alert on particular document access (either through alerts on the analytics workspace or through monitoring using Azure Sentinel if linked up).

 

@Rafael Dominguez wrote a series of blogs about creating a custom AIP tracking portal that uses the central reporting data -(https://techcommunity.microsoft.com/t5/azure-information-protection/how-to-build-a-custom-aip-tracki.... Definitely worth a look if you've not seen them already.

 

That said, there is a limitation currently - only the UL and classic clients on Windows devices can report their activity to the central reporting workspace. That means native AIP functionality in Office applications and any activity from MacOS, iOS and Android does not get reported. I'm hoping this is one of the gaps of functionality between the native and UL clients that is going to be closed in the near future.

View solution in original post