# Configure Wi-Fi Networks > Push predefined Wi-Fi configurations to Managed Android Devices using Applivery Policies — supports WPA-PSK, WPA-EAP, hidden SSIDs, and advanced network options. Source: https://docs.applivery.com/en/device-management/android/policies/configure-wifi-networks/ • Last updated: 2026-06-09 **Answers:** How do I push a Wi-Fi configuration to Managed Android Devices? · What is openNetworkConfiguration in Android Enterprise? · How do I configure WPA-EAP Wi-Fi on Android MDM? · What is the GUID field in a Wi-Fi network policy? · How does Auto Connect work on Managed Android Devices? · What is MAC Address Randomization Mode in Android MDM? · Can I configure hidden SSIDs on Managed Android Devices? · What is a BSSID Allowlist in an Android Wi-Fi policy? **Key topics:** Wi-Fi policy configuration, openNetworkConfiguration, Android Enterprise network management, Applivery MDM, Android, Applivery, Android Management API, Wi-Fi --- **TL;DR:** Use Applivery Android policies to push Wi-Fi configurations automatically to Managed Devices — define the SSID, security type, and advanced options like Auto Connect, MAC randomization, and proxy settings. Applivery lets you define Wi-Fi network configurations directly within an Android policy so that managed devices automatically receive the necessary connectivity settings — no manual setup required on each device. Configuration is based on `openNetworkConfiguration`, the standard format used by the Android Management API to declare Wi-Fi networks on managed devices. This is particularly useful in COBO/COPE deployments, kiosk-mode devices, and large-scale rollouts where minimizing user intervention is essential — devices connect to approved corporate networks automatically, from first boot. ## Prerequisites Before you start, make sure you have: - An Android device enrolled in Applivery with an Android Enterprise policy assigned. - The network SSID and its security type — for example, open, WPA-PSK, or WPA-EAP. - For 802.1X/EAP networks: the required authentication parameters and certificates, including CA certificates and, if applicable, a client certificate. :::warning If you plan to block manual Wi-Fi changes on the device, make sure at least one valid and tested network is already declared in the policy — otherwise the device may lose Wi-Fi access entirely. ::: ## Configuring a Wi-Fi network **Open the policy** Once in the [**Applivery Dashboard**](https://dashboard.applivery.io/), go to any of your **Policies** or [create a new one](https://docs.applivery.com/en/device-management/general-settings/create-device-policies/). From the left-hand menu, select **WiFi**, then click **\+ Add WiFi network**. ![add wifi network](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/df1eea51-794f-4b1c-8170-9cc18ac48426.png) **Configure the network** Fill in the network details according to the type of corporate network you need to deploy. See the [field reference](#field-reference) below for a description of each option. ![wifi network config](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/86fdfd55-df43-4e18-86b0-309831db7cbb.png) **Save and apply** Click **Save** to apply changes, then assign the Policy to the relevant devices or groups. Applivery will push the Wi-Fi configuration automatically to all targeted devices. ## Field reference ### General - **GUID** — Unique internal identifier for the network entry within the policy. It lets Applivery and Android distinguish this Wi-Fi entry from others, even when multiple entries share the same SSID across different policies or versions. - **Name** — A friendly label visible only in the Applivery Dashboard. It does not need to match the SSID; it is for administrative purposes only (for example, "Wi-Fi office floor 3"). - **SSID** — The actual name of the Wi-Fi network that the device will see and connect to. This maps to the `SSID` field in `openNetworkConfiguration` and must match exactly what is configured on the access point, including capitalization. - **Security** — The security type of the Wi-Fi network. Applivery supports the values defined by the Android Management API: `None` (open), `WEP-PSK`, `WPA-PSK`, and `WPA-EAP`. Selecting a value enables the corresponding fields — for example, a passphrase field for WPA-PSK, or EAP parameters and certificate selectors for WPA-EAP. ### Advanced configuration - **Auto Connect** — When enabled, the device connects to this network automatically whenever it is in range, without user intervention, provided the credentials are correct. - **MAC Address Randomization Mode** — Controls whether the device uses its real hardware MAC address or a randomized one for this network. Maps to `MACAddressRandomizationMode` in the Android Management API (Android 13+). Relevant in environments with MAC-based access control or network inventory management. - **Hidden SSID** — Marks the network as hidden, meaning the access point does not broadcast the SSID name. When enabled, the device still searches for and connects to the network using the configured SSID, even if it does not appear in the visible networks list. - **BSSID Allowlist** — An optional list of BSSIDs (MAC addresses of specific access points) that the device is allowed to associate with for this SSID. Restricts connectivity to specific radios — useful when the same SSID exists across multiple locations and you only want devices to connect to a defined subset. - **Proxy Settings** — Proxy configuration applied while the device is connected to this network. Supports no proxy, manual configuration (host, port, and exclusions), or automatic configuration via PAC URL, following the `ProxySettings` field of the Android Management API. ## Best practices - Enable **Auto Connect** for networks that must be available from first boot. - Validate the configuration on a **pilot group** before rolling it out to the entire fleet. - If you plan to block manual Wi-Fi modifications, confirm the policy contains a functional and tested network before enabling that restriction. - In environments with MAC-based access control, evaluate whether to fix **MAC Address Randomization Mode** based on your network infrastructure's expected behavior. Once the Policy is applied, the device shows the network as saved or connects automatically, depending on the `AutoConnect` setting. If the network does not apply as expected, review the security type, password, SSID visibility, certificates, and EAP parameters configured in the Policy.