Edit

Limitations of Azure Arc-enabled PostgreSQL

  • Article

This article describes limitations of Azure Arc-enabled PostgreSQL.

Note

As a preview feature, the technology presented in this article is subject to Supplemental Terms of Use for Microsoft Azure Previews.

The latest updates are available in the release notes.

High availability

Configuring high availability to recover from infrastructure failures isn't yet available.

Monitoring

Currently, local monitoring with Grafana is only available for the default postgres database. Metrics dashboards for user created databases will be empty.

Configuration

System configurations that are stored in postgresql.auto.conf are backed up when a base backup is created. This means that changes made after the last base backup, will not be present in a restored server until a new base backup is taken to capture those changes.

Roles and responsibilities

The roles and responsibilities between Microsoft and its customers differ between Azure managed services (Platform As A Service or PaaS) and Azure hybrid (like Azure Arc-enabled PostgreSQL).

Frequently asked questions

The table below summarizes answers to frequently asked questions regarding support roles and responsibilities.

Question Azure Platform As A Service (PaaS) Azure Arc hybrid services
Who provides the infrastructure? Microsoft Customer
Who provides the software?* Microsoft Microsoft
Who does the operations? Microsoft Customer
Does Microsoft provide SLAs? Yes No
Who’s in charge of SLAs? Microsoft Customer

* Azure services

Why doesn't Microsoft provide SLAs on Azure Arc hybrid services? Because with a hybrid service, you or your provider owns the infrastructure.

Related content