fix: bug #698

[davenewman777]

Overview/Summary

editing query to account for Zone Aligned configurations
Current query only supports Zone Spanning.

Related Issues/Work Items

#698

Breaking Changes

1. Replace me
2. Replace me

As part of this pull request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Ensured PR tests are passing
• Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
• Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

[Copilot]

Pull Request Overview

This PR updates an Azure Resource Graph query to support both Zone Spanning and Zone Aligned configurations for AKS clusters. The changes update the filtering condition to exclude clusters with any availability zones enabled and modify the comment to reflect the new behavior.

• Updated the inline documentation to clarify the query purpose.
• Changed the filter condition from "numOfAvailabilityZones < 2" to "numOfAvailabilityZones < 1" to capture clusters with no availability zones.

Comments suppressed due to low confidence (1)

azure-resources/ContainerService/managedClusters/kql/4f63619f-5001-439c-bacb-8de891287727.kql:10

• Confirm that changing the filter from 'numOfAvailabilityZones < 2' to '< 1' accurately captures the intended logic for Zone Aligned configurations, ensuring that clusters with exactly one zone are treated as valid.

| where numOfAvailabilityZones < 1