Enable Cross-Region Inference Globally (Same-Cloud, Same-Region) (Pending)¶

When this behavior change bundle is enabled, Snowflake sets the deployment default for CORTEX_ENABLED_CROSS_REGION to the geography-scoped value for your cloud provider and region, for eligible commercial accounts that have not already configured it. This enables Cortex features that require cross-region inference, including Cortex Code. All inference routing stays within your cloud provider. No data crosses to a different cloud provider.

If you have already set any explicit value for CORTEX_ENABLED_CROSS_REGION (including DISABLED), this BCR has no effect on your account. Finance-sector, healthcare-sector, government, FedRAMP, and VPS accounts are also excluded.

The following table shows the value this BCR sets for each supported cloud region:

Regions with no available same-cloud, same-region routing value are listed as Unchanged.

Before the change:

CORTEX_ENABLED_CROSS_REGION is unset by default for most accounts. For those accounts, Cortex features that require cross-region inference, such as Cortex Code, can’t be used. For new accounts created in new organizations within commercial regions after March 9, 2026, ANY_REGION is already the default.

After the change:

Snowflake sets the deployment default to the value for your cloud and region in the previous table (for example, AWS_US or AZURE_EU). Cross-region inference is enabled within your cloud provider, and features such as Cortex Code can be used. Regions listed as Unchanged aren’t affected.

How to opt out¶

You can opt out at any time by setting CORTEX_ENABLED_CROSS_REGION at the account level. An account setting overrides the deployment default this BCR sets. If you’ve already set a value on the account, this BCR has no effect.

To disable cross-region inference entirely, run the following command as ACCOUNTADMIN:

-- Disable cross-region inference entirely
ALTER ACCOUNT SET CORTEX_ENABLED_CROSS_REGION = 'DISABLED';

To restrict cross-region inference to a specific geography instead of disabling it:

-- Example: restrict to EU AWS regions only
ALTER ACCOUNT SET CORTEX_ENABLED_CROSS_REGION = 'AWS_EU';

For a full list of supported values, see CORTEX_ENABLED_CROSS_REGION.

Ref: 2376