Azure App Service SSL Not Enforced
The app still answers on plain HTTP, so credentials and session cookies can be read in transit.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enforce HTTPS on App Service.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Function Apps on Azure
- The fix, by hand
- App Service → the resource → TLS/SSL settings (Settings group).
- Set HTTPS Only to On.
- Set Minimum Inbound TLS Version = 1.2 (or 1.3 if all clients support it).
- Under Bindings, attach a managed certificate (free App Service Managed Certificate) or import from Key Vault for custom domains.
- Test the app over plain HTTP. It should now 301 to HTTPS.
- Update any monitoring probes / CI checks that still hit http://.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1311- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.