Firstly in step 1 to step 3, we launched the Plugin Registration tool and connected to our Dynamics 365 instance.

In step 4 to step 6, we registered the assembly that holds our plugin. For online instances, we are bound to use the sandbox isolation mode and database registered assemblies. Step 6 uploads our assembly to a Dynamics 365 instance's database.

Next, in step 7 and step 8, we registered a plugin step. This specific step allows the plugin to execute after an account is updated, and specifically when the account name is changed. There are a few events that the plugin can register to including: create, delete, assign, and more, as well as custom action messages. The message field has an autocomplete function to assist you when typing the message name. A plugin can be built in a generic fashion and registered to more than one entity by registering multiple steps for different entities or simply not specifying any entities in the primary entity field (not recommended due to the overhead of executing the logic for all entities).

Finally, in step 9 and step 10, we registered an image that will include the attributes we are interested in inspecting in our plugin. These steps are not required but were added just to illustrate how to register images. The images can be in the form of a pre-image (state of the record before any changes are applied) or post-image (state the record is in after the changes have been applied).