Configuring State-in-Time Data Collection for Azure Files
This topic describes how to enable State-in-Time data collection for an Azure Files monitoring plan in Netwrix Auditor, configure the monitoring scope using omit lists, and set up optional Azure diagnostic settings for activity-based reports.
Note: By default, Azure Files permission reports display only users and groups that you migrated to Entra ID from a local Windows domain and added directly to role-based access control (RBAC) or New Technology File System (NTFS) permissions. The reports don't display users who gain access through built-in (well-known) domain or Azure groups. To see all accounts that receive access rights through any groups, enable Active Directory integration. See Configuring Active Directory integration (optional).
Prerequisites
- An Azure Files monitoring plan must already exist in Netwrix Auditor Azure Files Configuration Overview
- The monitoring plan must target Azure file shares mounted via SMB (Netwrix Auditor doesn't support Azure File Sync or NFS).
- The service account that the monitoring plan uses must have sufficient permissions to enumerate file and folder ACLs on the Azure file shares.
- To collect "Times Accessed" data for the Excessive Access Permissions report, you need an Azure storage account configured to receive diagnostic logs.
Enabling State-in-Time data collection
To enable State-in-Time data collection in an Azure Files monitoring plan:
- In Netwrix Auditor, navigate to Configuration → Monitoring Plans.
- Select the Azure Files monitoring plan and click Edit.
- On the General tab, locate the State-in-Time section.
- Select the Collect data for state-in-time reports checkbox.
- (Optional) Click Modify in the Schedule section to customize the snapshot collection schedule. By default, Netwrix Auditor collects snapshots daily.
- Click Save to apply the changes.
After you save the monitoring plan, Netwrix Auditor begins collecting State-in-Time snapshots on the configured schedule.
Note: Netwrix Auditor collects the first snapshot at the next scheduled run. Reports won't contain data until then.
Configuring Active Directory integration (optional)
By default, Azure Files permission reports display only users and groups that you migrated to Entra ID from a local Windows domain and added directly to RBAC or NTFS permissions. The reports don't display users who gain access through built-in (well-known) domain or Azure groups. If your environment uses on-premises Active Directory (AD DS), you can provide read-only AD credentials so that Netwrix Auditor can:
- Resolve display names for on-premises accounts not synced to Microsoft Entra ID.
- List individual members of on-premises AD groups (including members of nested groups, resolved transitively) as separate rows in permission reports.
If you don't provide credentials, report output remains identical to earlier versions — this capability is optional and additive.
To configure Active Directory integration:
- In Netwrix Auditor, navigate to Configuration → Monitoring Plans.
- Select the Azure Files monitoring plan and click Edit.
- Open a monitored item (Azure Subscription or Azure Storage Account) and click Edit.
- Go to the Active Directory Integration tab. (The Learn more… link on this tab points to this section.)
- Turn on the toggle under Specify Active Directory account.
- In the User name field, enter an AD account with read access to Active Directory. Use the format
domain\useroruser@domain.local. - Enter the Password for the account.
- Click Save.
Note: If Netwrix Auditor can't authenticate with the configured AD account, it records a collection error in the System Health log and continues snapshot collection using cloud-resolved identities only. Netwrix Auditor records transient AD connectivity issues as warnings and doesn't stop collection for these issues.
Configuring the monitoring scope (omit lists)
Use omit lists to exclude specific folders or files from State-in-Time data collection, reducing collection time and storage requirements.
Netwrix Auditor for Azure Files supports three types of omit lists:
| Omit list type | Scope |
|---|---|
| All | Excludes objects from all data collection (activity and State-in-Time) |
| State-in-Time | Excludes objects from State-in-Time data collection only |
| User Activity | Excludes objects from activity data collection only |
Configuring omit lists in the Netwrix Auditor UI
- Open the Azure Files monitoring plan in edit mode.
- Navigate to the Scope tab.
- Click Omit List and specify the Universal Naming Convention (UNC) paths to exclude.
- Select the appropriate list type: All, State-in-Time, or User Activity.
- Save the monitoring plan.
Using omit list text files
You can also define omit lists using plain text files:
- Create a
.txtfile with one UNC path per line.- Example:
\\storageaccount.file.core.windows.net\share\SystemFolder\\storageaccount.file.core.windows.net\share\Temp
- Example:
- Place the file in the appropriate location or specify its path in the monitoring plan scope settings.
- Restart the data collection service to apply changes.
Configuring Azure diagnostic settings (optional)
The Times Accessed column in the Excessive Access Permissions in Azure Files report requires Azure diagnostic settings. Without diagnostic settings, "Times Accessed" defaults to 0 for all objects. Configuring Diagnostic Settings
Note: The current version supports only blob storage as the destination, not Event Hub or Log Analytics Workspace.
Schedule management and historical snapshots
Customizing the snapshot schedule
By default, Netwrix Auditor collects State-in-Time snapshots daily. To customize the schedule:
- Edit the Azure Files monitoring plan.
- In the State-in-Time section, click Modify.
- Select the days of the week for snapshot collection.
- Save the changes.
Importing historical snapshots
Historical snapshots let you generate reports for past dates. A Global administrator must import historical snapshots.
To import a historical snapshot:
- In Netwrix Auditor, go to Configuration → Monitoring Plans.
- Select the Azure Files monitoring plan.
- In the State-in-Time section, click Manage next to Historical snapshots.
- Select the snapshots you want to import.
- Click Import.
Note: Historical snapshot import isn't available for Office 365 data sources.