Wrong status reported when PowerShell DSC extension fails
I have a DSC extension that failed (using version 1.7 that have been removed) during a deployment but in the Audit log I still see the step as Succeeded (see the attached screenshot)
If the DSC or any other extension fails I expect that it fails the deployment and that it reflect so in the Audit log.
Steps to reproduce:
Deploy the following template or any other of your own that refer a version not available of the DSC extension. When the deployment reach that point and fails, go back in the Audit logs, the step should be shown as Succeeded.