Private registry publish with source

Author: mumian

articles/azure-resource-manager/bicep/media/private-module-registry/bicep-module-with-source-manifest.png

@@ -3,7 +3,7 @@ title: Create private registry for Bicep module
 description: Learn how to set up an Azure container registry for private Bicep modules
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 04/18/2023
+ms.date: 05/02/2024
 ---
 
 # Create private registry for Bicep modules
@@ -73,14 +73,38 @@ az bicep publish --file storage.bicep --target br:exampleregistry.azurecr.io/bic
 
 ---
 
+With Azure PowerShell version 11.6 and Azure CLI version xxxx, you can publish the Bicep source code with a module. If a module is published with source code to a registry, you can use `F12` (Go to Definition) to see the Bicep Code from Visual Studio Code with the Bicep extension version 0.27 or later. 
+
+# [PowerShell](#tab/azure-powershell)
+
+```azurepowershell
+Publish-AzBicepModule -FilePath ./storage.bicep -Target br:exampleregistry.azurecr.io/bicep/modules/storage:v1 -DocumentationUri https://www.contoso.com/exampleregistry.html -WithSource
+```
+
+# [Azure CLI](#tab/azure-cli)
+
+To run this deployment command, you must have the [latest version](/cli/azure/install-azure-cli) of Azure CLI.
+
+```azurecli
+az bicep publish --file storage.bicep --target br:exampleregistry.azurecr.io/bicep/modules/storage:v1 --documentationUri https://www.contoso.com/exampleregistry.html --with-source
+```
+
+---
+
+With the with source switch, you see an additional layer in the manifest:
+
+:::image type="content" source="./media/private-module-registry/bicep-module-with-source-manifest.png" alt-text="Bicep module registry with source.":::
+
+Note that if the Bicep module references a module in a Private Registry, the ACR endpoint will be visible. To hide the full endpoint, you can configure an alias for the private registry.
+
 ## View files in registry
 
 To see the published module in the portal:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Search for **container registries**.
 1. Select your registry.
-1. Select **Repositories** from the left menu.
+1. Select **Services** -> **Repositories** from the left menu.
 1. Select the module path (repository).  In the preceding example, the module path name is **bicep/modules/storage**.
 1. Select the tag. In the preceding example, the tag is **v1**.
 1. The **Artifact reference** matches the reference you'll use in the Bicep file.

articles/azure-resource-manager/bicep/private-module-registry.md

@@ -3,7 +3,7 @@ title: Create Bicep files by using Visual Studio Code
 description: Describes how to create Bicep files by using Visual Studio Code
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/05/2023
+ms.date: 05/02/2024
 ---
 
 # Create Bicep files by using Visual Studio Code
@@ -121,10 +121,14 @@ When your Bicep file uses modules that are published to a registry, the restore
 
 ## View type document
 
-From Visual Studio Code, you can easily open the template reference for the resource type you're working on. To do so, hover your cursor over the resource symbolic name, and then select **View type document**.
+From Visual Studio Code, you can open the template reference for the resource type you're working on. To do so, hover your cursor over the resource symbolic name, and then select **View type document**.
 
 :::image type="content" source="./media/visual-studio-code/visual-studio-code-bicep-view-type-document.png" alt-text="Screenshot of Visual Studio Code Bicep view type document.":::
 
+## Go go definition
+
+When defining a [module](./modules.md), regardless of the types of the referenced file - whether it is a local file, module registry file, template spec, you can open the referenced file by selecting or highlighting the module path and then press `[F12]`. If the referenced file is an [Azure Verified Modules(AVM)](https://aka.ms/avm), you can toggle between compiled JSON or Bicep file. To be able to open the Bicep file of a private registry module, ensure that the module is published to the registry with the `WithSource` switch enabled. For more information, see [Publish files to registry](./private-module-registry.md#publish-files-to-registry). The Visual Studio Code Bicep extension version 0.27 is required for opening Bicep file.
+
 ## Paste as Bicep
 
 You can paste a JSON snippet from an ARM template to Bicep file. Visual Studio Code automatically decompiles the JSON to Bicep. This feature is only available with the Bicep extension version 0.14.0 or newer. This feature is enabled by default. To disable the feature, see [VS Code and Bicep extension](./install.md#visual-studio-code-and-bicep-extension).