Skip to main content
Rose
Community Manager
June 16, 2026
StickyNews

Android 17 brings intelligent experiences and advanced safeguards for enterprise

Related products:Android Enterprise
  • June 16, 2026
  • 3 replies
  • 1488 views

Android is evolving from an operating system into an intelligence system. Android 17 supports this shift with intuitive tools designed to reduce daily friction. By pairing these new capabilities with robust enterprise controls, this update streamlines daily workflows without compromising digital defences.

While technical specs are available in our developer docs, here is a look at the latest advancements:

 

Intelligent experiences

 

New agentic capabilities are grounded in privacy and user control, ensuring that as your devices become smarter, they remain a secure partner for business.

  • Agentic automation: Gemini now uses on-screen context to execute multi-step workflows across apps, like identifying project specs in a PDF to update a tracking sheet, or converting a photo of a whiteboard session into a polished summary and sharing it with the team. To protect enterprise data, agents in the personal profile cannot access or automate apps in the Android Work Profile, and IT admins are able to disable AI automation entirely on managed devices. See our Gemini for Work Help Center article for more details on using and controlling Gemini on Android.
  • Extended Desktop experience: As a reminder, recent updates allow supported devices to extend their workspace to external displays via a multi-window desktop mode. Users can choose to run apps on the external display using desktop mode, or move them seamlessly between the internal and external screens for a full workstation experience.

Note: Custom launchers are not supported when extending desktop sessions across both displays. When a device is in Kiosk mode, Android Desktop is limited to "mirroring" the device display.

 

Advanced safeguards

 

Our commitment to built-in security businesses can trust remains the foundation of every update.

  • Local Network Protection: To enhance privacy, a new permission requires apps to request access before interacting with devices on a local network. IT admins can pre-grant this permission to ensure enterprise tools and local proxies continue to function seamlessly.
  • Certificate Transparency (CT): Android is strengthening defenses against man-in-the-middle attacks. By enforcing CT, the system ensures digital certificates are verified and logged, providing deeper security transparency without impacting Kiosk or locked-down configurations.

There are also some exciting consumer features in this release - like App Bubbles, which let you float apps over your workspace for instant, distraction free access, and, Pause Point, which helps maintain focus by adding a moment of intention to daily app habits. You can explore more in our latest Android Keyword.

 

Join the discussion

 

The Android Enterprise customer community is a great space to see how these updates are being implemented in the real world.

 

If you’re interested in a closer look at upcoming features, our Insiders programme is where testing opportunities for updates coming later this year are shared first. We’ve already seen some fantastic discussions around Desktop Mode. Register your interest here to stay ahead of the next updates and share your feedback directly with the team.

3 replies

Moombas
Level 4.4: KitKat
June 17, 2026

Let’s see how it goes with the implementations in the EMM/MDMs regarding the options to disable Gemini on work devices. The past showed often that we were kept out of scope quite often when new features arrive on new Android versions for customers.

Michel
Level: 4.1: Jelly bean
June 17, 2026

Lets hope that they see the importance of this! 

Lizzie
Community Manager
June 18, 2026

Thanks ​@Moombas and ​@Michel for your thoughts on this. 

 

Just to check are you talking specifically about having specific controls for Gemini features on devices or enterprise use cases in general? 

 

It would be great to hear what you would ideally like to see here. 

 

Thanks so much,

Lizzie

Welcome to the Community everyone!
Moombas
Level 4.4: KitKat
June 18, 2026

I meant regarding “IT admins can pre-grant this permission to ensure enterprise tools and local proxies continue to function seamlessly” but also in general as often new functionalities come without admin available settings until requested.

Lizzie
Community Manager
June 18, 2026

Thanks for the additional context here. 

 

Out of interest are there any specific features you’d like to have more control over, that you are particularly struggling to at the moment? 

Welcome to the Community everyone!
Alex_Muc
Level 3.0: Honeycomb
July 15, 2026
  • Certificate Transparency (CT): Android is strengthening defenses against man-in-the-middle attacks. By enforcing CT, the system ensures digital certificates are verified and logged, providing deeper security transparency without impacting Kiosk or locked-down configurations.

 

I looked at the documentation on Certificate Transparency. I'm not entirely sure yet what impact this feature might have.

 

If an app targets Android 17 (API level 37) or higher, CT is automatically enabled. For Android 16, it was available as an option. https://developer.android.com/about/versions/17/behavior-changes-17#ct-default

If developers decide to break from the standard for CT, they must configure this in the Network Security Config. https://developer.android.com/privacy-and-security/security-config#CertificateTransparencySummary

The Android CT Policy describes that not logged certificates or certificates containing insufficient Signed Certificate Timestamps (SCTs) are not considered mis-issued. https://developer.android.com/privacy-and-security/certificate-transparency-policy

 

How Certificate Transparency works is described here: https://certificate.transparency.dev/howctworks/

In theory, a Certificate Authority additionally communicates with log servers. During the certificate request a precertificate is submitted there, and the CA receives SCTs (Signed Certificate Timestamps) for the certificate. The SCTs are transmitted during the standard TLS handshake for client connections and the client can verify those.
There are apparently public monitoring servers that can identify suspicious certificates. I assume this data is reported to the monitoring servers via user agents such as Safari or Chrome.

 

As I understand it, CT gives website owners more ways to detect unauthorized certificates.

If certificates without Signed Certificate Timestamps (SCTs) are not considered mis-issued in Android, does this feature help prevent man-in-the-middle attacks on the client, since such attackers would not have SCTs in their own certificates?
I'd like to understand if Android 17 apps might not just verify and report, but reject connections due to the default Certificate Transparency settings. I'm not currently sure whether this could cause problems in the future with own PKIs, where log servers or SCTs for certificates might not be used.

@Rose Do you happen to know the answer to that? 😀 Additional security on the Internet is a good thing. I just want to make sure that communication to internal data center services isn't affected.

Kirk
Community Manager
July 15, 2026

Hey ​@Alex_Muc 

We’ll double check this with internal teams first and get back to you once we receive a response!