Skip to content

Commit d67d214

Browse files
Merge pull request #309461 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-12 18:00 UTC
2 parents 2db7edb + cb5477d commit d67d214

34 files changed

Lines changed: 363 additions & 189 deletions

articles/api-management/enable-availability-zone-support.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ When you create a new API Management instance in the **Premium** tier in a regio
3838
> [!IMPORTANT]
3939
> To ensure the reliability of your API Management instance, use the automatic availability zone support. To achieve maximum zone redundancy, deploy a minimum of two units in each region where you deploy API Management to ensure that an availability zone outage doesn't affect your instance. For more information, see [Reliability in API Management](../reliability/reliability-api-management.md).
4040
41-
## Manual availability zone support
41+
### Manual availability zone support
4242

43-
We recommend automatic availability zone configuration, but you can manually configure or update availability zones for an existing location of your API Management instance. The following sections provide steps for manually configuring zone redundancy on an existing location of your API Management instance, depending on whether the instance is injected in a virtual network.
43+
We recommend automatic availability zone configuration in the Premium tier, but you can manually configure or update availability zones for an existing location of your API Management instance. The following sections provide steps for manually configuring zone redundancy on an existing location of your API Management instance, depending on whether the instance is injected in a virtual network.
4444

4545
> [!NOTE]
4646
> You can optionally enable a *zonal* configuration, where the API Management instance or location is deployed in a single availability zone. Because it doesn't provide resiliency to an outage in that zone, this configuration generally isn't recommended except for specific scenarios. For more information, see [Reliability in API Management](../reliability/reliability-api-management.md).

articles/azure-app-configuration/emulator-overview.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: zhiyuanliang-ms
77
ms.author: zhiyuanliang
88
ms.service: azure-app-configuration
99
ms.topic: overview
10-
ms.date: 08/12/2025
10+
ms.date: 11/12/2025
1111
#Customer intent: I want to learn about how to Azure App Configuration emulator for local development.
1212
---
1313

@@ -26,8 +26,7 @@ The following table lists the features supported by the latest Azure App Configu
2626
| Web UI | Available |
2727
| Anonymous Authentication | Available |
2828
| [HMAC Authentication](./rest-api-authentication-hmac.md) | Available |
29-
| [Entra Id Authentication](./rest-api-authentication-azure-ad.md) | WIP |
30-
| .NET Aspire Integration | WIP |
29+
| .NET Aspire Integration | Available |
3130

3231
| API | Status |
3332
| ---------------------------------------------------------------- | --------- |
@@ -45,7 +44,7 @@ The following table lists the features supported by the latest Azure App Configu
4544
Use [Docker](https://hub.docker.com/) to pull the latest [App Configuration emulator image](https://mcr.microsoft.com/artifact/mar/azure-app-configuration/app-configuration-emulator/about) by using the following console command:
4645

4746
```console
48-
docker pull mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.0-preview
47+
docker pull mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.2
4948
```
5049

5150
### [GitHub](#tab/github)
@@ -81,7 +80,7 @@ The following command runs the App Configuration emulator Docker image. The `-p
8180
docker run -d -p 8483:8483 \
8281
-e Tenant:AnonymousAuthEnabled=true \
8382
-e Authentication:Anonymous:AnonymousUserRole=Owner \
84-
mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.0-preview
83+
mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.2
8584
```
8685

8786
If you want to have persisted data for the emulator, you can use a [bind mount](https://docs.docker.com/engine/storage/bind-mounts).
@@ -91,7 +90,7 @@ docker run -d -p 8483:8483 \
9190
-v "C:\aace:/app/.aace" \
9291
-e Tenant:AnonymousAuthEnabled=true \
9392
-e Authentication:Anonymous:AnonymousUserRole=Owner \
94-
mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.0-preview
93+
mcr.microsoft.com/azure-app-configuration/app-configuration-emulator:1.0.2
9594
```
9695

9796
### [GitHub](#tab/github)

articles/azure-netapp-files/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -489,6 +489,8 @@
489489
href: create-cross-zone-replication.md
490490
- name: Configure cross-zone-region replication
491491
href: cross-zone-region-replication-configure.md
492+
- name: Configure ransomware protection
493+
href: ransomware-configure.md
492494
- name: Relocate
493495
items:
494496
- name: Relocate volume to another region

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,11 +78,14 @@ Before creating an SMB volume, you need to create an Active Directory connection
7878
* **Network features**
7979
In supported regions, you can specify whether you want to use **Basic** or **Standard** network features for the volume. See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.
8080

81+
* **Availability Zone**
82+
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
83+
8184
* **Encryption key source**
8285
Select Microsoft Managed Key or Customer Managed Key. See [Configure customer-managed keys for Azure NetApp Files volume encryption](configure-customer-managed-keys.md) and [Azure NetApp Files double encryption at rest](double-encryption-at-rest.md) to learn more about this field.
8386

84-
* **Availability zone**
85-
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
87+
* **Advanced Ransomware Protection**
88+
Select **Enabled** to configure ransomware threat detection alerts for your volumes. For more information, see [Configure advanced ransomware protection](ransomware-configure.md).
8689

8790
* If you want to apply an existing snapshot policy to the volume, select **Show advanced section** to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu.
8891

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,14 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
9898
* **Network features**
9999
In supported regions, you can specify whether you want to use **Basic** or **Standard** network features for the volume. See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.
100100

101+
* **Availability zone**
102+
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
103+
101104
* **Encryption key source**
102105
You can select Microsoft Managed Key or Customer Managed Key. See [Configure customer-managed keys for Azure NetApp Files volume encryption](configure-customer-managed-keys.md) and [Azure NetApp Files double encryption at rest](double-encryption-at-rest.md) about using this field.
103106

104-
* **Availability zone**
105-
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
107+
* **Advanced Ransomware Protection**
108+
Select **Enabled** to configure ransomware threat detection alerts for your volumes. For more information, see [Configure advanced ransomware protection](ransomware-configure.md).
106109

107110
* If you want to apply an existing snapshot policy to the volume, select **Show advanced section** to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu.
108111

articles/azure-netapp-files/azure-netapp-files-introduction.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,7 @@ Azure NetApp Files provides built-in data management and security capabilities t
8989
| Azure platform integration and compliance certifications | Compliance with regulatory requirements and Azure platform integration. | Adheres to Azure standards and regulatory compliance and ensures audit and governance completion.
9090
| Azure Identity & Access Management (IAM) | Azure role-based access control (RBAC) allows you to manage permissions for resources at any level. | Simplifies access management and improves compliance with Azure-native RBAC, empowering you to easily control user access to configuration management.
9191
| AD/LDAP authentication, export policies, and access control lists (ACLs) | Authenticate and authorize access to data by using existing AD/LDAP credentials and allow for the creation of export policies and ACLs to govern data access and usage. | Prevents data breaches and ensures compliance with data security regulations, with enhanced granular control over access to data volumes, directories, and files. |
92+
| Built-in ransomware protection | Azure NetApp Files advanced ransomware protection can be enabled at the volume level, using machine learning to observe deviations in your volume behaviors that resemble ransomware attacks. | Ransomware protection enables you to stay vigilant and attuned to aberrations in your workloads, improving the resiliency of your applications with alerts customized to the specific patterns of your volumes. |
9293

9394
These features work together to provide a comprehensive data management solution that helps to ensure that your data is always available, recoverable, and secure.
9495

articles/azure-netapp-files/azure-netapp-files-metrics.md

Lines changed: 5 additions & 1 deletion
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: concept-article
8-
ms.date: 11/20/2025
8+
ms.date: 11/25/2025
99
ms.author: anfdocs
1010
# Customer intent: As a cloud storage administrator, I want to analyze performance and usage metrics for Azure NetApp Files, so that I can optimize storage provisioning and ensure efficient operation of my storage resources.
1111
---
@@ -185,6 +185,10 @@ Subscription quota metrics display subscription-level quotas relative to the imp
185185

186186
Total number of short-term clone volumes per subscription
187187

188+
- *Ransomware protection volumes per subscription*
189+
190+
Total number of volumes protected with advanced ransomware protection per subscription
191+
188192
- *Total TIBs per subscription*
189193

190194
Total regional capacity per subscription

articles/azure-netapp-files/create-volumes-dual-protocol.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,11 +111,15 @@ To create NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volu
111111
* **Network features**
112112
In supported regions, you can specify whether you want to use **Basic** or **Standard** network features for the volume. See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.
113113

114+
* **Availability zone**
115+
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
116+
114117
* **Encryption key source**
115118
You can select `Microsoft Managed Key` or `Customer Managed Key`. See [Configure customer-managed keys for Azure NetApp Files volume encryption](configure-customer-managed-keys.md) and [Azure NetApp Files double encryption at rest](double-encryption-at-rest.md) about using this field.
116119

117-
* **Availability zone**
118-
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
120+
* **Advanced Ransomware Protection**
121+
Select **Enabled** to configure ransomware threat detection alerts for your volumes. For more information, see [Configure advanced ransomware protection](ransomware-configure.md).
122+
119123

120124
* If you want to apply an existing snapshot policy to the volume, select **Show advanced section** to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu.
121125

28.2 KB
Loading
90.3 KB
Loading

0 commit comments

Comments
 (0)