Skip to content

Updated ADMX for WSLC#40422

Draft
craigloewen-msft wants to merge 2 commits intomasterfrom
user/crloewen/admx-update
Draft

Updated ADMX for WSLC#40422
craigloewen-msft wants to merge 2 commits intomasterfrom
user/crloewen/admx-update

Conversation

@craigloewen-msft
Copy link
Copy Markdown
Member

Summary of the Pull Request

Updated ADMX values for WSLC controls.

PR Checklist

Completed PR checklist, since it's just an ADMX no big changes or effort needed from the checklist.

  • Closes: Link to issue #xxx
  • Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
  • Tests: Added/updated if needed and all pass
  • Localization: All end user facing strings can be localized
  • Dev docs: Added/updated if needed
  • Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Simple ADMX change.

Validation Steps Performed

Validated ADMX compiles (It's known that the logic isn't implemented yet)

Copilot AI review requested due to automatic review settings May 5, 2026 14:53
Comment thread intune/WSL.admx
Copy link
Copy Markdown
Member

@benhillis benhillis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions / questions.

Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

Comment thread intune/WSL.admx Outdated
Comment thread intune/WSL.admx Outdated
Comment thread intune/WSL.admx Outdated
Comment thread intune/WSL.admx Outdated
Comment thread intune/WSL.admx
Comment thread intune/WSL.admx
<parentCategory ref="WSLContainerCLI" />
<supportedOn ref="windows:SUPPORTED_Windows10" />
<elements>
<text id="WSLContainerCLIRegistryAllowlist_Input" valueName="WSLContainerCLIRegistryAllowlist" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not <list>?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No idea if ADMX supports that or not. But a string seems easier for us to parse! So I'd opt for keeping it as a string

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ADMX supports having a list element. I don't know how this looks in Intune, but for the local Group Policy Editor, the experience for this with a list is IMO better than with a string. Especially once you have many or long values.

As an example, these are the first two policies that I found using string and list.
image
image

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

list seems better

Comment thread intune/en-US/WSL.adml Outdated
<string id="AllowWSLContainerCLIExplain">This policy controls whether the WSL Container CLI (wslc.exe) can be used on this machine. When enabled or not configured, users can use the WSL Container CLI. When set to disabled, the WSL Container CLI is blocked for all users.</string>

<string id="WSLContainerCLIRegistryAllowlist">Allowlist for WSL container CLI registries</string>
<string id="WSLContainerCLIRegistryAllowlistExplain">When enabled, the WSL Container CLI will only be allowed to pull images from the registries listed here. Specify registries as a semicolon-separated list of hostnames (e.g. "registry1.example.com;registry2.example.com").
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about when the policy is disabled or not configured?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made the verbage clearer

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's clear what happens when you disable the policy. Does it mean "there is no allowlist, so you cannot use any registry" or "there is no allowlist, so you can use any registry"

Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml Outdated
Comment thread intune/en-US/WSL.adml
<string id="WSLContainers">WSL Containers</string>
<string id="WSLContainerCLI">WSL Container CLI</string>
<string id="WSLContainerAPI">WSL Container API</string>
<string id="WSLContainer">WSL Container</string>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it Containers or Container?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants