View information about plug-in steps
Plug-ins contain code that enables server-side customization of Microsoft Dataverse data operations. Each plug-in is registered to execute at a specific point within that operation, which is called a step. You may need to find which plug-in steps are registered for specific events and you may need to temporarily disable plug-in steps to avoid issues caused by the plug-in.
This article describes how you can view information about plug-ins and disable and enable them using the Power Platform admin center or Power Apps. You can also perform these actions by installing and using the Plug-in Registration tool (PRT).
To view all plug-in steps for an environment, complete the following steps in Power Apps.
- Sign in to Power Apps.
- Select Solutions.
- Select Default Solution.
- Select Objects > Plug-in steps.
Plug-ins on the System User table can interfere with user sync operations. To make these more visible for system administrators, you can find information about these steps in the Power Platform admin center.
Follow these steps to view plug-in information such as the plug-in name, status, the user under whose identity the plug-in is executing, user license status, and more. You can use the information displayed in this experience to identify common issues related to plug-in execution.
Note
At this time, only plug-ins of the System User entity type are supported.
- Sign in to the Power Platform admin center.
- Select Environments in the navigation pane.
- Select an environment.
- Select Settings > Users + permissions > Plug-ins.
- View information about all plug-ins (System User entity type only) installed in the environment.
If you need to disable a plug-in, see Disable or enable a plug-in step.
If you need to change user impersonation for a plug-in, see Set user impersonation for a step.
To change the license assignment for a user in the Microsoft 365 admin center, see To assign a license.
When the system user table is updated with a SetBusiness unit, the post operation plug-in runs twice because these are two separate update operations in the event pipeline. However, the pre-operation plug-in is only run once.
To prevent the post operation from running twice, you can check for the businessunit field update and run your business process accordingly.
More information: Event execution pipeline