Skip to main content

Subscription Activity Logs Archived (Azure)

This test checks whether your Azure subscription has diagnostic settings configured to archive subscription-level Activity Logs to a valid Storage Account.

Upendra Varma avatar
Written by Upendra Varma
Updated over a month ago

What this test does

This test connects to your Azure subscription via the ComplyJet integration and verifies whether subscription-level Activity Logs are being archived to a valid Azure Storage Account.

Specifically, the test checks:

  1. If one or more Diagnostic Settings exist at the subscription scope.

  2. If those diagnostic settings have logs configured (the monitor only checks that logs exist, not which categories).

  3. If at least one setting includes a Storage Account destination.

  4. If the referenced Storage Account still exists and is valid in Azure.

If a valid storage account is found, the test passes and reports the storage account name.
If no valid diagnostic setting is found, or the storage account is missing, the test fails.
If the Azure API cannot be queried, the test reports an exception.

How to fix this (Remediation)

Follow these steps in the Azure Portal:

  1. Log in to the Azure Portal.

  2. In the menu/search bar, select Subscriptions and choose the subscription you want to configure.

  3. Go to Activity log. At the top of the page, click Export Activity Logs.

  4. On the Diagnostic settings page:

    • If a setting already exists routing logs to a storage account in the same subscription, verify it points to a valid account.

    • If none exists, click Add diagnostic setting.

  5. Provide a descriptive name (e.g., Subscription Activity Logs).

  6. Select the log categories you want (best practice: include Administrative, Security, ServiceHealth, Alert, Recommendation, Policy, Autoscale, ResourceHealth).

  7. Under Destination details, select Archive to a storage account.

    • Choose an existing storage account in the same subscription, or create a new one.

  8. Click Save.

  9. Return to ComplyJet and re-run the test to confirm logs are being archived successfully.

Did this answer your question?