Added step impersonation

Plus other updates to text and images

Author: phecke

powerapps-docs/developer/data-platform/media/disable-step-prt.png

@@ -1,7 +1,7 @@
 ---
 title: "Register a plug-in (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "Learn how to register a plug-in in a step of the Microsoft Dataverse event pipeline." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 04/07/2023
+description: "Learn how to register a plug-in assembly and step with the Microsoft Dataverse event framework pipeline." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.date: 06/22/2023
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "divkamath" # GitHub ID
@@ -10,45 +10,25 @@ ms.author: "jdaly" # MSFT alias of Microsoft employees only
 search.audienceType: 
   - developer
 contributors:
-  - PHecke
+  - phecke
   - ProfessorKendrick
 ---
 
 # Register a plug-in
 
 [!INCLUDE[cc-terminology](includes/cc-terminology.md)]
 
-You can use Power Platform Tools for Visual Studio to quickly create and deploy (register) plug-ins. A [quickstart](tools/devtools-create-plugin.md) article is available to show you how.
+After a plug-in is written and compiled, it must be registered with the event framework to execute when a specific entity type (table) and operation (message) is processed by Dataverse. To register a plug-in with the Dataverse event framework requires use of a tool - Plug-in Registration tool (PRT), or the Power Platform Tools extension for Visual Studio. 
 
-A more manual process of writing, registering, and debugging a plug-in is:
+The PRT specializes in object registrations and editing those registrations. This article describes how to register a plug-in assembly and step using the Plug-in Registration tool.
 
-1. Create a .NET Framework class library project in Visual Studio
-1. Add the `Microsoft.CrmSdk.CoreAssemblies` NuGet package to the project
-1. Implement the <xref:Microsoft.Xrm.Sdk.IPlugin> interface on classes to be registered on plug-in steps.
-1. Add your code to the <xref:Microsoft.Xrm.Sdk.IPlugin.Execute*> method required by the interface
-    1. Get references to services you need
-    1. Add your custom business logic
-1. Sign & build the assembly
-1. Test the assembly
-    1. Register the assembly in a test environment
-    1. Add your registered assembly and steps to an unmanaged solution
-    1. Test the behavior of the assembly
-    1. Verify expected trace logs are written
-    1. Debug the assembly as needed
+The Visual Studio extension provides a more feature rich development environment and covers the entire coding, deployment, and debugging/profiling flow. For information about using the Power Platform Tools extension for Visual Studio see [quickstart](tools/devtools-create-plugin.md).
 
-This topic describes how to register a plug-in assembly and step, and add them to a solution. Additional information can be found in these tutorials:
+## Plug-in Registration tool
 
-- [Tutorial: Write and register a plug-in](tutorial-write-plug-in.md)
-- [Tutorial: Debug a plug-in](tutorial-debug-plug-in.md)
-- [Tutorial: Update a plug-in](tutorial-update-plug-in.md)
+The Plug-in Registration tool (PRT) enables you to register your plug-in assemblies, and other types of objects, with Dataverse. PRT is one of several Dataverse tools available for download from NuGet.org. Follow the instructions in [Dataverse development tools](download-tools-nuget.md) to download PRT and optionally other development tools.
 
-## Plug-in Registration tool (PRT)
-
-You use the Plug-in Registration tool (PRT) to register your plug-in assemblies and steps.
-
-PRT is one of the tools available for download from NuGet. Follow the instructions in [Dataverse development tools](download-tools-nuget.md). That topic includes Power Platform CLI instructions to download PRT and other development tools from NuGet.
-
-After you download the PRT, use the [Connect using the Plug-in Registration tool](tutorial-write-plug-in.md#connect-using-the-plug-in-registration-tool) steps in the [Tutorial: Write and register a plug-in](tutorial-write-plug-in.md) to connect to your Microsoft Dataverse environment.
+After you download the PRT, follow the [Connect using the Plug-in Registration tool](tutorial-write-plug-in.md#connect-using-the-plug-in-registration-tool) instructions to connect the tool to your target Dataverse environment where your plug-in is to be registered.
 
 ## Register an assembly
 
@@ -76,55 +56,6 @@ After selecting the name of the Default Solution in the internal solution list,
 
 ![View all registered assemblies.](media/view-plug-in-assemblies-default-solution.png)
 
-### Query registered assemblies with code
-
-To view information about registered assemblies without the PRT or the application, use the following Web API query in your browser:
-
-```
-[org uri]]/api/data/v9.0/pluginassemblies
-?$filter=ishidden/Value eq false
-&$select=
-createdon,
-culture,
-customizationlevel,
-description,
-isolationmode,
-major,
-minor,
-modifiedon,
-name,
-pluginassemblyid,
-publickeytoken,
-version
-```
-
-Or use following FetchXml to retrieve it in a program you write:
-
-```xml
-<fetch>
-  <entity name='pluginassembly' >
-    <attribute name='createdon' />
-    <attribute name='culture' />
-    <attribute name='customizationlevel' />
-    <attribute name='description' />
-    <attribute name='isolationmode' />
-    <attribute name='major' />
-    <attribute name='minor' />
-    <attribute name='modifiedon' />
-    <attribute name='name' />
-    <attribute name='pluginassemblyid' />
-    <attribute name='publickeytoken' />
-    <attribute name='version' />
-    <filter type='and' >
-      <filter>
-        <condition attribute='ishidden' operator='eq' value='false' />
-      </filter>
-    </filter>
-  </entity>
-</fetch>
-```
-More information: [Use FetchXML with FetchExpression](org-service/entity-operations-query-data.md#use-fetchxml-with-fetchexpression)
-
 ## Add your assembly to a solution
 
 As described in [View registered assemblies](#view-registered-assemblies), the assembly registration you created was added to the system **Default Solution**. You should add your assembly to an unmanaged solution so you can distribute it to other organizations.
@@ -238,7 +169,6 @@ In Dataverse, only the following messages support entity images:
 |`SetState`|`EntityMoniker`|The table for which the state is set.|
 |`Update`|`Target`|The updated table.|
 
-
 #### Types of entity images
 
 There are two types of entity images: **Pre Image** and **Post Image**. When you configure them, these images will be available within the execution context as <xref:Microsoft.Xrm.Sdk.IExecutionContext.PreEntityImages> and <xref:Microsoft.Xrm.Sdk.IExecutionContext.PostEntityImages> properties respectively. As the names suggest, these snapshots represent what the table looks like before the operation and after the operation. When you configure an entity image, you'll define a table alias* value that will be the key value you'll use to access a specific entity image from the `PreEntityImages` or `PostEntityImages` properties.
@@ -252,7 +182,6 @@ When you configure an entity image, it's important that you recognize that the t
 - You can only have a **Post Image** for steps registered in the **PostOperation** stage of the execution pipeline because there's no way to know what the table properties will be until the transaction is completed.
 - For an `Update` operation that is registered in the **PostOperation** stage you can have both a **Pre Image** AND a **Post Image**.
 
-
 #### Add an entity image
 
 Use the [Power Platform Tools](tools/devtools-install.md) extension for Visual Studio to [add an entity image](tools/devtools-create-plugin.md#add-an-entity-image) to a plug-in step.
@@ -289,7 +218,6 @@ Plug-in assemblies can be versioned using a semantic versioning format of `major
 
   When an updated solution containing the revised assembly is imported, the assembly is considered a different assembly than the previous version of that assembly in the existing solution. Plug-in registration steps in the existing solution will continue to refer to the previous version of the assembly. If you want existing plug-in registration steps for the previous assembly to point to the revised assembly, you'll need to use the Plug-in Registration tool to manually change the step configuration to refer to the revised assembly type. This should be done before exporting the updated assembly into a solution for later import.
 
-
 ## Unregister or disable plug-ins and components
 
 You can unregister or disable plug-ins and their components using the Plug-in Registration tool (PRT).
@@ -310,28 +238,47 @@ You can also delete **Plug-in Assemblies** and **Sdk Message Processing Steps**
 > [!NOTE]
 > You cannot delete (unregister) any **Plug-in Assemblies** while existing **Sdk Message Processing Steps** depend on them. Entity images are not available to be deleted separately, but they will be deleted when any steps that use them are deleted.
 
-### Disable steps
+### Disable or enable a plug-in step
+
+With the Plug-in Registration tool running and logged into the target Dataverse environment, you can proceed to disable or enable plug-in steps. Disabling a step effectively turns off the plug-in from executing when Dataverse processes the entity and message combination specified in the step registration.
 
-The PRT provides commands to disable and enable steps.
+To disable or enable a registered plug-in step:
 
-![disable a step using the PRT.](media/disable-step-prt.png)
+1. Expand the target plug-in assembly node in the assembly view until you see the desired step registration node.
+1. Choose the step, and then choose **Enable** or **Disable** in either the context menu or the toolbar.
 
-![enable a step using the PRT.](media/enable-step-prt.png)
+|Disable a plug-in step|Enable a plug-in step|
+|--|---|
+|:::image type="content" source="media/enable-step-prt.png" alt-text="Disable a step using the Plug-in Registration tool.":::
+|:::image type="content" source="media/enable-step-prt.png" alt-text="Enable a step using the Plug-in Registration tool.":::|
 
-You can also disable steps in the solution explorer using the **Activate** and **Deactivate** commands.
+You can also disable or enable steps in the legacy Dataverse Solution Explorer user interface using the **Activate** and **Deactivate** command options.
 
-![foo.](media/step-activate-deactivate-commands-solution-explorer.png)
+![Changing a plug-in step in legacy Solution Explorer.](media/step-activate-deactivate-commands-solution-explorer.png)
+
+### Change user impersonation for a step
+
+With the Plug-in Registration tool running and logged into the target Dataverse environment, you can proceed to make changes to an existing step registration. In this section, we will discuss changing the user on whos behalf the plug-in will perform its operations. Meaning, the effective user that is performing the data operations initiated by the plug-in. By default, the calling user (the user that invoked an operation in Dataverse) is the owner of said operations. However a different user can be specified in the step registration. You will need to have the System Administrator or System Customizer role to perform this operation.
+
+To change the user in a registered plug-in step:
+
+1. Expand the target plug-in assembly node in the assembly view until you see the desired (Step) registration node.
+1. Select the step, and then select **Update** in either the context menu or the toolbar.
+1. Choose a different user from the drop-down list of available users next to the **Run in User's Context** label.
+1. Choose **Update Step**.
+
+More information: [Impersonate a user](impersonate-a-user.md)
 
 ## Next steps
 
 [Debug Plug-ins](debug-plug-in.md)
 
 ### See also
+
 [Write plug-ins to extend business processes](plug-ins.md)<br />
 [Write a plug-in](write-plug-in.md)<br />
 [Tutorial: Write and register a plug-in](tutorial-write-plug-in.md)<br />
 [Tutorial: Debug a plug-in](tutorial-debug-plug-in.md)<br />
 [Tutorial: Update a plug-in](tutorial-update-plug-in.md)<br />
 
-
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]