Astronomer is retiring the Azure Native ISV offering 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:
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.
The following dates apply to both affected groups:
The Azure Native ISV plan options remain visible in the Azure portal UI even though they’re no longer purchasable.
You can complete this migration yourself in a few minutes.
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.
you@yourcompany.com). This routes you to the standard Azure SSO connection.If you’re an Organization Owner, go to the authentication settings page and remove the old SSO connection. For step-by-step instructions, see Reconfigure SSO to a new identity provider.
The Developer PayGo and Team PayGo tiers default to Allow all login methods, 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.
If you want to add a new SSO connection, follow the steps in Register Astro as an application on Azure.
Your Astronomer account representative can guide you through this migration. Contact them directly if you have any questions.
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.
Complete these steps before your call:
you@yourcompany.com). This routes you to the standard Azure SSO connection.If you’re an Organization Owner, go to the authentication settings page and remove the old SSO connection. For step-by-step instructions, see Reconfigure SSO to a new identity provider.
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.
If you need to add a new SSO connection, follow the steps in Register Astro as an application on Azure.
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.
Regardless of which group you’re in:
Microsoft and Astronomer have jointly decided to retire the Azure Native ISV integration to enable a more unified Astro experience across all customers.
Yes. Your Deployments, schedulers, workers, Dag history, connections, and variables are all unaffected.
Yes. API authentication is separate from SSO and doesn’t change.
Yes, or you can move to a different plan. Your current pricing and plan terms are honored through the migration.
No.
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:
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.