-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[monitor-query] Only works with Azure Commercial Cloud #15663
Comments
As a follow up to #2 above, it appears that the option |
Thanks for reporting @davemedvitz @richardpark-msft Can you take an initial look here and loop in Daniel as needed if this is an Identity issue? |
@davemedvitz - I'll take a look at this today. I believe I just need to plumb the proper endpoint through a little further, so hopefully not an identity issue. |
@davemedvitz I'm very interested in talking to customers about their use cases and the beta 1 SDK that shipped last week. Please email me at scott dot addie at microsoft dot com if you're interested. Any feedback you can provide will help us build a better SDK for you and other customers. |
…horization scopes. (#15705) This PR makes it so you can pass in a custom endpoint and custom scopes for authentication. Without these you can't properly connect to government-based clouds. Example usage: ```typescript const dac = new DefaultAzureCredential({ authorityHost: AzureAuthorityHosts.AzureGovernment }); const client = new LogsQueryClient(dac, { endpoint: "https://api.loganalytics.us/v1", scopes: "https://api.loganalytics.us/.default" }); ``` Fixes #15663
@davemedvitz : we've now released 1.0.0-beta.2 based which fixes your issue: https://www.npmjs.com/package/@azure/monitor-query/v/1.0.0-beta.2 Thank you very much for reporting this issue. |
…horization scopes. (Azure#15705) This PR makes it so you can pass in a custom endpoint and custom scopes for authentication. Without these you can't properly connect to government-based clouds. Example usage: ```typescript const dac = new DefaultAzureCredential({ authorityHost: AzureAuthorityHosts.AzureGovernment }); const client = new LogsQueryClient(dac, { endpoint: "https://api.loganalytics.us/v1", scopes: "https://api.loganalytics.us/.default" }); ``` Fixes Azure#15663
Consider the following code, using the AzureCLI auth method for local development.
My expectation was that this would function, directing the client to the API endpoints in the Azure Gov Cloud. Instead, it errors on authentication.
As far as I can tell, there are two issues.
defaultMonitorScope
variable is hard coded to the Commercial cloud. If I change this locally the authentication works, but the queries still fail.endpoint
(although$host
does). Adjusting this locally appears to let the query work. (Not sure why this is an issue, as it appears to be set properly in the constructor forAzureLogAnalyticsContext
)I am using the 1.0.0-beta.1 version
Thank you.
Dave
The text was updated successfully, but these errors were encountered: