{"id":3741,"date":"2026-04-22T15:04:08","date_gmt":"2026-04-22T22:04:08","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-sdk\/?p=3741"},"modified":"2026-04-24T11:13:17","modified_gmt":"2026-04-24T18:13:17","slug":"azd-multi-language-hooks","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-sdk\/azd-multi-language-hooks\/","title":{"rendered":"Write azd hooks in Python, JavaScript, TypeScript, or .NET"},"content":{"rendered":"

Hooks are one of the most popular features in azd<\/code>, and now you can write them in Python, JavaScript, TypeScript, or .NET, not just Bash and PowerShell.<\/em><\/p>\n

What’s new?<\/h2>\n

The Azure Developer CLI (azd<\/code>) hook system now supports four more languages beyond Bash and PowerShell. You can write hook scripts in Python<\/strong>, JavaScript<\/strong>, TypeScript<\/strong>, or .NET<\/strong>. azd<\/code> automatically detects the language from the file extension, manages dependencies, and runs the script with no extra configuration required.<\/p>\n

Why it matters<\/h2>\n

Hooks let you run custom logic at key points in the azd<\/code> lifecycle before provisioning, after deployment, and more. Previously, hooks supported scripts written in Bash and PowerShell, which meant developers had to context-switch to a shell scripting language even if their project was entirely Python or TypeScript. Now you can write hooks in the same language as your application, reuse existing libraries, and skip the shell scripting.<\/p>\n

How to use it<\/h2>\n

Point a hook at a script file in azure.yaml<\/code>, and azd<\/code> infers the language from the extension. If the extension is ambiguous or missing, you can specify the language explicitly with the kind<\/code> field:<\/p>\n

hooks:\r\n  preprovision:\r\n    run: .\/hooks\/setup\r\n    run: .\/hooks\/setup.py\r\n    kind: python    # explicit \u2014 overrides extension inference<\/code><\/pre>\n
Here’s what a typical setup looks like:<\/p>\n
# azure.yaml\r\nhooks:\r\n  preprovision:\r\n    run: .\/hooks\/setup.py\r\n\r\n  postdeploy:\r\n    run: .\/hooks\/seed.ts\r\n\r\n  postprovision:\r\n    run: .\/hooks\/migrate.cs<\/code><\/pre>\n
Python hooks<\/h3>\n
Place a requirements.txt<\/code> or pyproject.toml<\/code> in the same directory as your script or a parent directory. azd<\/code> walks up the directory tree from the script location to find the nearest project file, creates a virtual environment, installs dependencies, and runs the script.<\/p>\n
hooks\/\r\n\u251c\u2500\u2500 setup.py\r\n\u2514\u2500\u2500 requirements.txt<\/code><\/pre>\n
Then reference the script in your azure.yaml<\/code>:<\/p>\n
hooks:\r\n  preprovision:\r\n    run: .\/hooks\/setup.py<\/code><\/pre>\n
JavaScript and TypeScript hooks<\/h3>\n
Place a package.json<\/code> in the same directory as your script or a parent directory. azd<\/code> runs npm install<\/code> (or the package manager specified in config<\/code>) and executes the script. TypeScript scripts run via npx tsx<\/code> with no compile step or tsconfig.json<\/code> needed:<\/p>\n
hooks\/\r\n\u251c\u2500\u2500 seed.ts\r\n\u2514\u2500\u2500 package.json<\/code><\/pre>\n
Then reference the script in your azure.yaml<\/code>:<\/p>\n
hooks:\r\n  postdeploy:\r\n    run: .\/hooks\/seed.ts<\/code><\/pre>\n
.NET hooks<\/h3>\n
Two modes are supported:<\/p>\n