Merge pull request #292700 from MicrosoftDocs/main

1/7/2025 AM Publish

Author: Taojunshen

articles/api-management/credentials-configure-common-providers.md

@@ -34,6 +34,8 @@ To configure any of the supported providers in API Management, first configure a
 
 * Depending on the provider and your scenario, you might need to retrieve other settings such as authorization endpoint URLs or scopes.
 
+* The provider's authorization endpoints must be reachable over the internet from your API Management instance. If your API Management instance is secured in a virtual network, configure network or firewall rules to allow access to the provider's endpoints.
+
 ## Microsoft Entra provider
 
 API credential manager supports the Microsoft Entra identity provider, which is the identity service in Microsoft Azure that provides identity management and access control capabilities. It allows users to securely sign in using industry-standard protocols.

articles/azure-cache-for-redis/cache-best-practices-memory-management.md

@@ -37,7 +37,7 @@ Configure your [maxmemory-reserved setting](cache-configure.md#memory-policies)
 
 - The `maxfragmentationmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, that is reserved to accommodate for memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high. When memory is reserved for such operations, it's unavailable for storage of cached data. The allowed range for `maxfragmentationmemory-reserved` is 10% - 60% of `maxmemory`. If you try to set these values lower than 10% or higher than 60%, they are re-evaluated and set to the 10% minimum and 60% maximum. The values are rendered in megabytes.
 
-- One thing to consider when choosing a new memory reservation value (`maxmemory-reserved` or `maxfragmentationmemory-reserved`) is how this change might affect a cache with large amounts of data in it that is already running. For instance, if you have a 53-GB cache with 49 GB of data and then change the reservation value to 8 GB, the max available memory for the system will drop to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system must evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](monitor-cache.md#create-your-own-metrics).
+- One thing to consider when choosing a memory reservation value (`maxmemory-reserved` or `maxfragmentationmemory-reserved`) is how this change might affect a cache with large amounts of data in it that is already running. For instance, if you have a 53-GB cache with with the reserved values set to the minimum of 10 GB, the max available memory for the system is approximately 42 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the limit of 42 GB, then the system must evict data until both `used_memory` and `used_memory_rss` are below 42 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](monitor-cache.md#create-your-own-metrics).
 
 > [!NOTE]
 > When you scale a cache up or down, both `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings automatically scale in proportion to the cache size. For example, if `maxmemory-reserved` is set to 3 GB on a 6-GB cache, and you scale to 12-GB cache, the settings automatically get updated to 6 GB during scaling. When you scale down, the reverse happens.

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/firewall-manager/secured-virtual-hub.md

@@ -5,15 +5,15 @@ author: vhorne
 ms.service: azure-firewall-manager
 services: firewall-manager
 ms.topic: concept-article
-ms.date: 06/13/2023
+ms.date: 01/07/2025
 ms.author: victorh
 ---
 
 # What is a secured virtual hub?
 
 A virtual hub is a Microsoft-managed virtual network that enables connectivity from other resources. When a virtual hub is created from a Virtual WAN in the Azure portal, a virtual hub VNet and gateways (optional) are created as its components.
 
-A *secured* virtual hub is an [Azure Virtual WAN Hub](../virtual-wan/virtual-wan-about.md#resources) with associated security and routing policies configured by Azure Firewall Manager. Use secured virtual hubs to easily create hub-and-spoke and transitive architectures with native security services for traffic governance and protection. Multiple secured hubs can be deployed within the same region or across regions part of the same Virtual WAN resource. Use Firewall Manager in the Azure Portal to add additional secured hubs. 
+A *secured* virtual hub is an [Azure Virtual WAN Hub](../virtual-wan/virtual-wan-about.md#resources) with associated security and routing policies configured by Azure Firewall Manager. Use secured virtual hubs to easily create hub-and-spoke and transitive architectures with native security services for traffic governance and protection. Multiple secured hubs can be deployed within the same region or across regions part of the same Virtual WAN resource. Use Firewall Manager in the Azure portal to add more secured hubs. 
 
 You can use a secured virtual hub to filter traffic between virtual networks (V2V), branch-to-branch (B2B)<sup>*</sup>, branch offices (B2V) and traffic to the Internet (B2I/V2I). A secured virtual hub provides automated routing. There's no need to configure your own UDRs (user defined routes) to route traffic through your firewall.
 

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/iot-operations/troubleshoot/known-issues.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.topic: troubleshooting-known-issue
 ms.custom:
   - ignite-2023
-ms.date: 11/07/2024
+ms.date: 01/07/2025
 ---
 
 # Known issues: Azure IoT Operations
@@ -25,6 +25,8 @@ This article lists the known issues for Azure IoT Operations.
 
 - If your deployment fails with the message `Error occurred while creating custom resources needed by system extensions`, you have encountered a known sporadic failure that will be fixed in a future release. As a work around, use the [az iot ops delete](/cli/azure/iot/ops#az-iot-ops-delete) command with the `--include-deps` flag to delete Azure IoT Operations from your cluster. When Azure IoT Operations and its dependencies are deleted from your cluster, retry the deployment.
 
+- If you deploy Azure IoT Operations in GitHub Codespaces, shutting down and restarting the Codespace causes a `This codespace is currently running in recovery mode due to a configuration error.` issue. Currently, there's no workaround for the issue. If you need a cluster that supports shutting down and restarting, choose one of the options in [Prepare your Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-prepare-cluster.md).
+
 ## MQTT broker
 
 - MQTT broker resources created in your cluster using Kubernetes aren't visible Azure portal. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.

articles/operator-nexus/concepts-cluster-management-upgrade.md

@@ -21,7 +21,7 @@ For Compute management, Microsoft delivers new software to the extensions and ag
 
 ## Impact to customer workloads
 
-The intent of these releases is no disruption to running workloads and on-premises resources retain availability throughout the upgrade. Therefore, the customer should see no impact. 
+The intent of these releases is no disruption to running workloads, instantiating new workloads, and on-premises resources retain availability throughout the upgrade. Therefore, the customer should see no impact. 
 
 ## Duration of on-premises updates
 

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.