We've shipped a hosted version of our MCP server with OAuth
Neon DocsAsk Neon AI
DiscordLog InSign Up
Docs/Neon on Azure

Neon on Azure

What you will learn:

  • Options for using Neon on Azure

  • About deploying Neon as an Azure Native ISV Service

  • About creating Neon projects in Azure regions

Deployment options on Azure

Neon offers the following deployment options on Azure:

  • Option 1: Deploy Neon as an Azure Native ISV Service — use Neon as a native Azure service, integrated with the Azure portal, CLI, and SDKs. This option enables you to manage Neon as part of your Azure infrastructure with unified billing in Azure.

    Public Preview

    This feature is in Public Preview. Please provide Feedback from the Neon Console or by connecting with us on Discord.

  • Option 2: Create Neon projects in Azure regions (no integration) — create a Neon project in an Azure region without using the native Azure integration. Project creation and billing is managed through Neon. There is no difference from a Neon project created in an AWS region — your Neon project simply resides in an Azure region instead of AWS region.

Option 1: Deploy Neon as an Azure Native ISV Service

This option integrates Neon natively into Azure, letting you manage your Neon organization alongside the rest of your Azure infrastructure. Key benefits include:

  • Azure-native management: Provision and manage Neon organizations directly from the Azure portal.

  • Single sign-on (SSO): Access Neon using your Azure credentials—no separate logins required.

  • Consolidated billing: Simplify cost management with unified billing through the Azure Marketplace.

  • Integrated workflows: Use the Azure CLI and SDK to manage Neon organizations as part of your regular workflows, integrated with your existing Azure resources.

    note

    Management of Neon projects, databases, and branches is supported through the Neon Console, CLI, and API. However, this public preview lays the groundwork for further deeper between Neon and Azure, including integration with other Azure native services.

Get started

To begin using Neon as an Azure Native ISV Service, refer to our Azure Marketplace instructions. After you setup the integration, familiarize yourself with Neon by stepping through Neon's Getting started guides. You can also manage your Neon Postgres Resource using the Azure CLI or SDK for .NET.

Option 2: Create Neon projects in Azure regions (no integration)

If you want to deploy a Neon project to an Azure region without using the Azure Native ISV Service integration, you can simply select one of our supported Azure regions when creating a Neon project. You might consider this option if:

  • Part of your infrastructure runs on Azure but you don't need the native integration
  • An Azure region is closer to your application than a Neon AWS region
  • You want to manage billing through Neon rather than Azure

Creating a Neon project in an Azure region without using the Azure Native ISV Service is supported via the Neon Console, CLI, and API.

To create a Neon project from the console, follow the Create project steps. Select Azure as the Cloud Service Provider, and choose one of the available Azure regions.

Azure region support

For supported Azure regions, refer to our Regions page. For the Public Preview, Neon supports a limited number of Azure regions. To request support for other Azure regions, see Request a region.

Azure examples

PreviousEnterprise sales process
NextOverview

Last updated on

Was this page helpful?

On this page

Edit this page on GitHub