Remove monitoring extensions section from documentation

[makokui]

Removed information about monitoring-related extensions for Azure Batch pools.

While it is possible to install AMA and other agents on Azure Batch node pools, a DCR cannot be directly associated by specifying the node pool. Since this wording could be misleading, I would suggest removing it.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 8af951e:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/batch/monitor-batch.md	✅Succeeded

For more details, please refer to the build report.

[v-dirichards]

@Padmalathas

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

[Copilot]

Pull Request Overview

This PR removes documentation about monitoring-related extensions that can be installed on Azure Batch pool compute nodes. The removal addresses potential confusion since Data Collection Rules (DCR) cannot be directly associated with Azure Batch node pools, making the original documentation misleading despite the technical possibility of installing the agents.

Key Changes:

• Removed the section describing monitoring extensions (Azure Monitor agents, Azure Diagnostics, and Log Analytics extensions) for Azure Batch pools
• Removed the reference link to agent comparison documentation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[v-dirichards]

@Padmalathas

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

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