Tag Archives: Beta

Beta Channel Update for ChromeOS / ChromeOS Flex

The Beta channel is being updated to OS version 16295.17.0 (Browser version 138.0.7204.22) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:
  1. File a bug

  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

  4. Interested in switching channels? Find out how.

Alon Bajayo

Google ChromeOS

Available in Open Beta: Migrate files from Microsoft SharePoint Online to Google Drive

What’s changing

Beginning today, the Google Workspace Migrate tool can be used to migrate files from Microsoft SharePoint Online to Google Drive. This allows admins to migrate data from SharePoint Online sites, including document libraries, folders, files and associated permissions, helping organizations transition to Google Workspace quickly and easily.

You can start and complete a migration in a few simple steps:

  • Connect to your SharePoint Online account from which you want to copy data.
  • Specify which sites you want to copy data from and which Drive folders should contain the copied data.
  • Specify users and groups whose permissions should be copied.

Example of a running Microsoft SharePoint Online migration



This feature is available in open beta, which means no additional sign-up is required.


Additional details

  • You can migrate data from up to 100 SharePoint Online sites at a time to Shared Drives in Google Drive.
  • You can find comprehensive reporting on migration progress, including site and file counts (migrated/skipped). You can also export migration reports for error investigation and troubleshooting. 
  • Delta updates are available to migrate newly added or updated files.

Getting started

Rollout pace


Availability

Available for Google Workspace:
  • Business Starter, Standard and Plus
  • Enterprise Starter, Standard and Plus
  • Education Fundamentals, Standard and Plus, the Teaching and Learning add-on
  • Essentials Starter, Enterprise Essentials, Enterprise Essentials Plus
  • Nonprofits

Resources


Available in beta: Edit client-side encrypted Microsoft Word files with Google Docs

What’s changing 

Launching in beta, you can now view and edit client-side encrypted Microsoft Word files in Google Docs. Any changes made are saved in the original Word format. This update makes it easy for you to leverage Google Workspace with the tools and formats you already use while preserving confidentiality of your sensitive data with client-side encryption. 


Eligible Google Workspace admins can use this form to request access to the beta. We’ll share more specific instructions once you’re accepted into the beta.

In Google Docs, navigate to File > Open.



Additional details

Note that with this release:
  • You can only view and edit .docx Word file types. Additional Word file types are not supported.
  • The maximum file size is 20MB.
  • As we continue to improve Office editing in encrypted Google Docs, you may encounter incompatibilities for certain features. Some features may not be displayed and may not be editable, but will be preserved in the document and viewable in Microsoft Office.
  • Other features may be lost or altered in the latest version of the file when it is edited in Google Docs. You will see a notification within the document if editing will cause any features to be lost.


Getting started

Rollout pace

  • The feature will be available immediately once you're accepted into the beta.

Availability

Available to Google Workspace 
  • Enterprise Plus
  • Education Standard and Plus
  • Frontline Plus


Available in beta: Edit client-side encrypted Microsoft Word files with Google Docs

What’s changing 

Launching in beta, you can now view and edit client-side encrypted Microsoft Word files in Google Docs. Any changes made are saved in the original Word format. This update makes it easy for you to leverage Google Workspace with the tools and formats you already use while preserving confidentiality of your sensitive data with client-side encryption. 


Eligible Google Workspace admins can use this form to request access to the beta. We’ll share more specific instructions once you’re accepted into the beta.

In Google Docs, navigate to File > Open.



Additional details

Note that with this release:
  • You can only view and edit .docx Word file types. Additional Word file types are not supported.
  • The maximum file size is 20MB.
  • As we continue to improve Office editing in encrypted Google Docs, you may encounter incompatibilities for certain features. Some features may not be displayed and may not be editable, but will be preserved in the document and viewable in Microsoft Office.
  • Other features may be lost or altered in the latest version of the file when it is edited in Google Docs. You will see a notification within the document if editing will cause any features to be lost.


Getting started

Rollout pace

  • The feature will be available immediately once you're accepted into the beta.

Availability

Available to Google Workspace 
  • Enterprise Plus
  • Education Standard and Plus
  • Frontline Plus


Available in beta: Edit client-side encrypted Microsoft Word files with Google Docs

What’s changing 

Launching in beta, you can now view and edit client-side encrypted Microsoft Word files in Google Docs. Any changes made are saved in the original Word format. This update makes it easy for you to leverage Google Workspace with the tools and formats you already use while preserving confidentiality of your sensitive data with client-side encryption. 


Eligible Google Workspace admins can use this form to request access to the beta. We’ll share more specific instructions once you’re accepted into the beta.

In Google Docs, navigate to File > Open.



Additional details

Note that with this release:
  • You can only view and edit .docx Word file types. Additional Word file types are not supported.
  • The maximum file size is 20MB.
  • As we continue to improve Office editing in encrypted Google Docs, you may encounter incompatibilities for certain features. Some features may not be displayed and may not be editable, but will be preserved in the document and viewable in Microsoft Office.
  • Other features may be lost or altered in the latest version of the file when it is edited in Google Docs. You will see a notification within the document if editing will cause any features to be lost.


Getting started

Rollout pace

  • The feature will be available immediately once you're accepted into the beta.

Availability

Available to Google Workspace 
  • Enterprise Plus
  • Education Standard and Plus
  • Frontline Plus


The Fourth Beta of Android 16

Posted by Matthew McCullough – VP of Product Management, Android Developer

Today we're bringing you Android 16 beta 4, the last scheduled update in our Android 16 beta program. Make sure your app or game is ready. It's also the last chance to give us feedback before Android 16 is released.

Android 16 Beta 4

This is our second platform stability release; the developer APIs and all app-facing behaviors are final. Apps targeting Android 16 can be made available in Google Play. Beta 4 includes our latest fixes and optimizations, giving you everything you need to complete your testing. Head over to our Android 16 summary page for a list of the features and behavior changes we've been covering in this series of blog posts, or read on for some of the top changes of which you should be aware.

Android 16 Release timeline showing Platform Stability milestone in April

Now available on more devices

The Android 16 Beta is now available on handset, tablet, and foldable form factors from partners including Honor, iQOO, Lenovo, OnePlus, OPPO, Realme, vivo, and Xiaomi. With more Android 16 partners and device types, many more users can run your app on the Android 16 Beta.

Android 16 Beta Release Partners: Google Pixel, iQOO, Lenovo, OnePlus, Sharp, Oppo, RealMe, vivo, Xiaomi, and Honor

Get your apps, libraries, tools, and game engines ready!

If you develop an SDK, library, tool, or game engine, it's even more important to prepare any necessary updates now to prevent your downstream app and game developers from being blocked by compatibility issues and allow them to target the latest SDK features. Please let your developers know if updates to your SDK are needed to fully support Android 16.

Testing involves installing your production app or a test app making use of your library or engine using Google Play or other means onto a device or emulator running Android 16 Beta 4. Work through all your app's flows and look for functional or UI issues. Review the behavior changes to focus your testing. Each release of Android contains platform changes that improve privacy, security, and overall user experience, and these changes can affect your apps. Here are several changes to focus on that apply, even if you aren't yet targeting Android 16:

Other changes that will be impactful once your app targets Android 16:

Get your app ready for the future:

    • Local network protection: Consider testing your app with the upcoming Local Network Protection feature. It will give users more control over which apps can access devices on their local network in a future Android major release.

Remember to thoroughly exercise libraries and SDKs that your app is using during your compatibility testing. You may need to update to current SDK versions or reach out to the developer for help if you encounter any issues.

Once you’ve published the Android 16-compatible version of your app, you can start the process to update your app's targetSdkVersion. Review the behavior changes that apply when your app targets Android 16 and use the compatibility framework to help quickly detect issues.

Two Android API releases in 2025

This Beta is for the next major release of Android with a planned launch in Q2 of 2025 and we plan to have another release with new developer APIs in Q4. This Q2 major release will be the only release in 2025 that includes behavior changes that could affect apps. The Q4 minor release will pick up feature updates, optimizations, and bug fixes; like our non-SDK quarterly releases, it will not include any intentional app-breaking behavior changes.

Android 16 2025 SDK release timeline

We'll continue to have quarterly Android releases. The Q1 and Q3 updates provide incremental updates to ensure continuous quality. We’re putting additional energy into working with our device partners to bring the Q2 release to as many devices as possible.

There’s no change to the target API level requirements and the associated dates for apps in Google Play; our plans are for one annual requirement each year, tied to the major API level.

Get started with Android 16

You can enroll any supported Pixel device to get this and future Android Beta updates over-the-air. If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. If you are currently on Android 16 Beta 3 or are already in the Android Beta program, you will be offered an over-the-air update to Beta 4.

While the API and behaviors are final and we are very close to release, we'd still like you to report issues on the feedback page. The earlier we get your feedback, the better chance we'll be able to address it in this or a future release.

For the best development experience with Android 16, we recommend that you use the latest Canary build of Android Studio Narwhal. Once you’re set up, here are some of the things you should do:

    • Compile against the new SDK, test in CI environments, and report any issues in our tracker on the feedback page.

We’ll update the beta system images and SDK regularly throughout the Android 16 release cycle. Once you’ve installed a beta build, you’ll automatically get future updates over-the-air for all later previews and Betas.

For complete information on Android 16 please visit the Android 16 developer site.

More options for exporting your Google Workspace data are available in open beta

What’s changing

Beginning today, Admins can choose from several options when exporting their organization’s data (also known as ‘takeout’). Specifically, they will be able to:

  • Export data from all or multiple services, such as Gmail, Chat, or Drive.
  • Export Drive data based on existing Drive labels
  • Export data from within a specific date range
  • Export data from selected shared drives


Exporting data for specific services

Exporting data based on specific Shared Drives

Exporting data based on specific or custom date range

Exporting data based on specific Drive labels







This update is available in open beta, which means no additional sign-up is required.


Who’s impacted

Admins

Why it’s important

In 2022, we introduced the ability for admins to export user generated content by organizational unit (OU) or group, and prior to that update, data export was limited to a customer’s full set of user generated content. With this update, we continue to give our customers more flexibility and specificity over the data they export, which is important as business and compliance needs evolve.

Getting started


Rollout pace


Availability

Resources


More options for exporting your Google Workspace data are available in open beta

What’s changing

Beginning today, Admins can choose from several options when exporting their organization’s data (also known as ‘takeout’). Specifically, they will be able to:

  • Export data from all or multiple services, such as Gmail, Chat, or Drive.
  • Export Drive data based on existing Drive labels
  • Export data from within a specific date range
  • Export data from selected shared drives


Exporting data for specific services

Exporting data based on specific Shared Drives

Exporting data based on specific or custom date range

Exporting data based on specific Drive labels







This update is available in open beta, which means no additional sign-up is required.


Who’s impacted

Admins

Why it’s important

In 2022, we introduced the ability for admins to export user generated content by organizational unit (OU) or group, and prior to that update, data export was limited to a customer’s full set of user generated content. With this update, we continue to give our customers more flexibility and specificity over the data they export, which is important as business and compliance needs evolve.

Getting started


Rollout pace


Availability

Resources


Beta update: Data loss prevention rules based on classification labels are now applied instantly in Gmail on the web

What’s changing

In November 2024, we announced an open beta for data classification labels in Gmail. To further enhance the experience, we’re pleased to announce that auto-classification labeling with data loss prevention (DLP) rules and actions triggered by classification labels detected in the message will now be applied instantly when using Gmail on the web. Previously, users were informed of any implications after messages left the inbox. With this update, the feedback is instant, providing the opportunity to educate users on why their message is classified, blocked or quarantined, and how to remedy the issue to keep their email communications flowing. 

With this new functionality, and with this feature still in an open beta period, we strongly encourage you to continue providing feedback so we can optimize the feature for general availability. You can also use the form to sign-up for feedback sessions with the Google user research team to provide more detailed feedback.




Who’s impacted

Admins and end users

Why it matters
Google Workspace's expansion of data classification labels to Gmail gives admins the ability to mitigate data exfiltration and gain a deeper understanding of shared data based on information type and sensitivity level to apply data protection policies appropriately. Some ways you can use Data Protection Rules with Classification Labels are:

    • Prevent messages based on a specific classification (e.g. Confidential, Internal, NTK) from being accidentally shared with unauthorized users.
      • You can create a rule with specific label(s) as a condition and choose an action to trigger when a message is sent:
        • Warn: users will see a notification that their message may contain sensitive information, helping to prevent accidental sharing. Note that this action does not block the message from being sent.
        • Block: users will be notified that their message will not be sent unless the label is changed or removed (if data organization policy allows).
        • You can also create a rule in a way that allows for sharing labeled messages only if confidential mode is enabled for the message.

    • Enforce classification on every message or specific messages
      • You can create a rule that warns users or blocks the message if a specific classification label is not found in the message. This can help educate users and drive adoption of your organization’s data classification policy among users.
    • Automatically apply classification labels messages if specific information types are found in the message
      • You can create a rule to automatically apply a specific classification label if certain criteria is met. For example, credit card information or medical information are contained within the email. 
      • You can also configure the rule to allow users to modify the label to a more appropriate one based on the situation and data classification policy of your organization.
    For more detailed information, please refer to our beta announcement as well as our Help Center.


    Additional details

    At this time, this update is only supported when using Gmail on the web. Stay tuned for further updates about instantaneous support in Gmail iOS and Android clients.

    Getting started

    Rollout pace

    Availability

    The Label Manager and manual classification is available to Google Workspace:
    • Frontline Starter and Standard
    • Business Standard and Plus
    • Enterprise Standard and Plus
    • Education Standard and Education Plus
    • Essentials, Enterprise Essentials, and Enterprise Essentials Plus


    Data loss prevention rules with labels as a condition or labels as an action are available to:
    • Enterprise Standard and Plus
    • Education Fundamentals, Standard, Plus, and the Teaching & Learning Upgrade
    • Frontline Standard
    • Cloud Identity Premium (with a Workspace Edition that includes Gmail)

    Resources



    Available in beta: Convert your client-side encrypted documents after a Vault or Takeout export

    What’s changing 

    After a Vault or Data export (takeout), admins can now convert their exported client-side encrypted documents to Word files. This allows organizations to maintain ownership over, access to, and analysis of sensitive data in a portable format even after it has been exported from Google Workspace. 


    Eligible Google Workspace admins can use this form to request access to the beta. We’ll share more specific instructions once you’re accepted into the beta.



    Getting started

    • Admins: Client-side encryption can be enabled at the domain, OU, and Group levels (Admin console > Data > Compliance > Client-side encryption). Visit our Help Center to learn more about client-side encryption.

    Rollout pace

    • The feature will be available immediately once you're accepted into the beta.

    Availability

    • Available to Google Workspace Enterprise Plus, Education Standard and Education Plus customers.

    Resources