Microsoft Dev Tunnels
- Free allowance
- Free with an account; the Dev tunnels limits table sets 5 GB of bandwidth per user, reset monthly.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quota5 GB of bandwidth per user, reset monthly
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | Free with an account; the Dev tunnels limits table sets 5 GB of bandwidth per user, reset monthly. unit GB; metered on downloaded-bytes |
|---|---|
| Price | USD 0 |
| Limits | |
| Binding | volume-quota 5 GB is 0.0045 TiB, so the byte allowance fails about 220 times before 1 TiB/month. Ports are TCP, with UDP hedged as 'may also be supported', so a WireGuard peer has no reliable path. |
| Identity | email 'All creation of dev tunnels requires either a Microsoft Entra ID, Microsoft, or GitHub account.' |
| Egress | 5 GB per user per month, stated in the Dev tunnels limits table; the same table caps a tunnel at 20 MB/s, 10 tunnels per user and 1500 HTTP requests per minute per port.; ingress: tcp free allowance: 5 GB per user per month, stated in the Dev tunnels limits table; the same table caps a tunnel at 20 MB/s, 10 tunnels per user and 1500 HTTP requests per minute per port. |
| Interface | cli devtunnel CLI. |
| Tooling | devtunnel CLI, VS Code and Visual Studio integration. |
| Composes with | Free TCP ingress for a free VM, with no card and no published cap. |
| Reliability | Designed for development traffic; the aggregator records that visitors see warnings on the URLs. |
| Notes | Corrected in the sweep's last pass: the overview and the FAQ state no quota, and the limits table does. 5 GB/month makes this a development endpoint, not an ingress path. The 20 MB/s ceiling is per tunnel and would allow 1 TiB in about 15 hours, so the monthly byte quota is what binds. |
| Evidence note | documented The allowance, the rate and the tunnel count are stated in one table. What is not stated is whether the 5 GB covers raw TCP forwarding as well as HTTP; the table names no protocol. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | learn.microsoft.com/en-us/azure/developer/dev-tunnels/overvi | 'Tunnel port - An IP port number (1-65535) that is allowed through a dev tunnel'; 'most often linked to TCP connections on either side, but UDP-based protocols may also be supported' |
| 2026-10-23 | learn.microsoft.com/en-us/azure/developer/dev-tunnels/faq | creating a tunnel requires an Entra ID, Microsoft or GitHub account; anonymous users cannot create tunnels |
| 2026-10-23 | learn.microsoft.com/en-us/azure/azure-resource-manager/manag | '## Dev tunnels limits'; 'Bandwidth | 5 GB per user'; 'Tunnels | 10 per user'; 'Data transfer rate | Up to 20 MB/s per tunnel'; 'The limits reset monthly' |
More fields 7
{
"wg_path": "none",
"wg_detail": "",
"ingress": "tcp",
"volume_tib_month": 0.0045,
"volume_stated": "5 GB per user per month, stated in the Dev tunnels limits table; the same table caps a tunnel at 20 MB/s, 10 tunnels per user and 1500 HTTP requests per minute per port.",
"bytes_transit": "yes",
"transit_note": ""
}Unknown values 2
$.per_object_cap.statedthe field does not apply to this kind of offer$.retention.statedthe field does not apply to this kind of offer