Azure-docs: Unclear for mutiple apps

[jwisener]

It’s unclear from the documentation provided, how to orchestrate across multiple app instances. For example, if I have a web app on one instance and say an API on another instance. The web app depends on the API being swapped before it should be swapped. How does one ensure, both are swapped together? For example, if a swap fails on either one then you want to the whole swap rolled back for both.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f6e09089-1ae2-8943-5ce2-9d48f458c81f
• Version Independent ID: ba780cba-f604-b0a4-a81a-23c7d2384762
• Content: Set up staging environments for web apps in Azure App Service
• Content Source: articles/app-service/deploy-staging-slots.md
• Service: app-service
• GitHub Login: @cephalin
• Microsoft Alias: cephalin

[BryanTrach-MSFT]

@jwisener Thanks for the feedback! We are currently investigating and will update you shortly.

[iamsunny]

+1 for multiple apps swap status reporting!

[Grace-MacJones-MSFT]

Upon further review we feel your feedback would be best received by the doc author to determine if an update to the current doc is necessary, or to create a new doc if they align with the feedback about swapping multiple apps.

[cephalin]

@jwisner This sounds like a scripting scenario and goes beyond the scope of this article. If you orchestrate with a script then you would verify the first swap before moving on, and so forth. If you need help on that, I suggest going to the Azure forum or StackOverflow. #please-close

[jwisener]

I don’t see how you can say it’s beyond the ‘scope’, given the documentation states it’s to reduce downtime and provide zero down time. No one ever creates apps that use just one machine. Most apps use an front end,
Api and at least a data store (sql or some sort of db). This describes in the document helps with nothing. Because as soon as you swap the front end your api is now out of sync.