Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
You can view many Microsoft Power Platform connector activities in Microsoft Purview, such as when connectors are created, updated, and deleted, or API calls. You can also view activity logs within specific date ranges to gain insights.
Regularly view Power Platform connectors activities in Microsoft Purview to:
- maintain governance, compliance, and security
- gain operational insights
- identify and troubleshoot problems
- mitigate failures.
This article covers prerequisites, how to access the logs in Microsoft Purview, and details about connector activity event types and categories.
Prerequisites
To view connector activity logs in Microsoft Purview, make sure you:
- Review and complete all the prerequisites in the overview article.
- Are an admin with a Microsoft Office 365 E1 or greater license.
- Are assigned either the Audit Logs or View-Only Audit Logs role in Microsoft Purview.
Learn more:
- Manage Dataverse auditing
- Auditing overview
- Learn more about auditing solutions in Microsoft Purview
- Permissions in the Microsoft Purview portal
Access the logs
Take these steps to sign in to the Microsoft Purview portal:
Sign in to the Microsoft Purview portal
In the Microsoft Purview portal, you can access the Audit page two ways:
- On the left navigation pane, select Solutions and then select Audit.
- Or, on the Home page, select the Audit solution card. If the Audit solution card isn't displayed, select View all solutions and then select Audit from the Core section.
The audit solution lets you search activities or create audit retention policies. On the Search page, you can filter for different Power Platform activities in the Activities list. Activities are mapped to event types and categories, which are listed in the tables in this article for you to reference.
The logs are also accessible to developers via the Office 365 Management API.
See Get started with search to learn more about searching the audit logs in Microsoft Purview.
Explore connector events
This table lists the connector events you can search for in the audit logs.
| Connector event | Description |
|---|---|
| API created | A custom API is created. |
| API edited | A custom API is updated. |
| API deleted | A custom API is deleted. |
| Connection created or edited | A connection is created or updated. |
| Connection deleted | A connection is deleted. |
| Connection edited | A connection is updated. |
| API permission added or edited | A custom API is shared or the permissions are updated. |
| API made solution-aware | A non-solution API is moved to a solution. |
| API permission removed | Sharing permissions of a custom API are removed. |
| Connection permission added or edited | A connection is shared or sharing permissions are updated. |
| Connection permission removed | Sharing permissions of a connection are removed. |
| Gateway cluster edited | A gateway cluster is updated. |
| Gateway permission added or edited | A gateway is shared or the sharing permissions are updated. |
| Gateway permission removed | Sharing permissions of a gateway are removed. |
Added ConnectionDlpEvaluationResult |
Connection is turned off due to data policies. |
View logged activity details
On Audit search, you can select a log and view its activity details. This table lists the available activity details.
Available activity details
The following table lists logging details available in the audit logs.
| Detail | Description |
|---|---|
Date |
Date and time in this format: YYYY-MM-DD HH:MM:SS |
IP Address |
Client's IP address |
Users |
User's email address |
Activity |
Event being audit logged |
Item |
Unique ID of the resource |
CreationTime |
Creation time |
Id |
Request Correlation ID |
Operation |
Name of the operation being audit logged |
OrganizationId |
The unique ID of the tenant |
UserType |
A digit representing the type of user. Examples: 0 = normal user, and 2 = admin user |
ClientIP |
Client's IP address |
ObjectID |
The unique ID of the user |
UserId |
Email address of the user |
AdditionalInfo |
Additional information about the event:EnvironmentName: The unique ID of the environmentActionName: The API action that led to the event |
ResourceId |
The unique ID of the resource. Examples: custom api, and connection or gateway |