Azure / Azure/azure-kusto-node
The SDK rejects the connection to `.kusto.fabric.microsoft.us` in gov cloud
- Dominant language
- TypeScript
- Stars
- 54
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
The allow-list entry for `https://login.microsoftonline.us` does not include the suffix `.kusto.fabric.microsoft.us`, therefore it rejects KQL database cluster in the Azure Government cloud (e.g., Fairfax).
There appears to be a sync gap between the internal ADO repo and this public repo. The suffix was added to the well-known Kusto endpoints in the internal ADO repository back in early March 2026 (see "Azure-Kusto-Service", PR 14938763), but that change never made it into this package.
**Expected behavior**
The host is recognised as trusted and the query is sent, exactly as it is for `*.kusto.fabric.microsoft.com` in the public cloud.
**Setup (please complete the following information):**
- SDK Version: 7.2.0
- node version: v20.20.2
- typescript version: 5.9.3
**Browser Setup (please complete the following information):**
- framework: React 18.3.1
- server env: yarn 4.9.1
- browser name/version: Microsoft Edge v151
**Desktop (please complete the following information):**
- OS: Windows 11 Enterprise
- Version: 10.0.26200
Contributor guide
Research direction
Start by locating the allow-list entry for https://login.microsoftonline.us and the existing *.kusto.fabric.microsoft.com endpoint handling. Add coverage for the .kusto.fabric.microsoft.us suffix so the host is recognised as trusted and the query is sent in Azure Government cloud; verify with the relevant SDK tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, node.js, typescript
- Domain
- api, cloud, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100