> ## Documentation Index
> Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Native ISV retirement

Astronomer is retiring the [Azure Native ISV offering](https://learn.microsoft.com/en-us/azure/partner-solutions/astronomer/overview) for Astro. The program is fully deprecated on July 1, 2026.

Your Astro platform keeps running throughout the migration. Your Organization, Workspaces, Astro Deployments, Dags, Dag history, users, and data are all preserved. This change affects how you're billed and how you sign in, not the Astro product you use every day.

Two affected groups need to take action:

* **Azure Native ISV PayGo plans**: If you purchased Astro through the Team PayGo or Developer PayGo plans on the Azure Native ISV offering, you complete a few short steps yourself.
* **Azure Native ISV annual contracts**: If you're on an annual Azure contract that runs on the Azure Native ISV integration, contact your Astronomer account representative for a guided migration.

If you purchased Astro directly through Astronomer (at `cloud.astronomer.io` or through a direct order form), this change doesn't affect you, regardless of which cloud you run on.

## Timeline

The following dates apply to both affected groups:

| Date                   | What happens                                                                         |
| ---------------------- | ------------------------------------------------------------------------------------ |
| Early April 2026       | The Azure Native ISV offering was delisted. Service is still active.                 |
| May 1 to June 30, 2026 | Migration window. Billing and SSO move to the standard Astronomer surface.           |
| July 1, 2026           | Full deprecation. The Azure Native ISV billing path and SSO connections are retired. |

<Note>
  The Azure Native ISV plan options remain visible in the Azure portal UI even though they're no longer purchasable.
</Note>

## Migrate from an Azure Native ISV PayGo plan

You can complete this migration yourself in a few minutes.

<Steps>
  <Step title="Add a credit card">
    1. Go to the [Astronomer billing page](https://cloud.astronomer.io/billing).
    2. Add a credit card as your payment method.

    After your card is on file, your Astro usage bills against it on a monthly cycle. Your current pricing and plan terms are honored, so you don't need to re-select a plan or re-sign anything.

    Astronomer terminates your Azure Native ISV subscription, so don't cancel it yourself in the Azure portal.

    Your current Azure billing remains active until July 1, 2026. After that, your credit card on file becomes the default payment method.
  </Step>

  <Step title="Verify that standard Azure SSO works">
    1. Go to [cloud.astronomer.io](https://cloud.astronomer.io/).
    2. Sign in with your corporate email address (for example, `you@yourcompany.com`). This routes you to the standard Azure SSO connection.
    3. Confirm that you have full access to your account.
  </Step>

  <Step title="Invite a backup Organization Owner">
    Before you remove the old SSO connection, invite a user that can sign in without SSO. This account gives you a way to access Astro during the period between removing the old SSO connection and configuring a new one.

    1. Invite a new user with an email address from a domain that you don't manage through SSO, such as a personal email address rather than `you@yourcompany.com`. Astro routes addresses outside your SSO domain to email and password authentication. See [Add a user to an Organization](/docs/astro/manage-organization-users#add-a-user-to-an-organization).
    2. Assign the user the Organization Owner role.
    3. Accept the invitation and confirm that the backup user can sign in with an email and password.

    If your Organization enforces SSO logins on an email address you want to use for the backup user, temporarily allow all login methods first. See [SSO enforcement](/docs/astro/configure-idp#sso-enforcement).
  </Step>

  <Step title="Remove the current SSO connection">
    If you're an Organization Owner, go to the [authentication settings page](https://cloud.astronomer.io/settings/authentication) and remove the old SSO connection. For step-by-step instructions, see [Reconfigure SSO to a new identity provider](/docs/astro/configure-idp#reconfigure-sso-to-a-new-identity-provider).

    The Developer PayGo and Team PayGo tiers default to [Allow all login methods](/docs/astro/configure-idp#sso-enforcement), so you can sign in with an email and password combination or Google authentication. You can stop the SSO reconfiguration here unless you want to add a new SSO connection.
  </Step>

  <Step title="(Optional) Reset the SSO connection to a new Azure AD connection">
    If you want to add a new SSO connection, follow the steps in [Register Astro as an application on Azure](/docs/astro/configure-idp#microsoft-entra-id).
  </Step>
</Steps>

## Migrate from an Azure Native ISV annual contract

<Note>
  Your Astronomer account representative can guide you through this migration. Contact them directly if you have any questions.
</Note>

### What to expect

Your Astronomer account representative contacts you within a few weeks to confirm your setup, walk through the billing and SSO migration on a short call, and schedule any coordination needed on your side.

Your billing method stays valid through the program deprecation. There is no billing interruption, no double-billing, and no action required from your procurement or finance team until your account representative proposes the next step. Your current pricing and plan terms are honored through the migration.

### Prepare for the migration call

Complete these steps before your call:

<Steps>
  <Step title="Verify that standard Azure SSO works">
    1. Go to [cloud.astronomer.io](https://cloud.astronomer.io/).
    2. Sign in with your corporate email address (for example, `you@yourcompany.com`). This routes you to the standard Azure SSO connection.
    3. Confirm that you have full access to your account.
  </Step>

  <Step title="Invite a backup Organization Owner">
    Before you remove the old SSO connection, invite a user that can sign in without SSO. This account gives you a way to access Astro during the period between removing the old SSO connection and configuring a new one.

    1. Invite a new user with an email address from a domain that you don't manage through SSO, such as a personal email address rather than `you@yourcompany.com`. Astro routes addresses outside your SSO domain to email and password authentication. See [Add a user to an Organization](/docs/astro/manage-organization-users#add-a-user-to-an-organization).
    2. Assign the user the Organization Owner role.
    3. Accept the invitation and confirm that the backup user can sign in with an email and password.

    If your Organization enforces SSO logins on an email address you want to use for the backup user, temporarily allow all login methods first. See [SSO enforcement](/docs/astro/configure-idp#sso-enforcement).
  </Step>

  <Step title="Remove the current SSO connection">
    If you're an Organization Owner, go to the [authentication settings page](https://cloud.astronomer.io/settings/authentication) and remove the old SSO connection. For step-by-step instructions, see [Reconfigure SSO to a new identity provider](/docs/astro/configure-idp#reconfigure-sso-to-a-new-identity-provider).
  </Step>

  <Step title="(Optional) Enable all login methods for your Organization">
    If your security or IT teams allow it, you can enable all login methods for your Organization. This shortens the migration because you don't have to set up a new SSO connection.

    1. Go to your [Organization's authentication settings page](https://cloud.astronomer.io/settings/authentication).
    2. In the **Advanced** section, select the option to enable all login methods.
  </Step>

  <Step title="(Optional) Reset the SSO connection to a new Azure AD connection">
    If you need to add a new SSO connection, follow the steps in [Register Astro as an application on Azure](/docs/astro/configure-idp#microsoft-entra-id).
  </Step>
</Steps>

If you have questions before your account representative contacts you, email `platform@astronomer.io`. Astronomer routes the question internally or loops in your representative if that's faster.

## What stays the same

Regardless of which group you're in:

* Your Astro Deployments continue running with no interruption.
* Your Dags, schedules, run history, connections, and variables are preserved.
* API tokens, service accounts, and Deployment keys continue to work.
* Workspace permissions and User Roles persist.
* You work with the same Astronomer support team under the same SLAs.

## Common questions

<AccordionGroup>
  <Accordion title="Why are we making this change?">
    Microsoft and Astronomer have jointly decided to retire the Azure Native ISV integration to enable a more unified Astro experience across all customers.
  </Accordion>

  <Accordion title="Will my Dags keep running during the migration?">
    Yes. Your Deployments, schedulers, workers, Dag history, connections, and variables are all unaffected.
  </Accordion>

  <Accordion title="Will my API keys and service accounts keep working?">
    Yes. API authentication is separate from SSO and doesn't change.
  </Accordion>

  <Accordion title="What happens if I do nothing by July 1, 2026?">
    * If you're on a PayGo plan, your Astro platform keeps running, but your Azure Native ISV subscription terminates. Without a credit card on file, billing moves to a manual state. Add a credit card at the [Astronomer billing page](https://cloud.astronomer.io/billing) to avoid any billing interruption. Resources are automatically spun down on July 15, 2026.
    * If you're on an annual contract, your account representative makes sure you land safely. Respond when they contact you.
  </Accordion>

  <Accordion title="Can I stay on the same Astro plan?">
    Yes, or you can move to a different plan. Your current pricing and plan terms are honored through the migration.
  </Accordion>

  <Accordion title="I bought directly through Astronomer. Does this affect me?">
    No.
  </Accordion>

  <Accordion title="What happens to the Astronomer resource in my Azure portal?">
    Astronomer terminates the Azure Native ISV resource connection after the migration. The resource served as a billing and authentication link between Azure and Astro, but didn't provision or manage any Azure infrastructure on your behalf.

    After migration:

    * The Astronomer resource in your Azure portal shows as terminated or delisted.
    * Your Astro Deployments continue running unchanged — they were never dependent on this Azure portal resource.
    * You can safely remove the terminated resource from your Azure portal view.

    After July 15, 2026, Astronomer spins down and deletes the Azure resource from the Azure portal. No action is required on your part — the resource removal is automatic.

    The Astro platform itself runs in Astronomer-managed infrastructure and is unaffected by the removal of this Azure portal integration resource.
  </Accordion>
</AccordionGroup>