From 2bfb5f032600b1be21c6d683efa9388afeaa5494 Mon Sep 17 00:00:00 2001 From: Daniel Date: Tue, 17 Dec 2024 10:07:09 -0400 Subject: [PATCH] docs: move preview notice --- content/docs/manage/azure.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/docs/manage/azure.md b/content/docs/manage/azure.md index 1223595da7..e772869008 100644 --- a/content/docs/manage/azure.md +++ b/content/docs/manage/azure.md @@ -6,8 +6,6 @@ isDraft: false updatedOn: '2024-12-03T15:29:17.189Z' --- - -

Options for using Neon on Azure

@@ -29,6 +27,7 @@ updatedOn: '2024-12-03T15:29:17.189Z' 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](https://portal.azure.com/#home), [CLI](https://learn.microsoft.com/en-us/cli/azure/neon?view=azure-cli-latest), and [SDKs](https://learn.microsoft.com/en-us/dotnet/api/overview/azure/neonpostgres?view=azure-dotnet-preview). 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