Ensure Azure Functions uses managed identity
Function Apps should use managed identities instead of storing credentials.
Security Impact
Stored credentials in configuration can be exposed through various attack vectors.
How to Remediate
Enable system-assigned or user-assigned managed identity for Function App.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your Azure environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Azure Functions resources across your Azure subscriptions every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- azure-functions-2
- Service
- Azure Functions
- Category
- Identity Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your Azure environment for this and 160+ other security checks.
Start Free TrialRelated Azure Functions Checks
View all checksEnsure Azure Functions uses HTTPS only
Ensure Azure Functions has diagnostic logging enabled
Ensure Azure Functions uses latest runtime version
Ensure Azure Functions uses minimum TLS 1.2
Ensure Azure Functions has CORS configured properly