Unable to enable Apache AGE extension on Azure PostgreSQL Flexible Server (PG 17.6) - InternalServerError

Question

Unable to enable Apache AGE extension on Azure PostgreSQL Flexible Server (PG 17.6) - InternalServerError

Marian Lambert 0

We are trying to enable the Apache AGE extension on an Azure Database for PostgreSQL Flexible Server.

Server details:

PostgreSQL version: 17.6

Tier: General Purpose (D2ds_v5)

Region: West Europe

According to the Azure documentation, AGE (v1.6.0, Preview) is listed as available for PostgreSQL 17.

However, enabling it fails when modifying the server parameters. When we add age to azure.extensions and click Save, the operation fails with an InternalServerError (Microsoft.DBforPostgreSQL/flexibleServers/configurations/write) in the Activity Log.

{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"InternalServerError\",\"message\":\"An unexpected error occured while processing the request. Tracking ID: '...'\"}]}}

We tried the following configurations:

Adding age only to azure.extensions

Adding age only to shared_preload_libraries

Adding age to both parameters

All attempts result in the same failure when saving the configuration.

Example Activity Log entry:

Pilladi Padma Sai Manisha 5,240 Reputation points Microsoft External Staff Moderator

2026-03-11T22:00:56.7533333+00:00
Hi Marian Lambert,
Thankyou for reaching microsoft Q&A!

The InternalServerError (Microsoft.DBforPostgreSQL/flexibleServers/configurations/write) you encountered while enabling the Apache AGE extension on PostgreSQL 17.6 Flexible Server occurs because Apache AGE is currently not supported on PostgreSQL 17.x.

According to the official Azure PostgreSQL extension support matrix, Apache AGE (v1.5.0) is supported only for PostgreSQL versions 13–16. When age is added to azure.extensions or shared_preload_libraries on a PostgreSQL 17 server, the platform validation fails because the extension binaries are not available for that engine version. As a result, the configuration update triggers an InternalServerError during the parameter update process.

For reference: https://learn.microsoft.com/azure/postgresql/azure-ai/generative-ai-age-overview https://techcommunity.microsoft.com/blog/adforpostgresql/introducing-support-for-graph-data-in-azure-database-for-postgresql-preview/4275628

To use Apache AGE, you will need to deploy or migrate to a PostgreSQL 16 Flexible Server, which is the latest version that currently supports this extension. After using PostgreSQL 16, you can configure the parameters:

azure.extensions = age shared_preload_libraries = age

Then create the extension in your database:

CREATE EXTENSION IF NOT EXISTS age CASCADE;

Once configured on PostgreSQL 16, the extension should load successfully and be available for use.

Please let us know if you have any further questions.
Marian Lambert 0 Reputation points

2026-03-12T08:09:50.07+00:00

Hi Pilladi Padma Sai Manisha,

thanks for your response!

I read that Azure Postgres supports AGE extension for PG version 17 according to this documentation: https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-by-engine?pivots=postgresql-17

As AGE is explicitly listed as supported there, I assumed it will work. Can you point me to the docs where it says its not supported for Pg 17?
Pilladi Padma Sai Manisha 5,240 Reputation points Microsoft External Staff Moderator

2026-03-12T22:53:27.78+00:00
Hi Marian Lambert
You are correct that the extensions by engine reference page lists Apache AGE under PostgreSQL 17. However, that page reflects the general extension catalog, and availability can differ based on the current deployment status and supported configuration parameters in Azure Database for PostgreSQL Flexible Server.

At present, the Apache AGE extension is supported up to PostgreSQL 16, and it is not currently enabled for PostgreSQL 17 Flexible Server instances. Because the extension binaries and required dependencies are not yet deployed for PG17 in the service backend, attempting to add age to parameters such as azure.extensions or shared_preload_libraries results in the InternalServerError you observed during the configuration update.

You can review the official documentation describing Apache AGE support and configuration here: https://learn.microsoft.com/en-us/azure/postgresql/azure-ai/generative-ai-age-overview

This page outlines the supported setup and prerequisites for enabling AGE in Azure Database for PostgreSQL.

If you require Apache AGE functionality at this time, the recommended approach is to use PostgreSQL 16 Flexible Server, where the extension is fully supported and can be enabled successfully using:

azure.extensions = age

Once these parameters are saved and the server restarts, the extension can be created in the database using:

CREATE EXTENSION IF NOT EXISTS age CASCADE;

We appreciate you bringing the documentation reference to our attention. If you have any further questions or need assistance validating your configuration, please feel free to let us know.