Unlink a backend from a static site build
One step with Microsoft Azure Functions. We can help you get access.
Get something done
Unlink a backend from a static site build
Use Microsoft Azure Functions: its WebApps API Client Static Sites API lets you unlink a backend from a static site build in a single step (DELETE /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/staticSites/{name}/builds/{environmentName}/linkedBackends/{linkedBackendName}). capabilities.work can help you get signed up and connected.
- Can I detach a backend from just one build environment of my static site?
- When I unlink a backend from a preview build, can I also clean up its auth configuration?
Say it to your AI assistant
- Unlink backend {linkedBackendName} from build {environmentName} of static site {name}.
- Unlink build backend {linkedBackendName} from {environmentName} and set auth cleanup to {isCleaningAuthConfig}.
For your developer
DELETE /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/staticSites/{name}/builds/{environmentName}/linkedBackends/{linkedBackendName} in WebApps API Client Static Sites API. Full spec on APIs.io.