Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 257/260 feeds/APIs · 416/439 docs · checked 21:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

GSA Windows client prerequisites and installation

This page's changes and edits · All guidance changes

Microsoft's edit ·

Fix Windows client doc: registry key table formatting and ARM64 guidance

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 24abe96 · +6 −6 lines · also on GitHub

⋯ 30 unchanged lines
3131 - Azure Virtual Desktop single-session is supported.
3232 - Azure Virtual Desktop multi-session isn't supported.
3333 - Windows 365 is supported.
34 + - Windows on Arm devices (such as Surface Pro and Surface Laptop with Snapdragon processors) require a separate client installer, available at **aka.ms/GlobalSecureAccess-WindowsOnArm**. Don't use the standard x64 installer on Arm64 devices.
3435 - You need local admin credentials to install or upgrade the Global Secure Access client.
3536 - The Global Secure Access client requires a license. For details, see the licensing section of [What is Global Secure Access](overview-what-is-global-secure-access.md). If needed, you can [buy licenses or get trial licenses](https://aka.ms/azureadlicense).
3637
⋯ 638 unchanged lines
675676
676677 ### Restrict nonprivileged users
677678 Administrators can prevent nonprivileged users on the Windows device from disabling or enabling the client by setting the following registry key:
678 −`Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Global Secure Access Client`
679 −`RestrictNonPrivilegedUsers REG_DWORD`
679 +`Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Global Secure Access Client`
680680
681 −|Data|Description|
682 −|--|--|
683 −| 0x0 | Nonprivileged users on the Windows device can disable and enable the client. |
684 −| 0x1 | Nonprivileged users on the Windows device are restricted from disabling and enabling the client. A UAC prompt requires local administrator credentials for disable and enable options. The administrator can also hide the disable button (see [Hide or unhide system tray menu buttons](#hide-or-unhide-system-tray-menu-buttons)). |
681 +|Value |Type |Data |Description |
682 +|---------|---------|---------|---------|
683 +|RestrictNonPrivilegedUsers |REG_DWORD |0x0 |Nonprivileged users on the Windows device can disable and enable the client. |
684 +|RestrictNonPrivilegedUsers |REG_DWORD |0x1 |Nonprivileged users on the Windows device are restricted from disabling and enabling the client. A UAC prompt requires local administrator credentials for disable and enable options. The administrator can also hide the disable button (see [Hide or unhide system tray menu buttons](#hide-or-unhide-system-tray-menu-buttons)). |
685685
686686 ### Disable or enable Private Access on the client
687687 This registry value controls whether Private Access is enabled or disabled for the client. If a user is connected to the corporate network, they can choose to bypass Global Secure Access and directly access private applications.
⋯ 36 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 03:31 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 21:54 UTC · 257 of 260 readable · 255 fully read · documentation 416/439 current