Skip to content
Data warehouse ⇄ Developer tools

Azure Synapse Analytics to Google Pubsub integration — real-time, two-way sync

Keep Azure Synapse Analytics and Google Pubsub in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Synapse Analytics and Google Pubsub

Close the gap between analytics and operations: Azure Synapse Analytics holds the record while Google Pubsub runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Azure Synapse Analytics is the central store where teams keep SQL pools, Tables (dedicated SQL pool), External tables, Views for reporting and analysis; Google Pubsub runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Ordering keys, Topics, Subscriptions, Messages produced in Google Pubsub are exactly what analysts want to measure in Azure Synapse Analytics, and the curated rows in Azure Synapse Analytics are what should drive the next action in Google Pubsub. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs SQL pools, Tables (dedicated SQL pool), External tables, Views in Azure Synapse Analytics with Ordering keys, Topics, Subscriptions, Messages in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Load CRM and ERP records into Synapse dedicated SQL pool tables for enterprise reporting.
  • 02 Publish warehouse aggregates (account health scores, LTV) from Synapse back into operational tools like a CRM.
  • 03 Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.
  • 04 Fan out CRM record changes to a topic and let billing, analytics, and notification subscriptions each react without coupling to the source.

Common sync patterns

Keep user and access records aligned

Where Google Pubsub manages users, directory, or access data, those records stay current in Azure Synapse Analytics — and can be provisioned back from it — so ownership and permissions match across both.

Operational data lands in Azure Synapse Analytics for analytics

Records created in Google Pubsub — issues, events, messages, metrics, or user changes — replicate into Azure Synapse Analytics tables as they happen, so reporting runs on current data instead of last night's export.

Warehouse signals reach Google Pubsub

A row scored, flagged, or enriched in Azure Synapse Analytics creates or updates the matching record in Google Pubsub, so the operational tool acts on the same data the analysts already see.

What you can sync between Azure Synapse Analytics and Google Pubsub

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure Synapse Analytics objects Google Pubsub objects How this pairing syncs
Schemas Namespaces that separate staging, integration, and presentation layers. Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Dead-letter topics to Google Pubsub — each maps to any object or custom field on the other side.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. External tables is specific to Azure Synapse Analytics and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side.
Views Curated projections used when downstream tools should not read base tables directly. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Views is specific to Azure Synapse Analytics and Topics to Google Pubsub — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. Materialized views is specific to Azure Synapse Analytics and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side.
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. SQL pools is specific to Azure Synapse Analytics and Messages to Google Pubsub — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics and Google Pubsub

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure Synapse Analytics Google Pubsub Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

DeliveryEach detected change is written to Google Pubsub through its API, with automatic retries and rate-limit backoff.

Google Pubsub Azure Synapse Analytics Sub-second propagation

DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.

DeliveryEach detected change is applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with Azure Synapse Analytics ⇄ Google Pubsub

Connect Azure Synapse Analytics and Google Pubsub for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Google Pubsub connection.

Real-time

Two-way sync

Changes in Azure Synapse Analytics or Google Pubsub instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Synapse Analytics or Google Pubsub data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure Synapse Analytics or Google Pubsub record.

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ Google Pubsub sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Google Pubsub.

How the Azure Synapse Analytics and Google Pubsub connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

Google Pubsub

Integration surface
REST and gRPC (Cloud Pub/Sub API v1)
Authentication
Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
Change detection
Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
Capabilities
read · write · webhooks
Rate limits
Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works

How to connect Azure Synapse Analytics to Google Pubsub — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure Synapse Analytics and Google Pubsub with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Synapse Analytics connected
    Google Pubsub connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics and Google Pubsub objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Synapse Analytics ⇄ Google Pubsub
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Synapse Analytics Google Pubsub
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Synapse Analytics and Google Pubsub integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 353 integrations available for Azure Synapse Analytics and Google Pubsub.

Popular · 4 of 353
All Azure Synapse Analytics integrations All Google Pubsub integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own