Skip to content
Hybrid cloud diagram with an on-premises data centre, private circuit, cloud gateway and restricted finance zone on a card over a photo.

Hybrid Cloud Architecture

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

Staff sign in through cloud identity, which syncs users and groups one way from the on-premises directory. Traffic between the data centre and the cloud crosses a private circuit that ends at the cloud gateway, with a VPN as backup. The finance database replicates encrypted changes to a read replica in the restricted cloud zone. Cloud applications read and write only that replica, and encryption keys held in the restricted zone unwrap the data keys it uses. Standard workloads call on-premises services through the gateway when needed.

The design point is data residency by sensitivity. Regulated finance data is stored in only two places, the on-premises database and the cloud replica, and standard services stay out of the restricted zone. The private circuit is the normal path, and the VPN carries traffic only while the circuit is down. Directory sync runs one way, so the on-premises directory stays the source of truth. To adapt it, change the regions and address ranges, and keep the restricted and standard zones separate.

Useful for

  • Planning a finance workload that must keep regulated data on premises
  • Connecting a data centre to a cloud region with a private circuit
  • Splitting public web services from regulated data across two zones

What's included

  • A designed cover slide
  • The diagram: 11 components and 8 connections as editable shapes
  • A components table and the 7-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename Staff, Directory services, Edge router and firewall and the other boxes inside On-premises data centre to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 7-step data flow and the 8-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download hybrid-cloud-architecture-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

Why use a private circuit instead of only a VPN?

A dedicated circuit gives a private path with steadier latency and bandwidth than a VPN over the public internet. The VPN is kept as backup, so connectivity survives a circuit failure, though at lower performance.

Why is directory sync one way?

Syncing only from the on-premises directory to cloud identity keeps the on-premises directory as the single source of truth. Changes made in the cloud cannot write back and alter accounts on premises.

Why use customer-managed keys for a regulated replica?

Customer-managed keys let your team control the key lifecycle, including rotation and revocation. Holding them in the restricted zone means the replica's data keys cannot be unwrapped outside that zone.

  • #infrastructure-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

More infrastructure diagram templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…