Merge pull request #313998 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/cost-management-billing/dataset-schema/cost-usage-details-mca.md

@@ -74,7 +74,7 @@ ms.author: vikdesai
 | 57 |term|Displays the term for the validity of the offer. For example: For reserved instances, it displays 12 months as the Term. For one-time purchases or recurring purchases, Term is one month (SaaS, Marketplace Support). Not applicable for Azure consumption.|
 | 58 |reservationId|Unique identifier for the purchased reservation instance.|
 | 59 |reservationName|Name of the purchased reservation instance.|
-| 60 |PricingModel|Identifier that indicates how the meter is priced. (Values: `On Demand`, `Reservation`, `Spot`, and `SavingsPlan`)|
+| 60 |pricingModel|Identifier that indicates how the meter is priced. (Values: `On Demand`, `Reservation`, `Spot`, and `SavingsPlan`)|
 | 61 |unitPrice|The price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (PayG price column) for your contract. For more information, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details).|
 | 62 |costAllocationRuleName|Name of the Cost Allocation rule that's applicable to the record.|
 | 63 |benefitId| Unique identifier for the purchased savings plan instance. |
@@ -346,4 +346,4 @@ ms.author: vikdesai
 | 57 |Term|Displays the term for the validity of the offer. For example: For reserved instances, it displays 12 months as the Term. For one-time purchases or recurring purchases, Term is one month (SaaS, Marketplace Support). Not applicable for Azure consumption.|
 | 58 |ReservationId|Unique identifier for the purchased reservation instance.|
 | 59 |ReservationName|Name of the purchased reservation instance.|
-| 60 |UnitPrice|The price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (PayG price column) for your contract. For more information, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details).|
+| 60 |UnitPrice|The price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (PayG price column) for your contract. For more information, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details).|

articles/synapse-analytics/metadata/overview.md

@@ -16,6 +16,10 @@ Azure Synapse Analytics allows the different workspace computational engines to
 
 The sharing supports the so-called modern data warehouse pattern and gives the workspace SQL engines access to databases and tables created with Spark. It also allows the SQL engines to create their own objects that aren't being shared with the other engines.
 
+> [!IMPORTANT]
+> Tables created in Spark with more than 1,024 columns may appear in Object Explorer but can't be queried from the serverless SQL pool due to incomplete metadata synchronization.
+>
+> **Workaround**: Avoid creating Spark tables with more than 1,024 columns if they need to be queried from the serverless SQL pool. Redesign the schema and recreate the table.
 ## Support the modern data warehouse
 
 The shared metadata model supports the modern data warehouse pattern in the following way: