Deploy to Azure Functions (Prisma ORM v6) (/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-azure-functions)

For the complete Prisma documentation index, see llms.txt. A markdown version of any docs page is available by appending .md to its URL.

Learn how to deploy a Prisma Client based REST API to Azure Functions and connect to an Azure SQL database

Location: ORM > v6 > Prisma Client > Deployment > Serverless > Deploy to Azure Functions

This guide explains how to avoid common issues when deploying a Node.js-based function app to Azure using Azure Functions.

Azure Functions is a serverless deployment platform. You do not need to maintain infrastructure to deploy your code. With Azure Functions, the fundamental building block is the function app. A function app provides an execution context in Azure in which your functions run. It is comprised of one or more individual functions that Azure manages, deploys, and scales together. You can organize and collectively manage multiple functions as a single logical unit.

[!NOTE] Use Prisma ORM without Rust binaries

If Prisma ORM's Rust engine binaries cause large bundle sizes, slow builds, or deployment issues (for example, in serverless or edge environments), you can use it without them using this configuration of your generator block:

generator client {
  provider   = "prisma-client-js" // or "prisma-client"
  engineType = "client"
}

Prisma ORM without Rust binaries has been Generally Available since v6.16.0.

Note that you need to use a driver adapter in this case.

When using this architecture:

• No Rust query engine binary is downloaded or shipped.
• The database connection pool is maintained by the native JS database driver you install (e.g., @prisma/adapter-pg for PostgreSQL).

This setup can simplify deployments in serverless or edge runtimes. Learn more in the docs here.

To learn why Prisma ORM moved from Rust binary engines to an all-TypeScript approach, and how the two compare in benchmarks, read this blog post.

• An existing function app project with Prisma ORM

While Prisma ORM works well with Azure functions, there are a few things to take note of before deploying your application.

When deploying a function app, the operating system that Azure functions runs a remote build is different from the one used to host your functions. Therefore, we recommend specifying the following binaryTargets options in your Prisma schema:

generator client {  provider      = "prisma-client-js"  binaryTargets = ["native", "debian-openssl-1.1.x"]}

Generally, when you use a FaaS (Function as a Service) environment to interact with a database, every function invocation can result in a new connection to the database. This is not a problem with a constantly running Node.js server. Therefore, it is beneficial to pool DB connections to get better performance. To solve this issue, you can use the Prisma Accelerate. For other solutions, see the connection management guide for serverless environments.

For more insight into Prisma Client's API, explore the function handlers and check out the Prisma Client API Reference

• Deploy to AWS Lambda: Learn how to deploy your Prisma ORM-backed applications to AWS Lambda with AWS SAM, Serverless Framework, or SST
• Deploy to Netlify: Learn how to deploy Node.js and TypeScript applications that are using Prisma Client to Netlify.
• Deploy to Vercel: Learn how to deploy a Next.js application based on Prisma Client to Vercel.