Merge pull request #209057 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: huypub

articles/synapse-analytics/database-designer/concepts-lake-database.md

@@ -24,7 +24,7 @@ The new database designer gives you the possibility to create a data model for y
 
 ## Data storage 
 
-Lake databases use a data lake on the Azure Storage account to store the data of the database. The data can be stored in Parquet or CSV format and different settings can be used to optimize the storage. Every lake database uses a linked service to define the location of the root data folder. For every entity, separate folders are created by default within this database folder on the data lake. By default all tables within a lake database use the same format but the formats and location of the data can be changed per entity if that is requested. 
+Lake databases use a data lake on the Azure Storage account to store the data of the database. The data can be stored in Parquet, Delta or CSV format and different settings can be used to optimize the storage. Every lake database uses a linked service to define the location of the root data folder. For every entity, separate folders are created by default within this database folder on the data lake. By default all tables within a lake database use the same format but the formats and location of the data can be changed per entity if that is requested. 
 
 
 ## Database compute

articles/synapse-analytics/security/how-to-set-up-access-control.md

@@ -238,7 +238,9 @@ You can grant access to a **single**, dedicated, SQL pool database. Use these st
     ```sql
     --Create user in the database
     CREATE USER [<[email protected]>] FROM EXTERNAL PROVIDER;
+    -- For Service Principals you would need just the display name and @domain.com is not required
     ```
+    
 
 2. Grant the user a role to access the database:
 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-service-capacity-limits.md

@@ -26,7 +26,7 @@ Maximum values allowed for various components of dedicated SQL pool in Azure Syn
 | Database connection |Maximum Concurrent open sessions |1024<br/><br/>The number of concurrent open sessions will vary based on the selected DWU. DWU1000c and above support a maximum of 1024 open sessions. DWU500c and below, support a maximum concurrent open session limit of 512. Note, there are limits on the number of queries that can execute concurrently. When the concurrency limit is exceeded, the request goes into an internal queue where it waits to be processed. |
 | Database connection |Maximum memory for prepared statements |20 MB |
 | [Workload management](resource-classes-for-workload-management.md) |Maximum concurrent queries |128<br/><br/>  A maximum of 128 concurrent queries will execute and remaining queries will be queued.<br/><br/>The number of concurrent queries can decrease when users are assigned to higher resource classes or when the [data warehouse unit](memory-concurrency-limits.md) setting is lowered. Some queries, like DMV queries, are always allowed to run and do not impact the concurrent query limit. For more information on concurrent query execution, see the [concurrency maximums](memory-concurrency-limits.md) article. |
-| [tempdb](sql-data-warehouse-tables-temporary.md) |Maximum GB |399 GB per DW100c. At DWU1000c, tempdb is sized to 3.99 TB. |
+| [tempdb](sql-data-warehouse-tables-temporary.md) |Maximum GB |399 GB per DW100c. For example, at DWU1000c, tempdb is sized to 3.99 TB. |
 ||||
 
 ## Database objects
@@ -94,4 +94,4 @@ DMV's will reset when a dedicated SQL pool is paused or when it is scaled.
 
 ## Next steps
 
-For recommendations on using Azure Synapse, see the [Cheat Sheet](cheat-sheet.md).
+For recommendations on using Azure Synapse, see the [Cheat Sheet](cheat-sheet.md).

articles/virtual-network/quick-create-portal.md

@@ -233,7 +233,7 @@ For more information about Azure Bastion, see [Azure Bastion](~/articles/bastion
 
 1. Complete the steps in [Connect to myVM1](#connect-to-myvm1), but connect to **myVM2**.
 
-1. Open PowerShell on **myVM2**, enter `ping myvm1`.
+1. Open PowerShell on **myVM2**, enter `ping myVM1`.
 
     You'll receive a successful reply message like this:
 

articles/web-application-firewall/afds/waf-front-door-tuning.md

@@ -15,6 +15,10 @@ ms.custom: devx-track-azurepowershell
 
 The Microsoft-managed Default Rule Set is based on the  [OWASP Core Rule Set (CRS)](https://github.com/SpiderLabs/owasp-modsecurity-crs/tree/v3.1/dev) and includes Microsoft Threat Intelligence Collection rules. It is often expected that WAF rules need to be tuned to suit the specific needs of the application or organization using the WAF. This is commonly achieved by defining rule exclusions, creating custom rules, and even disabling rules that may be causing issues or false positives. There are a few things you can do if requests that should pass through your Web Application Firewall (WAF) are blocked.
 
+> [!Note]
+> 
+> Managed Rule Set is not available for Azure Front Door Standard SKU. For more information about the different tier SKUs, refer to [Feature comparison between tiers](/azure/frontdoor/standard-premium/tier-comparison#feature-comparison-between-tiers)
+
 First, ensure you’ve read the [Front Door WAF overview](afds-overview.md) and the [WAF Policy for Front Door](waf-front-door-create-portal.md) documents. Also, make sure you’ve enabled [WAF monitoring and logging](waf-front-door-monitor.md). These articles explain how the WAF functions, how the WAF rule sets work, and how to access WAF logs.
 
 ## Understanding WAF logs