Align the AzAcSnap working directory with its override configuration

Source facts

AzAcSnap’s .azacsnaprc override file must be in the current working directory from which the tool is executed. Microsoft introduced this file in version 8.

For AzAcSnap 11b and later, the source documents AZURE_ENVIRONMENT as the cloud-management selector. The older AZURE_MANAGEMENT_ENDPOINT setting applies only to 9a, 10, and 10a and must not be set for version 11 or later. Since 9a, the documented overrides can also be supplied as environment variables. Microsoft Learn.

Applicability

Record the installed tool version, launching account, working directory, and intended Azure cloud. Compare interactive and scheduled invocation settings without assuming they start in the same place. Keep the tool’s global override file distinct from its workload configuration.

DSE recommendation

DSE recommends making the launch context part of the approved operational record. Use an explicit working directory and review the relevant environment with the automation owner. Remove assumptions carried from an older version’s setup notes only through an approved configuration change, and keep credentials out of diagnostic captures.

Verification

Run a permitted non-destructive configuration or connectivity test through each intended invocation path. Compare the actual directory, applicable selector, and observed management destination. Investigate differences before enabling scheduled backups; a successful interactive test does not by itself verify the scheduler’s configuration context.

Official references

Microsoft Learn: Tips for using Azure Application Consistent Snapshot tool for Azure NetApp Files | Microsoft Docs. Source retrieved September 9, 2026.