Cloud migration is top of mind for most companies with SAP applications. While the advantages of the cloud for SAP customers is generally understood, the move itself can be complicated and disruptive. So what actually are the business benefits and cost savings? How long will it take to recoup such an investment? Two recently published reports from Forrester and IDC can help to quantify the benefits and ROI. 

Getting answers to the million-dollar questions
Forrester and IDC bring different methodologies to the table; they asked somewhat different questions and used different models to calculate their financial KPIs. This allows you to get two different points of view on the same basic questions about value, risk, and ROI.

As it turns out, both reports found that customers who migrate their SAP environments to Google Cloud see an impressive return on their investments. From uptime and infrastructure to efficiency and productivity—both Forrester and IDC identified major benefits to companies that have made the move to Google Cloud.

Let’s walk through some of the highlights from both reports.

Forrester’s TEI model spotlights the power of uptime improvements
Based on in-depth conversations and quantitative research with six companies, here are the key findings from the Forrester Total Economic Impact (TEI) study for companies running SAP systems on Google Cloud: 

• Direct cost savings. When they compare cloud subscription and related costs to what they spent on legacy systems and infrastructure, most IT leaders expect a cloud migration to deliver up-front savings. But according to Forrester, the companies interviewed reported average savings of more than $3 million a year, including eliminated hardware purchases, right-sized software licensing, staffing efficiencies, and other operational cost savings.

• Dramatically improved uptime. Customers told Forrester that migrating SAP to Google Cloud pretty much eliminates downtime—planned or unplanned—as a significant IT concern. According to Forrester, companies realized an average of $1.5 million in savings per year by avoiding the revenue and user productivity losses that had once been a fact of life for their IT teams.
• Significant efficiency gains. Because Google Cloud works to mitigate performance bottlenecks, infrastructure mishaps, network delays and more, the companies Forrester interviewed reported a yearly average of $500,000 in productivity gains for SAP business users and frontline workers.

Companies also reported an annual average of $500,000 in additional IT efficiency gains after migrating SAP to Google Cloud. This quantifies what happens when IT practitioners no longer have to deal with the bottlenecks that come with legacy systems, and are able to spend their time on tasks that actually build value and help the business. Based on the Forrester analysis, the companies interviewed could expect average three-year net benefits of about $15.4 million.

“We benefit from any technical innovation in the infrastructure area because Google Cloud is doing that for us,” one customer told Forrester. “So, whenever there’s new hardware available or new processes or whatever, I don’t have to run the specific project to migrate from A to B.” 

IDC finds that good things happen when SAP downtime is reduced 
The IDC report highlights four areas where Google Cloud generates the most value for customers:

1. Cutting infrastructure costs. According to IDC, customers running SAP on Google Cloud spent 31% less on infrastructure each year, or an average of $233,000 less per company. The ability to scale SAP environments dynamically and to keep them right-sized was a major factor; so were the advantages of automated infrastructure monitoring and savings on software licenses once these companies could stop overprovisioning.

2. Giving a team better things to do. IDC found that the infrastructure, database, and security teams of the companies they interviewed reduced the time they need to maintain and manage SAP environments by an average of 66% per year, for a savings of $443,000, per company. As a result, these companies got the equivalent of a major staff expansion from their SAP migrations—giving them both the staff time and the expertise to focus on far more valuable activities.

3. Limiting unplanned downtime. These companies reported to IDC an average 98% reduction in unplanned downtime. Migrating SAP to Google Cloud significantly reduces the threat of downtime and saves the business an average of nearly $770,000 per year in lost revenue and user productivity. For some firms, the downtime savings topped $1 million per year.

4. Making users more productive. The companies interviewed told IDC that by avoiding downtime and disruptions associated with upgrade and maintenance tasks for their legacy SAP systems, they saved an average of $363,000 annually in user productivity. But there’s an even more interesting under-the-hood stat contributing to these gains: These companies reduced the time required to deploy new SAP compute and storage resources from an average of 8.8 days to 1 hour.

When IDC added up these and other savings associated with running SAP on Google Cloud, it found an average three-year savings of more than $3.5 million and a five-month payback period. 

“We acquired another company, so basically overnight we needed to be able to deal with that increase,” said one customer IDC spoke with. “We doubled our footprint overnight, and we had to take on hundreds of additional employees. We needed a platform that we could easily scale up if we required, and that’s the benefit of running SAP on Google Cloud for us.” 

Explore the reports
There is a lot to think about when considering a move of SAP systems to the cloud. The cloud has many advantages, but migration can seem complicated and tricky; we appreciate that you are looking to understand the full picture. These papers are a great place to start. 

Download the reports—Forrester’s “Total Economic Impact of SAP on Google Cloud” and IDC’s “Business Value of SAP for Google Cloud Environments.” Then, get in touch.

Google Cloud and Synopsys Inc are partnering to help semiconductor companies drive Electronic Design Automation (EDA) innovation in the cloud to accelerate time to market, and lower costs across the entire semiconductor product life cycle. Synopsys is the industry’s largest provider of EDA technology used in the design and verification of integrated circuits, or semiconductor chips. Bringing Synopsys technology onto Google Cloud enables customers to benefit from scalable cloud bursting and complementary licensing models to help them quickly deploy and scale Synopsys’ EDA tools. Semiconductor companies can significantly accelerate chip design and production, increase designer productivity, and empower innovation in power-performance-area optimization.

Google Cloud Platform has enabled high performance computing workloads, such as those used by today’s semiconductor chip designers, to deliver exceptionally fast results and reduce prototyping from years to months. Google Cloud’s HPC services have delivered highly scalable solutions across multiple industries – from scientific research to autonomous vehicle testing and simulation.

EDA software is a large consumer of high performance computing capacity in the cloud. With the release of Synopsys Cloud bring-your-own-cloud (BYOC) solution on Google Cloud, chip designers can now scale their Google Cloud infrastructure with Synopsys’s leading EDA tools under the flexible FlexEDA pay-per-use model and access unlimited EDA software license availability on-demand by the hour or minute.

The Synopsys Cloud BYOC deployment architecture on Google Cloud is enabled through their unique cloud metering service which uses Google Cloud regional MIGs (Managed Instance Groups) for autoscaling and multi-zone deployment. This enables the service to scale up to meet customer workload demands and scale down to optimize costs. Secrets used by Synopsys Cloud are securely stored in Google Secret Manager and usage data is encrypted using Google Cloud key management, providing customers with a highly secure design environment.

Synopsys Cloud also leverages Google Cloud’s Ops Agent and Operations Suite Dashboards are used to show metric data, alerting policies, and log entries, providing customers with detailed analytics visibility to make better chip design project lifecycle management decisions. The Synopsys Cloud BYOC solution has been validated with EDA workloads scaling out to thousands of cores on Google Cloud, using Google Filestore network file storage during validation to provide the highest throughput performance.

Vikram Bhatia, Head, Synopsys Cloud Product Management, Synopsys said, “With the release of Synopsys Cloud BYOC solution on Google Cloud, we are transforming the way our mutual semiconductor customers can design the chips of the future. Google Cloud has been leading the innovation wave for semiconductors in the cloud and we are excited about being an early adopter in leveraging those innovations for our unique EDA offerings on the cloud.” Customers can evaluate a full featured Synopsys Cloud BYOC environment on Google Cloud for free by signing up at: synopsys.com/cloud.

“Combined with GCP’s unique platform services for AI, security, and shared storage, the Synopsys Cloud BYOC solution creates a compelling package for semiconductor designers who will create the next generation of chips for the world’s insatiable needs” says Simon Floyd, Industry Director, Manufacturing & Transportation, Google Cloud.

Google Cloud provides everything you need, including free Google Cloud credits to get you up and running. Click here to learn more about Semiconductors on Google Cloud.

New locations in Eventarc

Back in August, we announced more Eventarc locations (17 new regions, as well as 6 new dual-region and multi-region locations to be precise). This takes the total number of locations in Eventarc to more than 30. You can see the full list in the Eventarc locations page or by running gcloud eventarc locations list . 

What does location mean in Eventarc?

An Eventarc location usually refers to the single region that the Eventarc trigger gets created in. However, depending on the trigger type, the location can be more than a single region:

• Pub/Sub triggers only support single-region locations.
• Cloud Storage triggers support single-region, dual-region, and multi-region locations.
• Cloud Audit Logs triggers support single-region locations and the special global region.

Before looking into trigger location in more detail, let’s look at other locations relevant in Eventarc.

What other locations are relevant in Eventarc?

Triggers connect event sources to event targets:

Each event source, event target, and trigger has its own location. Sometimes, these locations have to match and sometimes they can be different.  

Here’s an example of a trigger connecting Cloud Storage events from a bucket in the europe-west1 region to a Cloud Run service in the us-central1 region with a trigger located in the europe-west1 region:

  gcloud eventarc triggers create trigger-storage \
  --destination-run-service=hello \
  --destination-run-region=us-central1 \
  --location=europe-west1 \
  --event-filters="type=google.cloud.storage.object.v1.finalized" \
  --event-filters="bucket=my-bucket-in-europe-west1-region" \
  --service-account=$PROJECT_NUMBER-compute@developer.gserviceaccount.com

In many cases, you don’t have control over the location of the event source. In the example above, the Cloud Storage bucket is in the europe-west1 region. That’s the location that you need to work with and it has implications for the trigger location (which I’ll get to later). 

The location of the event target is the region of the service where you want the events to go. You get to choose this from one of the supported regions when you deploy your Cloud Run service. You typically want this to be in the same region as your event source for latency and data locality reasons (but this is not strictly a requirement). In the example above, the event source (bucket) is in europe-west1 but the event target (Cloud Run service) is in  us-central1 as specified by the --destination-run-region flag. 

The location of the trigger is dictated by the event source location, but the trigger type also comes into play. It is specified by the –location flag. Let’s take a look at the trigger location for each trigger type in more detail.

Location in Pub/Sub triggers

In a Pub/Sub trigger, you connect a Pub/Sub topic to an event target. Pub/Sub topics are global and not tied to a single region. However, when you create a Pub/Sub trigger, you need to specify a region for it (because Eventarc triggers need to live in a region) with the --location flag as follows:

  gcloud eventarc triggers create trigger-pubsub \
  --destination-run-service=hello \
  --destination-run-region=us-central1 \
  --location=us-central1 \
  --event-filters="type=google.cloud.pubsub.topic.v1.messagePublished" \
  --transport-topic=projects/your-projectid/topics/your-topic

By specifying a location, Eventarc automatically configures the geofencing feature in Pub/Sub such that events only persist in the specified location. As I noted above, you typically want to (but are not required to) choose the same region for the trigger and the Cloud Run service for lower latency and data locality. You can also use regional Pub/Sub service endpoints to publish to the topic to ensure that all of the data stays in a single region. 

Location in Cloud Storage triggers

In a Cloud Storage trigger, you connect a Cloud Storage bucket to an event target. A Cloud Storage bucket can be in a single-region (e.g. europe-west1), dual-region (e.g. eur4), or multi-region (e.g. eu) location. The location of the bucket dictates the location of the trigger and they have to match. The earlier trigger example was for a bucket in the  europe-west1 single-region location. Here’s another trigger connecting Cloud Storage events from a bucket in the eu multi-region location. Notice how the location flag matches the bucket region:

  gcloud eventarc triggers create trigger-storage \
  --destination-run-service=hello \
  --destination-run-region=us-central1 \
  --location=eu \
  --event-filters="type=google.cloud.storage.object.v1.finalized" \
  --event-filters="bucket=my-bucket-in-eu-multi-region" \
  --service-account=$PROJECT_NUMBER-compute@developer.gserviceaccount.com

If the bucket region and the trigger region do not match, you’ll see an error:

  ERROR: (gcloud.eventarc.triggers.create) INVALID_ARGUMENT: The request was invalid: Bucket "my-bucket-in-eu-multi-region" location "eu" does not match trigger location "europe-west1". Try again by creating the trigger in "eu".

Location in Cloud Audit Logs triggers

In a Cloud Audit Logs trigger, you connect any event source that emits Audit Logs to an event target. The location of the event source will dictate the trigger location. This is typically a single region but there is a special global region that’s necessary in some cases. 

For example, if you want to read Cloud Storage events from a bucket in the europe-west1 region with an Audit Logs trigger, you will create the trigger with the same location. Note that this will match all buckets in the europe-west1 region as there’s no filter by bucket in Audit Logs:

  gcloud eventarc triggers create trigger-auditlog \
  --destination-run-service=hello \
  --destination-run-region=us-central1 \
  --location=europe-west1 \
  --event-filters="type=google.cloud.audit.log.v1.written" \
  --event-filters="serviceName=storage.googleapis.com" \
  --event-filters="methodName=storage.objects.create" \
  --service-account=$PROJECT_NUMBER-compute@developer.gserviceaccount.com

On the other hand, if you want to match a dual-region or a multi-region bucket such as eu, you will create the trigger with the global location as Audit Logs triggers only support a single or global region. Note that this will match all buckets in all regions globally:

  gcloud eventarc triggers create trigger-storage \
  --destination-run-service=hello \
  --destination-run-region=us-central1 \
  --location=global \
  --event-filters="type=google.cloud.storage.object.v1.finalized" \
  --event-filters="bucket=my-bucket-in-europe-west1-region" \
  --service-account=$PROJECT_NUMBER-compute@developer.gserviceaccount.com

As you can see from this example, if you want to read Cloud Storage events, the native Cloud Storage trigger is a much better option, but this example illustrates a typical case in which a global Audit Log trigger is necessary. 

That wraps up this closer look at locations in Eventarc. Feel free to reach out to me on Twitter @meteatamel for any questions or feedback.

Google Cloud Results

• Enables accurate allocation of marketing spend to underserved areas
• Supports expansion into international markets
• Helps ensure accurate forecasting of inventory levels
• Improves accuracy of forecasted delivery times by at least 60%

Operating in India since 2011, Rebel Foods has grown from a brick-and-mortar business that provided wraps to customers to a cloud kitchen that delivers cuisine to about one million consumers per month. “We started with the Faasos food brand and now we have scaled up to 10 brands,” says Soumyadeep Barman, Chief Technology Officer at Rebel Foods. “We have doubled our revenue every year from 2014 until now, and we operate kitchens in 15 cities across India. Each kitchen offers at least seven of our brands to customers.”

Barman attributes Rebel Foods’ success to the fact that it is a full stack company. “We procure, we have our own inventory, we prepare the food, we deliver the food to customers, and we make sure customers are delighted every time they order,” he says.

The rapid emergence and adoption of mobile technologies and services in India gave the business its opportunity to expand quickly. “The boom in applications and the web really got going in India in about 2014,” Barman says. “The subsequent emergence of smart devices and mobile applications opened up new markets, including older people who had not really used a computer until then.”

The business released the first iteration of its mobile application in 2013 on servers in an on-premises data center. “However, we experienced breakages because our infrastructure was not scalable or dependable enough, and we decided to move to another solution,” Barman says.

Google Maps Platform delivers opportunity

In 2014, Rebel Foods decided to move to the cloud and selected Google Cloud because of its stability, reliability, and scalability.

The business also wanted to take advantage of the opportunities Google Maps Platform presented to improve the efficiency and effectiveness of its delivery service. With 175 kitchens delivering to about 900 locations across India, Rebel Foods needs to provide estimated delivery times and meet delivery guarantees, while accounting for all the factors that might affect how quickly a rider can reach a customer’s doorstep.

The business turned to Google Maps Platform Premier Partner Searce for support in leveraging Google Maps Platform APIs to deliver a compelling customer experience and improve its efficiency. “Searce helped us determine the Google Maps Platform APIs we should use across our mobile applications and websites, and how many licenses we needed to conduct activities like calculating estimated delivery time and reviewing order heat maps,” Barman says. “Thanks to the firm’s support, Google Maps Platform APIs were a game changer for us.”

Mapping customer locations

Customers accurately pinpoint their location in a map through functionality made available through the Places API and Geocoding API, in conjunction with the JavaScript API. Drivers use the Directions API to identify the quickest route to customers.

Customers can also track the progress of delivery and estimated time of arrival using an Android or iOS application, or the brand websites.

Deploying Google Maps Platform APIs enabled Rebel Foods to improve by up to 60 percent the accuracy of forecasted delivery times. “Rather than tell a customer we can reach them in, say, 45 minutes, based on previous experience and gut feeling, we can retrieve an accurate traffic scenario and calculate delivery times based on traffic congestion levels and likely average speeds,” Barman says

Allocating budget effectively

Google Maps Platform also allows the business to combine mapping of customers to individual kitchens and to how often customers place orders – and for what value. This enabled the business to understand where to allocate budget for local marketing to stimulate demand in underserved areas.

Google Maps Platform technologies complement Rebel Foods’ use of Google Cloud Platform services such as the BigQuery analytics data warehouse to process data used to forecast inventory levels and provide recommendations to customers based on previous usage and behaviors. The business also runs its key applications in Kubernetes Engine to achieve cost-effective scalability, so it can expand to international markets.

“We are targeting growth into a range of international markets in January 2019, including Australia, the Middle East, and Southeast Asia,” Barman says. “With the user data and experience provided by Google Maps Platform in particular, we are poised for success.”

In June, we shared our vision for navigating the future of hybrid work with a single connected experience in Google Workspace. Now, as many of our customers begin to embark on their own hybrid journeys, I wanted to share how we’re helping them bridge the gaps in this new way of working.

A dedicated place for team collaboration: Spaces are now live

Spaces are the central place for team collaboration in Workspace and starting today, Spaces are live for all users. Spaces are unique in that they are tightly integrated with Google Workspace tools like Calendar, Drive, Docs, Sheets, Slides, Meet, and Tasks, providing a better way for people to engage in topic-based discussions, share knowledge and ideas, move projects forward and build communities and team culture.

We hear from our customers that they’re continuing to work across a broad range of locations and working hours, and that Spaces can be a central hub for collaboration, both in real time and asynchronously. Instead of starting an email chain or scheduling a video meeting, teams can come together directly in a Space to move projects and topics along, whether it’s a team of 10 for “2022 Roadmap Planning” or a team of 1,000 for the “Company-wide All-Hands.”

With Spaces, teams can share ideas, collaborate on documents, and manage tasks from a single place. Because all their work is preserved for future reference, team members can easily jump in and contribute at a time that works best for them, seeing a full history of the conversations, context, and content along the way. Using Spaces has already helped my own team, which is spread across time zones and varied in its working styles. It’s been helpful to rely on Spaces to retain and structure foundational knowledge, whether it’s for onboarding a new teammate or preserving context when someone moves to a new role.

We’re just getting started with Spaces and I’m excited to share a little more about where we’ll take it next. 

In the coming months, our users will see: 

• Streamlined navigation: A flexible user interface helps users easily access their inbox, chats, Spaces and meetings—all from a single location—so they can stay on top of everything that’s important.
• Discoverable Spaces: Spaces and their content can be made discoverable to all members of an organization, so other people can find and join the conversation. Administrators can also set discoverability as the default for their organization.
• Enhanced search: Allows users to easily find content from within and across Spaces, or even discover new Spaces to join. “Search everything” in Spaces opens up powerful new collaboration possibilities and makes it easier to access the team’s collective knowledge base.
• In-line topic threading: The ability to reply to any message within a Space fuels deeper discussions and collaboration across teams and organizations.
• Robust security & admin features: Tools for content moderation, managing Spaces, and establishing the right rules for healthy communication across domains and companies.

Making meetings more hybrid friendly

Spaces will play an important role in laying the groundwork for meetings and, in some cases, reduce the number of meetings a team needs to gain alignment. Having a dedicated space for asynchronous collaboration, with access to all the right content and context, will help teams be more deliberate about scheduling meetings. This is top of mind for us and many of our customers given the rise in meeting fatigue over the last 18 months. But when having a meeting genuinely feels worthwhile, the experience of transitioning into (and out of) it from different collaboration touchpoints should be seamless. 

Over the past few months, in collaboration with many customers and across teams within Google, we developed a handbook for navigating hybrid work that includes best-practice blueprints for the five most common hybrid meeting types. Because meetings are a foundational piece of hybrid work, our goal is to make them as productive, immersive and inclusive as possible. 

Scheduling meetings that work across the entire team

With hybrid work, many teams—my own included—have locations and working hours that can change daily. When many of us were together in the office, we might have tended to schedule meetings at a time that favored the “in-office majority,” but now it’s especially important to schedule meetings that scale across the entire distributed team. 

Now, beyond indicating their virtual or physical presence when accepting meeting invites, team members can set their location for each work day in Calendar. When combined, these capabilities allow meeting organizers and on-site support teams to plan for the right mix of in-person and virtual attendance. They can also provide greater visibility and help set expectations across hybrid teams.

Making meetings more spontaneous

Remember when you’d casually bump into a colleague in the office hallway or a break room and start a conversation that sparked new ideas? That’s perhaps the thing I’m looking forward to most as more of my team plan their part-time return to the office. These casual encounters were always a great way to build relationships and learn about topics that might not come up in structured meetings. To help enable these spontaneous connections when teammates aren’t in the office together, we’re bringing Google Meet calling to Workspace.

Google Meet calling is a seamless experience of initiating a video or audio call between one or more participants, complementing more structured, scheduled video meetings. Our intention is to bring Meet calling to all the natural endpoints in Workspace where you’d initiate an ad-hoc call including chats, people cards, and Spaces, but this will come first to one-to-one chats within the Gmail mobile app. Soon I’ll be able to call members of my team directly from a one-to-one chat. This will ring their device running the Gmail mobile app and send a call chip to our chat on their laptop, so they can easily answer from any device. It’s not quite the same as a spontaneous hallway conversation, but it might be the next best thing in a hybrid setting.

Ensuring collaboration equity in hybrid meetings

How do we ensure that hybrid meetings aren’t two meetings in one, divided between those in-person and those who are remote? Effective hybrid meetings need a unified experience so that the people sitting together in the same room can interact with their remote colleagues seamlessly, without it ever feeling like there are two parallel conversations.

We designed Companion mode in Google Meet to specifically meet this challenge and we’ll start rolling it out to customers in November. With Companion mode I can host or join a meeting from within a conference room using my laptop while leveraging the in-room audio and video—and it all happens without any awkward audio feedback. This functionality lets me share content or see presentations up close on my own device, access the meeting chat and whiteboard, initiate and vote on polls, or post a question in Q&A, just as I would from home. And to ensure that users have greater choice over how they participate in meetings, live-translated captions will be available in Meet and through Companion mode by the end of the year. We’re currently working on translating meetings in English to French, German, Spanish and Portuguese, with many more languages coming in the future.

Expanding choice and flexibility for meeting hardware

While Companion mode keeps people in the room seamlessly connected to their remote colleagues, meeting hardware plays a crucial role in making hybrid meetings feel more immersive and human, with the ability for everyone to be clearly seen and heard. To provide more flexibility and choice on this foundation of how we come together in a hybrid work world, we’re announcing an expanded Google Meet hardware portfolio and interoperability with other conference room solutions.

First, we’re announcing two new all-in-one video conferencing devices to complement our Series One Room Kits. The Series One Desk 27 is an all-in-one 27” device that’s perfect for small shared spaces or your desktop, either in the office or at home. Series One Board 65 is an all-in-one 65” 4K device that can be paired with an optional stand for ultimate configuration flexibility—turning any room or space into a video collaboration hub in minutes. 

Both devices feature collaboration capabilities with the Jamboard app built right in, and each can be used as an external display. While optimized for Google Meet, USB-C connection from your laptop gives you the flexibility to use the meeting app of your choice while leveraging the high-fidelity audio and high-definition video on Series One Desk 27 and Board 65. You can learn more about these devices developed in partnership with Avocor through our on-demand webinar starting at 9 AM PT today.
https://www.youtube.com/embed/BR81EAce5BQ?enablejsapi=1&

We’re also proud to announce new third-party devices coming to the Google Meet hardware ecosystem. Google has certified the Logitech Rally Bar Mini and Rally Bar for Google Meet, which provide complete room solutions for small and mid-sized rooms. You can learn more about these Google Meet-certified products in Logitech’s September 21 webinar. Additionally, the Rayz Rally Pro is a new mobile device speaker dock by Appcessori that will automatically launch Google Meet for video meetings and provide an improved audio experience from your mobile device.

Certified Google Meet hardware ensures high-quality video and audio in meetings and is easy to deploy and manage. You can view our full Google Meet device portfolio and purchase directly from approved resellers by visiting the Google Meet Hardware website. 

While Google Meet customers enjoy a full-featured experience on Meet hardware, we realize they sometimes need to connect with people outside of their video calling network. To enable this, organizations can use Pexip for Google Meet to seamlessly join Meet meetings from the widest range of third-party video conferencing solutions. Today, we’re also announcing support for bidirectional interoperability with devices from Webex by Cisco and Google Meet hardware. Soon you’ll be able to launch a Google Meet meeting on Webex hardware and a Webex meeting on Google Meet hardware. Calling interoperability between Meet and Webex is supported on Series One Board 65, Series One Desk 27, and the rest of the Google Meet hardware portfolio, as well as Webex Room Series, Room Kit Series, Desk Series and Board Series. We expect general availability later this year. You can find more details here. We plan to give Meet users even broader calling interoperability with support for other conferencing services in the near future. 

Navigating hybrid work is a journey

We’re thrilled to bring these new Google Workspace experiences and devices to our customers, but we also realize that navigating hybrid work will be a journey of learning and adaptation for every organization. Two resources we recently developed can help along the way:

• Navigating hybrid work: A Google Workspace handbook
• The newly launched Future of Work site from Google Workspace, where you can keep up with all the ways work is changing.

Bridging the gaps in the emerging hybrid work world will necessarily be a combination of technology, workplace culture, and reimagining the use of physical spaces. But developing a “hybrid-first” mindset starts with the tools people use every day to connect, create, and collaborate, and Google Workspace will continue to play a crucial role in that evolution.