Inconsistent Behavior Across Azure Clouds
usabilityActiveStableThe command works in Azure Public Cloud but fails in Azure China, causing confusion and inconsistency for users managing multiple environments.
Score Breakdown
Heuristic ranking from public discussion signals — not a validated prediction of commercial opportunity, demand, or willingness to pay.
Composite 67/100 (High, unvalidated). Top driver: Willingness to pay (30% weight, 22.5 pts).
Heuristic only — often urgency map or random scaffolding on ingest, not measured mention frequency. Maps to XPS relevance (with market size).
LLM/mock judgment of intensity from title/summary text — not ops or ticket data. Maps to XPS quality (with willingness to pay).
LLM/mock purchase-intent guess from text — not invoices, surveys, or paid seats. Maps to XPS quality.
Heuristic/scaffold (often random or fixed on insert) — not a verified mention trajectory. Maps to XPS novelty.
Heuristic/scaffold (often random or fixed) — not TAM research. Maps to XPS relevance (with frequency).
Catalog notes (not predictive analysis)
Inconsistent Behavior Across Azure Clouds (usability). Catalog heuristic opportunity score: 67/100 — a chosen formula over discussion-signal facets, not evidence of demand, conversion, or willingness to pay. Treat as browsing rank, not a commercial prediction.
The command works in Azure Public Cloud but fails in Azure China, causing confusion and inconsistency for users managing multiple environments.
Source Examples
“az monitor log-analytics query fails in AzureChinaCloud with CloudEndpointNotSetException ### Describe the bug When running az monitor log-analytics query in **Azure China (AzureChinaCloud)**, the command consistently fails with: azure.cli.core.cloud.CloudEndpointNotSetException The exception is thrown during client initialization, before any HTTP request is sent to the Log Analytics service. This issue occurs across: Different workspaces Different KQL queries (e.g. Usage, AzureDiagnostics, StorageBlobLogs) To Reproduce Set Azure CLI cloud to Azure China: az cloud set --name AzureChinaCloud Login: az login Run any Log Analytics query: az monitor log-analytics query \ --workspace <workspace-id> \ --analytics-query "Usage" Expected behavior The command should successfully execute the Log Analytics query and return results, the same way it does in Azure Public Cloud. Actual behavior The command fails immediately with: azure.cli.core.cloud.CloudEndpointNotSetException No HTTP request is sent to the Log Analytics service. Debug output Relevant part of the stack trace: File ".../azext_loganalytics/aaz/latest/monitor/log_analytics/_query.py", line 75 self.QueryExecute(ctx=self.ctx)() File ".../azure/cli/core/aaz/_operation.py", line 37, in __init__ self.client = ctx.get_http_client(self.CLIENT_TYPE) File ".../azure/cli/core/aaz/_client.py", line 75, in __init__ raise CloudEndpointNotSetException() azure.cli.core.cloud.**CloudEndpointNotSetException** Analysis / Root Cause Based on the Azure CLI Core implementation in: azure/cli/core/_profile.py Azure CLI resolves service endpoints from the current cloud profile: endpoint = cloud.endpoints.get(endpoint_name) if not endpoint: raise CloudEndpointNotSetException() In AzureChinaCloud, the cloud profile does not appear to define the required endpoint for Log Analytics Query used by the log-analytics extension (AAZ-based). **As a result:** Client initialization fails CloudEndpointNotSetException is raised The query is never executed This suggests a missing or incomplete Log Analytics endpoint definition for AzureChinaCloud, rather than a user configuration or query issue. Environment Azure CLI version: az version # 2.78.0 Extension: log-analytics 1.0.0b1 OS:Windows 11 Cloud: AzureChinaCloud Other Log Analytics access methods (e.g. REST API / PowerShell) work in Azure China This appears to be a gap in Sovereign Cloud support for the new AAZ-based log-analytics extension **Ask Please confirm whether this is a known issue and advise: Whether a missing endpoint definition for AzureChinaCloud needs to be added Or if there is a recommended workaround until full support is available** ### Related command az monitor log-analytics query --workspace XXXXX --analytics-query 'kusto query' --debug ### Errors PS C:\Users\<USER>\AppData\Roaming\Code\User> az monitor log-analytics query --workspace <WORKSPACE_ID> --analytics-query <KQL_QUERY> --debug cli.knack.cli: Command arguments: ['monitor', 'log-analytics', 'query', '--workspace', '<WORKSPACE_ID>', '--analytics-query', '<KQL_QUERY>', '--debug'] cli.knack.cli: __init__ debug log: Enable color in terminal. cli.knack.cli: Event: Cli.PreExecute [] cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [...] cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate [] cli.azure.cli.core: Modules found from index for 'monitor': ['azure.cli.command_modules.monitor', 'azext_loganalytics'] cli.azure.cli.core: Loading command modules: Name Load Time Groups Commands monitor 1.729 23 70 cli.azure.cli.core: Loading extensions: Name Load Time Groups Commands Directory log-analytics 0.018 2 1 C:\Users\<USER>\.azure\cliextensions\log-analytics cli.azure.cli.core: Loaded 23 groups, 71 commands. cli.azure.cli.cor”
Competitive Landscape
- Existing solutions are either too expensive or too limited
- Most competitors target enterprise, leaving mid-market underserved
- Community scripts and manual processes are the primary alternative
Recommended Next Steps
- ✓Validate pain intensity with 5-10 target customer interviews
- ✓Build minimal viable solution addressing the core workflow
- ✓Test pricing with early adopters from community forums
Related Pain Points
Target Customers
- IT teams at mid-size organizations (100-2000 employees)
- MSPs and consultants managing multiple client environments
- Teams without dedicated specialist staff for this domain
Monetization Ideas
- 1SaaS subscription model ($99-$499/month depending on scale)
- 2Usage-based pricing aligned with value delivered
- 3Freemium tier to drive adoption and prove value