Merge pull request #477 from MicrosoftDocs/master

8/19/2019 AM Publish

docs/cloud-adoption/appendix/cloud-operating-model.md

@@ -15,7 +15,7 @@ layout: LandingPage
 
 In early 2018, Microsoft released the Cloud Operating Model (COM). The COM was a guide that helped customers understand the **what** and the **why** of digital transformation. This helped customers get a sense of all the areas that needed to be addressed: business strategy, culture strategy, and technology strategy. What was not included in the COM were the specific _how-to's_, which left customers wondering, "Where do we go from here?"
 
-In October 2018, we began a review of all the models that had proliferated across the Microsoft community, we found roughly 60 different cloud adoption models. A cross-Microsoft team was established to bring everything together as a dedicated engineering "product" with defined implementations across services, sales, and marketing. This effort culminated in the creation of a single model, the Microsoft Cloud Adoption Framework for Azure, designed to help customers understand the **what** and **why** and provide unified guidance on the **how** to help them accelerate their cloud journey. The goal of this project is to create a One Microsoft approach to cloud adoption.
+In October 2018, we began a review of all the models that had proliferated across the Microsoft community, we found roughly 60 different cloud adoption models. A cross-Microsoft team was established to bring everything together as a dedicated engineering "product" with defined implementations across services, sales, and marketing. This effort culminated in the creation of a single model, the Microsoft Cloud Adoption Framework for Azure, designed to help customers understand the **what** and **why** and provide unified guidance on the **how** to help them accelerate their cloud adoption. The goal of this project is to create a One Microsoft approach to cloud adoption.
 
 ## Using Cloud Operating Model practices within the Cloud Adoption Framework
 
@@ -48,7 +48,7 @@ COM included an infographic that outlined the various decisions and actions need
 
 The Cloud Adoption Framework follows a similar model. However, as the actions and decisions expanded into multiple decision trees, complexity quickly made a single graphical view appear overwhelming. To simplify the guidance and make it more immediately actionable, the single graphic has been decomposed into the following structures.
 
-At the executive level, the Cloud Adoption Framework has been simplified into the following three phases of adoption and two primary journeys.
+At the executive level, the Cloud Adoption Framework has been simplified into the following three phases of adoption and two primary governance guides.
 
 ![Executive level structure of the Cloud Adoption Framework](../_images/caf-structure.png)
 
@@ -63,7 +63,7 @@ The three phases of cloud adoption have been mapped to two specific journeys:
 - [Migrate](../getting-started/migrate.md): Move existing workloads to the cloud.
 - [Innovate](../getting-started/innovate.md): Modernize existing workloads and create new products and services.
 
-Additional resources required to be successful in a cloud adoption journey can be found in [Enabling adoption success](../getting-started/enable.md).
+Additional resources required for successful cloud adoption can be found in [Enabling adoption success](../getting-started/enable.md).
 
 ## Next steps
 

docs/cloud-adoption/appendix/roadmap.md

@@ -50,7 +50,7 @@ To successfully adopting the cloud, a customer must prepare its people, technolo
   - Prioritize workloads based on impacts to the business outcomes.
   - Create a cloud adoption plan based on the current digital estate and prioritized workloads.
 - **Ready:** Prepare the people, culture, and environment for change. This phase has three key components:
-  - Create a Cloud Strategy team and other organizational alignment.
+  - Create a cloud strategy team and other organizational alignment.
   - Create a skills readiness plan across roles and functions.
   - Establish an Azure foundation by preparing the cloud environment.
 - **Adopt:** Implement the desired changes across IT and business processes to help customers realize their business, technology, and people strategies. This phase includes several areas that will vary depending on what the organization is implementing:

docs/cloud-adoption/business-strategy/global-markets.md

@@ -30,7 +30,7 @@ It is important to understand which business units operate in foreign countries,
 
 It is important to understand how global users access applications that are not hosted in the same country as the user. Often time global WANs (Wide Area Networks) route users based on existing networking agreements. In a traditional on-premises world, some constraints limit WAN design. Those constraints can lead to poor user experiences if not properly understood before cloud adoption.
 
-In a cloud model, commodity internet opens up many new options as well. Communicating the spread of employees across multiple geographies can help the Cloud Adoption team design WAN solutions that create positive user experiences **and** potential reduce networking costs.
+In a cloud model, commodity internet opens up many new options as well. Communicating the spread of employees across multiple geographies can help the cloud adoption team design WAN solutions that create positive user experiences **and** potential reduce networking costs.
 
 ## External user usage patterns
 

docs/cloud-adoption/decision-guides/software-defined-network/index.md

@@ -23,7 +23,7 @@ Jump to: [PaaS Only](paas-only.md) | [Cloud-native](cloud-native.md) | [Cloud DM
 
 SDN provides several options with varying degrees of pricing and complexity. The above discovery guide provides a reference to quickly personalize these options to best align with specific business and technology strategies.
 
-The inflection point in this guide depends on several key decisions that your Cloud Strategy team have made before making decisions about networking architecture. Most important among these are decisions involving your [digital estate definition](../../digital-estate/index.md) and [subscription design](../subscriptions/index.md) (which may also require inputs from decisions made related to your cloud accounting and global markets strategies).
+The inflection point in this guide depends on several key decisions that your cloud strategy team has made before making decisions about networking architecture. Most important among these are decisions involving your [digital estate definition](../../digital-estate/index.md) and [subscription design](../subscriptions/index.md) (which may also require inputs from decisions made related to your cloud accounting and global markets strategies).
 
 Small single-region deployments of fewer than 1,000 VMs are less likely to be significantly affected by this inflection point. Conversely, large adoption efforts with more than 1,000 VMs, multiple business units, or multiple geopolitical markets, could be substantially affected by your SDN decision and this key inflection point.
 

docs/cloud-adoption/digital-estate/index.md

@@ -31,7 +31,7 @@ The measurement of a digital estate changes depending on the desired business ou
 After an organization understands the most important form of transformation, digital estate planning becomes much easier to manage.
 
 > [!TIP]
-> Each type of transformation can be measured with any of the three views. Companies commonly complete all three transformations in parallel. We strongly recommend that the leadership and cloud strategy team agree regarding the transformation that is most important for business success. That understanding serves as the basis for common language and metrics across multiple initiatives.
+> Each type of transformation can be measured with any of the three views. Companies commonly complete all three transformations in parallel. We strongly recommend that company leadership and the cloud strategy team agree regarding the transformation that is most important for business success. That understanding serves as the basis for common language and metrics across multiple initiatives.
 
 ## How can a financial model be updated to reflect the digital estate?
 

docs/cloud-adoption/digital-estate/rationalize.md

@@ -55,7 +55,7 @@ In an incremental rationalization process, an agent-less solution could be used
 
 ### Quantitative analysis: Streamline decisions
 
-Regardless of the approach to inventory discovery, quantitative analysis can drive initial decisions and assumptions. This is especially true when trying to identify the first workload or when the goal of rationalization is a high-level cost comparison. In an incremental rationalization process, the cloud strategy and cloud adoption teams limit the [five Rs of rationalization](5-rs-of-rationalization.md) to two concise decisions and only apply those quantitative factors. This streamlines the analysis and reduces the amount of initial data that's required to drive change.
+Regardless of the approach to inventory discovery, quantitative analysis can drive initial decisions and assumptions. This is especially true when trying to identify the first workload or when the goal of rationalization is a high-level cost comparison. In an incremental rationalization process, the cloud strategy team and the cloud adoption teams limit the [five Rs of rationalization](5-rs-of-rationalization.md) to two concise decisions and only apply those quantitative factors. This streamlines the analysis and reduces the amount of initial data that's required to drive change.
 
 For example, if an organization is in the midst of an IaaS migration to the cloud, you can assume that most workloads will either be retired or rehosted.
 
@@ -111,7 +111,7 @@ The first workload is often deployed in an experimental environment with no oper
 
 ### Qualitative analysis
 
-The cloud adoption and cloud strategy teams can work together to analyze this small workload. This collaboration creates a controlled opportunity to create and test qualitative analysis criteria. The smaller population creates an opportunity to survey the affected users, and to complete a detailed qualitative analysis in a week or less. For common qualitative analysis factors, see the specific rationalization target in the [5 Rs of rationalization](5-rs-of-rationalization.md).
+The cloud adoption teams and the cloud strategy team can work together to analyze this small workload. This collaboration creates a controlled opportunity to create and test qualitative analysis criteria. The smaller population creates an opportunity to survey the affected users, and to complete a detailed qualitative analysis in a week or less. For common qualitative analysis factors, see the specific rationalization target in the [5 Rs of rationalization](5-rs-of-rationalization.md).
 
 ### Migration
 
@@ -133,7 +133,7 @@ The traditional approach to rationalization attempts to meet all foreseeable nee
 
 ### Build the first backlogs
 
-The cloud adoption and cloud strategy teams can work together on the qualitative analysis for the first 10 workloads. This effort creates the first prioritized migration backlog and the first prioritized release backlog. This method enables the teams to iterate on the approach and provides sufficient time to create an adequate process for qualitative analysis.
+The cloud adoption teams and the cloud strategy team can work together on the qualitative analysis for the first 10 workloads. This effort creates the first prioritized migration backlog and the first prioritized release backlog. This method enables the teams to iterate on the approach and provides sufficient time to create an adequate process for qualitative analysis.
 
 ### Mature the process
 

docs/cloud-adoption/getting-started/migrate.md

@@ -93,7 +93,7 @@ The effort to realize the desired business outcomes may trigger slight changes t
 - The IT team is likely to adopt new skills to support workloads in the cloud.
 - Execution of a cloud migration encourages iterative or agile approaches.
 - Inclusion of cloud governance also tends to inspire DevOps approaches.
-- Creation of a Cloud Strategy team can lead to tighter integration between business and IT leaders.
+- Creation of a cloud strategy team can lead to tighter integration between business and IT leaders.
 - Collectively, these changes tend to lead to business and IT agility.
 
 Cultural change is not a goal of cloud migration or the Cloud Adoption Framework, but it is a commonly experienced outcome.

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

@@ -22,7 +22,7 @@ layout: LandingPage
         <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 to the business. 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/>However, cloud governance requires more than technical implementation. Subtle changes in the corporate narrative or corporate policies can affect adoption efforts significantly. Before implementation, it's important to look beyond IT while defining corporate policy.<br/><br/>
+Any change to business processes or technology platforms introduces risk to the business. 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/>However, cloud governance requires more than technical implementation. Subtle changes in the corporate narrative or corporate policies can affect adoption efforts significantly. Before implementation, it's important to look beyond IT while defining corporate policy.<br/><br/>
                 </div>
             </div>
         </div>

docs/cloud-adoption/governance/cost-management/business-risks.md

@@ -29,10 +29,10 @@ The cloud offers self-service capabilities that were previously unheard of in tr
 
 The Cost Management discipline attempts to address core business risks related to expenses incurred when hosting cloud-based workloads. Work with your business to identify these risks and monitor each of them for relevance as you plan for and implement your cloud deployments.
 
-Risks will differ between organization, but the following serve as common cost-related risks that you can use as a starting point for discussions within your Cloud Governance team:
+Risks will differ between organization, but the following serve as common cost-related risks that you can use as a starting point for discussions within your cloud governance team:
 
 - **Budget control:** Not controlling budget can lead to excessive spending with a cloud vendor.
-- **Utilization loss:** Prepurchases or precommitments that are not used can result in wasted investments.
+- **Utilization loss:** Prepurchases or precommitments that go unused can result in wasted investments.
 - **Spending anomalies:** Unexpected spikes in either direction can be indicators of improper usage.
 - **Overprovisioned assets:** When assets are deployed in a configuration that exceed the needs of an application or virtual machine (VM), they can increase costs and create waste.
 

docs/cloud-adoption/governance/cost-management/compliance-processes.md

@@ -13,7 +13,7 @@ ms.custom: governance
 
 # Cost Management policy compliance processes
 
-This article discusses an approach to creating processes that support a [Cost Management](./index.md) governance discipline. Effective governance of cloud costs starts with recurring manual processes designed to support policy compliance. This requires regular involvement of the Cloud Governance team and interested business stakeholders to review and update policy and ensure policy compliance. In addition, many ongoing monitoring and enforcement processes can be automated or supplemented with tooling to reduce the overhead of governance and allow for faster response to policy deviation.
+This article discusses an approach to creating processes that support a [Cost Management](./index.md) governance discipline. Effective governance of cloud costs starts with recurring manual processes designed to support policy compliance. This requires regular involvement of the cloud governance team and interested business stakeholders to review and update policy and ensure policy compliance. In addition, many ongoing monitoring and enforcement processes can be automated or supplemented with tooling to reduce the overhead of governance and allow for faster response to policy deviation.
 
 ## Planning, review, and reporting processes
 
@@ -29,7 +29,7 @@ This is the time to make a precommitment or prepurchase to maximize discounting.
 
 **Quarterly planning:** On a quarterly basis, review budgets with each billing unit leader to align forecast and actual spending. If there are changes to the plan or unexpected spending patterns, align and reallocate the budget.
 
-This quarterly planning process is also a good time to evaluate the current membership of your Cloud Governance team for knowledge gaps related to current or future business plans. Invite relevant staff and workload owners to participate in reviews and planning as either temporary advisors or permanent members of your team.
+This quarterly planning process is also a good time to evaluate the current membership of your cloud governance team for knowledge gaps related to current or future business plans. Invite relevant staff and workload owners to participate in reviews and planning as either temporary advisors or permanent members of your team.
 
 **Education and training:** On a bimonthly basis, offer training sessions to make sure business and IT staff are up-to-date on the latest Cost Management policy requirements. As part of this process review and update any documentation, guidance, or other training assets to ensure they are in sync with the latest corporate policy statements.
 

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

@@ -21,7 +21,7 @@ This article outlines potential tasks your company perform to develop and mature
 
 *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.
+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 improvement. Your cloud governance team will need to decide how much to invest in these activities to improve your Cost Management governance capabilities.
 
 > [!CAUTION]
 > Neither the minimum or potential activities outlined in this article are aligned to specific corporate policies or third-party compliance requirements. This guidance is designed to help facilitate the conversations that will lead to alignment of both requirements with a cloud governance model.
@@ -99,7 +99,7 @@ Once the transformation is complete, governance and operations must live on for
 - Analyze stakeholder value and cost reporting methods on a monthly basis.
 - Remediate underused assets and determine if they're worth continuing.
 - Detect misalignments and anomalies between the plan and actual spending.
-- Assist the cloud adoption teams and the Cloud Strategy team with understanding and resolving these anomalies.
+- Assist the cloud adoption teams and the cloud strategy team with understanding and resolving these anomalies.
 
 ## Next steps