Overview
What is Azure PostgreSQL Database: Azure Database for PostgreSQL is a fully managed Database-as-a-Service built on the open-source PostgreSQL engine. The current Flexible Server option separates compute and storage, runs PostgreSQL versions 11 through 18 across more than 60 Azure regions, and supports OLTP, analytics, and agentic AI workloads with native pgvector and azure_ai extension support.
How to integrate Azure PostgreSQL Database with Datagrid
Use the Azure PostgreSQL Database integration when Datagrid's AI agents need direct read access to managed PostgreSQL records in Azure. Set up the integration by configuring the connection fields, creating a read-only database user, and then confirming the objects the Datagrid imports for agent processing.
Configure the Azure PostgreSQL connection
Enter the Azure server details in Datagrid, then confirm that Azure networking permits the connection.
Open Datagrid and go to your integration settings.
Select the Azure PostgreSQL Database integration.
Enter the fully qualified host name, for example, servername.postgres.database.azure.com.
Enter the port, database name, username, and password.
Add the client egress IP to your Azure server firewall rules so Azure does not block the connection.
Set the SSL mode to require for Azure PostgreSQL Flexible Server connections.
Save the connection and confirm the import.
Use this connection artifact as the Datagrid-side checklist:
host=servername.postgres.database.azure.com
port=<your PostgreSQL port>
database=<database name>
username=<read-only username>
password=<password>
sslmode=requireCreate a read-only database user
For this integration, Datagrid documents PostgreSQL password authentication. The connection fields are host, port, database name, username, and password. For production, Datagrid recommends a dedicated integration role with SELECT grants. Avoid superuser accounts. Azure supports Microsoft Entra ID and managed identity authentication for other clients through the Entra concepts guide, but Datagrid documents username and password access for this integration.
Use this role and grant pattern. Replace placeholders with your database and schema names:
CREATE ROLE datagrid_reader LOGIN PASSWORD '<strong password>';
GRANT CONNECT ON DATABASE <database_name> TO datagrid_reader;
GRANT USAGE ON SCHEMA <schema_name> TO datagrid_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA <schema_name> TO datagrid_reader;
ALTER DEFAULT PRIVILEGES IN SCHEMA <schema_name>
GRANT SELECT ON TABLES TO datagrid_reader;Confirm imported database objects
Datagrid imports structured database objects from Azure PostgreSQL into agent workflows, including tables, views, materialized views, stored procedures, functions, custom queries, sequences, data types, schemas, and extensions, per the PostgreSQL docs.
Use this object list format to confirm the scope Datagrid should read:
schema=public
objects=tables, views, materialized views, stored procedures, functions, custom queries, sequences, data types, schemas, extensions
access=scoped SELECT grantsUse a custom query when agents only need a defined slice of operational records:
SELECT *
FROM <schema_name>.<table_name>
WHERE updated_at >= CURRENT_DATE - INTERVAL '1 day';After you scope the account and define the SSL and object settings, Datagrid can use Azure PostgreSQL records as a governed source for agent workflows.
Why use Azure PostgreSQL Database with Datagrid
Connecting Azure PostgreSQL to Datagrid turns managed relational data into an execution layer for Datagrid's AI agents. These benefits matter most when project teams need current operational records without manual exports.
Current records drive recurring outputs: Datagrid's AI agents assemble reports and validation results from the latest approved database scope.
Permission boundaries protect production systems: Teams can scope database access to the records Datagrid needs for reporting and validation workflows.
Broad object context expands analysis: Datagrid agents can work from base tables, database views, query logic, and extension-backed data. Flat exports are unnecessary for that analysis.
Cross-system processing combines live sources: Agents combine PostgreSQL records with project files and other connected systems, so analysis draws on both operational data and unstructured files.
Automated data consolidation improves consistency: Datagrid agents sync and consolidate information across sources and scan datasets for inconsistencies and duplicates.
What you can build with Azure PostgreSQL Database Datagrid integration
Project teams use Azure PostgreSQL records in Datagrid for recurring reports, validation, retrieval, and data consolidation.
Automated reporting from live records: Agents can pull production tables and views to generate recurring reports. An operations team can use daily order and status tables to produce a summary without running exports.
Cross-referenced data validation: Agents compare PostgreSQL records against project files or other connected systems and flag mismatches. A team can validate invoice records in a database against source project files.
Knowledge retrieval over structured data: Agents answer questions using imported tables and query results. A database becomes a queryable source for project teams.
Data consolidation across systems: Agents merge PostgreSQL records with data from other integrations and scan for duplicates and inconsistencies. This follows Datagrid's approach to agentic data organization.
Resources and documentation
Access management: Review Azure's least-privilege role guidance for creating a dedicated read-only integration role.
Flexible Server overview: Review the service overview and architecture.
Connection guide: Review connection strings, drivers, and TLS requirements.
TLS overview: Review Azure SSL enforcement and certificate guidance.
Frequently asked questions
What authentication does the Datagrid integration use for Azure PostgreSQL?
Enter the host, port, database name, username, password, and SSL mode in the integration settings.
Which data objects can Datagrid import from Azure PostgreSQL?
Datagrid imports the PostgreSQL object types listed in the Confirm imported database objects subsection.
Why does my connection fail with an SSL error?
Check the SSL mode in the saved integration settings, then verify the host, port, and credentials.
Why am I getting a "no pg_hba.conf entry for host" error?
For public-access servers, add the client egress IP to the server firewall rules, or Azure blocks connections by default. Add the IP range in the Azure portal, as described in the public networking overview.
Similar integrations
MS Fabric: Enables mirroring and OneLake ingestion from Azure PostgreSQL for analytics, CDC, and BI pipelines.
Azure Data Lake Storage: A landing zone for Fabric mirroring and ELT workflows, storing Parquet snapshots and extracted PostgreSQL data.
Azure Blob Storage: Holds unstructured files and extracted project files for RAG, preprocessing, and batch ingestion into PostgreSQL-backed AI workflows.
Databricks: Performs large-scale transformation, feature engineering, and scheduled writes between PostgreSQL and data warehouses for analytics and ML.
Snowflake: An analytical warehouse target for transformed PostgreSQL data and high-performance BI queries.
Google Cloud SQL - PostgreSQL: A cross-cloud managed Postgres peer for migration, multi-cloud replication, and comparative testing of Azure-hosted workloads.