The Azure Machine type is based on VMware implementing a Custom Resource that maps to a vRealize Orchestrator Azure plugin object type. All Custom Resources will have two lifecycle stages of Allocation Workflow and Deallocation Workflow, which are the workflows that are executed in vRealize Orchestrator when the object is "created" and "destroyed". There is no way to add additional lifecycle stages to Custom Resources. You can map custom day 2 operations to your custom resources objects, but that is the extent of the customization allowed.
