Skip to content

Update azure-monitor.md #125299

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update azure-monitor.md #125299

wants to merge 1 commit into from

Conversation

nubartol
Copy link
Contributor

Updated docs to clarify that using Azure Lighthouse for creating other resources not mentioned in this page is not supported and could impact the behavior of the Azure AD B2C tenant as per product group confirmation.

@nubartol
Update azure-monitor.md
595fb22 
Updated docs to clarify that using Azure Lighthouse for creating other resources not mentioned in this page is not supported and could impact the behavior of the Azure AD B2C tenant as per product group confirmation.
@prmerger-automator PRMerger Automator
Copy link
Contributor

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

@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit 595fb22:

✅ Validation status: passed

File Status Preview URL Details
articles/active-directory-b2c/azure-monitor.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Jak-MS
Copy link
Contributor

Jak-MS commented Dec 20, 2024

@kengaderdus
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 Dec 20, 2024
@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

@kengaderdus Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

1 similar comment
@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@PMEds28
Copy link
Contributor

PMEds28 commented May 23, 2025

@kengaderdus

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

@kengaderdus Would you add a comment to indicate what action to take on this PR?

Thanks!

@v-dirichards
Copy link
Contributor

@kengaderdus

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

v-dirichards commented Jul 17, 2025 •
edited
Loading

The author is still waiting on confirmation from the team.

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

@kengaderdus kengaderdus Awaiting requested review from kengaderdus

Assignees

@kengaderdus kengaderdus

Labels
aq-pr-triaged tracking label for the PR review team azure-active-directory/svc B2C/subsvc Change sent to author do-not-merge qualifies-for-auto-merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@nubartol @Jak-MS @v-ccolin @v-dirichards @PMEds28 @kengaderdus