Changes / Warehouses & lakehouses / Snowflake

End of supportmedium impact

Snowflake blocks password sign-in for all remaining legacy service users

Non-human users are blocked from password authentication, and existing LEGACY_SERVICE users are migrated to TYPE=SERVICE.

In effectsince August 2026 (77 days ago)

+ Add Snowflake dates to calendar

Who’s affected

Any Snowflake account that still has LEGACY_SERVICE users, meaning scripts, ETL/ELT tools, BI connectors, dbt jobs or other non-human logins that sign in with a password. Enforcement rolls out between August and October 2026, and each account is notified of its own date.

Not affected: Accounts with no LEGACY_SERVICE users, and service accounts already on key-pair or OAuth authentication. Human users are also not the target of this change.

What it costs

No price change in the record. The cost is engineering effort to move each non-human integration off passwords, plus outage risk if a password-based job is blocked first.

When to act

Enforcement is already rolling and may hit your account at any time, so inventory and cut over now; dates are account-specific and subject to change, and any extension has to be arranged for your account.

Blast radius: Scheduled loads, dbt profiles, BI extract refreshes, reverse-ETL and custom scripts that use a password will fail to authenticate. Downstream dashboards and models then go stale.

What should you do? decision tree

  1. you have not yet checked your enforcement date
    Find the notice sent to your account admins and confirm whether an extension applies to your account, since extensions are account-specific.
  2. you do not know which users are LEGACY_SERVICE
    Inventory service users in your account and list the tools, schedulers and scripts behind each one, with their owners.
  3. A user is already blocked or about to be
    Move that integration to key-pair or OAuth authentication on a TYPE=SERVICE user and update the client's stored credentials.
  4. A tool cannot support non-password auth
    Ask the vendor for a supported connector version, or put the job behind a wrapper that handles key-pair auth.
  5. you cannot finish before your date
    Request an extension from Snowflake and prioritise production pipelines and executive dashboards first.

Options

The facts straight from the source

Vendor / product
Snowflake · LEGACY_SERVICE users (all existing)
Change
End of support
Effective
August 2026
Rolling enforcement August–October 2026; existing LEGACY_SERVICE users are converted to TYPE=SERVICE (no passwords). Extensions are account-specific.
Plans affected
LEGACY_SERVICE
Existing contracts
Accounts are notified of their specific enforcement date. Dates are subject to change.
Source
docs.snowflake.com
Evidence
“Aug. 2026 - Oct. 2026 Human users Legacy service users Strong authentication for ALL users”

Date as quoted: “August 2026 - October 2026”

Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.

Related changes

Get the weekly brief

Get the Monday brief →One email a week: what changed in the data stack and whose clock is running.