@sohambasu963draftchecks…fix/dynamics365-region-field → master1 files · +11 −3updated 9h agoPlain ticket: https://app.plain.com/workspace/w_01JKXFGRQ1QC95DG0AH1NEKGKE/thread/th_01KTRWJ74RE2GS3FFA3NZ120FP/ — customer's org is on the crm8 (India) regional cluster, so every call fails at DNS: DNS resolution failed for {org}.api.crm.dynamics.com. The connector hardcodes the default US cluster (crm.dynamics.com) in the base URL, OAuth scope resource, and WhoAmI probe, so any org on a non-default cluster (crm2, crm4, crm8, crm11, ...) can never connect.
An internal Zen investigation reached the same diagnosis on April 9 (#buzz-support), but no fix shipped.
region connection field (strict baseUrl field, required: false, default: 'crm') — zero behavior change for existing connections since the default reproduces the exact current hosts.baseUrl, the user_impersonation OAuth scope resource, and the get_current_user_endpoint WhoAmI probe, via ${fields.region || 'crm'}.make validate-config file=apps/dynamics365/config.ts could not run in this environment: installing deps fails with a 401 from the private GitHub package registry (@composiohq/auth-config), so tsgo aborts with missing-module errors unrelated to this change. Please run validation in CI. The field shape mirrors existing optional-with-default region fields (e.g. apps/assemblyai/config.ts).
🤖 Generated with Claude Code