Merge pull request #294650 from MicrosoftDocs/main

2/13/2025 PM Publish

Author: Taojunshen

articles/azure-netapp-files/application-volume-group-manage-volumes.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/19/2021
+ms.date: 11/19/2024
 ms.author: anfdocs
 ---
 # Manage volumes in an application volume group for SAP HANA
@@ -14,24 +14,24 @@ You can manage a volume from its volume group. You can resize, delete, or change
 
 ## Steps
 
-1. From your NetApp account, select **Application volume groups**. Click a volume group to display the volumes in the group.  
+1. From your NetApp account, select **Application volume groups**. Select a volume group to display the volumes in the group.  
 
 2. Select the volume you want to resize, delete, or change throughput. The volume overview is displayed. 
 
     [![Screenshot that shows Application Volume Groups overview page.](./media/application-volume-group-manage-volumes/application-volume-group-overview.png)](./media/application-volume-group-manage-volumes/application-volume-group-overview.png#lightbox)  
 
-    * To resize the volume, click **Resize** and specify the quota in GiB.
+    * To resize the volume, select **Resize** and specify the quota in GiB.
 
     ![Screenshot that shows the Update Volume Quota window.](./media/application-volume-group-manage-volumes/application-volume-resize.png)
 
-    * To change the throughput for the volume, click **Change throughput** and specify the intended throughput in MiB/s.
+    * To change the throughput for the volume, select **Change throughput** and specify the intended throughput in MiB/s.
 
     ![Screenshot that shows the Change Throughput window.](./media/application-volume-group-manage-volumes/application-volume-change-throughput.png)
 
-    * To delete the volume in the volume group, click **Delete**. If you are prompted, type the volume name to confirm the deletion.  
+    * To delete the volume in the volume group, select **Delete**. If prompted, enter the volume name to confirm the deletion.  
 
     > [!IMPORTANT]
-    > The volume deletion operation cannot be undone.
+    > Volume deletion is permanent. It can't be undone.
     
     ![Screenshot that shows the Delete Volume window.](./media/application-volume-group-manage-volumes/application-volume-delete.png)
 

articles/azure-netapp-files/regional-capacity-quota.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 10/11/2021
+ms.date: 10/11/2024
 ms.author: anfdocs
 ---
 # Regional capacity quota for Azure NetApp Files
@@ -14,7 +14,7 @@ This article explains regional capacity quota of Azure NetApp Files.
 
 ## Display regional capacity quota
 
-You can click **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
+You can select **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
 
 For example: 
 

articles/azure-netapp-files/request-region-access.md

@@ -5,12 +5,12 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/15/2021
+ms.date: 02/10/2025
 ms.author: anfdocs
 ---
 # Request region access for Azure NetApp Files
 
-In some special situations, you might need to explicitly request access to a region. This article explains how to submit a request. 
+In special situations, you need to explicitly request access to a region. Learn how to submit a request. 
 
 ## Steps
 
@@ -23,7 +23,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Problem Description tab.](./media/shared/support-problem-descriptions.png)
 
-3. Under the **Additional details** tab, click **Enter details** in the Request Details field.  
+3. In the **Additional details** tab, select **Enter details** in the Request Details field.  
 
     ![Screenshot that shows the Details tab and the Enter Details field.](./media/shared/quota-additional-details.png)
 
@@ -33,7 +33,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Quota Details window for requesting region access.](./media/request-region-access/quota-details-region-access.png)
 
-5. Click **Save and continue**. Click **Review + create** to create the request.
+5. Select **Save and continue**. Click **Review + create** to create the request.
 
 ## Next steps  
 

articles/azure-netapp-files/solutions-benefits-azure-netapp-files-electronic-design-automation.md

@@ -25,13 +25,13 @@ Azure NetApp Files helps reduce the time EDA jobs take with a highly performant,
 
 The Azure NetApp Files large volumes feature is ideal for the storage needs of this most demanding industry, namely:  
 
-* **Large capacity single namespace:** Each volume offers from up to 500TiB of usable capacity under a single mount point. 
+* **Large capacity single namespace:** Each volume offers up to 1 PiB of usable capacity under a single mount point. You can [request a 2 PiB large volume](large-volumes-requirements-considerations.md).
 
 * **High I/O rate, low latency:** In testing using an EDA simulation benchmark, a single large volume delivered over 650K storage IOPS with less than 2 milliseconds of application latency. In a typical EDA workload, IOPS consists of a mixture or file creates, reads, writes, and a significant amount of other metadata operation. This result is considered to be enterprise-grade performance for many customers. This performance improvement is made possible by the way large volumes are able to parallelize incoming write operations across storage resources in Azure NetApp Files. Though many firms require 2ms or better response time, chip design tools can tolerate higher latency than this without impact to business.  
 
 * **At 826,000 operations per second:** the performance edge of a single large volume - the application layer peaked at 7ms of latency in our tests, which shows that more operations are possible in a single large volume at a slight cost of latency. 
 
-Tests conducted using an EDA benchmark found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge. See the table and chart below for regular and large volume side-by-side overview.
+Tests conducted using an EDA benchmark found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge. See the following table and chart for regular and large volumes side-by-side overview.
 
 
 | Scenario | I/O Rate at 2ms latency | I/O Rate at performance edge (~7 ms) | MiB/s at 2ms latency | MiB/s performance edge (~7 ms) | 
@@ -86,7 +86,7 @@ The EDA workload in this test was generated using a standard industry benchmark
 
 ## Test configuration 
 
-The results were produced using the below configuration details:
+The results were produced using the following configuration details:
 
 | Component | Configuration |
 | - | - | 

articles/azure-netapp-files/solutions-windows-virtual-desktop.md

@@ -5,14 +5,14 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 08/13/2020
+ms.date: 08/13/2024
 ms.author: anfdocs
 ---
 # Benefits of using Azure NetApp Files with Azure Virtual Desktop 
 
 This article provides best practice guidance on deploying Azure Virtual Desktop with Azure NetApp Files.
 
-Azure NetApp Files is a highly performant file storage service from Azure. It can provide up to 450,000 IOPS and sub-millisecond latency, capable of supporting extremely large scale of Azure Virtual Desktop deployments. You can adjust the bandwidth and change the service level of your Azure NetApp Files volumes on demand almost instantaneously without pausing IO while retaining data plane access. This capability allows you to easily optimize your Azure Virtual Desktop deployment scale for cost. You can also create space-efficient, point-in-time volume snapshots without impacting volume performance. This capability makes it possible for you to roll back individual [FSLogix user profile containers](../virtual-desktop/store-fslogix-profile.md) via a copy from the `~snapshot` directory, or to instantaneously roll back the entire volume at once via the volume revert capability.  With up to 255 (rotational) snapshots in place to protect a volume from data loss or corruption, administrators have many chances to undo what has been done.
+Azure NetApp Files is a highly performant file storage service from Azure. It can provide up to 450,000 I/OPS and sub-millisecond latency, capable of supporting extremely large scale of Azure Virtual Desktop deployments. You can adjust the bandwidth and change the service level of your Azure NetApp Files volumes on demand almost instantaneously without pausing IO while retaining data plane access. This capability allows you to easily optimize your Azure Virtual Desktop deployment scale for cost. You can also create space-efficient, point-in-time volume snapshots without impacting volume performance. This capability makes it possible for you to roll back individual [FSLogix user profile containers](../virtual-desktop/store-fslogix-profile.md) via a copy from the `~snapshot` directory, or to instantaneously roll back the entire volume at once via the volume revert capability. With up to 255 (rotational) snapshots in place to protect a volume from data loss or corruption, administrators have many chances to undo what has been done.
 
 ## Sample blueprints
 

articles/azure-netapp-files/troubleshoot-snapshot-policies.md

@@ -5,18 +5,18 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: troubleshooting
-ms.date: 09/23/2020
+ms.date: 09/23/2024
 ms.author: anfdocs
 ---
 # Troubleshoot snapshot policy errors
 
-This article describes error scenarios you might encounter when managing Azure NetApp Files snapshot policies. It also provides solutions that can help you address the issues.
+Learn about the possible error scenarios you can encounter when managing Azure NetApp Files snapshot policies and how to address them.
 
 ## Error conditions and resolutions 
 
 |     Error condition    |     Resolution    |
 |-|-|
-| Snapshot policy creation fails with invalid snapshot policy name. | An error occurs during snapshot policy creation if your snapshot policy name is invalid. The following guidelines apply for snapshot policy names:  <ul><li> The snapshot policy name cannot contain non-ASCII or special characters. </li> <li> The snapshot policy name must begin with a letter or a number and can contain letters, numbers, underscore ('_') and hyphens ('-') only. </li> <li> The snapshot policy name must be between 1 and 64 characters.  </li></ul> Revise the snapshot policy name according to the guidelines.  |
+| Snapshot policy creation fails with invalid snapshot policy name. | An error occurs during snapshot policy creation if your snapshot policy name is invalid. The following guidelines apply for snapshot policy names:  <ul><li> The snapshot policy name cannot contain non-ASCII or special characters. </li> <li> The snapshot policy name must begin with a letter or a number and can contain letters, numbers, underscore ('_') and hyphens ('-') only. </li> <li> The snapshot policy name must be between 1 and 64 characters. </li></ul> Revise the snapshot policy name according to the guidelines.  |
 | Snapshot policy creation fails with invalid values. | Azure NetApp Files fails to create a snapshot policy if you enter an invalid value for a field such as `Number of snapshots to keep` or `Minute on the hour to take snapshot`. The valid values are as follows:  <ul><li>The value must be a valid number.</li> <li>The value must be between 0 and 59.</li></ul> Make sure that a valid value is provided for the fields. | 
 | Snapshot policy creation fails with the error `Total number of snapshots to keep exceeds 255`. | Each volume can have a [maximum of 255 snapshots](azure-netapp-files-resource-limits.md). The maximum includes the sum of all hourly, daily, weekly, and monthly snapshots. <br> Decrease the `Snapshots to keep` value and try again. |
 | Assigning policy to a volume fails with the error `Total snapshot policy is over the max '255'`. | Each volume can have a [maximum of 255 snapshots](azure-netapp-files-resource-limits.md). When the sum of all on-demand, hourly, daily, weekly, and monthly snapshots exceeds the maximum, an error occurs. <br> Decrease the `snapshots to keep` value or delete some on-demand snapshots and try again. | 

articles/azure-netapp-files/use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: seanluce
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 06/30/2022
+ms.date: 10/30/2024
 ms.author: anfdocs
 ---
 

articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md

@@ -9,9 +9,6 @@ ms.custom: references_regions, engagement-fy23
 
 # Remove Arc-enabled Azure VMware Solution vSphere resources from Azure
 
-> [!CAUTION]
-> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
-
 In this article, learn how to cleanly remove your VMware vCenter environment from Azure Arc-enabled VMware vSphere. For VMware vSphere environments that you no longer want to manage with Azure Arc-enabled VMware vSphere, use the information in this article to perform the following actions: 
 
 - Remove guest management from VMware virtual machines (VMs). 
@@ -72,7 +69,7 @@ To uninstall the Linux agent, the command to use depends on the Linux operating
   sudo apt purge azcmagent
   ```
 
-- For RHEL, CentOS, Oracle Linux run the following command:
+- For RHEL and Oracle Linux run the following command:
 
     ```bash
     sudo yum remove azcmagent

articles/azure-vmware/tutorial-scale-private-cloud.md

@@ -44,6 +44,9 @@ We do not allow the mixing of AV36, AV36P, or AV52 SKUs within the same cluster.
 > [!NOTE]
 > Scaling down a cluster successfully requires all objects (VM/vmdk/iso/etc) on a vSAN datastore to be configured with a storage policy below or equal to [RAID level requirements](configure-storage-policy.md). 
 
+> [!CAUTION]
+> Deleting a cluster terminates all running workloads and components and is an irreversible operation. Once you delete a cluster, you cannot recover the data.
+
 1. In your Azure VMware Solution private cloud, under **Manage**, select **Clusters**.
 
 2. Select the cluster you want to scale, select **More** (...), then select **Edit**.

articles/communication-services/concepts/interop/teams-user/teams-shared-line-appearance.md

@@ -0,0 +1,57 @@
+---
+title: Microsoft Teams shared line appearance
+titleSuffix: An Azure Communication Services concept document
+description: Provides an overview of Teams shared line appearance and delegate calling for Teams users in Azure Communication Services Calling SDK.
+author: jamescadd
+manager: chpalmer
+services: azure-communication-services
+
+ms.author: jacadd
+ms.date: 2/6/2025
+ms.topic: conceptual
+ms.service: azure-communication-services
+ms.subservice: teams-interop
+---
+# Microsoft Teams shared line appearance
+
+[!INCLUDE [Public Preview Notice](../../../includes/public-preview-include.md)]
+Microsoft Teams shared line appearance lets a user choose a delegate to answer or handle calls on their behalf. This feature is helpful if a user has an administrative assistant who regularly handles the user's calls. In the context of Teams shared line appearance, a manager is someone who authorizes a delegate to make or receive calls on their behalf. A delegate can make or receive calls on behalf of the delegator.
+
+## Prerequisites
+
+- An Azure account with an active subscription. See [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). 
+- A deployed Communication Services resource. See [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).
+- Licensing requirements for delegator and delegates. See [Teams Phone license](/microsoftteams/shared-line-appearance#license-required).
+- Enable delegation and shared line appearance. See [Enable delegation](/microsoftteams/shared-line-appearance#enable-delegation-and-shared-line-appearance)
+- Assign delegates using [Microsoft Teams Client](https://support.microsoft.com/office/share-a-phone-line-with-a-delegate-in-microsoft-teams-16307929-a51f-43fc-8323-3b1bf115e5a8) or [Teams PowerShell](/microsoftteams/shared-line-appearance#use-powershell).
+- Optional: Complete the quickstart to add voice calling to Microsoft Teams user. See [Quickstart: Add voice calling to Microsoft Teams user](../../../quickstarts/voice-video-calling/get-started-call-to-teams-user.md).
+
+## Use Cases
+
+**Business Enterprises**: Team leads can delegate their call responsibilities during meetings or vacations to their assistants or colleagues, ensuring uninterrupted communication with stakeholders.
+
+**Contact Centers:** Supervisors can allocate their call flows to other available agents during breaks, making certain that no client query goes unanswered.
+
+**Healthcare:** Doctors or nurses can delegate their call flows to peers or assistants during surgeries or when attending critical cases, ensuring patient queries are addressed promptly.
+
+## Platform capabilities
+The following Azure Communication Services and Graph platforms currently support shared line appearance:
+
+| Capability                                                 | Calling SDK JS | Graph SDK |
+|------------------------------------------------------------|----------------|-----------|
+| Set up delegation (add/remove/update delegate permissions) | ❌             | ❌       |
+| Receive calls on behalf of another                         | ✔️            | ❌        |
+| Call a phone number on behalf of another                   | ✔️            | ❌        |
+| Call a Teams user on behalf of another                     | ✔️            | ❌        |
+| Receive an ACS user call on behalf of another Teams user   | ✔️            | ❌        |
+| Get the delegate view of shared lines                      | ❌             | ✔️       |
+| Get the delegate view of manager’s call activities         | ❌             | ❌       |
+| Get the manager view of delegates                          | ❌             | ✔️       |
+| Get shared call history                                    | ❌            | ❌        |
+| Delegate or manager can hold or resume                     | ✔️            | ❌        |
+
+> [!NOTE] 
+> Calling SDK for iOS, Android, and Windows do not currently support shared line appearance.
+
+For more information on the capabilities available during a shared line appearance call, see [Calling capabilities for Teams users](../teams-user-calling.md).