Azure · Cloud service
Azure App Service with OrchestrAI
Catalog exported 2026-09-02
Manage Azure App Service from chat: create web apps, add slots, set app settings, assign managed identities.
OrchestrAI exposes 5 App Service operations: 1 is low-risk (read-only or low-impact), and 4 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Developers use OrchestrAI to create an App Service web app, give it a system-assigned managed identity so it can reach Key Vault or Storage without secrets, and load its configuration through app settings. Adding a staging slot for a canary release is a low-risk step that fits the same conversation. Slot swaps and code deployment are not covered, so after a slot exists you still push the build and swap it through your existing pipeline.
Every App Service operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create App Service Deployment Slot |
Create a deployment slot for an Azure App Service Web App (e.g., staging, canary) | Low risk | No |
Assign App Service Identity |
Assign a managed identity to an Azure App Service Web App | Creates resources | No |
Create App Service Web App |
Create an Azure App Service Web App | Creates resources | No |
Set App Service Settings |
Set application settings for an Azure App Service Web App | Creates resources | No |
Delete App Service Web App |
Delete an Azure App Service Web App | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create a web app called acme-api in rg-app on the plan acme-plan with the Node 20 runtime
- Assign a system-assigned managed identity to acme-api
- Set DATABASE_URL and REDIS_URL app settings on acme-api and add a staging slot
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Is changing App Service app settings through OrchestrAI risky?
- Setting app settings is rated medium: it changes configuration, and OrchestrAI shows the plan before applying it. Deleting a web app is high risk and requires confirmation.
- Can OrchestrAI deploy my code to Azure App Service?
- No, it handles the app, slot, identity, and settings, but pushing code and swapping slots are not available operations.
- Which App Service operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete App Service Web App. None of them is classed destructive.
Other Azure services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.