Skip to content

Commit 2bdb78f

Browse files
Merge pull request #314504 from MicrosoftDocs/main
Auto Publish – main to live - 2026-04-09 06:00 UTC
2 parents 0b54d02 + ff1c9dc commit 2bdb78f

23 files changed

Lines changed: 377 additions & 418 deletions

articles/artifact-signing/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ To register an Artifact Signing resource provider by using the Azure CLI:
111111

112112
## Create an Artifact Signing account
113113

114-
An Artifact Signing account is a logical container that holds identity validation and certificate profile resources.
114+
An Artifact Signing account is a logical container that holds identity validation and certificate profile resources. An identity validation is available at the subscription id level and can be shared across all the Artifact Signing accounts within that subscription.
115115

116116
### Azure regions that support Artifact Signing
117117

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Creating a capacity pool enables you to create volumes within it.
2929
>To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from `2024-01-01`.
3030
* The Standard, Premium, and Ultra service levels are generally available (GA). No registration is required.
3131

32-
## <a name="considerations"> Considerations for the Flexible service level
32+
## <a name="considerations"></a>Considerations for the Flexible service level
3333

3434
* The Flexible service level is only available for manual QoS capacity pools.
3535
* The Flexible service level is only available on newly created capacity pools. You can't convert an existing capacity pool to use the Flexible service level.

articles/azure-netapp-files/faq-smb.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: azure-netapp-files
55
ms.topic: concept-article
66
author: b-hchen
77
ms.author: anfdocs
8-
ms.date: 12/08/2025
8+
ms.date: 04/09/2026
99
ms.custom: sfi-image-nochange
1010
# Customer intent: As an IT administrator using Azure NetApp Files, I want to understand the SMB protocol and its configurations, so that I can ensure optimal connectivity and performance for my organization's file sharing and storage needs.
1111
---
@@ -60,6 +60,12 @@ You can also map multiple NetApp accounts that are under the same subscription a
6060

6161
<a name='does-azure-netapp-files-support-azure-active-directory'></a>
6262

63+
## Does Azure NetApp Files support SMB symbolic links or widelinks?
64+
65+
No. Azure NetApp Files SMB volumes do not support UNIX symbolic links (symlinks) or widelinks. SMB clients cannot create or follow symbolic links.
66+
67+
Symbolic links created by NFS clients or other systems are not honored when accessed over SMB. Absolute symbolic links and widelinks that reference paths outside the SMB share are not available.
68+
6369
## Does Azure NetApp Files support Microsoft Entra ID?
6470

6571
Both [Microsoft Entra Domain Services](../active-directory-domain-services/overview.md) and [Active Directory Domain Services (AD DS)](/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview) are supported. You can use existing Active Directory domain controllers with Azure NetApp Files. Domain controllers can reside in Azure as virtual machines, or on premises via ExpressRoute or S2S VPN. Azure NetApp Files doesn't support AD join for [Microsoft Entra ID](../active-directory/fundamentals/index.yml) at this time.

articles/azure-netapp-files/object-rest-api-access-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: anfdocs
1111

1212
# Configure object REST API for Azure NetApp Files (preview)
1313

14-
Azure NetApp Files supports access to S3 objects with the [object REST API](object-rest-api-introduction.md) feature. With the object REST API, you can connect to services such as Azure AI Search, Microsoft Fabric, Microsoft Foundry, Azure Databricks, OneLake, and other S3‑compatible clients.
14+
Azure NetApp Files supports access to objects with the [object REST API](object-rest-api-introduction.md) feature. With the object REST API, you can connect to services such as Azure AI Search, Microsoft Fabric, Microsoft Foundry, Azure Databricks, OneLake, and other S3‑compatible clients.
1515

1616
This article describes how to configure object REST API access and walks you through the two supported certificate workflows. Choose the workflow that best matches your security and operational requirements.
1717

articles/azure-netapp-files/replication-requirements.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,8 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
5454
5555
* When you revert a source volume that has an active volume replication relationship, only snapshots dated more recently than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume by using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
5656

57+
* If the source volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail. To prevent overfilling the destination volume, add 20% extra capacity when creating the data protection volume. To prevent overprovisioning, you can reduce the volume size after the initial replication completes.
58+
5759
## Cross-region replication requirements and considerations
5860

5961
* Azure NetApp Files replication is only available in specific fixed region pairs. For more information, see [Supported cross-region replication pairs](#supported-region-pairs).
@@ -74,7 +76,7 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
7476

7577
* If you use the cool access feature, understand the considerations in [Manage Azure NetApp Files storage with cool access](manage-cool-access.md#considerations).
7678

77-
* If the volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail, depending on the rate of data changes.
79+
* If the source volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail. To prevent overfilling the destination volume, add 20% extra capacity when creating the data protection volume. To prevent overprovisioning, you can reduce the volume size after the initial replication completes.
7880

7981
### <a name="supported-region-pairs"></a>Supported cross-region replication pairs
8082

articles/azure-netapp-files/volume-delete.md

Lines changed: 6 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: how-to
8-
ms.date: 04/22/2025
8+
ms.date: 04/09/2026
99
ms.author: anfdocs
1010
# Customer intent: As a cloud administrator, I want to delete an Azure NetApp Files volume, so that I can manage storage resources effectively and prevent unnecessary costs.
1111
---
@@ -14,7 +14,10 @@ ms.author: anfdocs
1414
This article describes how to delete an Azure NetApp Files volume.
1515

1616
> [!IMPORTANT]
17-
> If the volume you want to delete is in a replication relationship, follow the steps in [Delete source or destination volumes](cross-region-replication-delete.md#delete-source-or-destination-volumes).
17+
> If the volume you want to delete is in a replication relationship, follow the steps in [Delete source or destination volumes](cross-region-replication-delete.md#delete-source-or-destination-volumes).
18+
19+
> [!IMPORTANT]
20+
> If the volume you're deleting isn't protected by Azure NetApp Files backup, and no cross-zone or cross-region replicas exist, it is **not possible** to recover the volume after deletion. Any volume snapshots are deleted along with the volume deletion.
1821
1922
## Before you begin
2023

@@ -31,4 +34,5 @@ This article describes how to delete an Azure NetApp Files volume.
3134
## Next steps
3235

3336
* [Delete volume replications or volumes](cross-region-replication-delete.md)
37+
* [Restore a backup to a new volume](backup-restore-new-volume.md)
3438
* [Troubleshoot volume errors for Azure NetApp Files](troubleshoot-volumes.md)

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
2121

2222
* [Secure object REST API access using Azure Key Vault certificates and credentials](object-rest-api-access-configure.md) (preview)
2323

24-
Azure NetApp Files now supports Azure Key Vault–based certificates and credentials for the object REST API, enabling secure, S3‑compatible access to volumes. Certificates can be generated and stored directly in Azure Key Vault and automatically retrieved during bucket creation, while S3 access credentials are securely managed in Key Vault, eliminating the need to manually upload or store sensitive information.
24+
Azure NetApp Files now supports Azure Key Vault–based certificates and credentials for the object REST API, enabling secure, S3‑compatible access to volumes. Certificates can be generated and stored directly in Azure Key Vault and automatically retrieved during bucket creation, while access credentials are securely managed in Key Vault, eliminating the need to manually upload or store sensitive information.
2525

26-
This native integration with Azure Key Vault simplifies certificate lifecycle management, centralizes certificate and credential storage, strengthens security, and aligns Object REST API access with enterprise key and credential management best practices.
26+
This native integration with Azure Key Vault simplifies certificate lifecycle management, centralizes certificate and credential storage, strengthens security, and aligns object REST API access with enterprise key and credential management best practices.
2727

2828
* [Storage with cool access enhancement](cool-access-introduction.md#throughput-for-premium-and-ultra-service-levels) for Premium and Ultra service levels (preview)
2929

articles/bastion/.openpublishing.redirection.bastion.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,11 @@
44
"redirect_url": "/azure/bastion/configure-host-scaling",
55
"source_path_from_root": "/articles/bastion/configure-host-scaling-powershell.md",
66
"redirect_document_id": true
7+
},
8+
{
9+
"redirect_url": "/troubleshoot/azure/bastion/welcome-azure-bastion",
10+
"source_path_from_root": "/articles/bastion/troubleshoot.md",
11+
"redirect_document_id": false
712
}
813
]
914
}

0 commit comments

Comments
 (0)