Azure Storage Accounts are general-purpose storage containers that can host Blob, Table, File Share, and Queue services within a single account. Cloudmon monitors usage, request volume, latency, and availability to give you a full picture of your storage health.
Cloudmon automatically discovers all Azure Storage Accounts linked to your monitored Azure account. Navigate to Cloud → Azure → [Select Account] → Azure Storage Account to view the full list. Click any account name to open its detailed monitoring view.
The list displays all discovered storage accounts 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 storage account opens its detail page. The overview displays configuration and status information, including the account ID, Access Tier, minimum TLS version, DNS Endpoint Type, Provisioning State, Primary Location, SKU, and Public Network Access status. Security settings such as Shared Key Access, Cross Tenant access, OAuth authentication policy, and HTTP Traffic settings are also shown, alongside the Primary Endpoints for Blob, Queue, and Table services, Encryption details, and Network Rule Set configuration.
Displays a summary count of Blob Containers, Tables, File Shares, and Queues within the account. Each resource type is listed in a searchable table. For Blob Containers, the table shows the container name, Lease Status, Lease State, Legal Hold status, and Last Modified timestamp.
Cloudmon collects performance data, including Used Capacity, Transactions, Ingress, Egress, Success Server Latency, Success E2E Latency, and Availability, among other metrics. These are displayed as time-series charts for the selected time period.
Surfaces actionable insights from Azure Advisor specific to this storage account. Recommendations may include enabling zone redundancy to improve high availability, enforcing a minimum TLS version to strengthen security, restricting public network access to reduce exposure, or switching to a more cost-effective replication tier based on actual usage. Each recommendation shows its impact level (High, Medium, or Low) 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 |
| High Success E2E Latency | Network conditions or client-side issues are adding latency beyond the server processing time | Compare Success Server Latency and Success E2E Latency — a large gap points to network or client-side delays rather than a storage issue |