CloudDocs Structure
  • 06 Nov 2020
  • 1 Minute to read
  • Contributors
  • Dark
  • PDF

CloudDocs Structure

  • Dark
  • PDF

This article will brief you with what CloudDocs documentation holds for Azure Subscription usage as in readable output.

Executive Summary

When said document ‘it's vast’ is one thing that strikes our mind, which ultimately pulls time in reading all of it. But with the executive summary, readers can rapidly become acquainted with a precise document without having to read it all. Thus, saving time, effort, and energy.

What does an executive summary of CloudDocs contain?

  1. It contains the subscription details for which you generated the document, along with date-time.
  2. It has information about the expenses spent on total subscription usage, and resource group/location wise charges.
  3. It holds data on the exact location of resources, the resource groups, the resource types for that subscription.

Exec summary.png

Added -Executive Summary.png

Billing & Metrics

This section within CloudDocs is to visualize and acquire a descriptive analysis of your billing and metrics information for Azure Subscription usage by way of chart representation.
Not just resource-group/location/type-wise illustration, besides specifics on SQL server usage, responsive time of the apps used, and a lot more, which helps in a better understanding of the revenue cycle and provides insights to have the best gross profit.


Billing and Metrics.png

Resource Details

It represents details of the type of resources used in the subscription, where the resource’s id, name, resource type, resource group, location, properties, tags and many more will be listed respectively.

Resource Details 2.png

Added - Resource Details.png


(Applicable only for Document360 platform)
Archives in CloudDocs are used to locate the previously generated document that remains important and must be retained for future reference. Date-time in archives is the factor that lets us differentiate between the different instances of the cloud document.

Resource Details 3.png

We'd love to hear your thoughts
Please visit our feedback system to suggest new Features or Enhancements. You can also take a look at our Roadmap

Was this article helpful?

What's Next