Analytics and central reporting for the AIP classic client (public preview)
This article describes procedures to use for central reporting when using the Azure Information Protection classic client.
For more information, see Analytics and central reporting for Azure Information Protection in the main AIP documentation.
As of March 1, 2022, we are sunsetting the AIP audit log and analytics, with a full retirement date of September 31, 2022. For more information, see Removed and retired services.
Prevent the classic client from sending auditing data
To prevent the Azure Information Protection classic client from sending auditing, set the policy setting of Send audit data to Azure Information Protection analytics to Off:
| Requirement | Instructions |
|---|---|
| To configure most users to send data, with a subset of users who cannot send data | Set Send audit data to Azure Information Protection analytics to Off in a scoped policy for the subset of users. This configuration is typical for production scenarios. |
| To configure only a subset of users who send data | Set Send audit data to Azure Information Protection analytics to Off in the global policy, and On in a scoped policy for the subset of users. This configuration is typical for testing scenarios. |
Content matches for deeper analysis
Azure Information Protection lets you collect and store the actual data that's identified as being a sensitive information type (predefined or custom). For example, this can include credit card numbers that are found, as well as social security numbers, passport numbers, and bank account numbers. The content matches are displayed when you select an entry from Activity logs, and view the Activity Details.
By default, Azure Information Protection clients don't send content matches. To change this behavior so that content matches are sent, select a checkbox as part of the configuration for Azure Information Protection analytics. The checkbox is named Enable deeper analytics into your sensitive data.
If you want most users who are using this client to send content matches but a subset of users cannot send content matches, select the checkbox and then configure an advanced client setting in a scoped policy for the subset of users.
Usage logging for the RMS and the AIP classic client
The Azure Rights Management Service (RMS) provides the data protection for your organization's documents and emails and it can log every request to it.
These requests include when users protect documents and email and also consume this content, actions performed by your administrators for this service, and actions performed by Microsoft operators to support your Azure Information Protection deployment.
The following request types are relevant for users with the AIP classic client only. For more information about usage logging, see the main Azure Information Protection documentation.
| Request type | Description |
|---|---|
| DeleteTemplateById | A call is made from the Azure portal, to delete a template by template ID. |
| DocumentEventsCsv | A call is made from the document tracking site to download the .CSV file for a single document. |
| ExportTemplateById | A call is made from the Azure portal to export a template based on a template ID. |
| FEGetAllTemplates | A call is made, from a mobile device (front-end) to get the templates. |
| GetAllDocs | A call is made from the document tracking site to load the all documents page for a user, or search all documents for the tenant. Use this value with the admin-action and acting-as-admin fields: - admin-action is empty: A user views the all documents page for their own documents. - admin-action is true and acting-as-user is empty: An administrator views all documents for their tenant. - admin-action is true and acting-as-user is not empty: An administrator views the all documents page for a user. |
| GetAllTemplates | A call is made from the Azure portal, to get all the templates. |
| GetConnectorAuthorizations | A call is made from the RMS connectors to get their configuration from the cloud. |
| GetSingle | A call is made from the document tracking site to navigate to a single document page. |
| GetTemplateById | A call is made from the Azure portal to get a template by specifying a template ID. |
| LoadEventsForMap | A call is made from the document tracking site to navigate to the map view for a single document. |
| LoadEventsForSummary | A call is made from the document tracking site to navigate to the timeline view for a single document. |
| LoadEventsForTimeline | A call is made from the document tracking site to navigate to the map view for a single document. |
| ImportTemplate | A call is made from the Azure portal to import a template. |
| RevokeAccess | A call is made from the document tracking site to revoke a document. |
| SearchUsers | A call is made from the document tracking site to search all users in a tenant. |
| UpdateNotificationSettings | A call is made from the document tracking site to change the notification settings for a single document. |
| UpdateTemplate | A call is made from the Azure portal to update an existing template. |