I’m configuring a Windows 11 kiosk using Assigned Access with the 2022 schema and trying to achieve the following:
Goal
- Allow users to click the Wi-Fi icon in the taskbar to connect to networks
Prevent access to the Settings app in general (outside of Wi-Fi)
Current behavior
The Wi-Fi icon can be shown via systemTray.wifi = true in TaskbarLayout
However, the icon is not clickable unless the Settings backend is allowed
From testing, the Wi-Fi flyout only becomes functional when the following app is added to AllowedApps:
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
Once this is allowed, users can technically access other Settings pages (even if search is hidden and Settings is not pinned).
Questions
Is there any supported way (in Assigned Access 2022) to allow the network/Wi-Fi flyout only, without enabling the full Settings app?
Is <AllowNetworkStatusFlyout>true</AllowNetworkStatusFlyout> expected to work independently in the 2022 schema, or does it still rely on the Immersive Control Panel?
If this is not possible by design, can Microsoft confirm this limitation so it can be planned around?
At the moment, the only viable workaround appears to be:
Allowing the Settings app
Hiding discovery paths (search, pins)
Optionally deep-linking users to ms-settings:network-wifi
I’d appreciate confirmation on whether this is the intended and only supported approach.I’m configuring a Windows 11 kiosk using Assigned Access with the 2022 schema and trying to achieve the following:
Goal
Allow users to click the Wi-Fi icon in the taskbar to connect to networks
Prevent access to the Settings app in general (outside of Wi-Fi)
Current behavior
The Wi-Fi icon can be shown via systemTray.wifi = true in TaskbarLayout
However, the icon is not clickable unless the Settings backend is allowed
From testing, the Wi-Fi flyout only becomes functional when the following app is added to AllowedApps:
<App
Once this is allowed, users can technically access other Settings pages (even if search is hidden and Settings is not pinned).
Questions
Is there any supported way (in Assigned Access 2022) to allow the network/Wi-Fi flyout only, without enabling the full Settings app?
Is <AllowNetworkStatusFlyout>true</AllowNetworkStatusFlyout> expected to work independently in the 2022 schema, or does it still rely on the Immersive Control Panel?
If this is not possible by design, can Microsoft confirm this limitation so it can be planned around?
At the moment, the only viable workaround appears to be:
Allowing the Settings app
Hiding discovery paths (search, pins)
Optionally deep-linking users to ms-settings:network-wifi
I’d appreciate confirmation on whether this is the intended and only supported approach.