Merge pull request #276800 from RoseHJM/ade-freshness-01

ADE - Key Concepts - freshness updates

Author: Jill Grant

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

@@ -1,24 +1,26 @@
 ---
 title: Key concepts and roles
 titleSuffix: Azure Deployment Environments
-description: Learn the key concepts, role definitions, and terminology for Azure Deployment Environments.
+description: Learn the key concepts, role definitions, features, and terminology for Azure Deployment Environments.
 ms.service: deployment-environments
 ms.custom: build-2023
-ms.topic: conceptual
+ms.topic: concept-article
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 04/25/2023
+ms.date: 05/30/2024
+
+#customer intent: As a platform engineer, I want to understand the key concepts and roles in Azure Deployment Environments so that I can effectively deploy environments for my scenarios.
 ---
 
 # Key concepts for Azure Deployment Environments
 
-In this article, you'll learn about the key concepts and components of Azure Deployment Environments. This knowledge helps you more effectively deploy environments for your scenarios.
+In this article, you learn about the key concepts and components of Azure Deployment Environments. This knowledge helps you more effectively deploy environments for your scenarios.
 
-As you learn about Deployment Environments, you'll also encounter components of [Microsoft Dev Box](../dev-box/overview-what-is-microsoft-dev-box.md), a complementary service that shares certain architectural components. Dev Box provides developers with a cloud-based development workstation, called a dev box, which is configured with the tools they need for their work.  
+As you learn about Deployment Environments, you might encounter components of [Microsoft Dev Box](../dev-box/overview-what-is-microsoft-dev-box.md), a complementary service that shares certain architectural components. Dev Box provides developers with a cloud-based development workstation, called a dev box, which is configured with the tools they need for their work.  
 
 This diagram shows the key components of Deployment Environments and how they relate to each other. You can learn more about each component in the following sections.
 
-:::image type="content" source="media/concept-environments-key-concepts/deployment-environments-architecture.png" alt-text="Diagram showing the key components of Deployment Environments.":::
+:::image type="content" source="media/concept-environments-key-concepts/deployment-environments-architecture-new.png" alt-text="Diagram showing the key components of Deployment Environments.":::
 
 ## Dev centers
 
@@ -33,7 +35,7 @@ A dev center is a collection of [Projects](#projects) that require similar setti
 
 In Deployment Environments, a project represents a team or business function within the organization. When you associate a project with a dev center, all the settings for the dev center are automatically applied to the project. 
 
-Each project can be associated with only one dev center. Platform engineers can configure environments for a project by specifying which environment types are appropriate for the development team.
+Each project can be associated with only one dev center. Platform engineers can configure environments for a project by specifying which environment types are appropriate for the development team. To make environment definitions available for a specific development team, Project Admins can attach a catalog to a project.
 
 To enable developers to create their own deployment environments, you must [provide access for developers to projects](how-to-configure-deployment-environments-user.md) by assigning the Deployment Environments User role.
 
@@ -47,7 +49,7 @@ An environment is a collection of Azure resources on which your application is d
 
 In Azure Deployment Environments, you use [managed identities](../active-directory/managed-identities-azure-resources/overview.md) to provide elevation-of-privilege capabilities. Identities can help you provide self-serve capabilities to your development teams without giving them access to the target subscriptions in which the Azure resources are created. 
 
-The managed identity that's attached to the dev center needs to be granted appropriate access to connect to the catalogs. You should grant Contributor and User Access Administrator access to the target deployment subscriptions that are configured at the project level. The Azure Deployment Environments service uses the specific managed identity to perform the deployment on behalf of the developer.
+The managed identity attached to the dev center or project needs to be granted appropriate access to connect to the catalogs. You should grant Contributor and User Access Administrator access to the target deployment subscriptions that are configured at the project level. The Azure Deployment Environments service uses the specific managed identity to perform the deployment on behalf of the developer.
 
 ## Dev center environment types
 
@@ -64,11 +66,13 @@ Project environment types allow you to automatically apply the right set of poli
 
 ## Catalogs
 
-Catalogs help you provide a set of curated IaC templates for your development teams to create environments. Microsoft provides a [*quick start* catalog](https://github.com/microsoft/devcenter-catalog) that contains a set of sample environment definitions. You can attach the quick start catalog to a dev center to make these environment definitions available to all the projects associated with the dev center. You can modify the sample environment definitions to suit your needs. 
+Catalogs help you provide a set of curated IaC templates for your development teams to create environments. You can attach a catalog to a dev center make environment definitions available to all the projects associated with the dev center. You can also attach a catalog to a project to provide environment definitions to that specific project.
+
+Microsoft provides a [*quick start* catalog](https://github.com/microsoft/devcenter-catalog) that contains a set of sample environment definitions. You can attach the quick start catalog to a dev center or project to make these environment definitions available to developers. You can modify the sample environment definitions to suit your needs. 
 
 Alternately, you can attach your own catalog. You can attach either a [GitHub repository](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories) or an [Azure DevOps Services repository](/azure/devops/repos/get-started/what-is-repos) as a catalog. 
 
-Deployment environments scan the specified folder of the repository to find [environment definitions](#environment-definitions). The environments then make those environment definitions available to all the projects associated with the dev center.
+Deployment environments scan the specified folder of the repository to find [environment definitions](#environment-definitions). Those environment definitions are available to all the projects associated with the dev center.
 
 ## Environment definitions