Skip to content

Repo sync for protected branch #2881

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

Merged
learn-build-service-prod merged 4 commits into from
Apr 29, 2026
Merged

Repo sync for protected branch #2881

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
72d932b
Increase custom workload group limit from 10 to 16
yahavx-ms Apr 29, 2026
f11d202
Merge pull request #7453 from yahavx-ms/patch-15
prmerger-automator[bot] Apr 29, 2026
f41d961
Merge pull request #7454 from MicrosoftDocs/main
learn-build-service-prod[bot] Apr 29, 2026
df9c971
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Apr 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions data-explorer/kusto/management/workload-groups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,12 @@ Workload groups allow you to group together sets of management commands and quer
:::moniker range="azure-data-explorer"
Together with [workload group policies](#workload-group-policies), workload groups serve as a resource governance system for incoming requests to the cluster. When a request is initiated, it gets classified into a workload group. The classification is based on a user-defined function defined as part of a [request classification policy](request-classification-policy.md). The request follows the policies assigned to the designated workload group throughout its execution.

Workload groups are defined at the cluster level, and up to 10 custom groups can be defined in addition to the three [built-in workload groups](#built-in-workload-groups).
Workload groups are defined at the cluster level, and up to 16 custom groups can be defined in addition to the three [built-in workload groups](#built-in-workload-groups).
::: moniker-end
:::moniker range="microsoft-fabric"
Together with [workload group policies](#workload-group-policies), workload groups serve as a resource governance system for incoming requests to the eventhouse. When a request is initiated, it gets classified into a workload group. The classification is based on a user-defined function defined as part of a [request classification policy](request-classification-policy.md). The request follows the policies assigned to the designated workload group throughout its execution.

Workload groups are defined at the eventhouse level, and up to 10 custom groups can be defined in addition to the three [built-in workload groups](#built-in-workload-groups).
Workload groups are defined at the eventhouse level, and up to 16 custom groups can be defined in addition to the three [built-in workload groups](#built-in-workload-groups).
::: moniker-end
> [!NOTE]
> Requests that aren't queries or management commands, such as streaming ingestion requests, aren't included in the scope of workload groups.
Expand Down