Runtime installations on Azure Functions

May considering this:

Bundle the Utility with Your Function
•    Place the runtime binaries/scripts in your function app’s file system (e.g., under function_app/tools/).
•    Reference them directly in your Python code.
•    Works if the utility is lightweight and doesn’t require complex installation.
2. Use Azure Functions Custom Handlers / Extensions
•    If the ETL runtime is not Python native, you can wrap it with a custom handler (essentially a process your function triggers).
•    This allows you to call external executables packaged with your function.
3. Leverage Azure Functions Premium Plan with Docker
•    Package the ETL runtime inside a custom Docker image.
•    Deploy your function app using that image.
•    This is the most robust way to ensure the runtime is always present, since the container image defines the environment.
4. Call Out to Informatica Cloud / External Service
•    Instead of installing the runtime locally, invoke Informatica jobs via their REST API or SDK.
•    This avoids the need to embed the runtime in Azure Functions at all.
•    Often the recommended approach for serverless, since it keeps the function lightweight.