1.15.22 — WebApp routes survive address restore
Editorial identity incomplete
2026-08-22
Taking a WebApp offline and restoring its address now keeps its custom API and path routes instead of silently rebuilding only the managed sign-in routes.
- Keeps custom routes as part of the WebApp’s durable serving configuration, independent of any one hostname.
- Automatically captures routes from apps created before this release when they first go offline or change address.
- Recreates those routes on the restored primary address before reapplying the live release.
- Revalidates every retained destination against the selected domain and tenant before changing DNS; an unsafe or retired destination produces a visible refusal instead of a partial restore.
- Continues to derive and protect hosted sign-in/account routes separately.