Skip to content

Commit 6230302

Browse files
committed
fix a link
1 parent 614251d commit 6230302

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Module setting for Bicep config
33
description: Describes how to customize configuration values for modules in Bicep deployments.
44
ms.topic: conceptual
5-
ms.date: 04/08/2022
5+
ms.date: 11/10/2022
66
---
77

88
# Add module settings in the Bicep config file
@@ -122,7 +122,7 @@ You can override the public module registry alias definition in the bicepconfig.
122122

123123
## Credentials for publishing/restoring modules
124124

125-
To [publish](bicep-cli.md#publish) modules to a private module registry or to [restore](bicep-cli.md#restore) external modules to the local cache, the account must have the correct permissions to access the registry. You can configure the credential precedence for authenticating to the registry. By default, Bicep uses the credentials from the user authenticated in Azure CLI or Azure PowerShell. To customize the credential precedence, see [Add credential precedence to Bicep config](bicep-config.md#credential-precedence).
125+
To [publish](bicep-cli.md#publish) modules to a private module registry or to [restore](bicep-cli.md#restore) external modules to the local cache, the account must have the correct permissions to access the registry. You can configure the credential precedence for authenticating to the registry. By default, Bicep uses the credentials from the user authenticated in Azure CLI or Azure PowerShell. To customize the credential precedence, see [Add credential precedence to Bicep config](bicep-config.md#configure-credential-precedence).
126126

127127
## Next steps
128128

0 commit comments

Comments
 (0)