Extensibility model note

Author: RoseHJM

articles/deployment-environments/concept-azure-developer-cli-with-deployment-environments.md

@@ -5,7 +5,7 @@ author: RoseHJM
 ms.author: rosemalcolm
 ms.service: azure-deployment-environments
 ms.topic: concept-article
-ms.date: 10/21/2024
+ms.date: 11/08/2024
 
 # Customer intent: As a platform engineer, I want to understand ADE and `azd` work together to provision application infrastructure and deploy application code to the new infrastructure.
 
@@ -66,8 +66,7 @@ Most `azd` templates also optionally include one or more of the following folder
 
 Azure Deployment Environments catalogs consist of environment definitions: IaC templates that define the infrastructure resources that are provisioned for a deployment environment. Azure Developer CLI uses environment definitions in the catalog attached to the dev center to provision new environments. 
 
-> [!NOTE]
-> Currently, Azure Developer CLI works with ARM templates stored in the Azure Deployment Environments dev center catalog.
+Azure Developer CLI works with ARM templates stored in the Azure Deployment Environments dev center catalog. It also supports other IaC templates, such as Bicep and Terraform through the ADE extensibility model. To learn how to configure the ADE extensibility model, see [Azure Deployment Environments extensibility model](/azure/developer/azure-developer-cli/ade-extensibility-model).
 
 To properly support certain Azure Compute services, Azure Developer CLI requires more configuration settings in the IaC template. For example, you must tag app service hosts with specific information so that `azd` knows how to find the hosts and deploy the app to them.