Skip to content

Commit 0d5da7f

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-limits-assignments-custom-roles
2 parents 51e7601 + e394e1a commit 0d5da7f

File tree

4 files changed

+2
-8
lines changed

4 files changed

+2
-8
lines changed

articles/azure-netapp-files/volume-hard-quota-guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 11/26/2024
8+
ms.date: 02/20/2025
99
ms.author: anfdocs
1010
---
1111
# What changing to volume hard quota means for your Azure NetApp Files service
@@ -240,7 +240,7 @@ Yes, the consumed snapshot capacity counts towards the provisioned space in the
240240

241241
A common misconception is that Azure NetApp Files *volumes* would automatically grow upon filling up. Volumes were thinly provisioned with a size of 100 TiB, regardless of the actual set quota, while the underlying *capacity pool* would automatically grow with 1-TiB increments. This change addresses the (visible and usable) *volume* size to the set quota, and *capacity pools* thus no longer automatically grow. This change results in commonly desired accurate client-side space and capacity reporting. It avoids "runaway" capacity consumption.
242242

243-
### Does this change have any effect on volumes replicated with cross-region-replication (preview)?
243+
### Does this change have any effect on volumes replicated with cross-region-replication?
244244

245245
The hard volume quota isn't enforced on replication destination volumes.
246246

articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-android.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ ms.date: 09/26/2024
66
ms.author: jiyoonlee
77
---
88

9-
[!INCLUDE [public-preview-note](../../../../includes/public-preview-include.md)]
10-
119
In this quickstart you are going to learn how to start a call from Azure Communication Services user to Teams Auto Attendant. You are going to achieve it with the following steps:
1210

1311
1. Enable federation of Azure Communication Services resource with Teams Tenant.

articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-ios.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ ms.date: 09/26/2024
66
ms.author: jiyoonlee
77
---
88

9-
[!INCLUDE [public-preview-note](../../../../includes/public-preview-include.md)]
10-
119
In this quickstart you are going to learn how to start a call from Azure Communication Services user to Teams Auto Attendant. You are going to achieve it with the following steps:
1210

1311
1. Enable federation of Azure Communication Services resource with Teams Tenant.

articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-windows.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ ms.date: 09/26/2024
66
ms.author: jiyoonlee
77
---
88

9-
[!INCLUDE [public-preview-note](../../../../includes/public-preview-include.md)]
10-
119
In this quickstart you are going to learn how to start a call from Azure Communication Services user to Teams Auto Attendant. You are going to achieve it with the following steps:
1210

1311
1. Enable federation of Azure Communication Services resource with Teams Tenant.

0 commit comments

Comments
 (0)