diff --git a/intune/epm/create-elevation-rules.md b/intune/epm/create-elevation-rules.md
index e956035747..6c711ec0e4 100644
--- a/intune/epm/create-elevation-rules.md
+++ b/intune/epm/create-elevation-rules.md
@@ -67,7 +67,9 @@ Each elevation rule instructs EPM on how to:
 
     - **Deny all** – All child processes launch without elevated context.
 
-    - **Allow child processes to run elevated** – Any child process launched by the elevated parent will automatically run elevated. When this option is selected, rule evaluation for the child process is skipped, including deny rules. This means a child process may run elevated even when an explicit deny rule exists for that process.
+    - **Allow all child processes to run elevated** – Any child process launched by the elevated parent will automatically run elevated. When this option is selected, rule evaluation for the child process is skipped, including deny rules. This means a child process may run elevated even when an explicit deny rule exists for that process.
+
+    - **Not configured** – No child process behavior is specified in the policy. Child processes inherit the parent's elevated context (default Windows behavior), and rule evaluation for the child process is skipped, including deny rules. This behavior is equivalent to **Allow all child processes to run elevated**. Note that the default selection when creating a rule is **Require rule to elevate**.
 
     **Best practice:** Avoid creating overly broad elevation rules for applications that can start other processes (for example, command shells or script engines) to prevent unintended elevation.