Skip to content

Commit 061aaff

Browse files
Merge pull request #232066 from RoseHJM/ADE-MDB-SEO-1
ADE & MDB - SEO changes
2 parents 9bef0aa + 2fd2568 commit 061aaff

39 files changed

+111
-97
lines changed

.openpublishing.publish.config.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -984,8 +984,6 @@
984984
".openpublishing.redirection.baremetal-infrastructure.json",
985985
".openpublishing.redirection.defender-for-cloud.json",
986986
".openpublishing.redirection.defender-for-iot.json",
987-
".openpublishing.redirection.deployment-environments.json",
988-
".openpublishing.redirection.dev-box.json",
989987
".openpublishing.redirection.healthcare-apis.json",
990988
".openpublishing.redirection.iot-hub-device-update.json",
991989
".openpublishing.redirection.json",
@@ -1042,6 +1040,8 @@
10421040
"articles/stream-analytics/.openpublishing.redirection.stream-analytics.json",
10431041
"articles/synapse-analytics/.openpublishing.redirection.synapse-analytics.json",
10441042
"articles/virtual-machine-scale-sets/.openpublishing.redirection.virtual-machine-scale-sets.json",
1045-
"articles/virtual-machines/.openpublishing.redirection.virtual-machines.json"
1043+
"articles/virtual-machines/.openpublishing.redirection.virtual-machines.json",
1044+
"articles/dev-box/.openpublishing.redirection.dev-box.json",
1045+
"articles/deployment-environments/.openpublishing.redirection.deployment-environments.json"
10461046
]
10471047
}

articles/deployment-environments/concept-common-components.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Azure Deployment Environments and Microsoft Dev Box common elements
3-
description: Discover the components that are shared by Azure Deployment Environments Preview and Microsoft Dev Box.
2+
title: Components common to Microsoft Dev Box and Azure Deployment Environments
3+
description: Discover the components that are shared by Azure Deployment Environments and Microsoft Dev Box.
44
ms.service: deployment-environments
55
ms.custom: ignite-2022
66
ms.topic: conceptual

articles/deployment-environments/concept-environments-key-concepts.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: Azure Deployment Environments key concepts
3-
description: Learn the key concepts behind Azure Deployment Environments.
2+
title: Key concepts and roles
3+
titleSuffix: Azure Deployment Environments
4+
description: Learn the key concepts, role definitions, and terminology for Azure Deployment Environments.
45
ms.service: deployment-environments
56
ms.custom: ignite-2022
67
ms.topic: conceptual
@@ -9,7 +10,7 @@ author: RoseHJM
910
ms.date: 10/12/2022
1011
---
1112

12-
# Key concepts for new Azure Deployment Environments Preview users
13+
# Key concepts for Azure Deployment Environments Preview
1314

1415
Learn about the key concepts and components of Azure Deployment Environments Preview. This knowledge can help you more effectively deploy environments for your scenarios.
1516

articles/deployment-environments/concept-environments-scenarios.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: User scenarios for Azure Deployment Environments
3-
description: Learn about scenarios enabled by Azure Deployment Environments.
2+
title: Usage scenarios for Azure Deployment Environments
3+
description: Learn how Azure Deployment Environments can be integrated into CI/CD pipelines, create sandboxes, and hackathon environments.
44
ms.service: deployment-environments
55
ms.custom: ignite-2022
66
ms.topic: conceptual
@@ -42,7 +42,7 @@ In this scenario, Azure Deployment Environments provides the following benefits:
4242
- Teams can access a fully configured environment when it's needed.
4343
- Developers can test the latest version of an application by using reusable templates to quickly create new ad hoc environments.
4444

45-
## Trainings, hands-on labs, and hackathons
45+
## Training, hands-on labs, and hackathons
4646

4747
A project in Azure Deployment Environments acts as a container for transient activities like workshops, hands-on labs, trainings, or hackathons. You can create a project to provide custom templates to each user.
4848

articles/deployment-environments/configure-catalog-item.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Add and configure a catalog item
33
titleSuffix: Azure Deployment Environments
4-
description: Learn how to add and configure a catalog item in your repository to use in your Azure Deployment Environments Preview dev center projects.
4+
description: Learn how to add and configure a catalog item to use in your dev center projects. Catalog items contain an IaC template that defines the environment.
55
services: Azure Deployment Environments
66
author: RoseHJM
77
ms.author: rosemalcolm
@@ -12,7 +12,7 @@ ms.custom: devdivchpfy22, ignite-2022
1212

1313
---
1414

15-
# Add and configure a catalog item
15+
# Add and configure a catalog item in Azure Deployment Environments
1616

1717
In Azure Deployment Environments Preview, you can use a [catalog](concept-environments-key-concepts.md#catalogs) to provide your development teams with a curated set of predefined [infrastructure as code (IaC)](/devops/deliver/what-is-infrastructure-as-code) templates called [*catalog items*](concept-environments-key-concepts.md#catalog-items).
1818

articles/deployment-environments/how-to-configure-catalog.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Add and configure a catalog
33
titleSuffix: Azure Deployment Environments
4-
description: Learn how to add and configure a catalog in your Azure Deployment Environments Preview dev center to provide deployment templates for your development teams.
4+
description: Learn how to add and configure a catalog in your Azure Deployment Environments dev center to provide deployment templates for your development teams. Catalogs are specialized repositories stored in GitHub or Azure DevOps.
55
ms.service: deployment-environments
66
ms.custom: ignite-2022
77
author: RoseHJM
@@ -10,7 +10,7 @@ ms.date: 10/12/2022
1010
ms.topic: how-to
1111
---
1212

13-
# Add and configure a catalog
13+
# Add and configure a catalog from GitHub or Azure DevOps
1414

1515
Learn how to add and configure a [catalog](./concept-environments-key-concepts.md#catalogs) in your Azure Deployment Environments Preview dev center. You can use a catalog to provide your development teams with a curated set of infrastructure as code (IaC) templates called [catalog items](./concept-environments-key-concepts.md#catalog-items).
1616

articles/deployment-environments/how-to-configure-deployment-environments-user.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Provide access to developers
2+
title: Provide user access to projects for developers
33
titleSuffix: Azure Deployment Environments
4-
description: Learn how to configure access for developers by using the Deployment Environments User built-in role.
4+
description: Learn how to configure access to projects for developers by using the Deployment Environments User built-in role.
55
ms.service: deployment-environments
66
ms.custom: ignite-2022
77
ms.author: rosemalcolm
@@ -11,7 +11,7 @@ ms.topic: how-to
1111
---
1212

1313

14-
# Provide access to developers
14+
# Provide access for developers to projects in Deployment Environments
1515

1616
In Azure Deployment Environments, development team members must get access to a specific project before they can create deployment environments. By using the built-in Deployment Environments User role, you can assign permissions to Active Directory users or groups at either the project level or the environment type level.
1717

articles/deployment-environments/how-to-configure-devcenter-environment-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Configure dev center environment types
33
titleSuffix: Azure Deployment Environments
4-
description: Learn how to configure dev center environment types to define environments that your developers can deploy.
4+
description: Learn how to define dev center level permissions and deployment settings for the environments that developers can deploy.
55
ms.service: deployment-environments
66
ms.custom: ignite-2022
77
ms.author: rosemalcolm
@@ -10,7 +10,7 @@ ms.date: 10/12/2022
1010
ms.topic: how-to
1111
---
1212

13-
# Configure environment types for your dev center
13+
# Configure environment types for a dev center
1414

1515
In Azure Deployment Environments Preview, you use [environment types](./concept-environments-key-concepts.md#dev-center-environment-types) to define the environments that development teams can deploy. You have the flexibility to name the environment types according to the nomenclature that your enterprise uses: for example, sandbox, dev, test, or production. You can specify deployment settings and the permissions that are available to developers per environment type and per project.
1616

articles/deployment-environments/how-to-configure-managed-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Configure a managed identity
33
titleSuffix: Azure Deployment Environments
4-
description: Learn how to configure a managed identity to deploy environments in your Azure Deployment Environments Preview dev center.
4+
description: Learn how to configure a managed identity to deploy environments in your Azure Deployment Environments dev center.
55
ms.service: deployment-environments
66
ms.custom: ignite-2022
77
author: RoseHJM
@@ -10,7 +10,7 @@ ms.date: 10/12/2022
1010
ms.topic: how-to
1111
---
1212

13-
# Configure a managed identity
13+
# Configure a managed identity for a dev center
1414

1515
A [managed identity](../active-directory/managed-identities-azure-resources/overview.md) adds elevated-privileges capabilities and secure authentication to any service that supports Azure Active Directory (Azure AD) authentication. Azure Deployment Environments Preview uses identities to give development teams self-serve deployment capabilities without giving them access to the subscriptions in which Azure resources are created.
1616

0 commit comments

Comments
 (0)