Azure
Public Exposure Audit
Every publicly-reachable Azure resource — storage, SQL, VMs, App Gateways — critical vs expected.
Live preview — demo data
Same idea on another cloud
What this pane shows
A cross-service roll-up: public Storage accounts, SQL databases with public-network-access enabled, Virtual Machines with public IPs, public Function Apps, public Application Gateways and Load Balancers. Critical exposures are surfaced first; expected ones (web frontends) are grouped separately.
Key use cases
- Find a database, queue or storage resource that's accidentally public.
- Confirm intentional public-facing infrastructure has the expected configuration.
- Audit external attack surface during a security review.
- Catch a new service launching with the public-access default still on.
How to embed
lp.js is the single-entry loader: it injects the shared LightPane runtime
(and sd-embed.css) once per page. Add this pane's own stylesheet and script;
the pane mounts itself wherever the matching <div> is in the DOM.
<!-- In <head> — this pane's stylesheet -->
<link rel="stylesheet" href="https://lightpane.io/_pane-tests/azure/public-exposure/public-exposure.css">
<!-- Your access key (inline, or set window.lpEmbed.accessKey from your own JS) -->
<script>window.lpEmbed = { accessKey: "<your-access-key>" };</script>
<!-- Where the pane should appear -->
<div class="lp-azure-public-exposure-panel" data-lp-account="<your-account-alias>"></div>
<!-- Before </body> — shared loader + this pane's script -->
<script src="https://lightpane.io/embed/lp.js"></script>
<script src="https://lightpane.io/_pane-tests/azure/public-exposure/public-exposure.js" defer></script>
Tier
Available on Explorer and above.
Build notes
No outstanding build notes.