Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-fix

Author: HeidiSteen

articles/azure-functions/functions-premium-plan.md

@@ -262,7 +262,7 @@ These are the currently supported maximum scale-out values for a single plan in
 |Japan West| 100 | 20 |
 |Jio India West| 100 | 20 |
 |Korea Central| 100 | 20 |
-|Korea South| Not Available | 20 |
+|Korea South| 40 | 20 |
 |North Central US| 100 | 20 |
 |North Europe| 100 | 100 |
 |Norway East| 100 | 20 |

articles/azure-monitor/essentials/activity-log.md

@@ -25,6 +25,7 @@ For details on how to create a diagnostic setting, see [Create diagnostic settin
 > [!NOTE]
 > * Entries in the Activity Log are system generated and can't be changed or deleted.
 > * Entries in the Activity Log are representing control plane changes like a virtual machine restart, any non related entries should be written into [Azure Resource Logs](resource-logs.md)
+> * Entries in the Activity Log are typically a result of changes (create, update or delete operations) or an action having been initiated.  Operations focused on reading details of a resource are not typically captured.
 
 ## Retention period
 
@@ -277,6 +278,7 @@ If a log profile already exists, you first must remove the existing log profile,
     |enabled | Yes |True or False. Used to enable or disable the retention policy. If True, then the `days` parameter must be a value greater than zero.
     | categories |Yes |Space-separated list of event categories that should be collected. Possible values are Write, Delete, and Action. |
 
+
 ---
 
 ### Data structure changes
@@ -309,3 +311,4 @@ Learn more about:
 * [Platform logs](./platform-logs-overview.md)
 * [Activity log event schema](activity-log-schema.md)
 * [Activity log insights](activity-log-insights.md)
+

articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md

@@ -24,7 +24,7 @@ For information about monitoring a volume’s capacity, see [Monitor the capacit
 ## Considerations
 
 * Volume quotas are indexed against `maxfiles` limits. Once a volume has surpassed a `maxfiles` limit, you cannot reduce the volume size below the quota that corresponds to that `maxfiles` limit. For more information and specific limits, see [`maxfiles` limits](azure-netapp-files-resource-limits.md#maxfiles-limits-).
-* Capacity pools with Basic network features have a minimum size of 4 TiB. For capacity pools with Standard network features, the minimum size is 2 TiB. For more information, see [Resource limits](azure-netapp-files-resource-limits.md)
+* Capacity pools with Basic network features have a minimum size of 4 TiB. For capacity pools with Standard network features, the minimum size is 1 TiB. For more information, see [Resource limits](azure-netapp-files-resource-limits.md)
 
 ## Resize the capacity pool using the Azure portal 
 

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -32,7 +32,7 @@ The following table describes resource limits for Azure NetApp Files:
 |  Number of volumes per capacity pool     |    500   |    Yes     |
 |  Number of snapshots per volume       |    255     |    No        |
 |  Number of IPs in a virtual network (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |   <ul><li>**Basic**: 1000</li><li>**Standard**: [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)</li></ul>  |    No    |
-|  Minimum size of a single capacity pool   |  2 TiB*     |    No  |
+|  Minimum size of a single capacity pool   |  1 TiB*     |    No  |
 |  Maximum size of a single capacity pool    |  1000 TiB   |   Yes   |
 |  Minimum size of a single regular volume    |    100 GiB    |    No    |
 |  Maximum size of a single regular volume     |    100 TiB    |    No    |
@@ -54,7 +54,8 @@ The following table describes resource limits for Azure NetApp Files:
 |  Maximum number of manual backups per volume per day |  5  |  No  |
 |  Maximum number of volumes supported for cool access per subscription per region |  10  |  Yes  |
 
-\* [!INCLUDE [Limitations for capacity pool minimum of 2 TiB](includes/2-tib-capacity-pool.md)]
+
+\* [!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
 
 For more information, see [Capacity management FAQs](faq-capacity-management.md).
 

articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md

@@ -21,10 +21,22 @@ Creating a capacity pool enables you to create volumes within it.
 
 ## Before you begin 
 
-* You must have already [created a NetApp account](azure-netapp-files-create-netapp-account.md).
+* You must have already [created a NetApp account](azure-netapp-files-create-netapp-account.md).   
 * If you are using Azure CLI, ensure that you are using the latest version. For more information, see [How to update the Azure CLI](/cli/azure/update-azure-cli).
 * If you are using PowerShell, ensure that you are using the latest version of the Az.NetAppFiles module. To update to the latest version, use the 'Update-Module Az.NetAppFiles' command. For more information, see [Update-Module](/powershell/module/powershellget/update-module).
 * If you are using the Azure REST API, ensure that you are specifying the latest version.
+* If this is your first time using a 1-TiB capacity pool, you must first register the feature: 
+    1. Register the feature: 
+        ```azurepowershell-interactive
+        Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANF1TiBPoolSize
+        ```
+    2. Check the status of the feature registration: 
+        > [!NOTE]
+        > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
+        ```azurepowershell-interactive
+        Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANF1TiBPoolSize
+        ```
+        You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
 
 
 ## Steps 
@@ -47,9 +59,10 @@ Creating a capacity pool enables you to create volumes within it.
 
     * **Size**     
      Specify the size of the capacity pool that you are purchasing.        
-     The minimum capacity pool size is 2 TiB. You can change the size of a capacity pool in 1-TiB increments.   
-        > [!NOTE]
-        > You can only take advantage of the 2-TiB minimum if all the volumes in the capacity pool are using Standard network features. If any volume is using Basic network features, the minimum size is 4 TiB.
+     The minimum capacity pool size is 1 TiB. You can change the size of a capacity pool in 1-TiB increments.
+    
+    >[!NOTE]
+    >[!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
 
     * **Enable cool access**  *(for Standard service level only)*   
         This option specifies whether volumes in the capacity pool will support cool access. This option is currently supported for the Standard service level only. For details about using this option, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md). 

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 02/23/2023
+ms.date: 07/27/2023
 ms.author: anfdocs
 ---
 # Storage hierarchy of Azure NetApp Files

articles/azure-netapp-files/includes/2-tib-capacity-pool.md

@@ -4,7 +4,7 @@ description: include file
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 02/22/2023
+ms.date: 11/27/2023
 ms.author: anfdocs
 ms.custom: include file
 
@@ -13,4 +13,6 @@ ms.custom: include file
 # azure-netapp-files-resize-capacity-pools-or-volumes.md
 ---
 
-2-TiB capacity pool sizing is currently in preview. You can only take advantage of the 2-TiB minimum if all the volumes in the capacity pool are using Standard network features. If any volume is using Basic network features, the minimum size is 4 TiB.
+1-TiB capacity pool sizing is currently in preview. You can only take advantage of the 1-TiB minimum if all the volumes in the capacity pool are using Standard network features. The generally available minimum size for capacity pools with all volumes using Standard network features is 2 TiB. If any volume is using Basic network features, the minimum size is 4 TiB.
+
+To use the 1-TiB minimum, you must first [register for the preview](../azure-netapp-files-set-up-capacity-pool.md#before-you-begin). 

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

@@ -13,16 +13,22 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.custom: devx-track-linux
 ms.topic: overview
-ms.date: 11/08/2023
+ms.date: 11/27/2023
 ms.author: anfdocs
 ---
 
 # What's new in Azure NetApp Files
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
-
+  
 ## November 2023
 
+* [Capacity pool enhancement:](azure-netapp-files-set-up-capacity-pool.md) New lower limits
+
+    * 2 TiB capacity pool: The 2 TiB lower limit for capacity pools using Standard network features is now generally available (GA).
+
+    * 1 TiB capacity pool: Azure NetApp Files now supports a lower limit of 1 TiB for capacity pool sizing with Standard network features. This feature is currently in preview.
+
 * [Metrics enhancement: Throughput limits](azure-netapp-files-metrics.md#volumes)
 
     Azure NetApp Files now supports a "throughput limit reached" metric for volumes. The metric is a Boolean value that denotes the volume is hitting its QoS limit. With this metric, you know whether or not to adjust volumes so they meet the specific needs of your workloads. 

articles/communication-services/how-tos/calling-sdk/audio-conferencing.md

@@ -0,0 +1,30 @@
+---
+title: Teams Meeting Audio Conferencing
+titleSuffix: An Azure Communication Services how-to guide
+description: Use Azure Communication Services SDKs to retrieve Teams Meeting Audio Conferencing Details
+author: cnwankwo
+ms.author: cnwankwo
+ms.service: azure-communication-services
+ms.subservice: teams-interop
+ms.topic: how-to 
+ms.date: 09/28/2023
+ms.custom: template-how-to
+---
+
+
+# Microsoft Teams Meeting Audio Conferencing 
+In this article, you learn how to use Azure Communication Services Calling SDK to retrieve Microsoft Teams Meeting audio conferencing details. This functionality allows users who are already connected to a Microsoft Teams Meeting to be able to get the conference ID and dial in phone number associated with the meeting. At present, Teams audio conferencing feature returns a conference ID and only one dial-in toll or toll-free phone number depending on the priority assigned. In the future, Teams audio conferencing feature will return a collection of all toll and toll-free numbers, giving users control on what Teams meeting dial-in details to use
+
+## Prerequisites
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). 
+- A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
+- A user access token to enable the calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
+- Optional: Complete the quickstart to [add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md)
+
+[!INCLUDE [Audio Conferencing Client-side JavaScript](./includes/audio-conferencing/audio-conferencing-web.md)]
+
+## Next steps
+- [Learn how to manage calls](./manage-calls.md)
+- [Learn how to manage video](./manage-video.md)
+- [Learn how to record calls](./record-calls.md)
+- [Learn how to transcribe calls](./call-transcription.md)

articles/communication-services/how-tos/calling-sdk/includes/audio-conferencing/audio-conferencing-web.md

@@ -0,0 +1,38 @@
+---
+ms.author: cnwankwo
+ms.service: azure-communication-services
+ms.topic: include
+ms.date: 09/28/2023
+---
+[!INCLUDE [Install SDK](../install-sdk/install-sdk-web.md)]
+
+TeamsMeetingAudioConferencing is an extended feature of the core `Call` API. You first need to import calling Features from the Calling SDK:
+
+```js
+import { Features} from "@azure/communication-calling";
+```
+
+Then you can get the feature API object from the call instance:
+
+```js
+const audioConferencingFeature = call.feature(Features.TeamsMeetingAudioConferencing);
+```
+
+### Get the audio conferencing details of a meeting
+Use the following API, to get the audio conferencing details of a meeting
+```js
+try {
+     const details: SDK.TeamsMeetingAudioConferencingDetails = audioConferencingFeature.getTeamsMeetingAudioConferencingDetails();
+     console.log(`Microsoft Teams Meeting Conference Id: ${details.phoneConferenceId}`);
+     details.phoneNumbers.forEach(dialInPhoneNumber => {
+        if (dialInPhoneNumber.tollPhoneNumber) { 
+             console.log(`Dial-In Toll PhoneNumber: ${dialInPhoneNumber.tollPhoneNumber.phoneNumber}`);
+        }
+        else if (dialInPhoneNumber.tollFreePhoneNumber) { 
+            console.log(`Dial-In TollFree PhoneNumber: ${dialInPhoneNumber.tollFreePhoneNumber.phoneNumber}`);
+        } 
+    })
+} catch (e) {
+    console.error(e);
+}
+```