Skip to content

Conversation

@WolfgangOfner
Copy link
Contributor

Added necessary permissions to access LAW and ALB logs and metrics.

Grafana only has access to the default Log Analytics Workspace. If another LAW is used then Grafana won't see it. After assigning the Monitoring Reader role, Grafana can see the LAW and the user can select it as a data source.
The same for the application gateway for containers, except Grafana never has default access and always needs the Monitoring Reader role (or similar) assigned to read and display the data.

Added necessary permissions to access LAW and ALB logs and metrics.
@prmerger-automator
Copy link
Contributor

@WolfgangOfner : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 686a687:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/for-containers/prometheus-grafana.md ✅Succeeded

For more details, please refer to the build report.

@ttorble ttorble requested a review from Copilot January 5, 2026 15:41
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds documentation about required Azure RBAC permissions for Grafana to access Log Analytics Workspace (LAW) and Application Gateway for Containers metrics. The changes address scenarios where Grafana lacks default access to these resources by instructing users to assign the Monitoring Reader role to Grafana's managed identity.

  • Added guidance for assigning Monitoring Reader role to access custom Log Analytics Workspaces
  • Added guidance for assigning Monitoring Reader role to access Application Gateway for Containers metrics

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ttorble
Copy link
Contributor

ttorble commented Jan 5, 2026

@mbender-ms

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jan 5, 2026
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 2d58be2:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/for-containers/prometheus-grafana.md ✅Succeeded

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit bf571c8:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/for-containers/prometheus-grafana.md ✅Succeeded

For more details, please refer to the build report.

@mbender-ms
Copy link
Contributor

Thanks for the suggestion, @WolfgangOfner.

In the pre-requisites of the article, the required permissions are called out. Your addition is not needed when follow as written.

#please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants