Update delegated-deployments-setup.md

Updated the documentation to reflect the latest approval behaviors. OnDeploymententRequested doesn't work even when Export Step Required is disabled. Confirmed by MS Support should always use OnApprovalStarted.

power-platform/alm/delegated-deployments-setup.md

@@ -31,7 +31,7 @@ For a delegated deployment with a service principal, follow these steps.
     Lower permission security roles cannot deploy plug-ins and other code components.
 1. Choose (check) **Is delegated deployment** on a pipeline stage, select **Service Principal**, and enter the Client ID. Click **Save**.
 1. Create a cloud flow within the pipelines host environment. Alternative systems can be integrated using pipelines' Dataverse API's.
-1. Select the **OnApprovalStarted** trigger. **OnDeploymentRequested** can also be used if **Pre-Export Step Required** is disabled on the pipeline stage.
+1. Select the **OnApprovalStarted** trigger.
 1. Add steps for your desired custom logic.
 1. Insert an approval step. Use Dynamic content for sending deployment request information to the approver(s).
 1. Insert a condition.
@@ -75,7 +75,7 @@ To deploy as the pipeline stage owner, follow these steps.
     - The pipeline stage owner’s identity will be used for all deployments to this stage.
     - Similarly, this identity must be used to approve deployments.
 1.	Create a cloud flow in a solution within the pipelines host environment.
-    1. Select the **OnApprovalStarted** trigger. **OnDeploymentRequested** can also be used if **Pre-Export Step Required** is disabled on the pipeline stage.
+    1. Select the **OnApprovalStarted** trigger.
     1. Insert actions as desired. For example, an approval.
     1. Add Dataverse **Perform an unbound action**.  
       Action Name: UpdateApprovalStatus (20 = completed, 30 = rejected)