Coverage · Azure

Find the weak points in your Azure cloud.

Spot risky access, exposed resources and configuration gaps across your Azure environment. Give your team the evidence and guidance to act, with read-only access.

Read-only checks
50
Areas covered
7
Changes we make
0
Scan duration
Varies

The problem

Know which cloud settings need attention.

Azure settings are spread across services, subscriptions and portals. Tenant Strike brings the findings together, explains why they matter, and points your administrator toward the next step. Your team keeps control of every change.

What we look at

50 checks across 7 service categories.

  • Access & permissions

    Who owns each subscription, overly broad roles, outside guests with access, stale app credentials, and whether sensitive access is time-limited.

  • Storage

    Storage left open to the public, anonymous access, unencrypted transfers, weak firewall rules, recovery (soft delete), and private connections.

  • Servers

    Servers exposed directly to the internet, missing disk encryption, antivirus coverage, out-of-date operating systems, and insecure web apps.

  • Networking

    Remote-access (SSH/RDP) and database ports open to the internet, overly permissive rules, public addresses, DDoS protection, and web firewalls.

  • Databases

    Databases reachable from anywhere, weak sign-in controls, missing encryption, and whether threat protection is turned on.

  • Logging & alerts

    Whether activity is being recorded, kept long enough, and whether anyone gets alerted when something critical changes.

  • Security policy

    Whether Microsoft's own security baseline and threat-protection plans are switched on, and which high-priority recommendations are open.

How it works

From read-only access to a clear Azure report.

  1. 01

    Give read-only access

    In the Azure portal, give the Tenant Strike app Microsoft's built-in 'Reader' role — their own read-only role. Follow the setup guidance to grant access to your chosen scope.

  2. 02

    Pick your subscriptions

    Tenant Strike shows the subscriptions it can see. You choose which ones to scan — one, some, or all. It's never all-or-nothing.

  3. 03

    Scan

    Review the available Azure checks alongside your Microsoft 365 findings. Results are grouped by subscription, with assessment gaps clearly identified.

Sample finding

See the finding and the next step.

Review the severity, affected resource and recommended action. Use the guidance and supporting links to investigate and make the change with your administrator.

Storage account allows anonymous blob access

CRITICALFAIL

Subscription: Production · East US

The storage account acmestorageprod001 allows anonymous public access (allowBlobPublicAccess=true). Review the account and container settings to determine whether business data is publicly accessible.

Fix path

Set allowBlobPublicAccess to false at the account level. Portal: Storage account → Configuration → Allow Blob anonymous access → Disabled → Save.

Attacker’s View™

This setting is a starting point for investigation. Check which containers permit public access, what data they hold, and whether that exposure is intended. Prioritize any sensitive data and review the supporting evidence with your administrator.

Microsoft Learn — Prevent anonymous public read access →

Related coverage

Give read-only access and scan your first subscription.

Pro includes 50 Azure checks alongside Microsoft 365 and Vulnerability Watch. Connect with your Azure administrator.