Skip to main content
Validate the install in two passes: confirm the workspace components are healthy, then run a query.

Verify the workspace

A healthy deployment shows console-*, envoy-*, xds-*, and the metadata service pods (mds-schema-*, mds-storage-*) all Running. Metadata service pods may take 1–2 minutes to appear after the workspace configuration is created. Confirm the query-router LoadBalancer has an external IP:

Run a query

  1. Open the Console at your configured hostname (https://<CONSOLE_HOSTNAME>).
  2. In the SQL Editor, select your cluster and a catalog.
  3. Run a simple query against a table you can see:
If results return, your Azure In-VPC deployment is working end to end.

If something fails

See Troubleshooting for pods stuck pending, image pull errors, the load balancer not getting an external IP, Workload Identity annotation issues, and stuck namespace termination.

Next steps

Keep going across e6data

Connect your tools

Python, JDBC, PostgreSQL protocol, Tableau, Power BI and notebooks.

Control who sees what

Catalog access control, column masking and row filters.

Add live data

Stream Kafka, CDC and HTTP data into Iceberg tables with Ingest Engine.
Last modified on September 29, 2026