deployment

To configure deployment targets, set up production run and build commands, then specify autoscale or VM targets based on your environment's scaling needs. This aligns deployment settings across environments before publishing releases.

To diagnose production deployment failures, inspect runtime logs to identify errors and review geography settings to ensure correct regional configuration. This helps troubleshoot issues across deployment targets effectively.

The best way to publish releases is to align deployment settings for your chosen target—autoscale, VM, scheduled, or static—and execute the publish command when configuration is complete.

Yes, you can manage scheduled and static deployments by selecting those deployment targets during configuration. This supports aligning settings and publishing releases across various target types.

Specifying geography settings is required when publishing a release to ensure the deployment targets the correct region. This configuration is part of aligning settings before the publish action.

To troubleshoot runtime issues after deployment, access and inspect the deployment logs to diagnose errors. Reviewing geography settings also helps identify regional configuration problems affecting runtime behavior.