Android 16 NFC Management for Business Devices: What Owners Should Know

Android 16 lets IT admins turn a device's NFC radio on or off and stop users from changing that setting. If you run company-owned Android phones, tablets, or point-of-sale handhelds, that is a new lever you can pull from your device management tool instead of walking around with a checklist.

What Android 16 added

Google's enterprise page for Android 16 lists two NFC changes under "NFC management." Both are small on paper. Both are useful in practice.

Turn the radio on or off

IT admins can enable or disable NFC on the device through NfcAdapter.enable() and NfcAdapter.disable(). An independent write-up from Bayton describes this as programmatic control over the NFC radio, so a device policy controller (DPC) can switch the NFC controller without the user touching Settings.

Lock the setting

Android 16 also adds a user restriction, UserManager.DISALLOW_CHANGE_NEAR_FIELD_COMMUNICATION_RADIO, which prevents users from making changes to NFC settings. Pair it with the on/off call and you get a device where NFC is in the state you chose and stays there.

Who can use these controls

It isn't a setting an employee flips on a personal phone. For custom DPCs, Bayton reports the APIs are restricted to Device Owners and Profile Owners of company-owned devices. In plain terms: the device has to be enrolled and managed by your organization.

If you use a managed service instead of writing your own DPC, the route is different. For Android Management API (AMAPI) deployments, Bayton says NFC control is available through the device connectivity policy. We couldn't confirm the exact AMAPI field name in Google's reference, so ask your MDM vendor which setting maps to it and which Android 16 devices it covers.

Not sure how Android and iPhone differ on NFC in general? We cover what each platform can really do with NFC. These controls are Android-only.

Where fleets will use it

Bayton points to two fits: dedicated devices where NFC should only be active during specific workflows, such as point-of-sale, and security policies that require NFC to be off across the whole fleet.

Picture a warehouse scanner that never needs NFC. Switch it off and lock the setting, and nobody re-enables it by accident. Or picture a checkout tablet that should only accept taps while a sale is open. A DPC could turn NFC on for that workflow and off afterward. That second pattern is our example, not something the sources walk through, so treat it as an idea to prototype.

If you track stock with tags, keep your reader devices out of the "NFC off" group. Our guide to NFC for retail inventory covers what tap-to-track can and can't do.

What the docs leave open

Neither source says what happens to NFC-dependent features when the radio is disabled. Contactless payments and building-access badges both rely on NFC, so expect them to stop working, and confirm it on one device before you roll anything out. Our explainer on how NFC wallet passes work shows why those features lean on the radio.

The sources also don't describe how the restriction behaves on personal devices with a work profile (BYOD). Test it before you promise your staff either outcome.

A sensible rollout:

• Pilot on one company-owned device running Android 16.
• Check payments, badges, and any tag-reading app you use.
• Only then apply the policy to a group.

For checking tags before and after a policy change, NFCore reads and writes NDEF tags on iPhone, and the Android version on Google Play works the same way. It runs on-device with no account and no cloud upload.

Bottom line

Android 16 gives admins a clean way to set NFC on or off and keep users from changing it, but only on company-owned, managed devices. Test the side effects on one unit, then roll it out.

Frequently Asked Questions

Can I turn off NFC on my employees' personal phones?

The sources describe the custom DPC APIs as restricted to Device Owners and Profile Owners of company-owned devices. They don't describe behavior on personal work profiles, so confirm with your MDM vendor before assuming it works there.

Does this change anything on iPhones?

No. These are Android 16 platform controls. Apple manages iPhones through its own MDM framework, which this article doesn't cover.

Will contactless payments still work if NFC is off?

The sources don't say how payment or badge features behave with the radio disabled. Taps rely on the NFC radio, so test on one device first rather than planning a rollout around an assumption.

Is a managed Android device a replacement for NFCore?

They do different jobs. These controls decide whether the radio is on. NFCore is for reading and writing tags on devices you control.