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 20

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:

Marian Lambert 20 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 11,705 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.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-13T20:36:36.21+00:00

Hi Marian Lambert,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Marian Lambert 20 Reputation points

2026-03-16T08:14:26.9733333+00:00

Hi Pilladi Padma Sai Manisha,

thanks for the clarification. Could you please point me to a documentation page where these different support variants or the actually supported versions are listed?

Ideally, either a page that explicitly lists which PostgreSQL versions support which extensions in Azure Database for PostgreSQL Flexible Server, or a section in the documentation that explains that availability can vary depending on deployment status and therefore may not always match the general extension catalog.

Because I am only finding the page that states that age with PG 17 is indeed supported on Azure.

That would help me better understand which versions are guaranteed to be supported in which context.

Thanks!
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-16T19:10:53.6833333+00:00

Hi Marian Lambert,
The primary reference for extension availability in Azure Database for PostgreSQL Flexible Server is the extensions catalog page below, which lists extensions by PostgreSQL engine version: https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-by-engine?pivots=postgresql-17

However, this page represents the general extension catalog. In practice, extension availability can depend on backend enablement and deployment status, which means an extension listed in the catalog may not yet be fully available for all engine versions.

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

At present, the validated and commonly supported configuration for Apache AGE is with PostgreSQL versions 13–16. For PostgreSQL 17, the catalog entry may appear, but backend enablement may still be limited, which can result in the configuration error you observed.

For immediate use of Apache AGE, we recommend PostgreSQL 16 Flexible Server, where the extension is fully supported.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-17T18:59:29.79+00:00

Hi Marian Lambert,

Just checking in did the solution we provided resolve your issue. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Marian Lambert 20 Reputation points

2026-03-18T22:23:48.36+00:00

Hi Pilladi Padma Sai Manisha,

thanks for following up. The issue is not resolved from our side — downgrading to PostgreSQL 16 is not trivial and requires internal justification.The problem is that the only official source I can find explicitly lists AGE as supported for PostgreSQL 17: https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-by-engine?pivots=postgresql-17. We planned around this. Without an official Microsoft source that contradicts it — a documentation page, known issues list, or blog post — I cannot make the case for a downgrade internally.

Could you either point me to such a source, or escalate to the Azure PostgreSQL product team to either fix the backend enablement or correct the documentation?

Thank you!
Manoj Kumar Boyini 19,510 Reputation points Microsoft External Staff Moderator

2026-03-19T12:35:25.07+00:00

Hi Marian Lambert,

I kindly request you to please share the details requested in the private message for further investigation.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-24T22:02:06.54+00:00

Hi Marian Lambert,

Thank you for your patience and for sharing the details.

After checking with our engineering team, the issue is occurring because your PostgreSQL server is currently on an older maintenance version, which is causing the failure when enabling the Apache AGE extension.

You can either wait for the upcoming maintenance rollout in the next 1–2 months, after which the extension should work as expected, or we can schedule a maintenance activity at your preferred time. Please note this would involve approximately 1 hour of downtime.

Kindly let us know how you would like to proceed.

Answer accepted by question author

0 additional answers

Your answer

Marian Lambert 20 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 11,705 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.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-13T20:36:36.21+00:00

Hi Marian Lambert,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Marian Lambert 20 Reputation points

2026-03-16T08:14:26.9733333+00:00

Hi Pilladi Padma Sai Manisha,

thanks for the clarification. Could you please point me to a documentation page where these different support variants or the actually supported versions are listed?

Ideally, either a page that explicitly lists which PostgreSQL versions support which extensions in Azure Database for PostgreSQL Flexible Server, or a section in the documentation that explains that availability can vary depending on deployment status and therefore may not always match the general extension catalog.

Because I am only finding the page that states that age with PG 17 is indeed supported on Azure.

That would help me better understand which versions are guaranteed to be supported in which context.

Thanks!
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-16T19:10:53.6833333+00:00

Hi Marian Lambert,
The primary reference for extension availability in Azure Database for PostgreSQL Flexible Server is the extensions catalog page below, which lists extensions by PostgreSQL engine version: https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-by-engine?pivots=postgresql-17

However, this page represents the general extension catalog. In practice, extension availability can depend on backend enablement and deployment status, which means an extension listed in the catalog may not yet be fully available for all engine versions.

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

At present, the validated and commonly supported configuration for Apache AGE is with PostgreSQL versions 13–16. For PostgreSQL 17, the catalog entry may appear, but backend enablement may still be limited, which can result in the configuration error you observed.

For immediate use of Apache AGE, we recommend PostgreSQL 16 Flexible Server, where the extension is fully supported.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-17T18:59:29.79+00:00

Hi Marian Lambert,

Just checking in did the solution we provided resolve your issue. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Marian Lambert 20 Reputation points

2026-03-18T22:23:48.36+00:00

Hi Pilladi Padma Sai Manisha,

thanks for following up. The issue is not resolved from our side — downgrading to PostgreSQL 16 is not trivial and requires internal justification.The problem is that the only official source I can find explicitly lists AGE as supported for PostgreSQL 17: https://learn.microsoft.com/en-us/azure/postgresql/extensions/concepts-extensions-by-engine?pivots=postgresql-17. We planned around this. Without an official Microsoft source that contradicts it — a documentation page, known issues list, or blog post — I cannot make the case for a downgrade internally.

Could you either point me to such a source, or escalate to the Azure PostgreSQL product team to either fix the backend enablement or correct the documentation?

Thank you!
Manoj Kumar Boyini 19,510 Reputation points Microsoft External Staff Moderator

2026-03-19T12:35:25.07+00:00

Hi Marian Lambert,

I kindly request you to please share the details requested in the private message for further investigation.
Pilladi Padma Sai Manisha 11,705 Reputation points Microsoft External Staff Moderator

2026-03-24T22:02:06.54+00:00

Hi Marian Lambert,

Thank you for your patience and for sharing the details.

After checking with our engineering team, the issue is occurring because your PostgreSQL server is currently on an older maintenance version, which is causing the failure when enabling the Apache AGE extension.

You can either wait for the upcoming maintenance rollout in the next 1–2 months, after which the extension should work as expected, or we can schedule a maintenance activity at your preferred time. Please note this would involve approximately 1 hour of downtime.

Kindly let us know how you would like to proceed.

Answer 1

Hi Marian Lambert,
Thankyou for reaching microsoft Q&A!

Thank you for your patience while this issue was being investigated.

Our backend engineering team has completed the required maintenance activities on the affected PostgreSQL Flexible Server instances. The maintenance was applied successfully, and no further issues are currently observed from the platform side related to extension enablement.

At this point, we kindly request you to reattempt enabling the Apache AGE extension by updating the azure.extensions and/or shared_preload_libraries parameters as per your earlier configuration. Please ensure the settings are saved successfully and, if prompted, allow the server to restart.