Merge pull request #272900 from nachoalonsoportillo/patch-1

Remove limitations section since defect in azure_storage extension is fixed

Author: ttorble

articles/postgresql/flexible-server/concepts-query-store.md

@@ -276,9 +276,6 @@ This function discards all statistics gathered so far by Query Store. It discard
 This function discards all statistics gathered in-memory by Query Store (that is, the data in memory that hasn't been flushed yet to the on disk tables supporting persistence of collected data for Query Store). This function can only be executed by the server admin role (**azure_pg_admin**).
 
 
-## Limitations and known issues
-[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
-
 ### Read-only mode
 When an Azure Database for PostgreSQL - Flexible Server instance is in read-only mode, such as when the `default_transaction_read_only` parameter is set to `on`, or if read-only mode is [automatically enabled due to reaching storage capacity](concepts-limits.md#storage), Query Store does not capture any data.
 

articles/postgresql/flexible-server/concepts-storage-extension.md

@@ -227,10 +227,6 @@ When the Azure Database for PostgreSQL flexible server administrator decides tha
 SELECT * FROM azure_storage.account_user_remove('mystorageaccount', 'support');
 ```
 
-## Limitations and known issues
-
-[!INCLUDE [Note Query Store and Azure Storage compability](includes/note-query-store-azure-storage-compability.md)]
-
 ## Next steps
 
 - If you don't see an extension that you want to use, let us know. Vote for existing requests or create new feedback requests in our [feedback forum](https://aka.ms/pgfeedback).