Public mode

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

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 19:52 UTC Customize Public modeDiscuss ChangeIntel on Discord

GSA Android client deployment

This page's changes and edits · All guidance changes

Microsoft's edit ·

Fix GSA macOS and Android client docs based on user feedback

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 125f9df · +14 −4 lines · also on GitHub

⋯ 2 unchanged lines
33 description: The Global Secure Access client secures network traffic at the end-user device. This article describes how to download and install the Android client app.
44 #customer intent: As an administrator, I want to set up and deploy the Global Secure Access mobile client for Android devices.
55 ms.topic: how-to
6 −ms.date: 10/13/2025
6 +ms.date: 02/21/2026
77 ms.author: jayrusso
88 author: HULKsmashGithub
99 ms.reviewer: cagautham
⋯ 35 unchanged lines
4545
4646 The Global Secure Access client also supports non-Microsoft mobile device management (MDM) scenarios. These scenarios, known as *Global Secure Access only mode*, require enabling a traffic forwarding profile and configuring the app based on the vendor documentation.
4747
48 +When configuring through a non-Microsoft MDM, use the following key-value pairs in the managed app configuration:
49 +
50 +| Configuration key | Value | Details |
51 +|----------------------------------|-------|---------|
52 +| Global Secure Access | 1–3 | Required. Controls whether Global Secure Access is enabled in the Defender app. See the table in [Deploy Microsoft Defender for Endpoint on Android](#deploy-microsoft-defender-for-endpoint-on-android) for detailed value descriptions. |
53 +| GlobalSecureAccessPrivateChannel | 0–3 | Optional. Controls the Private Access channel. See the table in [Deploy Microsoft Defender for Endpoint on Android](#deploy-microsoft-defender-for-endpoint-on-android) for detailed value descriptions. |
54 +
4855 ## Deploy Microsoft Defender for Endpoint on Android
4956
5057 To deploy Microsoft Defender for Endpoint on Android, create an MDM profile and configure Global Secure Access.
⋯ 10 unchanged lines
6168
6269 1. On the **Settings** tab:
6370 1. Set **Configuration settings format** to **Use configuration designer**.
64 − 1. Use the JSON editor to configure the disabled configuration keys:
71 + 1. Add the Global Secure Access configuration keys:
6572 1. Select the **+ Add** button.
66 − 1. In the search field, type `global` and select these configuration keys:
73 + 1. In the search field, type `global` and select the configuration keys listed in the following table:
6774 - **Global Secure Access** (this key is required to enable Global Secure Access).
6875 - **GlobalSecureAccessPrivateChannel** (this optional key enables Global Secure Access Private channel).
69 − 1. Set the appropriate values for each configuration key according to the following table:
76 + 1. Set the appropriate values for each configuration key according to the following table:
77 +
78 + > [!NOTE]
79 + > The Android configuration keys differ from the iOS client keys. On Android, use `Global Secure Access` and `GlobalSecureAccessPrivateChannel` as shown here. Don't use the iOS key names (`EnableGSA`, `EnableGSAPrivateChannel`).
7080
7181 | Configuration key | Value | Details |
7282 |----------------------------------|----------|-----------|
⋯ 58 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 19:52 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current