GSA Android client deployment

This page's changes and edits · All guidance changes

Microsoft's edit · 1 Apr 00:01 UTC

edit pass: installing-the-global-secure-access-client

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 3d1ad03 · +20 ~~−21~~ lines · also on GitHub

⋯ 76 unchanged lines

7777 1. On the **Settings** tab:

7878

7979 1. Set **Configuration settings format** to **Use configuration designer**.

80 − 1. Add the Global Secure Access configuration keys:

81 − 1. Select the **+ Add** button.

82 − 1. In the search field, type **global** and select the configuration keys listed in the following table.

83 − 1. Set the appropriate values for each configuration key according to the following table.

80 + 1. Select the **+ Add** button.

81 + 1. In the search field, type **global** and select the Global Secure Access configuration keys listed in the following table.

82 + 1. Set the appropriate values for each configuration key according to the following table.

8483

85 − > [!NOTE]

86 − > 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`).

87 − >

88 − > The `GlobalSecureAccessPA` configuration key is no longer supported.

84 + > [!NOTE]

85 + > 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`).

86 + >

87 + > The `GlobalSecureAccessPA` configuration key is no longer supported.

8988

90 − | Configuration key | Value | Details |

91 − |----------------------------------|----------|-----------|

92 − | `Global Secure Access` | No value | Global Secure Access isn't enabled and the tile isn't visible. |

93 − | | `0` | Global Secure Access isn't enabled and the tile isn't visible. |

94 − | | `1` | The tile is visible and defaults to `false` (disabled state). The user can enable or disable Global Secure Access by using the toggle in the app. |

95 − | | `2` | The tile is visible and defaults to `true` (enabled state). The user can override Global Secure Access. The user can enable or disable Global Secure Access by using the toggle in the app. |

96 − | | `3` | The tile is visible and defaults to `true` (enabled state). The user *can't* disable Global Secure Access. |

97 − | `GlobalSecureAccessPrivateChannel` | No value | Global Secure Access defaults to value 2 behavior. |

98 − | | `0` | Private Access isn't enabled and the toggle option isn't visible to the user. |

99 − | | `1` | The Private Access toggle is visible and defaults to the disabled state. The user can enable or disable Private Access. |

100 − | | `2` | The Private Access toggle is visible and defaults to the enabled state. The user can enable or disable Private Access. |

101 − | | `3` | The Private Access toggle is visible but unavailable, and defaults to the enabled state. The user *can't* disable Private Access. |

89 + | Configuration key | Value | Details |

90 + |----------------------------------|----------|-----------|

91 + | `Global Secure Access` | No value | Global Secure Access isn't enabled and the tile isn't visible. |

92 + | | `0` | Global Secure Access isn't enabled and the tile isn't visible. |

93 + | | `1` | The tile is visible and defaults to `false` (disabled state). The user can enable or disable Global Secure Access by using the toggle in the app. |

94 + | | `2` | The tile is visible and defaults to `true` (enabled state). The user can override Global Secure Access. The user can enable or disable Global Secure Access by using the toggle in the app. |

95 + | | `3` | The tile is visible and defaults to `true` (enabled state). The user *can't* disable Global Secure Access. |

96 + | `GlobalSecureAccessPrivateChannel` | No value | Global Secure Access defaults to value `2` behavior. |

97 + | | `0` | Private Access isn't enabled and the toggle option isn't visible to the user. |

98 + | | `1` | The Private Access toggle is visible and defaults to the disabled state. The user can enable or disable Private Access. |

99 + | | `2` | The Private Access toggle is visible and defaults to the enabled state. The user can enable or disable Private Access. |

100 + | | `3` | The Private Access toggle is visible but unavailable, and it defaults to the enabled state. The user *can't* disable Private Access. |

102101

103102 :::image type="content" source="media/how-to-install-android-client/create-policy-settings.png" alt-text="Screenshot of the Settings tab in the pane for creating an app configuration policy." lightbox="media/how-to-install-android-client/create-policy-settings-expanded.png":::

104103

⋯ 16 unchanged lines

121120

122121 Because the Android client is integrated with Defender for Endpoint, it's helpful to understand the user experience. The client appears in the Defender dashboard after onboarding to Global Secure Access. Onboarding happens by enabling a traffic forwarding profile.

123122

124 −![Screenshot of the Defender app that shows the Global Secure Access tile on the dashboard.](media/how-to-install-android-client/defender-endpoint-dashboard.png)

123 +![Screenshot of the Global Secure Access tile on the dashboard of the Defender app.](media/how-to-install-android-client/defender-endpoint-dashboard.png)

125124

126125 *The client is disabled by default when it's deployed to user devices.* Users need to enable the client from the Defender app. To enable the client, tap the toggle.

127126

⋯ 24 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:16 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.