Merge pull request #292695 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/azure-government/documentation-government-csp-list.md

@@ -569,6 +569,7 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[Project Hosts](https://www.projecthosts.com)|
 |[Quiet Professionals, LLC](https://quietprofessionalsllc.com)|
 |[R3, LLC](https://www.r3-it.com/)|
+|[Rackspace Technology](https://www.rackspace.com)|
 |[Red River](https://www.redriver.com)|
 |[RSM US, LLP](https://rsmus.com)|
 |[SAIC](https://www.saic.com)|

articles/iot-hub/iot-hub-devguide-query-language.md

@@ -271,8 +271,8 @@ In routes conditions, the following string functions are supported:
 | UPPER(x) | Returns a string expression after converting lowercase character data to uppercase. |
 | SUBSTRING(string, start [, length]) | Returns part of a string expression starting at the specified character zero-based position and continues to the specified length, or to the end of the string. |
 | INDEX_OF(string, fragment) | Returns the starting position of the first occurrence of the second string expression within the first specified string expression, or -1 if the string isn't found.|
-| STARTSWITH(x, y) | Returns a Boolean indicating whether the first string expression starts with the second. |
-| ENDSWITH(x, y) | Returns a Boolean indicating whether the first string expression ends with the second. |
+| STARTS_WITH(x, y) | Returns a Boolean indicating whether the first string expression starts with the second. |
+| ENDS_WITH(x, y) | Returns a Boolean indicating whether the first string expression ends with the second. |
 | CONTAINS(x,y) | Returns a Boolean indicating whether the first string expression contains the second. |
 
 ## Query examples with the service SDKs

articles/service-bus-messaging/test-locally-with-service-bus-emulator.md

@@ -214,7 +214,7 @@ CONFIG_PATH="<Replace with path to Config.json file>"
 ACCEPT_EULA="N"
 
 # 3. MSSQL_SA_PASSWORD to be filled by user as per policy : https://learn.microsoft.com/sql/relational-databases/security/strong-passwords?view=sql-server-linux-ver16 
-MSSQL_SA_PASSWORD: ""
+MSSQL_SA_PASSWORD=""
 ```
 
 > [!IMPORTANT]

articles/storage/files/understanding-billing.md

@@ -19,7 +19,7 @@ Azure Files has multiple pricing models including provisioned and pay-as-you-go
 
 - **Provisioned billing models**: In a provisioned billing model, the primary costs of the file share are based on the amount of storage, IOPS (input and output operations per second), and throughput you provision when you create or update your file share, regardless of how much you use. Azure Files has two different provisioned models *provisioned v2* and *provisioned v1*.
     - **Provisioned v2**: In the provisioned v2 model, you have the ability to separately provision storage, IOPS, and throughput, although we provide a recommendation for you to help you with first time provisioning.
-    - **Provisioned v1**: In the provisioned v1 model, you provision the amount of storage you need for the share while IOPS and throughput are determined based on how much storage you provision. The provisioned v1 model for Azure Files is only available for SSD file shares.
+    - **Provisioned v1**: In the provisioned v1 model, you provision the amount of storage you need for the share while IOPS and throughput are determined based on how much storage you provision. The provisioned v1 model for Azure Files is only available for SSD (premium) file shares.
 
 - **Pay-as-you-go billing model**: In a pay-as-you-go model, the cost of the file share is based on how much you use the share, in the form of used storage, transaction, and data transfer costs. The pay-as-you-go model for Azure Files is only available for HDD file shares. We recommend using the provisioned v2 model for new HDD file share deployments.