edits

Author: v-thepet

articles/devtest-labs/deliver-proof-concept.md

@@ -5,9 +5,9 @@ ms.topic: how-to
 ms.date: 03/21/2022
 ---
 
-# Deliver a proof of concept 
+# Deliver a proof of concept for Azure DevTest Labs
 
-This article describes how enterprises can deliver a successful proof of concept or pilot for deploying Azure DevTest Labs. Proof of concept uses a concentrated effort from a single team to establish organizational value.
+This article describes how an enterprise can deliver a successful proof of concept or pilot for an Azure DevTest Labs deployment. Proof of concept uses a concentrated effort from a single team to establish organizational value.
 
 Every enterprise has different requirements for incorporating Azure DevTest Labs into their organization. Proof of concept is a first step toward a successful end-to-end deployment.
 
@@ -25,7 +25,7 @@ Key [DevTest Labs scenarios](devtest-lab-guidance-get-started.md) include cloud
 - Configuring test environments.
 - Enabling VM and Azure resource access.
 - Setting up sandboxes for learning and experimentation.
-- Configuring lab policies and cost controls that follow corporate regulations.
+- Configuring lab policies and cost controls that comply with corporate regulations.
 
 ## Prerequisites 
 
@@ -43,7 +43,7 @@ Learn about Azure and DevTest Labs by using the following resources:
 
 ### Get an Azure subscription
 
-- Enterprises might have an existing [Enterprise Agreement](https://azure.microsoft.com/pricing/purchase-options/enterprise-agreement) that enables access to Azure, and can use an existing or new subscription for DevTest Labs. If there's an Enterprise Agreement in place, an [Enterprise Dev/Test subscription](https://azure.microsoft.com/offers/ms-azr-0148p/) gives you access to Windows 10/Windows 8.1 client operating systems, and discounted rates for development and testing workloads.
+- Enterprises with an existing [Enterprise Agreement](https://azure.microsoft.com/pricing/purchase-options/enterprise-agreement) that enables access to Azure can use an existing or new subscription for DevTest Labs. If there's an Enterprise Agreement in place, an [Enterprise Dev/Test subscription](https://azure.microsoft.com/offers/ms-azr-0148p/) gives you access to Windows 10/Windows 8.1 client operating systems, and discounted rates for development and testing workloads.
 
 - Alternatively, you can use a [Visual Studio subscription](https://azure.microsoft.com/pricing/member-offers/visual-studio-subscriptions) for the pilot deployment, and take advantage of free Azure credits.
 
@@ -69,7 +69,7 @@ Do these tasks to scope the pilot:
 - Decide on the pilot duration, such as two weeks or a month.
 - Decide how to dispose of the pilot resources when the pilot ends.
 
-There's a tendency to try to make the pilot perfect, so it will mirror the final state after DevTest Labs rollout. However, trying to make the proof of concept perfect means too much effort before you can start the pilot. The purpose of the pilot is to determine the right decisions for scaling up and rolling out the final service.
+There's a tendency to try to make the pilot perfect, so it will mirror the final state after DevTest Labs rollout. However, trying to make the proof of concept perfect is too much effort before you can start the pilot. The purpose of the pilot is to determine the right decisions for scaling up and rolling out the final service.
 
 ## Make other planning and design decisions
 
@@ -79,7 +79,7 @@ A full DevTest Labs solution includes some important planning and design decisio
 
 The enterprise-level requirements for resources in Azure can extend beyond the [available quotas within a single subscription](/azure/azure-resource-manager/management/azure-subscription-service-limits). You might need several Azure subscriptions, or you might need to make service requests to increase initial subscription limits. For more information, see [Scalability considerations](devtest-lab-reference-architecture.md#scalability-considerations).
 
-It's important to decide how to distribute resources across subscriptions before final, full-scale rollout, because it's difficult to move resources to another subscription later. For example, you can't move a lab to another subscription after it's created. One valuable resource is the [subscription decision guide](/azure/architecture/cloud-adoption/decision-guides/subscriptions/).
+It's important to decide how to distribute resources across subscriptions before final, full-scale rollout, because it's difficult to move resources to another subscription later. For example, you can't move a lab to another subscription after it's created. The [Subscription decision guide](/azure/architecture/cloud-adoption/decision-guides/subscriptions) is a valuable planning resource.
 
 ### Network topology
 
@@ -97,29 +97,29 @@ DevTest Labs also supports [connecting existing virtual networks to the lab](dev
 
 There are several options for enterprise users to remotely access DevTest Labs VMs:
 
-- The easiest and most secure method is to use browser connectivity through Azure Bastion. Your VMs don't need to use public IP addresses. For more information, see [Enable browser connection to DevTest Labs VMs with Azure Bastion](enable-browser-connection-lab-virtual-machines.md).
+- The easiest and most secure method is to use browser connectivity through Azure Bastion. The VMs don't need to use public IP addresses. For more information, see [Enable browser connection to DevTest Labs VMs with Azure Bastion](enable-browser-connection-lab-virtual-machines.md).
 
 - Another option is to use public IPs or a [shared public IPs](devtest-lab-shared-ip.md), and connect through Remote Desktop Protocol (RDP) or secure shell (SSH).
 
 - If the preceding options aren't sufficient, you can connect through a remote access gateway, as shown in the [DevTest Labs enterprise reference architecture](devtest-lab-reference-architecture.md). For more information, see [Configure a lab to use Remote Desktop Gateway](configure-lab-remote-desktop-gateway.md).
 
-- Enterprises can also connect their labs to their on-premises networks through ExpressRoute or a site-to-site VPN. This option enables direct RDP or SSH connections to the VMs based on their private IP addresses. There's no exposure to the internet.
+- Enterprises can also connect their labs to their on-premises networks through ExpressRoute or a site-to-site VPN. This option enables direct RDP or SSH connections to the VMs based on their private IP addresses, with no exposure to the internet.
 
 ### Lab access and permissions
 
-Before final DevTest Labs rollout, it's important to decide broadly who to give each level of lab access. The two key DevTest Labs [permission levels](devtest-lab-add-devtest-user.md) are Owner and DevTest Labs User. A common model is for the budget owner, such as the team lead, to be the lab owner, with the team members as lab users. This model lets the person responsible for the budget adjust lab policy settings and keep the team within budget.
+Before final DevTest Labs rollout, it's important to decide broadly who to give each level of lab access. The two key DevTest Labs [permission levels](devtest-lab-add-devtest-user.md) are Owner and DevTest Labs User. A common model is for the budget owner, such as the team lead, to be the lab owner, with the team members as lab users. The person responsible for the budget can then adjust lab policy settings and keep the team within budget.
 
 ## Complete the proof of concept 
 
-After you cover the defined scenarios, complete the pilot. Gather feedback from the users, determine if the pilot was successful, and decide if the organization will move ahead on an enterprise-scale DevTest Labs rollout. Start to consider automating deployment of DevTest Labs and associated resources to ensure consistency throughout the scaled rollout.
+After you cover the defined scenarios, complete the pilot. Gather feedback from the users, determine if the pilot was successful, and decide if the organization will move ahead on an [enterprise-scale](devtest-lab-guidance-scale.md) DevTest Labs rollout. Start to consider automating deployment of DevTest Labs and associated resources to ensure consistency throughout the scaled rollout.
 
 ## Example proof-of-concept plan
 
 This following example shows a plan for scoping a DevTest Labs proof of concept.
 
 ### Overview
 
-An enterprise plans to develop a new Azure environment based on DevTest Labs for vendors to use. The DevTest Labs environment will be isolated from the corporate network. To determine if the solution will meet the requirements, the organization develops a proof of concept to validate the end-to-end solution.
+An enterprise plans to develop a new Azure DevTest Labs for vendors to use, which is isolated from the corporate network. To determine if the solution will meet the requirements, the organization develops a proof of concept to validate the end-to-end scenario.
 
 ### Goals
 
@@ -135,11 +135,11 @@ The proof of concept has the following goals:
 
 The solution has the following requirements:
 
-- Vendor teams use a set of labs in Azure DevTest Labs.
-- The labs connect to a network infrastructure that supports the requirements.
+- Vendor teams can use a set of labs in Azure DevTest Labs.
 - The vendors have access to the labs via Azure AD and role assignments.
 - Vendors have a way to successfully connect to their resources, such as a site-to-site VPN that enables accessing VMs without using public IP addresses.
-- A set of artifacts installs the software that the vendors need on the VMs.
+- The labs connect to a network infrastructure that supports the requirements.
+- DevTest Labs installs the set of software artifacts that vendors need on the VMs.
 
 ### Prerequisites 
 
@@ -156,12 +156,11 @@ The solution has the following requirements:
 - Decide what Azure region to use for the proof of concept.
 - Decide whether to join lab VMs to the Azure AD domain, and whether to use Azure Active Directory Domain Services (Azure AD DS) or another method.
 - Identify the vendors who will use the proof of concept environment.
-- Determine the required resources for the vendors, such as applications available on the VMs.
+- Determine the required resources for the vendors, such as software available on the VMs.
 - Decide on the Azure services, other than VMs, that the vendors can use in DevTest Labs.
 - Plan how to train vendors to use the lab.
 
 ## Next steps 
 
 - [Scale up a DevTest Labs deployment](devtest-lab-guidance-orchestrate-implementation.md)
 - [Orchestrate DevTest Labs implementation](devtest-lab-guidance-orchestrate-implementation.md)
-- [What is Azure Virtual Network?](/azure/virtual-network/virtual-networks-overview)

articles/devtest-labs/media/use-paas-services/environments.png

@@ -7,7 +7,9 @@ ms.date: 03/21/2022
 
 # Use PaaS services in Azure DevTest Labs
 
-This article describes platform-as-a-service (PaaS) support in Azure DevTest Labs. DevTest Labs supports PaaS through *environments*, which can include both PaaS and infrastructure-as-a-service (IaaS) resources. Environments contain services and software like virtual machines (VMs), databases, virtual networks, and web apps that are customized to work together. DevTest Labs creates environments by using preconfigured Azure Resource Manager (ARM) templates from a Git repository. Keeping the ARM templates under source control promotes consistent deployment and improved management of environments.
+This article describes platform-as-a-service (PaaS) support in Azure DevTest Labs. DevTest Labs supports PaaS through *environments*, which can include both PaaS and infrastructure-as-a-service (IaaS) resources. Environments contain services and software like virtual machines (VMs), databases, virtual networks, and web apps that are customized to work together.
+
+DevTest Labs creates environments by using preconfigured Azure Resource Manager (ARM) templates from Git repositories. Keeping the ARM templates under source control promotes consistent environment deployment and management.
 
 The following image shows a SharePoint farm created as an environment in a lab.
 
@@ -20,35 +22,35 @@ DevTest Labs PaaS environments support the following scenarios:
 - Developers can create multiple, independent environments.
 - Testers can test different configurations asynchronously and automatically.
 - Staging and production pipeline integration can happen without any template changes.
-- Having all development machines and environments in the same lab improves managability and cost reporting.
+- Lab owners can configure policies and track costs for the environment as a whole.
 
 ### Developer scenarios
 
-To create an environment, developers select an environment template instead of a machine image, and enter any required information. Environments for individual developers allow faster change deployment and improved inner loop debugging. Developers can destroy environments any time and recreate them by using the latest template. This capability helps reduce downtime from manually creating systems or recovering from faults.
+To create an environment, a developer selects an environment template rather than a machine image, and enters any required information. Individual developer environments allow faster change deployment and improved inner loop debugging. Developers can destroy their environments anytime, and recreate them by using the latest templates. This capability helps reduce downtime manually creating systems or recovering from faults.
 
 ### Test scenarios
 
-DevTest Labs environments allow independent, asynchronous testing of specific code and configurations. Testers can use continuous integration and continuous deployment (CI/CD) pipelines to set up environments with code from individual pull requests, and do automated and manual testing. PaaS services help improve the CI/CD pipeline with focused deployments with access controlled by the lab. Automation can manage and track multiple environments across subscriptions and labs.
+DevTest Labs environments allow independent, asynchronous testing of specific code and configurations. Testers can use continuous integration and continuous deployment (CI/CD) pipelines to set up environments, apply code from individual pull requests, and do automated and manual testing. Automation can manage and track multiple environments across subscriptions and labs.
 
 ### Cost tracking
 
 The overall cost trend for a lab includes Azure resources within environments. The cost by resources doesn't break out the different resources within an environment, but displays the environment as a single cost. For more information, see [Track costs associated with a lab in Azure DevTest Labs](devtest-lab-configure-cost-management.md).
 
 ### Access and roles
 
-Lab owners can grant DevTest Labs access and assign user roles. For more information, see [Add lab owners, contributors, and users in Azure DevTest Labs](devtest-lab-add-devtest-user.md).
+Lab owners can grant lab access and assign user roles. For more information, see [Add lab owners, contributors, and users in Azure DevTest Labs](devtest-lab-add-devtest-user.md).
 
-The DevTest Labs resource provider creates resources on the lab user's behalf, so lab users don't need any extra permissions to create and use environments. However, lab owners can extend Contributor permissions to lab users so they can configure and manage their own PaaS resources, such as adding or removing resources. For more information, see [Configure environment user rights](devtest-lab-create-environment-from-arm#configure-environment-user-rights).
+The DevTest Labs resource provider creates resources on the lab user's behalf, so lab users don't need any extra permissions to create and use environments. However, lab owners can extend Contributor permissions to lab users so they can configure and manage their own PaaS resources, such as adding or removing resources. For more information, see [Configure environment user rights](devtest-lab-create-environment-from-arm.md#configure-environment-user-rights).
 
-This functionality allows lab owners to customize the resources or configuration without granting subscription-level access. The lab user can add or remove Azure resource only within the managed resource group. To further customize lab user roles and access, see [Grant user permissions to specific lab policies](devtest-lab-grant-user-permissions-to-specific-lab-policies.md).
+Lab owners can customize resource access or permissions without granting subscription-level access. The lab user can add or remove Azure resources only within the managed resource group. To further customize lab user roles and access, see [Grant user permissions to specific lab policies](devtest-lab-grant-user-permissions-to-specific-lab-policies.md).
 
 ## Environment templates
 
-In large organizations, development teams typically provide environments such as customized or isolated testing environments. The IT group provides environments that all teams within a business unit or a division can use.
+In large organizations, development teams typically provide customized or isolated testing environments. The IT group provides environments that all teams within a business unit or a division can use.
 
-For information on setting up environments, see [Use ARM templates to create DevTest Labs environments](devtest-lab-create-environment-from-arm.md). DevTest Labs has a public repository of preconfigured ARM templates for creating environments. For more information about the public environments, see [Enable and configure public environments](devtest-lab-create-environment-from-arm.md#enable-and-configure-public-environments).
+To enable and configure environment creation for labs, see [Use ARM templates to create DevTest Labs environments](devtest-lab-create-environment-from-arm.md). DevTest Labs has a public repository of preconfigured ARM templates for creating certain environments. For more information about the public environments, see [Enable and configure public environments](devtest-lab-create-environment-from-arm.md#enable-and-configure-public-environments).
 
-You can also create or configure your own ARM environment templates, store them in a private Git repositories, and connect those repositories to labs. For more information, see [Azure Resource Manager (ARM) templates in Azure DevTest Labs](devtest-lab-use-arm-and-powershell-for-lab-resources.md).
+You can also create or configure your own ARM environment templates, store them in private Git repositories, and connect those repositories to labs. For more information, see [Use Azure Resource Manager (ARM) templates in Azure DevTest Labs](devtest-lab-use-arm-and-powershell-for-lab-resources.md).
 
 ## Template customization
 
@@ -60,14 +62,16 @@ You can provide certain custom lab information in ARM templates when creating en
 
 ### Existing virtual network
 
-[Connect environments to the lab's virtual network](connect-environment-lab-virtual-network.md) describes how to modify an ARM template to use the `$(LabSubnetId)` token. When creating an environment, DevTest Labs then replaces the `$(LabSubnetId)` token with the first lab subnet where **Use in virtual machine creation** is set to **true**. This modification allows the environment to use previously created virtual networks. To use the same ARM template in test, staging, and production environments, use `$(LabSubnetId)` as a value in an ARM template parameter.
+When you create an environment, DevTest Labs can replace the `$(LabSubnetId)` token with the first lab subnet where **Use in virtual machine creation** is set to **true**. This modification allows the environment to use previously created virtual networks.
+
+[Connect environments to the lab's virtual network](connect-environment-lab-virtual-network.md) describes how to modify an ARM template to use the `$(LabSubnetId)` token. To use the same ARM template in test, staging, and production environments, use `$(LabSubnetId)` as a value in an ARM template parameter.
 
 ### Nested templates
 
 DevTest Labs supports [nested ARM templates](/azure/azure-resource-manager/templates/linked-templates). To use `_artifactsLocation` and `_artifactsLocationSasToken` tokens to create a URI to a nested ARM template, see [Deploy DevTest Labs environments by using nested templates](deploy-nested-template-environments.md). For more information, see the **Deployment artifacts** section of the [Azure Resource Manager Best Practices Guide](https://github.com/Azure/azure-quickstart-templates/blob/master/1-CONTRIBUTION-GUIDE/best-practices.md#deployment-artifacts-nested-templates-scripts).
 
 ## Next steps
-- 
+
 - [Use ARM templates to create DevTest Labs environments](devtest-lab-create-environment-from-arm.md)
 - [Create an environment with a self-contained Service Fabric cluster in Azure DevTest Labs](create-environment-service-fabric-cluster.md)
 - [Connect an environment to your lab's virtual network in Azure DevTest Labs](connect-environment-lab-virtual-network.md)