-
Notifications
You must be signed in to change notification settings - Fork 235
docs: add azure migration guide #4052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Deployment failed with the following error: Learn More: https://vercel.link/3Fpeeb1 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds a new migration guide to help users move from the Azure Native Integration to a Neon-managed organization before deprecation.
- Introduces step-by-step instructions for locating the new organization, transferring projects, updating configuration, and deleting the Azure-managed resource.
- Includes a table of contents and support references.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| 1. Sign in to the Azure Portal | ||
| 2. Open your Neon resource created through the Azure Marketplace | ||
| 3. Confirm that no projects remain in your Azure-managed organization | ||
| 4. Select **Delete** to remove the Neon resource and cancel your Azure subscription |
Copilot
AI
Oct 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The phrase 'cancel your Azure subscription' can be misread as canceling the entire Azure account. Consider clarifying that this action cancels the Neon Marketplace subscription (for this resource) and add terminal punctuation, e.g., 'cancel the associated Neon SaaS subscription in Azure Marketplace.'
| 4. Select **Delete** to remove the Neon resource and cancel your Azure subscription | |
| 4. Select **Delete** to remove the Neon resource and cancel the associated Neon SaaS subscription in Azure Marketplace. |
|
|
||
| ## Locate your new Neon-managed organization | ||
|
|
||
| 1. Sign in to the Neon Console at https://console.neon.tech |
Copilot
AI
Oct 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use descriptive link text for better accessibility and consistency. Suggest: 'Sign in to the Neon Console.'
| 1. Sign in to the Neon Console at https://console.neon.tech | |
| 1. Sign in to the [Neon Console](https://console.neon.tech) |
|
|
||
| ## Delete your Azure-managed resource | ||
|
|
||
| 1. Sign in to the Azure Portal |
Copilot
AI
Oct 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Provide an explicit link target for the portal to aid navigation and accessibility. Suggest: 'Sign in to the Azure Portal.'
| 1. Sign in to the Azure Portal | |
| 1. Sign in to the [Azure Portal](https://portal.azure.com) |
| 1. Go to **Organization** -> **Settings** -> **Transfer projects** | ||
| 2. Click **Select all** and click **Next** | ||
| 3. Choose your new Neon-managed organization as the destination | ||
| 4. Confirm the transfer |
Copilot
AI
Oct 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] For consistency with earlier bullet lists, add terminal periods to each step; also remove the repeated 'click' in step 2 for clarity, e.g., 'Click Select all, then Next.'
| 1. Go to **Organization** -> **Settings** -> **Transfer projects** | |
| 2. Click **Select all** and click **Next** | |
| 3. Choose your new Neon-managed organization as the destination | |
| 4. Confirm the transfer | |
| 1. Go to **Organization** -> **Settings** -> **Transfer projects**. | |
| 2. Click **Select all**, then **Next**. | |
| 3. Choose your new Neon-managed organization as the destination. | |
| 4. Confirm the transfer. |
|
|
||
| 1. Sign in to the Azure Portal | ||
| 2. Open your Neon resource created through the Azure Marketplace | ||
| 3. Confirm that no projects remain in your Azure-managed organization |
Copilot
AI
Oct 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Add terminal periods to these steps to match punctuation style used elsewhere in the page.
| 3. Confirm that no projects remain in your Azure-managed organization | |
| 3. Confirm that no projects remain in your Azure-managed organization. |
…tabase/website into add-azure-migration-guide
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| - Members and project collaborators need to be re-added after migration. | ||
| - Application connection strings remain the same after transfer because the project structure does not change. | ||
|
|
||
| <Steps> |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| updatedOn: '2025-10-16T00:00:00.000Z' | ||
| --- | ||
|
|
||
| The Neon Azure Native Integration is deprecated and reaches end of life on **January 31, 2026**. Migrate your projects to a Neon-managed organization before this date to continue using Neon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make this an "important" note?
| The Neon Azure Native Integration is deprecated and reaches end of life on **January 31, 2026**. Migrate your projects to a Neon-managed organization before this date to continue using Neon. | ||
|
|
||
| ## Before you begin | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This jumps into the list without a lead in sentence/context, and the list is informational rather than traditional prereqs. Maybe add something like :"Before you begin your migration, be aware of the following" or something stating that certain things are already set up for you to facilitate your migration.
| updatedOn: '2025-10-16T00:00:00.000Z' | ||
| --- | ||
|
|
||
| The Neon Azure Native Integration is deprecated and reaches end of life on **January 31, 2026**. Migrate your projects to a Neon-managed organization before this date to continue using Neon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The Neon Azure Native Integration is deprecated and reaches end of life on **January 31, 2026**. Migrate your projects to a Neon-managed organization before this date to continue using Neon. | |
| The Neon Azure Native Integration is deprecated and reaches end of life on **January 31, 2026**. This guide describe how to migrate your projects to a Neon-managed organization before this date to continue using Neon. |
| - Application connection strings remain the same after transfer because the project structure does not change. | ||
|
|
||
| <Steps> | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To migrate your projects to a Neon-managed organization:
| - You can find it in the organization dropdown named `neon-managed-[org-name]` where `[org-name]` is the original organization name. | ||
| - You can [rename this organization](/docs/manage/orgs-manage#rename-an-organization) at any time. | ||
| - Admins from your existing organization have been added to the new one. | ||
| - Members and project collaborators need to be re-added after migration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I make a list of members / collaborators before I start?
| After the transfer: | ||
|
|
||
| - Re-add any members or project collaborators who need access. | ||
| - Update any organization [API keys](/docs/manage/api-keys) if you were using them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we say "update", does that mean I need to create API keys for my new Neon-managed org and replace keys created for the old org anywhere I might use them? Maybe explain that a little more.
Eventually they'll be removed/redirected.
No description provided.