Azure File Share provides fully managed cloud file shares accessible via SMB and NFS protocols. Cloudmon monitors capacity, snapshot counts, transaction volume, and latency across all your File Share resources.
Azure File Share is used to replace or supplement on-premises file servers, providing shared access to files from anywhere without the need to manage infrastructure. Cloudmon automatically discovers all File Share resources linked to your monitored Azure account. Navigate to Cloud → Azure → [Select Account] → Azure File Share to view the full list. Click any resource name to open its detailed monitoring view.
The list displays all discovered File Share resources with the following details:
| Column | Description |
| Name | The name of the resource as configured in Azure. |
| Kind | The storage account type, for example, StorageV2. |
| Resource Group | The Resource Group this resource belongs to. |
| Location | The Azure region where the resource is deployed. |
| Creation Time | The date and time the resource was created. |
| Size | The replication and performance tier, for example, Standard_LRS or Standard_GZRS. |
| Actions | Toggle to enable or disable monitoring, and an edit icon to update the configuration. |
Selecting a File Share resource opens its detail page. The overview displays key details, including the Primary Location, SKU, Resource Group, Subscription, Status, and Monitoring Status, among other configuration and availability information.
Cloudmon collects key metrics such as File Capacity, File Share Count, File Share Snapshot Count, File Share Capacity Used, Transactions, Ingress, and Egress, among other performance indicators including snapshot size, latency, and availability. These are displayed as time-series charts for the selected time period.
Lists all file shares within the selected resource. Each entry shows:
| Column | Description |
| Name | The name of the file share. |
| Access Tier | The access tier configured for the file share, for example, Transaction Optimised, Hot, or Cool. |
| Quota (GiB) | The maximum storage size provisioned for the file share, in gibibytes. |
| Lease Status | Indicates whether the file share is currently locked, for example, Unlocked. |
| Lease State | The current state of the lease, for example Available. |
| Last Modified | The timestamp of the most recent modification to the file share. |
Surfaces actionable insights from Azure Advisor specific to this File Share resource. Recommendations may include enabling soft delete to protect file shares from accidental deletion, switching to a more cost-effective access tier based on usage patterns, or enabling large-file share support for workloads requiring more than 5 TiB of capacity. Each recommendation shows its impact level and category across Cost, Security, High Availability, Performance, and Operational Excellence.
| Symptom | Likely Cause | Fix |
| Resource not appearing in the list | Discovery has not run since the resource was created, or the service was not selected during Azure account setup | Trigger a manual rediscovery from Settings → Monitoring → Probes → Azure, or edit the account to enable the missing service |
| Metrics showing no data | The resource may have had no activity during the selected time window, or polling has not completed yet | Wait for the next polling cycle or reduce the selected time range to a period with known activity |
| Availability dropping below 100% | The storage service experienced a transient error or outage during the monitored period | Review the metric timeline to identify when the drop occurred and cross-reference with Azure Service Health |
| Alarms not triggering as expected | Alarm thresholds may not be configured for this resource | Go to Settings and add or review alarm triggers |
| File Share Capacity Used is near the Quota limit | The file share is approaching its provisioned size limit | Increase the Quota in the Azure portal, or delete unused files to free capacity |
| Snapshot Count is growing unexpectedly | Automated snapshot policies may be creating snapshots without a retention limit | Review snapshot policies in the Azure portal and set an appropriate retention window |