Skip to main content

Verification

Use this checklist to confirm that your Azure integration is healthy and that Cloudaware is ingesting the expected data.

Check Directory and Subscription Status in Cloudaware​

In Cloudaware, go to Admin (Admin Console):

  1. Select Microsoft Azure → CONFIGURED.
  2. On the Active Directories tab:
    • Confirm that the Azure Active Directory tenant you added shows a green status indicator.
    • If the status is red, review the error message tooltip and see Troubleshooting.
  3. On the Subscriptions tab:
    • Confirm that each onboarded subscription is present and shows a green status.
    • Investigate any Untracked or red‑status subscriptions; revisit suggestions in Troubleshooting.

Validate Sample Resources in CMDB​

In Cloudaware CMDB Navigator:

  • Navigate to MICROSOFT AZURE → COMPUTE → Virtual Machines.
    • Confirm that a representative set of virtual machines from your subscriptions is present.
    • Verify key fields such as subscription, resource group, region, power state, and tags.
  • Navigate to STORAGE, NETWORKING, and any other categories relevant to your environment.
    • Spot‑check that new or recently changed resources in the Azure portal appear in Cloudaware after the next discovery run.

If Key Vaults, AKS clusters, reservations, Intune devices, or App Service configuration are in scope, verify that their corresponding objects are present; if not, revisit the extended permissions in Least-Privilege Policies.

Confirm Freshness of Data​

For selected objects (for example, a virtual machine or storage account):

  • Check the Created By timestamp in Cloudaware (for initial setup).

    tip

    Allow initial collection latency for as little as 5 minutes or as long as 24 hours, depending on scope, connector scheduling, and platform load.

  • Check the Last Modified By timestamp to compare with the time of your most recent changes in the Azure portal. Prefer resources where a known recent change occurred (e.g., tag update, resize, configuration change) to view updates in the CMDB within the expected processing window.

    note

    Last Modified By in Cloudaware can’t be treated as a freshness SLA for static or rarely changing resources.

If timestamps are stale across many objects, there may be an integration or scheduling issue.

Validate Reporting Behavior​

Once inventory looks correct:

  • Open the CMDB list view for the relevant resource type and confirm that the default list views organize resources as expected, including populated columns for name, resource ID, and any available telemetry or cost data.
  • Open cost, security, or operational dashboards that include Microsoft Azure data and verify that counts and totals are reasonable.

When to Contact Support​

Contact Cloudaware Support at support@cloudaware.com with screenshots and example resource IDs if:

  • A directory or subscription remains red after you have confirmed credentials and RBAC.
  • Specific services (for example, AKS or Key Vault) remain empty despite correct permissions.
  • Data appears significantly delayed or inconsistent across regions or subscriptions.