How does revocation work?
Revocation Lists can be implemented in order to revoke any entities in the RMS infrastructure. This includes protected content, principals, licenses, applications and certificates. A revocation policy must be defined in a Rights Policy Template if it is to be used. When a client attempts to access protected content, a cached Revocation List is checked (or if required, a new Revocation List is downloaded to the client machine and cached). If it is determined that any entity involved in the current operation has been revoked, the RMS-enabled application will prevent the Use License from binding to the content, and will therefore prevent the consumption of the content.
