Use AVM

Author: mumian

articles/azure-resource-manager/bicep/bicep-config-modules.md

@@ -3,7 +3,7 @@ title: Module setting for Bicep config
 description: Describes how to customize configuration values for modules in Bicep deployments.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/16/2024
+ms.date: 06/10/2024
 ---
 
 # Add module settings in the Bicep config file
@@ -100,7 +100,7 @@ For a template spec, use:
 module stgModule  'ts/CoreSpecs:storage:v1' = {
 ```
 
-An alias has been predefined for the [public module registry](./modules.md#path-to-module). To reference a public module, you can use the format:
+An alias has been predefined for [Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/). To reference an Azure verified module, you can use the format:
 
 ```bicep
 br/public:<file>:<tag>

articles/azure-resource-manager/bicep/bicep-using.md

@@ -3,7 +3,7 @@ title: Using statement
 description: Describes how to use the using statement in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 10/11/2023
+ms.date: 06/10/2024
 ---
 
 # Using statement
@@ -29,7 +29,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   using '<path>/<file-name>.json'
   ```
 
-- To use public module:
+- To use [Azure Verified Modules](./modules.md##path-to-module):
 
   ```bicep
   using 'br/public:<file-path>:<tag>'
@@ -38,7 +38,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   For example:
 
   ```bicep
-  using 'br/public:storage/storage-account:3.0.1'
+  using 'br/public:avm/res/storage/storage-account:0.9.0' 
 
   param name = 'mystorage'
   ```

articles/azure-resource-manager/bicep/media/modules/bicep-azure-verified-modules-avm-reference.png

@@ -3,14 +3,14 @@ title: Bicep modules
 description: Describes how to define a module in a Bicep file, and how to use module scopes.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/02/2024
+ms.date: 06/06/2024
 ---
 
 # Bicep modules
 
 Bicep enables you to organize deployments into modules. A module is a Bicep file (or an ARM JSON template) that is deployed from another Bicep file. With modules, you improve the readability of your Bicep files by encapsulating complex details of your deployment. You can also easily reuse modules for different deployments.
 
-To share modules with other people in your organization, create a [template spec](../bicep/template-specs.md), [public registry](https://github.com/Azure/bicep-registry-modules), or [private registry](private-module-registry.md). Template specs and modules in the registry are only available to users with the correct permissions.
+To share modules with other people in your organization, create a [template spec](../bicep/template-specs.md), or [private registry](private-module-registry.md). Template specs and modules in the registry are only available to users with the correct permissions.
 
 > [!TIP]
 > The choice between module registry and template specs is mostly a matter of preference. There are a few things to consider when you choose between the two:
@@ -93,32 +93,42 @@ For example, to deploy a file that is up one level in the directory from your ma
 
 ### File in registry
 
-#### Public module registry
+#### Azure Verified Modules
 
-The public module registry is hosted in a Microsoft container registry (MCR). The source code and the modules are stored in [GitHub](https://github.com/azure/bicep-registry-modules). To view the available modules and their versions, see [Bicep registry Module Index](https://aka.ms/br-module-index). 
+> [!NOTE]
+> Non-AVM modules are retired from the public registry.
+
+[Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) are pre-built, pre-tested, and pre-verified modules for deploying resources on Azure. These modules are created by Microsoft or trusted partners and are designed to simplify and accelerate the deployment process for common Azure resources and configurations. Select the highlighted numbers in the following screenshot to see the list of modules.
 
-:::image type="content" source="./media/modules/bicep-public-module-registry-modules.png" alt-text="The screenshot of public module registry.":::
+:::image type="content" source="./media/modules/bicep-azure-verified-modules-avm.png" alt-text="The screenshot of Azure Verified Modules(AVM).":::
 
-Select the versions to see the available versions. You can also select **Source code** to see the module source code, and open the Readme files.
+The module list shows the latest version. Select the version number to see a list of available versions:
 
-There are only a few published modules currently. More modules are coming. If you like to contribute to the registry, see the [contribution guide](https://github.com/Azure/bicep-registry-modules/blob/main/CONTRIBUTING.md).
+:::image type="content" source="./media/modules/bicep-azure-verified-modules-avm-version.png" alt-text="The screenshot of Azure Verified Modules(AVM).":::
 
-To link to a public registry module, specify the module path with the following syntax:
+To link to an Azure verified module, specify the module path with the following syntax:
 
 ```bicep
 module <symbolic-name> 'br/public:<file-path>:<tag>' = {}
 ```
 
-- **br/public** is the alias for the public module registry. This alias is predefined in your configuration.
+- **br/public** is the alias for Azure Verfied Modules. This alias is predefined in your configuration.
 - **file path** can contain segments that can be separated by the `/` character.
 - **tag** is used for specifying a version for the module.
 
 For example:
 
-::: code language="bicep" source="~/azure-docs-bicep-samples/syntax-samples/modules/registry-definition-public.bicep" highlight="1" :::
+```bicep
+module storage 'br/public:avm/res/storage/storage-account:0.9.0' = {
+  name: 'myStorage'
+  params: {
+    name: 'store${resourceGroup().name}'
+  }
+}
+```
 
 > [!NOTE]
-> **br/public** is the alias for the public registry. It can also be written as
+> **br/public** is the alias for Azure Verified Modules. It can also be written as:
 >
 > ```bicep
 > module <symbolic-name> 'br:mcr.microsoft.com/bicep/<file-path>:<tag>' = {}
@@ -149,7 +159,14 @@ The full path for a module in a registry can be long. Instead of providing the f
 
 An alias for the public module registry has been predefined:
 
-::: code language="bicep" source="~/azure-docs-bicep-samples/syntax-samples/modules/alias-definition-public.bicep" highlight="1" :::
+```bicep
+module storage 'br/public:avm/res/storage/storage-account:0.9.0' = {
+  name: 'myStorage'
+  params: {
+    name: 'store${resourceGroup().name}'
+  }
+}
+```
 
 You can override the public alias in the bicepconfig.json file.
 

articles/azure-resource-manager/bicep/media/modules/bicep-azure-verified-modules-avm-version.png

@@ -3,7 +3,7 @@ title: Create parameters files for Bicep deployment
 description: Create parameters file for passing in values during deployment of a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 04/01/2024
+ms.date: 06/10/2024
 ---
 
 # Create parameters files for Bicep deployment
@@ -43,7 +43,7 @@ using './azuredeploy.json'
 ```
 
 ```bicep
-using 'br/public:storage/storage-account:3.0.1'
+using 'br/public:avm/res/storage/storage-account:0.9.0' 
 ...
 ```
 

articles/azure-resource-manager/bicep/media/modules/bicep-azure-verified-modules-avm.png

@@ -3,12 +3,12 @@ title: Create private registry for Bicep module
 description: Learn how to set up an Azure container registry for private Bicep modules
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 05/10/2024
+ms.date: 06/10/2024
 ---
 
 # Create private registry for Bicep modules
 
-To share [modules](modules.md) within your organization, you can create a private module registry. You publish modules to that registry and give read access to users who need to deploy the modules. After the modules are shared in the registries, you can reference them from your Bicep files. To contribute to the public module registry, see the [contribution guide](https://github.com/Azure/bicep-registry-modules/blob/main/CONTRIBUTING.md).
+To share [modules](modules.md) within your organization, you can create a private module registry. You publish modules to that registry and give read access to users who need to deploy the modules. After the modules are shared in the registries, you can reference them from your Bicep files. To use Azure Verified Modules, see [Bicep Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/).
 
 To work with module registries, you must have [Bicep CLI](./install.md) version **0.4.1008 or later**. To use with Azure CLI, you must also have version **2.31.0 or later**; to use with Azure PowerShell, you must also have version **7.0.0** or later.
 

articles/azure-resource-manager/bicep/modules.md

@@ -1,15 +1,15 @@
 ---
 title: Publish modules to private module registry
 description: Publish Bicep modules to private module registry and use the modules.
-ms.date: 04/18/2023
+ms.date: 06/10/2024
 ms.topic: quickstart
 ms.custom: mode-api, devx-track-bicep
 #Customer intent: As a developer new to Azure deployment, I want to learn how to publish Bicep modules to private module registry.
 ---
 
 # Quickstart: Publish Bicep modules to private module registry
 
-Learn how to publish Bicep modules to private modules registry, and how to call the modules from your Bicep files. Private module registry allows you to share Bicep modules within your organization.  To learn more, see [Create private registry for Bicep modules](./private-module-registry.md). To contribute to the public module registry, see the [contribution guide](https://github.com/Azure/bicep-registry-modules/blob/main/CONTRIBUTING.md).
+Learn how to publish Bicep modules to private modules registry, and how to call the modules from your Bicep files. Private module registry allows you to share Bicep modules within your organization.  To learn more, see [Create private registry for Bicep modules](./private-module-registry.md). 
 
 ## Prerequisites