Skip to main content

Migrating to account-specific access URLs

Account-specific access URLs are being assigned to dbt accounts as part of our ongoing efforts to improve your experience and strengthen security. Each account will receive its own unique dbt platform and API access URLs, replacing the legacy region URLs that accounts share today. An account-specific access URL starts with a prefix unique to your account, such as ab123.

DeploymentLegacy region URL (shared)Account-specific access URL
Multi-tenant (North America)cloud.getdbt.comab123.us1.dbt.com
Multi-tenant (EMEA)emea.dbt.comab123.eu1.dbt.com
Multi-tenant (APAC)au.dbt.comab123.au1.dbt.com
Single tenantacme.getdbt.comab123.acme.dbt.com

What does this mean for me?​

If your account has been assigned a new access URL, please review the migration timeline and update your account's external integrations using the integration checklist.

If your account has not been assigned a new access URL, you will receive an email and in-app notification with a scheduled enablement date. When the change takes effect, you'll be automatically redirected to your account-specific access URL. Account sign-in remains the same. Both your new access URL and your legacy region URL will support integrations according to the dates on the migration timeline. You can update most integrations any time before the end-of-support date, but network rules must be ready before your assignment date. For a summary, refer to the update checklist by date.

Update network rules before your assignment date

If your organization uses network allowlisting or IP restrictions, update the following before your assignment date so access isn't disrupted:

If your account uses inbound private connectivity (ingress PrivateLink), dbt Support will contact you before your assignment with guidance for your configuration.

Migration timeline​

Accounts across all regions and service providers are being assigned new access URLs. Legacy region URLs will continue to support integrations until the end-of-support date for your account.

StageStatusTimeline
Multi-tenant account-specific access URL assignment✅ CompletedJanuary 2026
Single tenant account-specific access URL assignmentIn ProgressApril 2026 - March 2027
Legacy region URL end of support (multi-tenant)ScheduledFebruary 3, 2027
Legacy region URL end of support (single tenant)ScheduledProvided in your assignment notification

Integration checklist​

Review the following checklist before the legacy region URL end-of-support date documented in the migration timeline. Update each integration that uses a dbt access URL. If your integration isn't in this list, please speak with your IT or applicable team to identify whether you need to take action.

The managed dbt GitHub application, the Slack application, and GitLab webhooks are updated automatically. Self-managed GitHub Enterprise applications and inbound Azure DevOps service hooks are not included.

Identity and access management​

IntegrationAction required
SAML 2.0 SSONo change to your identity provider application. Update any identity provider-initiated sign-in links to your new access URL.
Google Workspace SSOUpdate or add an OAuth client
SCIM (Okta)Update the SCIM base URL in Okta

Git providers​

GitLab and Azure DevOps repositories connected before your account had an account-specific access URL keep using your legacy region URL for OAuth until you update them. Repositories connected after that already use your new access URL.

For GitLab, account admins can update an existing GitLab application to your new account access URL in dbt platform. See Update redirect URIs in dbt platform. You can't yet update an existing Azure DevOps repository. Instead, recreate the repository to generate a redirect URI based on your new account access URL.

IntegrationAction required
GitLab (managed app)Add the new redirect URI to your GitLab group application, then update it in dbt platform
GitLab (bring-your-own app)Add the new redirect URI to your GitLab group application, then update it in dbt platform
Azure DevOps (service principal)Update or add an app registration
GitHub Enterprise (self-managed app)Before your assignment date, add the callback URL from your assignment notification email to your GitHub app. Update webhook URLs to your new access URL before the end-of-support date.

Data platform connections​

Data platform connections created before your account had an account-specific access URL keep using your legacy region URL for OAuth until you update them. Connections created after that already use your new access URL, so they need no changes.

Account admins can update older Snowflake, Databricks, and BigQuery OAuth connections to your new access URL directly in dbt platform. See Update redirect URIs in dbt platform.

IntegrationAction required
Snowflake OAuthAdd the new redirect URI to your security integration, then update it in dbt platform
Snowflake External OAuthUpdate the redirect URI in your IdP application
Databricks OAuthAdd the new redirect URI to your Databricks OAuth app, then update it in dbt platform
BigQuery OAuthAdd the new redirect URI to your Google Cloud OAuth client, then update it in dbt platform
Redshift External OAuthUpdate the redirect URI in your IdP application

Update redirect URIs in dbt platform​

If your account has an account-specific access URL, dbt platform flags each Snowflake, Databricks, or BigQuery OAuth connection and GitLab application that still uses a legacy redirect URI. Updating connections requires the Account Admin or Project Creator permission set. Updating a GitLab application requires the Account Admin permission set.

  1. In dbt platform Account settings, go to Connections (or Integrations for GitLab) and select a flagged item. The page shows the new redirect URI.
  2. Add the new redirect URI to the OAuth configuration in your data platform or GitLab, alongside the existing one. The existing URI keeps working until you remove it.
  3. In dbt platform, click Update redirect URI.
  4. Test data platform connections by signing in again from your development credentials. For GitLab, repeat the personal GitLab authorization flow from Account settings > Personal profile > Linked accounts. Confirm that the relevant OAuth flow returns successfully to dbt platform before removing the old redirect URI.

Updating the redirect URI doesn't interrupt active sessions. The new URI takes effect the next time a session expires and the user signs in again.

If sign-in fails after the update, you have 7 days to roll back this change. Open the connection or GitLab application and click Revert to previous URI to restore the previous redirect URI while you troubleshoot. After you confirm that every integration works with the new URI, remove the old URI from your data platform or GitLab.

If several connections share one OAuth app, add the new redirect URI once to that app, then update each connection in dbt platform.

Network and API​

IntegrationAction required
Network allowlistsAdd your new access URL and API access URLs to your allowlist policies before your assignment date. See the note on network rules.
Inbound webhooksUpdate access URLs in your webhook configurations
API integrationsUpdate access URLs in your API clients
Terraform providerUpdate access URLs in your Terraform configuration
Browser bookmarksUpdate personal and shared bookmarks

Validating IP restrictions​

If you've received notification of a new access URL assignment and have IP restrictions enabled, review the network rules that point specifically at your legacy region URL. These include VPN split-tunneling rules, proxy (PAC) rules, and firewall egress rules. Update these rules for your new access URL before your account's scheduled assignment date so access isn't disrupted.

To confirm your new access URL is accessible, send a test request from the same network you'd normally use to reach your legacy region URL. Replace NEW_ACCESS_URL with your account's new access URL and ACCOUNT_ID with your account ID:

  • Browser: Go to https://NEW_ACCESS_URL/api/v2/accounts/ACCOUNT_ID/
  • Terminal: Run curl https://NEW_ACCESS_URL/api/v2/accounts/ACCOUNT_ID/
ResultResponse detailWhat it means
✅ Passed{ ... "detail": "Authentication credentials were not provided." ... }The request reached the API and passed IP restrictions. There's no authenticated session, which is expected for this test.
⚠️ Blocked{ ... "user_message": "Forbidden: Access denied" ... }The request's IP address isn't on your allowlist. Update your network egress rules for the new access URL and test again.

FAQs​

 Why are access URLs changing?

We are transitioning from generic region URLs to account-specific URLs to enhance your experience and strengthen security. This change provides more descriptive URLs to improve dbt URL management, and enables stronger cookie and token policies to protect account data.

 How do I know if my account has new access URLs?

Sign in to your dbt platform account. If your browser location starts with an account prefix, such as ab123.us1.dbt.com, your account has been assigned a new access URL. If your browser location is a legacy region URL, such as cloud.getdbt.com, emea.dbt.com, or au.dbt.com, your account has not been assigned a new access URL. You may refer to API Access URLs.

 How do I find my account's new access URLs?

Refer to API Access URLs.

 What do I need to update before and after my assignment date?
WhenWhat to update
Before your assignment dateNetwork allowlists, VPN, proxy, and firewall rules for IP restrictions, and callback URLs for self-managed GitHub Enterprise applications
After your assignment date, before the end-of-support dateOAuth redirect URIs for data platform connections and Git providers, identity and access management settings, API clients, Terraform configurations, inbound webhooks, and bookmarks
 What happens if my integrations are not updated by the end-of-support date?

After the end-of-support date, legacy region URLs are no longer actively supported. Update your integrations before this date to avoid disruption. For assistance, contact dbt Support.

 Do my API tokens and API calls keep working?

Yes. Personal access tokens and service tokens work with both your legacy region URL and your new access URL. API requests to legacy region URLs are served directly rather than redirected, so update your API clients to your new access URL before the end-of-support date.

 What is unaffected by the migration to new access URLs?

The following are unaffected:

  • Your dbt project code, models, and configurations
  • Your data platform credentials (OAuth connections need a redirect URI update; see Data platform connections)
  • Your account settings, environments, jobs, and schedules
  • The managed dbt GitHub application, the Slack application, and GitLab webhooks
  • Egress private connectivity
  • The underlying dbt platform functionality

For questions or assistance, contact dbt Support.

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

0
Loading