I'm considering a chatbot, perhaps in Teams, that employees could use to create Azure sandbox environments for learning and testing. Does Logic Apps seem like a good fit, and what should I watch out for?
Would Logic Apps work for an Azure sandbox chatbot?
Asked by
four-and-a-half-tries
Answers
Logic Apps seems like a reasonable fit for a straightforward request and provisioning flow. The low-code approach could make it quick to put together an initial version without building a full custom application.
I'd start with a small flow that accepts a request, provisions a sandbox and reports the result back. More elaborate enterprise features can come later if people actually use it.
Reply to this answer
Check the pricing for the specific Logic Apps plan and connectors before settling on the workflow. Calls to SQL or external APIs, polling frequency and connector usage could all affect the cost.
Be careful about applying Power Apps connector labels or pricing directly to Logic Apps. The models differ, and some connectors in the Logic Apps Standard plan are available as in-app connectors without a per-execution connector charge. Check the current pricing for the exact setup rather than assuming every connector works the same way.
Reply to this answer
The chatbot is only the front door. Think through how a sandbox request should work across tenants and what enterprise features you might need as adoption grows. A simple flow can be a useful starting point, but that part deserves its own design discussion.
Reply to this answer
Add your answer
Answers are reviewed before publication.
trivia without buzzers:
Good distinction. I'd also look at polling intervals when estimating usage, especially for a flow that's checking frequently even when nobody is requesting a sandbox.