Functionality differences for geodatabases in Azure Database for PostgreSQL

Geodatabases in Microsoft Azure Database for PostgreSQL behave similarly to geodatabases in PostgreSQL with the following exceptions:

• You must use either the PostGIS geometry or geography data type for the spatial fields in your feature classes; ST_Geometry storage is not supported.
• The geodatabase administrator cannot drop client connections.
• You cannot use the Create Database User geoprocessing tool to add users to the geodatabase.