The Filter query parameters used while executing the FetchXML JSON of Key Value pair reflecting the values that were created or updated Unique identifier of the user GUID in the organization The customer engagement apps schema contains fields specific to customer engagement apps and partner teams. The Microsoft 365 audit type (Regular, System) IP Address of the user or corporate gatewayĪ unique value used to associate related rows (e.g., when a large row is split) You can find this ID under Dynamics Developer Resources. Unique identifier of the organization from which the log was generated. IP address of the user or corporate gateway Field nameĭate and time of when the log was generated in UTC The Base schema contains the common fields. Some fields are common to all applications that send audit data to Microsoft 365, while others are specific to customer engagement apps. Schemas define which fields are sent to the Microsoft 365 Security and Compliance Center. They might contain critical customer information. Logging multimedia assets that are shown when a report is displayed. Critical customer content information might be displayed on the report.Įxporting a report to different formats moves the data outside of the secure environment and is vulnerable to threats. Microsoft support engineer activities on customer tenant and environment. Microsoft support engineer activities on customer environment. Critical customer content information is part of these views.Įxporting data to Excel moves the data outside of the secure environment and is vulnerable to threats.Īctions taken via the core platform or surround apps calling into the SDK to perform an action needs to be logged. Users of Dynamics view information in bulk, like grid views, Advanced Find search, etc. Logging all CRUD activities essential for understanding the impact of a problem and being compliant with data protection impact assessments (DPIA). The following are a sample of user events you can audit. Logging takes place at the SDK layer which means a single action can trigger multiple events that are logged. Available for production and not sandbox environments.A Microsoft 365 Enterprise E3 or E5 subscription is required to do Activity Logging.This topic covers how you can set customer engagement apps to audit a broad range of data processing activities and use the Microsoft 365 Security and Compliance Center to review the data in activity reports. This information from Activity Logging can be used when you perform a Data Protection Impact Assessment (DPIA) addressing the use of Office, Power Apps, Microsoft Power Automate, and customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation). It's critical that you audit the entirety of data processing actions taking place to be able to analyze for possible security breaches. Protecting data, preserving privacy, and complying with regulations such as the General Data Protection Regulation are certainly some of the highest priorities for your business.