Update New VNet Subnet IDs to Avoid Service Interruptions
Update
We are extending the deadline to update VNet subnet IDs (BCR-1955) in the Azure – East US 2 (Virginia) and Azure – West US 2 (Washington) regions to September 18, 2025, at 19:00 UTC. Services will remain available until that time, and we will work directly with customers who are ready to transition to the new set of VNets before the scheduled deadline to ensure a smooth changeover.
What happened?
In May 2025, we announced a future update to the VNet subnet IDs in the affected Azure regions. The update was implemented on August 14, 2025; however, based on feedback, we’ve extended the timeline to give you more flexibility in completing the required changes.
How will this affect my service?
If the required changes are not implemented by the new deadline, you may begin experiencing service interruptions, such as being unable to perform replication, access databases, run queries, and ingest data via Snowpipe. Affected customers may encounter error messages at that time, such as: “Something went wrong: Error received from the customer managed key (CMK) provider caused by user: 'Your request cannot be completed because of the failure of an external dependency. Please try again later.'”
Additional information about how to add the VNet subnet IDs can be found in the following documentation:
Update
Scheduled
To avoid service interruptions, please follow the instructions outlined in BCR-1955 by 19:00 UTC on Monday, August 18, 2025, if you use Azure policies based on subnet IDs for services like external stage, external volume, Key Vault, or API Gateway that interface with Snowflake in the Azure - East US 2 (Virginia) or Azure - West US 2 (Washington) regions.
What happened?
In May 2025, we announced a future update to the VNet subnet IDs in the Azure - East US 2 (Virginia) and Azure - West US 2 (Washington) regions, which was implemented on August 14, 2025. We’ve made a temporary configuration change to extend the deadline for customers so that they can implement the required changes by 19:00 UTC on August 18, 2025. However, we’re unable to extend the deadline further as the subnet updates are required to ensure the continued resiliency of services.
How will this affect my service?
If you do not implement the required changes by the specified date and time, you may begin experiencing service interruptions, such as being unable to perform replication, access databases, run queries, and ingest data via Snowpipe. Affected customers will begin encountering error messages at that time, such as the following: “Something went wrong: Error received from the customer managed key (CMK) provider caused by user: 'Your request cannot be completed because of the failure of an external dependency. Please try again later.'”
Additional information about how to add the VNet subnet IDs can be found in the following documentation: