Neon on Azure
newWhat 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.
- 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.
Deploy Neon from Azure Marketplace
Deploy Neon Postgres as Native ISV Service from the Azure Marketplace
Getting started with Neon
Familiarize yourself with Neon by stepping through our Getting started guides
Azure CLI — az neon
Manage your Neon Resource with the Azure CLI
Azure SDK for .NET
Manage your Neon Resource with the Azure 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.
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.
Related resources
.NET
Connect a .NET (C#) application to Neon
Azure Functions
Connect from Azure Functions to Neon
Connect from Entity Framework
Connect a Dotnet Entity Framework application to Neon
Entity Framework Schema Migrations
Schema migration with Neon and Entity Framework
Replicate data from Azure PostgreSQL
Replicate data from Azure PostgreSQL to Neon
ASP.NET with Neon and Entity Framework
Building ASP.NET Core Applications with Neon and Entity Framework Core
ASP.NET Core, Swagger, and Neon
Building a RESTful API with ASP.NET Core, Swagger, and Neon
Neon Read Replicas with Entity Framework
Scale your .NET application with Entity Framework and Neon Postgres Read Replicas