Merge pull request #215931 from gmndrg/main

Update Table projection requirements

Author: prmerger-automator[bot]

articles/search/knowledge-store-projection-overview.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 10/15/2021
+ms.date: 10/25/2022
 ---
 
 # Knowledge store "projections" in Azure Cognitive Search
@@ -166,9 +166,11 @@ Recall that projections are exclusive to knowledge stores, and are not used to s
 
 1. Check your results in Azure Storage. On subsequent runs, avoid naming collisions by deleting objects in Azure Storage or changing project names in the skillset.
 
+1. If you are using [Table projections](knowledge-store-projections-examples.md#define-a-table-projection) check [Understanding the Table Service data model](/rest/api/storageservices/Understanding-the-Table-Service-Data-Model) and [Scalability and performance targets for Table storage](/azure/storage/tables/scalability-targets) to make sure your data requirements are within Table storage documented limits.
+
 ## Next steps
 
 Review syntax and examples for each projection type.
 
 > [!div class="nextstepaction"]
-> [Define projections in a knowledge store](knowledge-store-projections-examples.md)
+> [Define projections in a knowledge store](knowledge-store-projections-examples.md)