|
| 1 | +--- |
| 2 | +title: What is Azure Adaptive Cloud? |
| 3 | +description: Introduction to Azure Adaptive Cloud, enabling organizations to leverage cloud-native and AI technologies across hybrid, multicloud, edge, and IoT. |
| 4 | +author: asergaz |
| 5 | +ms.author: sergaz |
| 6 | +ms.topic: overview |
| 7 | +ms.date: 02/20/2025 |
| 8 | +#Customer intent: As a newcomer to Azure Adaptive Cloud, I want to understand what Azure Adaptive Cloud is, what services are available, and examples of business cases so I can figure out where to start. |
| 9 | +--- |
| 10 | + |
| 11 | +<!-- |
| 12 | +Remove all the comments in this template before you sign-off or merge to the main branch. |
| 13 | +
|
| 14 | +This template provides the basic structure of a Concept article pattern. See the [instructions - Concept](../level4/article-concept.md) in the pattern library. |
| 15 | +
|
| 16 | +You can provide feedback about this template at: https://aka.ms/patterns-feedback |
| 17 | +
|
| 18 | +Concept is an article pattern that defines what something is or explains an abstract idea. |
| 19 | +
|
| 20 | +There are several situations that might call for writing a Concept article, including: |
| 21 | +
|
| 22 | +* If there's a new idea that's central to a service or product, that idea must be explained so that customers understand the value of the service or product as it relates to their circumstances. A good recent example is the concept of containerization or the concept of scalability. |
| 23 | +* If there's optional information or explanations that are common to several Tutorials or How-to guides, this information can be consolidated and single-sourced in a full-bodied Concept article for you to reference. |
| 24 | +* If a service or product is extensible, advanced users might modify it to better suit their application. It's better that advanced users fully understand the reasoning behind the design choices and everything else "under the hood" so that their variants are more robust, thereby improving their experience. |
| 25 | +
|
| 26 | +--> |
| 27 | + |
| 28 | +<!-- 1. H1 |
| 29 | +----------------------------------------------------------------------------- |
| 30 | +
|
| 31 | +Required. Set expectations for what the content covers, so customers know the content meets their needs. The H1 should NOT begin with a verb. |
| 32 | +
|
| 33 | +Reflect the concept that undergirds an action, not the action itself. The H1 must start with: |
| 34 | +
|
| 35 | +* "\<noun phrase\> concept(s)", or |
| 36 | +* "What is \<noun\>?", or |
| 37 | +* "\<noun\> overview" |
| 38 | +
|
| 39 | +Concept articles are primarily distinguished by what they aren't: |
| 40 | +
|
| 41 | +* They aren't procedural articles. They don't show how to complete a task. |
| 42 | +* They don't have specific end states, other than conveying an underlying idea, and don't have concrete, sequential actions for the user to take. |
| 43 | +
|
| 44 | +One clear sign of a procedural article would be the use of a numbered list. With rare exception, numbered lists shouldn't appear in Concept articles. |
| 45 | +
|
| 46 | +--> |
| 47 | + |
| 48 | +# What is Azure Adaptive Cloud? |
| 49 | + |
| 50 | +<!-- 2. Introductory paragraph |
| 51 | +---------------------------------------------------------- |
| 52 | +
|
| 53 | +Required. Lead with a light intro that describes what the article covers. Answer the fundamental “why would I want to know this?” question. Keep it short. |
| 54 | +
|
| 55 | +* Answer the fundamental "Why do I want this knowledge?" question. |
| 56 | +* Don't start the article with a bunch of notes or caveats. |
| 57 | +* Don’t link away from the article in the introduction. |
| 58 | +* For definitive concepts, it's better to lead with a sentence in the form, "X is a (type of) Y that does Z." |
| 59 | +
|
| 60 | +--> |
| 61 | + |
| 62 | +The adaptive cloud approach unifies siloed teams, distributed sites, and sprawling systems into a single operations, security, application, and data model, enabling organizations to leverage cloud-native and AI technologies to work simultaneously across hybrid, multicloud, edge, and IoT. |
| 63 | + |
| 64 | +## [Section 1 heading] |
| 65 | +TODO: add your content |
| 66 | + |
| 67 | +## [Section 2 heading] |
| 68 | +TODO: add your content |
| 69 | + |
| 70 | +## [Section n heading] |
| 71 | +TODO: add your content |
| 72 | + |
| 73 | +<!-- 5. Next step/Related content ------------------------------------------------------------------------ |
| 74 | +
|
| 75 | +Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both. |
| 76 | + - For Next step, provide one link to the next step in a sequence. Use the blue box format |
| 77 | + - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links. |
| 78 | +
|
| 79 | +--> |
| 80 | + |
| 81 | +## Next steps |
| 82 | + |
| 83 | +TODO: Add your next step link(s) |
| 84 | + |
| 85 | +> [!div class="nextstepaction"] |
| 86 | +> [Write concepts](article-concept.md) |
0 commit comments