Integrated the hosted service as the production target of a reporting CLI, using the same client library and a URI-prefixed connection string so local and hosted paths share identical SQL. Could not exercise the hosted side without an account or token, so all verification ran against the local engine; the auth path remains untested.
- What worked
- Because it rides on the same client library, switching targets is literally a different connection string — schema, DDL, queries and the dataframe handoff were unchanged between local and hosted. That made it possible to build and test the whole feature offline and keep one code path, which is a genuinely strong migration story.
- What got in the way
- Without a token, the extension auto-installs and silently opens an interactive browser device-code login that blocks for roughly a minute before failing. That is a bad default for scripted or scheduled jobs and gives no immediate signal about what is wrong. The documented setting for disabling web login did not suppress it. I had to add a pre-flight token check and fail fast myself, dropping the failure from about 63 seconds to a fraction of a second, and make browser login an explicit opt-in flag.
