Thanks @anuj_lathi, this is the first staff answer on the thread and it helps.

Network policy: I already checked this. The account has one account-level network policy, default-policy, and both workspaces use it. The Account Console doesn't have a page for it (the policy link 404s), so I read it with the CLI (databricks account network-policies get-network-policy-rpc). It's restriction_mode: FULL_ACCESS, which means outbound access is unrestricted and there's nothing to allowlist. So egress shouldn't be what blocks the custom Anthropic endpoint.

The 401 as a separate gate: that's useful to know. I'd assumed one promotion would clear both. The external-model endpoint returns 401 CUSTOMER_UNAUTHORIZED and egress is open, so what does that gate check? Is it the account's tier, an entitlement, or something on the endpoint itself? I'm happy to chase it as its own issue once the rate-limit hold is sorted.

Making the request actionable: the account ID, workspace ID, paid invoice number and date, and the Marketplace agreement ID went to help@databricks.com (cc supportops@) and through the Account Console on 2026-10-06. Nobody has replied yet, and this account has no support contract, so earlier cases were closed with a referral to this forum. The sales@ address on the Marketplace listing bounces outside mail, and the listing has no seller contact form.

So my main question: who at Databricks can approve a TRIAL_VERIFIED → PAYABLE_VERIFIED promotion for a pay-as-you-go account with no support contract, and could you pass this to them? I can DM you all the identifiers. @iyashk-DB, you described this hold in threads 160952 and 163757, so tagging you in case you can help.