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

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

Learn Build status updates of commit 36fcfb7:

⚠️ Validation status: warnings

articles/azure-large-instances/workloads/epic/create-a-volume-group.md

• Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'azure-baremetal-infrastructure'.

articles/azure-large-instances/workloads/epic/index.yml

• Line 9, Column 15: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'azure-baremetal-infrastructure'.

articles/azure-resource-manager/templates/form-view-overview.md

• Line 4, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/baremetal-infrastructure/index.yml

• Line 11, Column 15: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'azure-baremetal-infrastructure'.

articles/container-apps/confidential-compute.md

• Line 7, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/cost-management-billing/reservations/fabric-capacity.md

• Line 8, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/durable-task/common/durable-task-metrics.md

• Line 5, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/energy-data-services/concepts-analytics-consumption-zone.md

• Line 5, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/firmware-analysis/release-notes.md

• Line 6, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/logic-apps/automation/compare-automation-services.md

• Line 6, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/logic-apps/connector-namespace/connector-namespace-hosted-mcp.md

• Line 8, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/redis/best-practices-flash-optimized.md

• Line 5, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/virtual-wan/azure-vpn-client-linux-retirement.md

• Line 7, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

articles/vpn-gateway/azure-vpn-client-linux-retirement.md

• Line 7, Column 11: [Warning: ms-topic-invalid - See documentation] Invalid value for 'ms.topic': 'conceptual'.

docfx.json

• Line 1089, Column 85: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'azure-baremetal-infrastructure'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@kengaderdus

Can you review the proposed changes? Please note, all validation warnings must be resolved before we can merge.

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