Merge pull request #449 from MicrosoftDocs/master

8/13/2019 AM Publish

docs/best-practices/data-partitioning.md

@@ -55,7 +55,7 @@ Figure 1 shows horizontal partitioning or sharding. In this example, product inv
 
 ![Horizontally partitioning (sharding) data based on a partition key](./images/data-partitioning/DataPartitioning01.png)
 
-*Figure 1. Horizontally partitioning (sharding) data based on a partition key.*
+*Figure 1 - Horizontally partitioning (sharding) data based on a partition key.*
 
 The most important factor is the choice of a sharding key. It can be difficult to change the key after the system is in operation. The key must ensure that data is partitioned to spread the workload as evenly as possible across the shards.
 
@@ -75,7 +75,7 @@ The most common use for vertical partitioning is to reduce the I/O and performan
 
 ![Vertically partitioning data by its pattern of use](./images/data-partitioning/DataPartitioning02.png)
 
-*Figure 2. Vertically partitioning data by its pattern of use.*
+*Figure 2 - Vertically partitioning data by its pattern of use.*
 
 In this example, the application regularly queries the product name, description, and price when displaying the product details to customers. Stock count and last- ordered date are held in a separate partition because these two items are commonly used together.
 
@@ -95,7 +95,7 @@ When it's possible to identify a bounded context for each distinct business area
 
 ![Functionally partitioning data by bounded context or subdomain](./images/data-partitioning/DataPartitioning03.png)
 
-*Figure 3. Functionally partitioning data by bounded context or subdomain.*
+*Figure 3 - Functionally partitioning data by bounded context or subdomain.*
 
 This partitioning strategy can help reduce data access contention across different parts of a system.
 

docs/best-practices/monitoring.md

@@ -385,7 +385,7 @@ You can envisage the entire monitoring and diagnostics process as a pipeline tha
 
 ![Stages in the monitoring and diagnostics pipeline](./images/monitoring/Pipeline.png)
 
-*Figure 1. The stages in the monitoring and diagnostics pipeline.*
+*Figure 1 - The stages in the monitoring and diagnostics pipeline.*
 
 Figure 1 highlights how the data for monitoring and diagnostics can come from a variety of data sources. The instrumentation and collection stages are concerned with identifying the sources from where the data needs to be captured, determining which data to capture, how to capture it, and how to format this data so that it can be easily examined. The analysis/diagnosis stage takes the raw data and uses it to generate meaningful information that an operator can use to determine the state of the system. The operator can use this information to make decisions about possible actions to take, and then feed the results back into the instrumentation and collection stages. The visualization/alerting stage phase presents a consumable view of the system state. It can display information in near real time by using a series of dashboards. And it can generate reports, graphs, and charts to provide a historical view of the data that can help identify long-term trends. If information indicates that a KPI is likely to exceed acceptable bounds, this stage can also trigger an alert to an operator. In some cases, an alert can also be used to trigger an automated process that attempts to take corrective actions, such as autoscaling.
 
@@ -522,7 +522,7 @@ Data collection is often performed through a collection service that can run aut
 
 ![Example of collecting instrumentation data](./images/monitoring/TelemetryService.png)
 
-*Figure 2. Collecting instrumentation data.*
+*Figure 2 - Collecting instrumentation data.*
 
 Note that this is a simplified view. The collection service is not necessarily a single process and might comprise many constituent parts running on different machines, as described in the following sections. Additionally, if the analysis of some telemetry data must be performed quickly (hot analysis, as described in the section [Supporting hot, warm, and cold analysis](#supporting-hot-warm-and-cold-analysis) later in this document), local components that operate outside the collection service might perform the analysis tasks immediately. Figure 2 depicts this situation for selected events. After analytical processing, the results can be sent directly to the visualization and alerting subsystem. Data that's subjected to warm or cold analysis is held in storage while it awaits processing.
 
@@ -554,7 +554,7 @@ One approach to implementing the pull model is to use monitoring agents that run
 
 ![Illustration of using a monitoring agent to pull information and write to shared storage](./images/monitoring/PullModel.png)
 
-*Figure 3. Using a monitoring agent to pull information and write to shared storage.*
+*Figure 3 - Using a monitoring agent to pull information and write to shared storage.*
 
 > [!NOTE]
 > Using a monitoring agent is ideally suited to capturing instrumentation data that's naturally pulled from a data source. An example is information from SQL Server Dynamic Management Views or the length of an Azure Service Bus queue.
@@ -565,7 +565,7 @@ To address these issues, you can implement queuing, as shown in Figure 4. In thi
 
 ![Illustration of using a queue to buffer instrumentation data](./images/monitoring/BufferedQueue.png)
 
-*Figure 4. Using a queue to buffer instrumentation data.*
+*Figure 4 - Using a queue to buffer instrumentation data.*
 
 The local data-collection service can add data to a queue immediately after it's received. The queue acts as a buffer, and the storage writing service can retrieve and write the data at its own pace. By default, a queue operates on a first-in, first-out basis. But you can prioritize messages to accelerate them through the queue if they contain data that must be handled more quickly. For more information, see the [Priority Queue pattern](../patterns/priority-queue.md). Alternatively, you can use different channels (such as Service Bus topics) to direct data to different destinations depending on the form of analytical processing that's required.
 
@@ -577,7 +577,7 @@ The instrumentation data that the data-collection service retrieves from a singl
 
 ![Example of using a service to consolidate instrumentation data](./images/monitoring/Consolidation.png)
 
-*Figure 5. Using a separate service to consolidate and clean up instrumentation data.*
+*Figure 5 - Using a separate service to consolidate and clean up instrumentation data.*
 
 ### Storing instrumentation data
 
@@ -594,7 +594,7 @@ You can implement an additional service that periodically retrieves the data fro
 
 ![Partitioning and storage of data](./images/monitoring/DataStorage.png)
 
-*Figure 6. Partitioning data according to analytical and storage requirements.*
+*Figure 6 - Partitioning data according to analytical and storage requirements.*
 
 The same instrumentation data might be required for more than one purpose. For example, performance counters can be used to provide a historical view of system performance over time. This information might be combined with other usage data to generate customer billing information. In these situations, the same data might be sent to more than one destination, such as a document database that can act as a long-term store for holding billing information, and a multidimensional store for handling complex performance analytics.
 

docs/cloud-adoption/business-strategy/business-outcomes/how-to-use-the-business-outcome-template.md

@@ -28,23 +28,23 @@ Introduced by Kate Johnson at the Microsoft Digital Transformation Academy, busi
 
 ![Business outcomes visualized as a house with stakeholders, over business outcomes, over technical capabilities](../../_images/business-outcome-house.png)
 
-*Figure 1: Business outcomes visualized as a house with stakeholders, over business outcomes, over technical capabilities.*
+*Figure 1 - Business outcomes visualized as a house with stakeholders, over business outcomes, over technical capabilities.*
 
 The business outcome template focuses on simplified conversations that can quickly engage stakeholders without getting too deep into the technical solution. By rapidly understanding and aligning the key performance indicators (KPIs) and business drivers that are important to stakeholders, your team can think about high-level approaches and transformations before diving into the implementation details.
 
 An example can be found on the "Example Outcome" tab of the spreadsheet, as shown below. To track multiple outcomes, add them to the "Collective Outcomes" tab.
 
 ![Example of a business outcome template](../../_images/business-outcome-template.png)
 
-*Figure 2: Example of a business outcome template.*
+*Figure 2 - Example of a business outcome template.*
 
 ## Why is this template relevant?
 
 Discovery is a fundamental tenet of enterprise architecture. If discovery is limited to technical discovery, the solution is likely to miss many opportunities to improve the business. Enterprise architects, solution architects, and other technically minded leaders can master the discovery process by using this template. In effective discovery processes, these leaders consider five key aspects of the business outcome before leading a transformation journey, as shown in the following image:
 
 ![Five areas of focus in discovery: stakeholders, outcomes, drivers, KPIs, and capabilities](../../_images/business-outcome-focus-areas.png)
 
-*Figure 3: Five areas of focus in discovery: stakeholders, outcomes, drivers, KPIs, and capabilities.*
+*Figure 3 - Five areas of focus in discovery: stakeholders, outcomes, drivers, KPIs, and capabilities.*
 
 **Stakeholders**: Who in the organization is likely to see the greatest value in a specific business outcome? Who is most likely to support this transformation, especially when things get tough or time consuming? Who has the greatest stake in the success of this transformation? This person is a potential stakeholder.
 

docs/cloud-adoption/governance/corporate-policy.md

@@ -36,7 +36,7 @@ Any change to business processes or technology platforms introduces risk to the
                     <div class="cardText" style="padding-left:0px;">
 <img src="../_images/operational-transformation-govern-highres.png" alt="Diagram of the Cloud Adoption Framework governance model: Corporate policy and governance disciplines">
 <br/>
-<i>Figure 1. Visual of corporate policy and the Five Disciplines of Cloud Governance</i>
+<i>Figure 1 - Visual of corporate policy and the Five Disciplines of Cloud Governance.</i>
                     </div>
                 </div>
             </div>

docs/cloud-adoption/governance/cost-management/discipline-improvement.md

@@ -19,7 +19,7 @@ This article outlines potential tasks your company perform to develop and mature
 
 ![Four phases of adoption](../../_images/adoption-phases.png)
 
-*Figure 1. Adoption phases of the incremental approach to cloud governance.*
+*Figure 1 - Adoption phases of the incremental approach to cloud governance.*
 
 No single document can account for the requirements of all businesses. As such, this article outlines suggested minimum and potential example activities for each phase of the governance maturation process. The initial objective of these activities is to help you build a [Policy MVP](../journeys/index.md#an-incremental-approach-to-cloud-governance) and establish a framework for incremental policy evolution. Your Cloud Governance team will need to decide how much to invest in these activities to improve your Cost Management governance capabilities.
 

docs/cloud-adoption/governance/deployment-acceleration/discipline-improvement.md

@@ -19,7 +19,7 @@ This article outlines some potential tasks your company can engage in to better
 
 ![Four phases of adoption](../../_images/adoption-phases.png)
 
-*Figure 1. Adoption phases of the incremental approach to cloud governance.*
+*Figure 1 - Adoption phases of the incremental approach to cloud governance.*
 
 It's impossible for any one document to account for the requirements of all businesses. As such, this article outlines suggested minimum and potential example activities for each phase of the governance maturation process. The initial objective of these activities is to help you build a [Policy MVP](../journeys/index.md#an-incremental-approach-to-cloud-governance) and establish a framework for incremental policy evolution. Your Cloud Governance team will need to decide how much to invest in these activities to improve your Identity Baseline governance capabilities.
 

docs/cloud-adoption/governance/governance-disciplines.md

@@ -1,7 +1,7 @@
 ---
 title: "The Five Disciplines of Cloud Governance"
 titleSuffix: Microsoft Cloud Adoption Framework for Azure
-description: Overview of governance content within the Cloud Adoption Framework
+description: Learn about the Five Disciplines of Cloud Governance in the Cloud Adoption Framework.
 author: BrianBlanchard
 ms.author: brblanch
 ms.date: 02/11/2019
@@ -17,39 +17,39 @@ layout: LandingPage
 <!-- markdownlint-disable MD033 -->
 
 <ul class="panelContent cardsI">
-<li style="display: flex; flex-direction: column;">
-    <div class="cardSize">
-        <div class="cardPadding" style="padding-bottom:10px;">
-            <div class="card" style="padding-bottom:10px;">
-                <div class="cardText" style="padding-left:0px;">
-Any change to business processes or technology platforms introduces risk. Cloud Governance teams, whose members are sometimes known as cloud custodians, are tasked with mitigating these risks, with minimal interruption to adoption or innovation efforts.<br/><br/>The Cloud Adoption Framework governance model guides these decisions (regardless of the chosen cloud platform) by focusing on [development of corporate policy](./corporate-policy.md) and the [Five Disciplines of Cloud Governance](#disciplines-of-cloud-governance). [Actionable design guides](./actionable-journeys/index.md) demonstrate this model using Azure services. This landing page lists the disciplines of the Cloud Adoption Framework governance model.
-                </div>
-            </div>
-        </div>
-    </div>
-</li>
-<li style="display: flex; flex-direction: column;">
-    <a href="../_images/operational-transformation-govern-highres.png" style="display: flex; flex-direction: column; flex: 1 0 auto;">
+    <li style="display: flex; flex-direction: column;">
         <div class="cardSize">
             <div class="cardPadding" style="padding-bottom:10px;">
                 <div class="card" style="padding-bottom:10px;">
                     <div class="cardText" style="padding-left:0px;">
-<img src="../_images/operational-transformation-govern-highres.png" alt="Diagram of the Cloud Adoption Framework governance model: Corporate policy and governance disciplines">
-<br>
-<i>Figure 1. Diagram of corporate policy and the Five Disciplines of Cloud Governance</i>
+    Any change to business processes or technology platforms introduces risk. Cloud governance teams, whose members are sometimes known as cloud custodians, are tasked with mitigating these risks and ensuring minimal interruption to adoption or innovation efforts.<br/><br/>The Cloud Adoption Framework governance model guides these decisions (regardless of the chosen cloud platform) by focusing on <a href="./corporate-policy.md">development of corporate policy]</a> and the <a href="#disciplines-of-cloud-governance">Five Disciplines of Cloud Governance</a>. <a href="./journeys/index.md">Actionable design guides</a> demonstrate this model using Azure services. Learn about the disciplines of the Cloud Adoption Framework governance model below.
                     </div>
                 </div>
             </div>
         </div>
-    </a>
-</li>
+    </li>
+    <li style="display: flex; flex-direction: column;">
+        <a href="../_images/operational-transformation-govern-highres.png" style="display: flex; flex-direction: column; flex: 1 0 auto;">
+            <div class="cardSize">
+                <div class="cardPadding" style="padding-bottom:10px;">
+                    <div class="card" style="padding-bottom:10px;">
+                        <div class="cardText" style="padding-left:0px;">
+    <img src="../_images/operational-transformation-govern-highres.png" alt="Diagram of the Cloud Adoption Framework governance model: Corporate policy and governance disciplines">
+    <br>
+    <i>Figure 1 - Diagram of corporate policy and the Five Disciplines of Cloud Governance.</i>
+                        </div>
+                    </div>
+                </div>
+            </div>
+        </a>
+    </li>
 </ul>
 
 <!-- markdownlint-enable MD033 -->
 
 ## Disciplines of Cloud Governance
 
-Across each cloud provider, there are common governance disciplines that can serve as a guide to help inform policies and align toolchains. These disciplines guide decisions regarding the proper level of automation and enforcement of corporate policy across cloud providers.
+With any cloud platform, there are common governance disciplines that help inform policies and align toolchains. These disciplines guide decisions about the proper level of automation and enforcement of corporate policy across cloud platforms.
 
 <!-- markdownlint-disable MD033 -->
 
@@ -85,7 +85,7 @@ Across each cloud provider, there are common governance disciplines that can ser
                     </div>
                     <div class="cardText">
                         <h3>Security Baseline</h3>
-                        <p>Security is a complex and personal topic, unique to each company. Once security requirements are established, cloud governance policies and enforcement applies those requirements across network, data and asset configurations.</p>
+                        <p>Security is a complex topic, unique to each company. Once security requirements are established, cloud governance policies and enforcement apply those requirements across network, data, and asset configurations.</p>
                     </div>
                 </div>
             </div>
@@ -104,7 +104,7 @@ Across each cloud provider, there are common governance disciplines that can ser
                     </div>
                     <div class="cardText">
                         <h3>Identity Baseline</h3>
-                        <p>Inconsistencies in the application of identity requirements can increase the risk of breach. The Identity Baseline discipline focuses on ways to ensure identity is consistently applied across cloud adoption efforts.</p>
+                        <p>Inconsistencies in the application of identity requirements can increase the risk of breach. The Identity Baseline discipline focuses ensuring that identity is consistently applied across cloud adoption efforts.</p>
                     </div>
                 </div>
             </div>
@@ -123,7 +123,7 @@ Across each cloud provider, there are common governance disciplines that can ser
                     </div>
                     <div class="cardText">
                         <h3>Resource Consistency</h3>
-                        <p>Cloud operations depends on consistency in resource configuration. Through governance tooling, resources can consistently be configured to manage risks related to on-boarding, drift, discoverability, and recovery.</p>
+                        <p>Cloud operations depend on consistent resource configuration. Through governance tooling, resources can be configured consistently to manage risks related to onboarding, drift, discoverability, and recovery.</p>
                     </div>
                 </div>
             </div>
@@ -142,7 +142,7 @@ Across each cloud provider, there are common governance disciplines that can ser
                     </div>
                     <div class="cardText">
                         <h3>Deployment Acceleration</h3>
-                        <p>Centralization, standardization, and consistency in deployment and configuration approaches improve governance practices. When made available through cloud-based governance tooling, they create a cloud factor that can accelerate deployment activities.</p>
+                        <p>Centralization, standardization, and consistency in approaches to deployment and configuration improve governance practices. When provided through cloud-based governance tooling, they create a cloud factor that can accelerate deployment activities.</p>
                     </div>
                 </div>
             </div>