diff --git a/blog-service/2025-10-15-collection.md b/blog-service/2025-10-15-collection.md
new file mode 100644
index 0000000000..dda24dfdd0
--- /dev/null
+++ b/blog-service/2025-10-15-collection.md
@@ -0,0 +1,36 @@
+---
+title: Snowflake Authentication Update (Collection)
+image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
+keywords:
+  - c2c
+  - snowflake
+hide_table_of_contents: true    
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+### What's changing?
+
+Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols.
+
+Snowflake has signed the CISA *Secure by Design* pledge and is committed to adopting security best practices, including:
+- Eliminating high-risk authentication methods (for example, password-only access)
+- Enforcing multi-factor authentication (MFA)
+- Reducing the risk of credential theft and unauthorized access
+
+These changes are designed to strengthen Snowflake’s overall security posture and better protect your data.
+
+### Next steps
+
+As an interim measure, Sumo Logic recommends you to use the Programmatic Access Tokens (PATs) to authenticate your Sumo Logic integration with Snowflake before 1st November 2025. This ensures continued access and seamless data collection from the Snowflake platform.
+
+Refer to [Using programmatic access tokens for authentication](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) for step-by-step instructions to authenticate the integration with Snowflake.
+
+:::note
+- Programmatic Access Tokens (PATs) provide a short-term authentication solution, with each token expiring after approximately one year. So, you must generate a new token annually until a long-term multifactor authentication solution becomes available.
+- Sumo Logic is actively developing a long-term authentication solution using OAuth 2.0, which will provide enhanced security and ease of use. More information and rollout timelines for OAuth 2.0 support will be shared in the upcoming release.
+:::
+
+[Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source/#vendor-configuration).
+
+For more information, contact your Technical Account Engineer (TAE) or reach out to Sumo Logic Support.
\ No newline at end of file
diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md
index 580b4411d3..e13c28d98a 100644
--- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md
+++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md
@@ -37,6 +37,9 @@ The Snowflake Logs source requires you to provide the following data to setup th
 - **Account Identifier**. An account identifier uniquely identifies a Snowflake account within your organization, as well as throughout the global network of Snowflake-supported cloud platforms and cloud regions. For more information, see [Account identifiers](https://docs.snowflake.com/en/user-guide/admin-account-identifier).
 - **Username**. Snowflake account's login username. For example, `SUMOLOGIC`.
 - **Password**. Snowflake account's login password. For example, `yufncixxxxxxxxxp55hbdy7`.
+  :::note
+  Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols. Sumo Logic recommends that you update your integration to [Programmatic Access Tokens (PATs)](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) before 1st November 2025 to ensure continued access.
+  :::
 
 Once you have all the required values, set up the source configuration to collect your desired log types available in the configuration section.
 
diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md
index 6233821326..3228e90775 100644
--- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md
+++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md
@@ -27,6 +27,9 @@ To collect metric data from the Snowflake SQL API, you must have an authorized S
 1. Collect your admin account identifier following the instructions in the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/admin-account-identifier). The identifier should look something like this: `wp00000.us-east-2.aws`.
 1. Take note of the database name you plan to query.
 1. Collect your Snowflake Programmatic Access Token following the instructions in the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens).
+  :::note
+  Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols. Sumo Logic recommends that you update your integration to [Programmatic Access Tokens (PATs)](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) before 1st November 2025 to ensure continued access.
+  :::
 1. Optional additional information such as a role, warehouse, or schema name can also be configured with the source.
 
 ### Source configuration