A company wants to extend their Lifecycle Workflows to trigger a custom script in an on-premises environment whenever a new user is onboarded. Which feature should be used to integrate the workflow with the custom script?
This is the supported method for extending Lifecycle Workflows. The custom task extension allows the workflow to send a payload to a Logic App, which can then use connectors to interact with on-premises systems, databases, or other third-party SaaS applications to complete the onboarding process.
Why this answer
Lifecycle Workflows in Microsoft Entra ID Governance support 'Custom Task Extensions' that allow you to call an external service — specifically an Azure Logic App — as part of a workflow. The Logic App can then execute the custom script in the on-premises environment (e.g., via an on-premises data gateway or hybrid runbook worker). This is the designed extensibility mechanism for integrating Lifecycle Workflows with external systems and custom code.
Exam trap
SC-300 often tests the misconception that Lifecycle Workflows can directly execute scripts or call Graph APIs — candidates overlook that the supported extension path is a Custom Task Extension invoking an Azure Logic App.
How to eliminate wrong answers
Option A is wrong because Lifecycle Workflows do not provide a built-in 'Microsoft Graph API call' task that lets you arbitrarily invoke external scripts — the supported extension mechanism is the Custom Task Extension, not direct Graph calls from the task list. Option B is wrong because dynamic groups are membership rules based on user attributes; they do not trigger PowerShell scripts on membership changes, and they have no execution capability. Option D is wrong because Conditional Access 'Custom Authentication Extensions' are used during the authentication flow to call external systems for additional authentication signals — they are not part of Lifecycle Workflows and cannot trigger onboarding scripts.