You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/monitor-app-configuration.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,12 +49,12 @@ For more information about App Configuration metrics, see [supported metrics for
49
49
Azure App Configuration logs include activity logs and resource logs.
50
50
51
51
### Activity logs
52
-
[Activity logs](/azure/azure-monitor/reference/tables/azureactivity) provide insight into subscription-level events and show management plane activities (create, update, delete operations on your App Configuration resource). However, they don't capture data plane operations like key-value reads and writes. You can view them in the **Activity log** blade. Alternatively, follow the steps in [Log collection](#log-collection) to route them to Log Analytics workspace for more complex querying scenarios.
52
+
[Activity logs](/azure/azure-monitor/reference/tables/azureactivity) provide insight into subscription-level events and show all control plane CRUD operations for your App Configuration resource. However, they don't capture data plane operations like key-value reads and writes. You can view activity logs in the **Activity log** blade. Alternatively, follow the steps in [Log collection](#log-collection) to route them to a Log Analytics workspace for more complex querying scenarios.
53
53
54
54
### Resource logs
55
55
App Configuration provides two types of resource logs.
56
-
-**Audit logs**: Capture write operations (create, update, delete) on your data plane resources, such as key-values. Audit logs don't include data plane read operations but include management plane operations. Entries are unaggregated. Query them in the **AACAudit** table. For more information, refer to [AACAudit](/azure/azure-monitor/reference/tables/AACAudit).
57
-
-**HTTP request logs**: Capture both read and write operations on your data plane resources, such as key-values. Operations are aggregated for better performance and to reduce log volume. Aggregation is based on HTTP method and status code. Each log entry may represent multiple similar operations within a certain time window. Query them in the **AACHttpRequest** table. For more information, refer to [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest).
56
+
-**Audit logs**: Capture data plane write operations (create, update, and delete), such as key-values modifications, and all control plane CRUD operations. Audit logs don't include data plane read operations. Unlike HTTP request logs, entries of audit logs are not aggregated. Query them in the **AACAudit** table. For more information, refer to [AACAudit](/azure/azure-monitor/reference/tables/AACAudit).
57
+
-**HTTP request logs**: Capture both read and write operations on your data plane resources, such as key-values. Entries of HTTP request logs are aggregated for better performance and to reduce log volume. Aggregation is based on HTTP method and status code. Each log entry may represent multiple requests within a certain time window. Refer to the HitCount field for the number of requests whose logs are aggregated. Query them in the **AACHttpRequest** table. For more information, refer to [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest).
58
58
59
59
#### Log collection
60
60
Metrics and the activity log are collected and stored automatically, and can be routed to other locations by using a diagnostic setting.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/data-protection-disaster-recovery-options.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-ahibbard
6
6
ms.service: azure-netapp-files
7
7
ms.topic: concept-article
8
-
ms.date: 08/28/2025
8
+
ms.date: 03/03/2026
9
9
ms.author: anfdocs
10
10
# Customer intent: "As a data administrator, I want to assess the data protection and disaster recovery options available in Azure NetApp Files, so that I can choose the most effective solutions to ensure data integrity and availability for my organization's needs."
11
11
---
@@ -37,7 +37,7 @@ Azure NetApp Files supports a fully managed backup solution for long-term recove
37
37
### Benefits
38
38
39
39
- Increased productivity, reliably integrated service that is easy to manage and can be set once
40
-
- Application-consistent backups with [AzAcSnap integration](azacsnap-introduction.md)
40
+
- Application-consistent backups with [AzAcSnap integration](azacsnap-introduction.md), [SnapCenter snapshot and backup orchestration](https://www.netapp.com/snapcenter/), or third-party tools
41
41
- Retain daily, weekly, monthly backups for extended periods of time on cost-efficient cloud storage without media management
42
42
43
43
To learn more, see [How snapshots can be vaulted for long-term retention and cost savings](snapshots-introduction.md#how-snapshots-can-be-vaulted-for-long-term-retention-and-cost-savings). To get started with backups, see [Configure policy-based backups for Azure NetApp Files](backup-configure-policy-based.md).
@@ -78,8 +78,8 @@ Choosing the best data protection option for your Azure NetApp Files deployment
78
78
| Use case | In-region solution | Cross-region solution |
79
79
| --- | --- | --- |
80
80
| Ad hoc backup | On-demand snapshots | - |
81
-
| Application consistent data protection | AzAcSnap | - |
82
-
| Data corruption and ransomware protection |Scheduled snapshots| Cross-region replication |
81
+
| Application consistent data protection | AzAcSnap, [SnapCenter](https://docs.netapp.com/us-en/snapcenter/get-started/concept_snapcenter_overview.html)| - |
82
+
| Data corruption and ransomware protection |Advanced ransomware protection| Cross-region replication |
**Error message**: Azure File Share Backup requires a minimum SAS expiration period of 8 hours.
333
+
334
+
**Cause**: If the SAS token expiry is shorter than 8 hours, the Backup service cannot renew the token in time. This leads to authentication failures and can interrupt ongoing backup or restore operations.
335
+
336
+
**Recommended action**: Set the SAS expiry upper limit to 8 hours or more to ensure the Backup service can successfully renew the SAS token and maintain uninterrupted backup and restore activities.
337
+
328
338
## Common policy modification errors
329
339
330
340
### BMSUserErrorConflictingProtectionOperation- Another configure protection operation is in progress for this item
Copy file name to clipboardExpand all lines: articles/migrate/set-discovery-scope.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,11 @@ This article describes how to limit the scope of discovery for servers in VMware
18
18
19
19
When you set up the appliance, it connects to vCenter Server and starts discovery. Before you connect the appliance to vCenter Server, you can limit discovery to vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual servers. To set the scope, you assign permissions on the account that the appliance uses to access the vCenter Server.
20
20
21
+
Watch the following video to learn how to discover on-premises servers running in a VMware environment as part of your migration to Azure.
If you haven't set up a vCenter Server user account that Azure Migrate uses for discovery, do that now for [assessment](tutorial-discover-vmware.md#prepare-vmware) or [agentless migration](migrate-support-matrix-vmware-migration.md#agentless-migration).
@@ -100,7 +132,9 @@ Existing or new caches that match the attributes you select get the reservation
100
132
101
133
- You can update the scope of the reservation through the Azure portal, PowerShell, Azure CLI, or the API.
102
134
103
-
- You can cancel, exchange, or refund reservations with certain limitations. For more information, see [Self-service exchanges and refunds for Azure Reservations](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations).
135
+
## Exchange existing Reservations with Azure Managed Redis
136
+
137
+
You can cancel, exchange, or refund reservations with certain limitations. For more information, see [Self-service exchanges and refunds for Azure Reservations](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations).
Copy file name to clipboardExpand all lines: articles/storage/blobs/network-file-system-protocol-known-issues.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,9 @@ This article describes limitations and known issues of Network File System (NFS)
24
24
25
25
- NFS 3.0 support can't be disabled in a storage account after you enable it.
26
26
27
-
- Geo-redundant storage (GRS), Geo-zone-redundant storage (GZRS), and Read-access geo-redundant storage (RA-GRS) redundancy options aren't supported when you create an NFS 3.0 storage account.
27
+
- Geo-Redundant Storage (GRS) is supported only for unplanned failover scenarios and isn't supported for planned failover.
28
+
29
+
- Geo-zone-redundant storage (GZRS) and Read-access geo-redundant storage (RA-GRS) redundancy options aren't supported when you create an NFS 3.0 storage account.
28
30
29
31
- Access control lists (ACLs) can't be used to authorize an NFS 3.0 request. In fact, if the ACL or a blob or directory contains an entry for a named user or group, that file becomes inaccessible on the client for nonroot users. You have to remove these entries to restore access to nonroot users on the client. For information about how to remove an ACL entry for named users and groups, see [How to set ACLs](data-lake-storage-access-control.md#how-to-set-acls).
0 commit comments