Merge pull request #305719 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-18 05:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-netapp-files/manage-cool-access.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 09/16/2025
+ms.date: 09/17/2025
 ms.author: anfdocs
 ms.custom:
   - build-2025
@@ -88,7 +88,7 @@ There are several considerations to be aware of when using cool access.
 
 ## Enable cool access 
 
-You must register for cool access with the Premium or Ultra service levels before you can enable it at the capacity pool and volume levels. No registration is required for the Standard service level. 
+You must register for cool access with the Flexible, Premium, or Ultra service levels before you can enable it at the capacity pool and volume levels. No registration is required for the Standard service level. 
 
 ### Register the feature 
 
@@ -138,7 +138,7 @@ No registration is required to use cool access at the Standard service level.
 
 # [Flexible](#tab/flexible)
 
-Cool access with the Flexible service level is currently in preview. You must register the feature before using it. 
+You must register cool access with the Flexible service level before using it. 
 
 1. Register the feature: 
 

articles/azure-netapp-files/whats-new.md

@@ -19,6 +19,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## September 2025
 
+* [Flexible service level](manage-cool-access.md?tabs=flexible#register-the-feature) with cool access is now generally available (GA)
+
+    Azure NetApp Files supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. This feature is now generally available (GA).
+
 * [Flexible service level](azure-netapp-files-set-up-capacity-pool.md) is now generally available (GA)
 
     The [Flexible service level](azure-netapp-files-service-levels.md#Flexible) allows you to independently configure storage capacity and throughput, optimizing costs by right-sizing according to storage and performance requirements. With separate pricing for capacity and throughput, the Flexible service level prevents overprovisioning and supports up to 640 MiB/second per TiB. This throughput is five times the performance of the Ultra service level, making it ideal for demanding workloads and offering higher throughput for smaller capacity pools and adapting to changing requirements without the need for volume moves. 

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

@@ -42,7 +42,7 @@ If you need more information about a particular diagnostic code, select the **Fe
 | <a id='BCP025' />BCP025 | Error | The property `{property}` is declared multiple times in this object. Remove or rename the duplicate properties. |
 | <a id='BCP026' />BCP026 | Error | The output expects a value of type `{expectedType}`, but the provided value is of type `{actualType}`. |
 | <a id='BCP028' />BCP028 | Error | Identifier `{identifier}` is declared multiple times. Remove or rename the duplicates. |
-| <a id='BCP029' />BCP029 | Error | The resource type isn't valid. Specify a valid resource type of format `<types>@<apiVersion>`. |
+| <a id='BCP029' />[BCP029](./diagnostics/bcp029.md) | Error | The resource type isn't valid. Specify a valid resource type of format `<types>@<apiVersion>`. |
 | <a id='BCP030' />BCP030 | Error | The output type isn't valid. Specify one of the following types: `{ToQuotedString(validTypes)}`. |
 | <a id='BCP031' />BCP031 | Error | The parameter type isn't valid. Specify one of the following types: `{ToQuotedString(validTypes)}`. |
 | <a id='BCP032' />BCP032 | Error | The value must be a compile-time constant. |

articles/azure-resource-manager/bicep/diagnostics/bcp029.md

@@ -0,0 +1,59 @@
+---
+title: BCP029
+description: The resource type isn't valid. Specify a valid resource type of format <types>@<apiVersion>.
+ms.topic: reference
+ms.custom: devx-track-bicep
+ms.date: 09/17/2025
+---
+
+# Bicep diagnostic code - BCP029
+
+This diagnostic occurs when you specify an invalid format of a resource type.
+
+## Description
+
+The resource type isn't valid. Specify a valid resource type of format \<types>@\<apiVersion>.
+
+## Level
+
+Error
+
+## Solution
+
+Use the valid format of resource type.
+
+## Examples
+
+The following example raises the diagnostic because the `Microsoft.Storage/storageAccounts` resource type requires an API version:
+
+```bicep
+param location string = resourceGroup().location
+
+resource storage 'Microsoft.Storage/storageAccounts' = {
+  name: 'mystorageacct'
+  location: location
+  sku: {
+    name: 'Standard_LRS'
+  }
+  kind: 'StorageV2'
+}
+```
+
+You can fix the diagnostic by providing an API version:
+
+```bicep
+param location string = resourceGroup().location
+
+resource storage 'Microsoft.Storage/storageAccounts@2025-01-01' = {
+  name: 'mystorageacct'
+  location: location
+  sku: {
+    name: 'Standard_LRS'
+  }
+  kind: 'StorageV2'
+}
+```
+
+## Next steps
+
+For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

articles/azure-resource-manager/bicep/toc.yml

@@ -636,6 +636,8 @@ items:
             href: diagnostics/bcp009.md
           - name: BCP018
             href: diagnostics/bcp018.md
+          - name: BCP029
+            href: diagnostics/bcp029.md
           - name: BCP033
             href: diagnostics/bcp033.md
           - name: BCP035

articles/communication-services/tutorials/audio-quality-enhancements/includes/web.md

@@ -6,7 +6,7 @@ author: sloanster
 ms.author: micahvivion
 
 services: azure-communication-services
-ms.date: 06/28/2025
+ms.date: 09/17/2025
 ms.topic: include
 ms.service: azure-communication-services
 ms.subservice: calling
@@ -35,12 +35,13 @@ Key traits for echo cancelation:
 > **Noise Suppression** features are available in GA WebJS SDK version `1.28.4` or later, alongside the Azure Communication Services Calling Effects SDK version GA `1.1.2` or later. Alternatively, if you opt to use the public preview version, Calling SDK versions `1.24.2-beta.1` and later also support noise suppression.
 
 > [!IMPORTANT]
-> **Echo Cancellation** features are available in public preview SDK version [1.37.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1371-beta1-2025-06-16). Also note that to use echo cancelation you must use public preview audio effects SDK version beta version [1.21.1-beta](https://www.npmjs.com/package/@azure/communication-calling-effects/v/1.2.1-beta.1) or later.
+> **Echo Cancellation** features are available in GA WebJS SDK version [1.38.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-2025-09-02) or later. Also note that to use echo cancelation you must use the audio effects SDK version GA version [1.31.1](https://www.npmjs.com/package/@azure/communication-calling-effects/v/1.3.1) or later. Alternatively, if you opt to use the public preview version, Calling SDK versions [1.38.1-beta.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1381-beta1-2025-07-21) and later also support noise suppression.
 
 > [!NOTE]
 > - Utilizing audio effects is available only on Chrome and Edge desktop browsers.
 > - The audio effects library isn't a standalone module and can't function independently. To utilize its capabilities the effects package must be integrated with the Azure Communication Services Calling client library for WebJS.
 > - If you use the GA version of the Calling SDK, you must use the [GA version](https://www.npmjs.com/package/@azure/communication-calling-effects/v/latest) of the Calling audio effects package.
+> - If you use the public preview version of the Calling SDK, you must use the [public prevew version](https://www.npmjs.com/package/@azure/communication-calling-effects/v/latest) of the Calling audio effects package.
 
 ## Install the Audio Effects Package
 Use the `npm install` command to install the Azure Communication Services Audio Effects SDK for JavaScript.

articles/healthcare-apis/known-issues.md

@@ -20,6 +20,7 @@ Refer to the table for details about resolution dates or possible workarounds.
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
+| Customers are seeing inconsistent behavior with custom search parameters after reindex | Sept 16, 2025 | We recently updated the infrastructure with a reindex operation, which caused the latest search parameters to be out of sync for a period ranging from minutes to potentially days. Please create a support ticket to get the parameters synchronized.||
 | Customers are unable to select storage account in the FHIR instance export configuration. The issue is caused by throttling due to a large number of resource groups and storage accounts, leading to errors like "Storage account doesn't exist" on the Export blade. | May 15, 2025 2:05 pm PST | PowerShell commands to configure the storage account for export manually:<br><br>Run this command to install the Az Module: <br>```Install-Module -Name Az```<br><br> If Az module is already installed:<br>```Update-Module -Name Az```<br><br> Connect to Azure Account:<br>```Connect-AzAccount```<br><br>Initialize the variable resourceGroupName, fhirServiceName, and storageAccountName:<br>```$resourceGroupName = "YOUR_RESOURCEGROUP_NAME"```<br>```$fhirServiceName = "YOUR_FHIRSERVICE_NAME"```<br>```$exportConfig = @{ "storageAccountName" = "YOUR_STORAGEACCOUNT_NAME" }```<br><br>Run this command to set the storage account for export:<br>```Set-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName -ApiVersion "2021-11-01" -Properties @{ "exportConfiguration" = $exportConfig }```<br><br>Running this command confirms  if the setting was successful: <br>```Get-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName \| Select-Object -ExpandProperty Properties \| Select-Object -ExpandProperty exportConfiguration```| -- |
 | Patient-everything operation returns a 500 error when run using a SMART patient fhirUser token. |  April 9, 2025 | A fix is being released in the upcoming FHIR release. | |
 |Customers can't access FHIR, DICOM, or Medtech through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | November 1, 2024  |

articles/reliability/TOC.yml

@@ -280,6 +280,8 @@ items:
       href: ../databox/data-box-disk-faq.yml?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json#how-can-i-recover-my-data-if-an-entire-region-fails-
     - name: Azure Elastic SAN
       href: reliability-elastic-san.md
+    - name: Azure Files
+      href: reliability-storage-files.md
     - name: Azure NetApp Files
       href: reliability-netapp-files.md
     - name: Azure Queue Storage

articles/reliability/availability-zones-enable-zone-resiliency.md

@@ -152,7 +152,7 @@ This table summarizes the availability zone support for many Azure services and
 | [Azure Elastic SAN](reliability-elastic-san.md#availability-zone-migration) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment |
 | [Azure Event Hubs](./reliability-event-hubs.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Always zone-resilient |
 | [Azure ExpressRoute](/azure/expressroute/expressroute-howto-gateway-migration-portal) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Modification |
-| [Azure Files](migrate-storage.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Enablement |
+| [Azure Files](./reliability-storage-files.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Enablement |
 | [Azure Firewall](./reliability-firewall.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | Modification |
 | [Azure Functions](reliability-functions.md#availability-zone-migration) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment |
 | [Azure HDInsight](reliability-hdinsight.md#availability-zone-migration) | | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | Redeployment |

articles/reliability/availability-zones-service-support.md

@@ -60,7 +60,7 @@ Some Azure services are *nonregional*, which means that you don't deploy the ser
 | [Azure Event Grid](reliability-event-grid.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
 | [Azure Event Hubs](/azure/event-hubs/event-hubs-business-continuity-outages-disasters#availability-zones) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
 | [Azure ExpressRoute](../expressroute/designing-for-high-availability-with-expressroute.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
-| [Azure Files](../storage/common/storage-redundancy.md#supported-azure-storage-services) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
+| [Azure Files](./reliability-storage-files.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
 | [Azure Firewall](reliability-firewall.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
 | [Azure Firewall Manager](../firewall-manager/quick-firewall-policy.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
 | [Azure Functions](./reliability-functions.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |