What this changes

• Corrects the Snowflake key-pair OpenSSL command and public-key SQL instructions.
• Updates the Snowflake key-pair authentication labels to match the current UI.
• Separates individual-credential prompts from service-account setup instructions.
• Updates the AzureAD and Okta authentication field labels.
• Fixes the Okta Snowflake account URL placeholder.
• Fixes the Snowpark heading hierarchy, introduction, and Python environment guidance.

Why

The documentation audit compared these Snowflake integration and Snowpark instructions with the current product UI and provider documentation. The changes correct reproducible wording, command, placeholder, and navigation drift.

Finding 1: misleading

When creating a Snowflake integration, select "Key-pair" as the authentication type.

• Documented: The authentication method is labeled Key-pair.
• Actual: The current choices are Key-pair (individual credentials) and Key-pair (service account).
• Reproduced: Yes.
• Correction: Names both current authentication choices.

Finding 2: blocking

For an unencrypted private key:

• Documented: The command uses --no-crypt.
• Actual: The tested OpenSSL command accepts -nocrypt.
• Reproduced: Yes.
• Correction: Uses the current unencrypted PKCS#8 command.

Finding 3: blocking

The public key should begin with -----BEGIN PRIVATE KEY-----.

• Documented: The public-key example uses a private-key header.
• Actual: The public-key command produces a public-key header, and Snowflake SQL uses the key contents without PEM delimiters.
• Reproduced: Yes.
• Correction: Uses the public-key contents without PEM delimiters.

Finding 4: misleading

Select Azure AD as the authentication method and fill in Client ID and Client Secret based on <OAUTH_CLIENT_ID> and <OAUTH_CLIENT_SECRET> defined in the section above.

• Documented: The method is labeled Azure AD.
• Actual: The current Deepnote method is labeled AzureAD.
• Reproduced: Yes.
• Correction: Uses the current AzureAD label.

Finding 5: misleading

Fill in Authorization Server as the <OKTA_AUTHORIZATION_SERVER_ID>.

• Documented: The field is named Authorization Server.
• Actual: The current field is named Authorization server ID.
• Reproduced: Yes.
• Correction: Uses the current field label.

Finding 6: blocking

external_oauth_audience_list = ('<snowflake_account_url')

• Documented: The placeholder is incomplete.
• Actual: The placeholder needs a closing angle bracket.
• Reproduced: Yes.
• Correction: Uses <snowflake_account_url>.

Finding 7: misleading

The Snowpark + Deepnote integration makes the warehouse feels like an in-memory object.

• Documented: The introduction uses “makes ... feels”.
• Actual: The sentence requires “makes ... feel”.
• Reproduced: Yes.
• Correction: Fixes the grammar.

Finding 8: misleading

Note that Snowpark requires Python 3.10 or later (this can be selected from the environments tab in Deepnote).

• Documented: The environment is selected from an environments tab.
• Actual: The current product exposes a Python environment dropdown in the right sidebar.
• Reproduced: Yes.
• Correction: Describes the current dropdown and links to custom environments.

Follow-up review fixes

• Limits the Snowpark Python guidance to versions 3.10 through 3.13 in Deepnote.
• Changes the Snowpark How to connect heading to the correct document level.
• Explains that individual-credential users enter their username and private key on first resource access, while service-account credentials are entered during integration setup.

How this was verified

The documented workflows were checked through the approved Chrome-based audit workflow. Independent UI, command, syntax, package, and navigation checks were completed where they did not require provider credentials. No credentials or sensitive values are included in this change.

Unverified by human

This draft uses a user-authorized incomplete-verification exception. The following items remain for human validation:

https://deepnote.com/docs/snowflake

Safe credential-free replacement screenshot for the illustrated Snowflake authentication form; the new and existing forms auto-populate stored connection values.

Human follow-up: capture and review the current authentication-form state with a safe test connection, without exposing credentials.

https://deepnote.com/docs/snowflake-with-key-pair-authentication

First-use key-pair authentication through the schema browser or query, including the required username and private key prompt and its screenshot.

Human follow-up: use a test Snowflake account, register the public key, complete first-use authentication, and verify a schema or query result.

https://deepnote.com/docs/snowflake-oauth

Snowflake OAuth authorization through the external provider, including the resulting first-use sign-in state and required screenshot.

Human follow-up: complete the provider consent and sign-in flow with a test OAuth application, then verify the resulting authenticated integration.

https://deepnote.com/docs/snowflake-with-azure-ad

Azure AD authorization through the external identity provider, including the resulting first-use sign-in state and required screenshot.

Human follow-up: complete the Azure client and consent configuration, enter the secret interactively, finish the Snowflake security integration, and verify Deepnote authentication.

https://deepnote.com/docs/snowflake-with-okta

Okta authorization through the external identity provider, including the resulting first-use sign-in state and required screenshot.

Human follow-up: complete the Okta client and authorization-server configuration, finish the Snowflake security integration, and verify Deepnote authentication.

https://deepnote.com/docs/snowpark

Creating a real Snowpark Session and running table or DataFrame operations against Snowflake, which requires a Snowflake credentialed connection.

Human follow-up: use a test Snowflake connection, create a real Session, read a test table, run a DataFrame operation, and confirm the result.

User explicitly authorized this incomplete-verification draft exception for the snowflake-and-snowpark batch on 2026-08-19.

Summary by CodeRabbit

• Documentation
  • Clarified Snowflake Azure AD, key-pair, and Okta authentication setup instructions.
  • Corrected key-generation commands, SQL examples, and OAuth configuration details.
  • Distinguished individual-credential and service-account authentication methods.
  • Improved Snowpark integration wording and clarified support for Python 3.10–3.13 environments.