fixes

Author: alexwolfmsft

articles/azure-developer-cli/TOC.yml

@@ -123,8 +123,6 @@
       href: project-name-validation.md
     - name: Customize workflows using command and event hooks
       href: azd-extensibility.md
-    - name: Interactive hooks
-      href: interactive-hooks.md
     - name: Enable demo mode
       href: demo-mode.md
     - name: Configure template sources

articles/azure-developer-cli/azd-extensibility.md

@@ -165,8 +165,6 @@ hooks:
 
 The `azd hooks run` command allows you to execute hooks independently of their normal trigger events. This is useful for testing and debugging hooks without going through the entire workflow.
 
-### Basic usage
-
 ```bash
 azd hooks run <hook-name>
 ```
@@ -189,6 +187,33 @@ azd hooks run postup -e staging
 azd hooks run predeploy --service frontend --platform posix -e production --interactive
 ```
 
+## Configure interactive mode
+
+Hooks run in interactive mode by default. Interactive hooks mode allows you to run hook scripts with direct console interaction, making it easier to debug, monitor, and interact with your hooks in real-time. You can explicitly set the `interactive` property in your hook configuration if you want to disable interactive mode for a specific hook:
+
+```yaml
+hooks:
+  postprovision:
+    shell: sh
+    run: ./scripts/setup-database.sh
+    interactive: false # Default is true
+```
+
+For service-specific hooks:
+
+```yaml
+services:
+  api:
+    project: ./src/api
+    language: js
+    host: appservice
+    hooks:
+      postdeploy:
+        shell: sh
+        run: ./scripts/post-deploy-verification.sh
+        interactive: false  # Override the default interactive mode
+```
+
 ### Use environment variables with hooks
 
 Hooks can get and set environment variables in the `.env` file using the `azd env get-values` and `azd set <key> <value>` commands. Hooks can also retrieve environment variables from your local environment using the `${YOUR_ENVIRONMENT VARIABLE}` syntax. `azd` automatically sets certain environment variables in the `.env` file when commands are run, such as `AZURE_ENV_NAME` and `AZURE_LOCATION`. Output parameters from the `main.bicep` file are also set in the `.env` file. The [manage environment variables](/azure/developer/azure-developer-cli/manage-environment-variables) page includes more information about environment variable workflows.

articles/azure-developer-cli/azd-init-workflow.md

@@ -159,4 +159,4 @@ After initializing your project with `azd init`, you can:
 - [Azure Developer CLI commands](azd-commands.md)
 - [Azure.yaml schema reference](azd-schema.md)
 - [Azure Developer CLI templates](azd-templates.md)
-- [Template galleries](template-galleries.md)
+- [Template galleries](azd-template-galleries.md)