Now that we have an overview of what Azure Stack is, how it works, and how we could work with it, let's go on and discuss some scenarios where Azure Stack could fit. Here are some examples:

Basically, you should in general think about public Azure and how to move your IT services to it. If there is a reason why a service does not fit public Azure, Azure Stack might work.

The general scenarios for Azure Stack are as follows:

• Edge and disconnected solutions: Edge and disconnected solutions are everything when not much internet connectivity is available or not intended. Therefore, the disconnected mode is suitable, because with Azure AD an internet connection is really needed.
• Data sovereignty: Data sovereignty is the most important reason, as if a customer is not able to, not willing to, or does not have to move specific data to the public cloud, Azure Stack fits completely, as stack lives on the premise, where the data needs to reside.
• Cloud applications: Developing cloud applications is often something that needs to be done on the premises, therefore Azure Stack is the one and only option. After a major release or update is available, the application could then be moved from development stage to public Azure.

To make the corresponding use cases for Azure Stack a little bit easier to understand, Microsoft has published some use cases that might fit and has described them in a little bit more detail. These are the following:

• Configure hybrid cloud connectivity
• Machine learning solution with Azure Stack
• Azure Stack staged data analysis
• Azure Stack cloud burst scenario
• Azure Stack geo-distributed applications

While working through these scenarios, you will figure out that there is a step-by-step guide available to easily understand and set up these scenarios.

Let's have a little bit of a deeper look into each of them.