Merge pull request #220819 from Rodrigossz/main

Update analytical-store-introduction.md

Author: prmerger-automator[bot]

articles/cosmos-db/analytical-store-introduction.md

@@ -327,7 +327,7 @@ Here's a map of all the property data types and their representations in the ana
   * Spark pools in Azure Synapse will represent these columns as `undefined`.
   * SQL serverless pools in Azure Synapse will represent these columns as `NULL`.
 
-##### Using full fidelity schema on Spark
+##### Using full fidelity schema with Spark
 
 Spark will manage each datatype as a column when loading into a `DataFrame`. Let's assume a collection with the documents below.
 
@@ -388,7 +388,7 @@ sql_results = spark.sql("SELECT sum(price.float64),count(*) FROM Pizza where tim
 sql_results.show()
 ```
 
-##### Using full fidelity schema on SQL
+##### Using full fidelity schema with SQL
 
 Considering the same documents of the Spark example above, customers can use the following syntax example:
 
@@ -468,10 +468,13 @@ FROM OPENROWSET('CosmosDB',
 
 It's possible to use full fidelity Schema for API for NoSQL accounts, instead of the default option, by setting the schema type when enabling Synapse Link on an Azure Cosmos DB account for the first time. Here are the considerations about changing the default schema representation type:
 
- * This option is only valid for accounts that **don't** have Synapse Link already enabled.
- * It isn't possible to reset the schema representation type, from well-defined to full fidelity or vice-versa.
- * Currently Azure Cosmso DB for MongoDB isn't compatible with this possibility of changing the schema representation. All MongoDB accounts will always have full fidelity schema representation type.
- * Currently this change can't be made through the Azure portal. All database accounts that have Synapse Link enabled by the Azure portal will have the default schema representation type, well-defined schema.
+* Currently, if you enable Synapse Link in your NoSQL API account using the Azure Portal, it will be enabled as well-defined schema.
+* Currently, if you want to use full fidelity schema with NoSQL or Gremlin API accounts, you have to set it at account level in the same CLI or PowerShell command that will enable Synapse Link at account level.
+* Currently Azure Cosmso DB for MongoDB isn't compatible with this possibility of changing the schema representation. All MongoDB accounts will always have full fidelity schema representation type.
+* It's not possible to reset the schema representation type, from well-defined to full fidelity or vice-versa.
+* Currently, containers schema in analytical store are defined when the container is created, even if Synapse Link has not been enabled in the database account.
+  * Containers or graphs created before Synapse Link was enabled with full fidelity schema at account level will have well-defined schema.
+  * Containers or graphs created after Synapse Link was enabled with full fidelity schema at account level will have full fidelity schema.
 
 The schema representation type decision must be made at the same time that Synapse Link is enabled on the account, using Azure CLI or PowerShell.