Azure App Service operations field guide

The operating rhythm

For App Service work, the safest rhythm is boring on purpose: confirm the target app, confirm configuration, confirm identity, confirm private dependencies, then verify the release with health endpoints and logs.

Checks that catch most problems

• Verify the active subscription, resource group, app name, slot, and deployment source before changing anything.
• Inspect application settings for stale connection strings, old ports, disabled feature flags, or missing managed identity settings.
• Keep App Service health checks pointed at a lightweight process endpoint, then test dependency endpoints separately.
• Use private DNS and port checks from inside App Service when a private endpoint is involved.

What good diagnostics should prove

Diagnostics should answer whether the app is alive, whether the database path works, whether the cache path works, and whether the identity used by the app is the identity you intended. When those facts are visible, Azure becomes much less mysterious.