> This page location: Migrate to Neon > Region migration > Azure regions deprecation > Full Neon documentation index: https://neon.com/docs/llms.txt # Azure regions deprecation What's changing, what to do, and answers to common questions Neon Azure regions are deprecated and will no longer be supported as of **August 27, 2026**. This guide explains what the deprecation means and what actions are available if you have active projects in Azure regions. You should receive personalized email communication about your specific projects and next steps. This guide answers common questions and provides general guidance during the deprecation. ## Key dates | Date | What changes | | :-------------- | :-------------------------------------------------------------------------------------------------------------------------- | | April 7, 2026 | Azure regions are deprecated. New project creation in Azure regions is restricted. Existing projects keep running normally. | | August 27, 2026 | Azure regions are no longer supported. Projects that haven't been migrated or deleted may be removed. | We'll contact organizations with active Azure projects directly to discuss migration options and timelines. ## What to do If you have one or more projects in an Azure region, take action before **August 27, 2026** or your projects may be removed and may not be recoverable. You have three options: 1. **Delete the project** if you no longer need it. This also stops storage costs from accruing. See [Delete a project](https://neon.com/docs/manage/projects#delete-a-project). 2. **Migrate to a Neon AWS region.** Best if you don't need Azure residency. See [Migrate to another Neon region](https://neon.com/docs/import/migrate-neon-to-another-region) for the available migration methods. 3. **Migrate to Databricks Lakebase.** Best if you need to keep your Postgres data in Azure. Lakebase is powered by the same serverless Postgres technology as Neon, under the Databricks product line. See [Migrate Neon to Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase). If none of these fit your requirements, [export your data in Postgres-compatible form](https://neon.com/docs/guides/export-neon-postgres-compatible) so you can move it elsewhere. ## Frequently asked questions ### Does this affect my Neon projects? Only if your project is in an Azure region (`azure-eastus2`, `azure-westus3`, or `azure-gwc`). Projects in AWS regions are not affected. ### How do I find out which region a project is in? You can check from the Console, the CLI, or the API: - **Console.** Open your project, then check the **Project settings** widget on the project dashboard. The region is shown in the **Region** row. - **CLI.** Run `neon projects list`. The `Region Id` column shows each project's region. - **API.** Call `GET /projects` and check the `region_id` field on each project. ![Project settings widget showing the project region](https://neon.com/docs/import/azure-regions-deprecation/project-settings-region.png) ### Will my Azure project keep running until August 27, 2026? Yes. Until that date, your Azure project keeps running as it does today. Compute, storage, branching, and connections are unaffected. ### What happens on August 27, 2026? On that date, Azure regions are no longer supported. Projects that haven't been migrated or deleted may be removed, and removed projects may not be recoverable. ### What if I do nothing? Your project continues running until August 27, 2026. After that, it becomes eligible for removal with no guarantee of recovery. We'll reach out before then to discuss your options. ### I picked Azure for data residency. What are my options? Migrate to [Databricks Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase). Lakebase is powered by the same serverless Postgres technology as Neon, under the Databricks product line. It supports Azure regions, so you can keep your data in Azure. For specific Lakebase region availability, see the [Lakebase Postgres documentation](https://docs.databricks.com/aws/en/oltp). ### What changes about my project when I migrate to a new region? A region migration creates a **new** Neon project in the target region. The new project gets a new hostname, so plan to update connection strings in your application. The new project also has a different project ID. Project-level settings (branches, integrations, autoscaling configuration, IP Allow rules, monitoring, and so on) are configured per project. Review the [migration guide](https://neon.com/docs/import/migrate-neon-to-another-region) for the steps and decisions specific to your migration method. ### Should I take a backup before migrating? If your migration method uses `pg_dump` and `pg_restore`, the dump itself is a backup. If you're using logical replication or the [Import Data Assistant](https://neon.com/docs/import/import-data-assistant), it's still good practice to take a `pg_dump` snapshot of your source database before you start. See [Backups](https://neon.com/docs/manage/backups) for details. ### I need more time. Can I get an extension? Reply to the migration outreach email when you receive it. If you have specific constraints, such as regulatory requirements, application architecture changes, or customer migration dependencies, we'll work through them with you to find a workable timeline. ### How do I contact Neon about my Azure projects? Keep an eye on your inbox for communication from us about the deprecation. If you have questions before then, contact [Neon Support](https://console.neon.tech/app/projects?modal=support). --- ## Related docs (Region migration) - [Overview](https://neon.com/docs/import/region-migration) - [Neon to another region](https://neon.com/docs/import/migrate-neon-to-another-region) - [Neon to Lakebase](https://neon.com/docs/guides/migrate-neon-to-lakebase) - [Postgres-compatible export](https://neon.com/docs/guides/export-neon-postgres-compatible)