Skip to content
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

[Azure.Monitor.Ingestion] Update AuthorizationScope #38998

Closed
nisha-bhatia opened this issue Sep 27, 2023 · 0 comments · Fixed by #39078
Closed

[Azure.Monitor.Ingestion] Update AuthorizationScope #38998

nisha-bhatia opened this issue Sep 27, 2023 · 0 comments · Fixed by #39078
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. Monitor Monitor, Monitor Ingestion, Monitor Query
Milestone

Comments

@nisha-bhatia
Copy link
Member

Priority: high

The AuthorizationScope in Ingestion currently defaults to the public cloud.
While we do have sovereign support, update the AuthorizationScope to also be set by the user.
Update constructor in LogsIngestionClient

@nisha-bhatia nisha-bhatia added Monitor Monitor, Monitor Ingestion, Monitor Query Client This issue points to a problem in the data-plane of the library. labels Sep 27, 2023
@nisha-bhatia nisha-bhatia self-assigned this Sep 27, 2023
@scottaddie scottaddie added this to the 2023-10 milestone Sep 28, 2023
@scottaddie scottaddie added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Sep 28, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jan 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. Monitor Monitor, Monitor Ingestion, Monitor Query
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants