Skip to content

Commit 5f3971e

Browse files
author
RoseHJM
committed
Fixed blocking errors.
1 parent 8571ffd commit 5f3971e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/devtest-labs/devtest-lab-guidance-governance-resources.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The **first recommended practice** is to review organizations' Azure taxonomy wh
2626

2727
The **second recommended practice** is to enable the DevTest subscription within the Azure Enterprise portal. It allows an organization to run client operating systems that aren't typically available in an Azure enterprise subscription. Then, use enterprise software where you pay only for the compute and don't worry about licensing. It ensures that the billing for designated services, including gallery images in IaaS such as Microsoft SQL Server, is based on consumption only. Details about the Azure DevTest subscription can be found [here](https://azure.microsoft.com/offers/ms-azr-0148p/) for Enterprise Agreement (EA) customers and [here](https://azure.microsoft.com/offers/ms-azr-0023p/) for Pay as you Go customers.
2828

29-
:::image type="content" source="media/devtest-lab-guidance-governance/resource-alignment-with-subscriptions.png" alt-text="Resource alignment with subscriptions":::
29+
:::image type="content" source="media/devtest-lab-guidance-governance/resource-alignment-with-subscriptions.png" alt-text="Diagram showing how resources alignment with subscriptions.":::
3030

3131
This model provides an organization the flexibility to deploy Azure DevTest Labs at scale. An organization can support hundreds of labs for various business units with 100 to 1000 virtual machines running in parallel. It promotes the notion of a centralized enterprise lab solution that can share the same principles of configuration management and security controls.
3232

@@ -101,8 +101,8 @@ As part of your organization's overall governance and configuration management s
101101

102102
An organization may apply corporate security policies by:
103103

104-
1. Developing and publishing a comprehensive security policy. The policy articulates the rules of acceptable use associated with the using software, cloud assets. It also defines what clearly violates the policy.
105-
2. Develop a custom image, custom artifacts, and a deployment process that allows for orchestration within the security realm that is defined with active directory. This approach enforces the corporate boundary and sets a common set of environmental controls. These controls against the environment a developer can consider as they develop and follow a secure development lifecycle as part of their overall process. The objective also is to provide an environment that isn't overly restrictive that may hinder development, but a reasonable set of controls. The group policies at the organization unit (OU) that contains lab virtual machines could be a subset of the total group policies that are found in production. Alternatively, they can be an another set to properly mitigate any identified risks.
104+
- Developing and publishing a comprehensive security policy. The policy articulates the rules of acceptable use associated with the using software, cloud assets. It also defines what clearly violates the policy.
105+
- Developing a custom image, custom artifacts, and a deployment process that allows for orchestration within the security realm that is defined with active directory. This approach enforces the corporate boundary and sets a common set of environmental controls. These controls against the environment a developer can consider as they develop and follow a secure development lifecycle as part of their overall process. The objective also is to provide an environment that isn't overly restrictive that may hinder development, but a reasonable set of controls. The group policies at the organization unit (OU) that contains lab virtual machines could be a subset of the total group policies that are found in production. Alternatively, they can be another set to properly mitigate any identified risks.
106106

107107
### Data integrity
108108

0 commit comments

Comments
 (0)