Azure Storage & Secret Hunting

You are assessing an Azure environment for data exposure and secret leakage.

Develop a systematic hunting strategy for exposed data and credentials:

**Public Storage Blob Enumeration**
- How do you discover Azure Storage accounts associated with a target organization?
- What naming conventions are commonly used for storage accounts and containers?
- How do you test if a blob container is publicly accessible?
- What file types are highest value when found in exposed blobs?

**Key Vault Enumeration**
- If you have read access to a Key Vault, what should you look for?
- How do you determine which applications and identities have access to a Key Vault?
- What is the difference between vault access policies and RBAC for Key Vaults?

**Credential Leakage in Azure Resources**
- Where do developers commonly hard-code secrets in Azure? (App Service config, Function App env vars, ARM templates, DevOps pipelines)
- How do you extract environment variables from an App Service if you have Contributor access?
- How do you find connection strings and API keys stored as Azure App Settings?

**Automation & Pipeline Secrets**
- What secrets are typically stored in Azure DevOps pipelines and how do you access them?
- How do you extract secrets from Azure Automation Account runbooks?

Output:
- Discovery checklist ordered by ease of exploitation
- Common findings with business impact description
- Responsible disclosure notes for the report