Skip to content

Commit edbcaa9

Browse files
committed
update vscode authentication
1 parent 1663d2e commit edbcaa9

File tree

4 files changed

+28
-12
lines changed

4 files changed

+28
-12
lines changed

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

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Bicep config file
33
description: Describes the configuration file for your Bicep deployments
44
ms.topic: conceptual
5-
ms.date: 11/02/2022
5+
ms.date: 12/06/2022
66
---
77

88
# Configure your Bicep environment
@@ -29,12 +29,12 @@ You can configure the credential precedence for authenticating to the registry.
2929

3030
```json
3131
{
32-
"cloud": {
33-
"credentialPrecedence": [
34-
"AzureCLI",
35-
"AzurePowerShell"
36-
]
37-
}
32+
"cloud": {
33+
"credentialPrecedence": [
34+
"AzureCLI",
35+
"AzurePowerShell"
36+
]
37+
}
3838
}
3939
```
4040

@@ -47,6 +47,8 @@ The available credential types are:
4747
- VisualStudio
4848
- VisualStudioCode
4949

50+
[!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
51+
5052
## Intellisense
5153

5254
The Bicep extension for Visual Studio Code supports intellisense for your `bicepconfig.json` file. Use the intellisense to discover available properties and values.
@@ -55,6 +57,6 @@ The Bicep extension for Visual Studio Code supports intellisense for your `bicep
5557

5658
## Next steps
5759

58-
* [Add module settings in Bicep config](bicep-config-modules.md)
59-
* [Add linter settings to Bicep config](bicep-config-linter.md)
60-
* Learn about the [Bicep linter](linter.md)
60+
- [Add module settings in Bicep config](bicep-config-modules.md)
61+
- [Add linter settings to Bicep config](bicep-config-linter.md)
62+
- Learn about the [Bicep linter](linter.md)

articles/azure-resource-manager/bicep/deploy-vscode.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Deploy Bicep files from Visual Studio Code.
44
author: mumian
55
ms.author: jgao
66
ms.topic: conceptual
7-
ms.date: 08/04/2022
7+
ms.date: 12/06/2022
88
---
99

1010
# Deploy Bicep files from Visual Studio Code
@@ -29,6 +29,8 @@ After you select the command, you follow the wizard to enter the values:
2929

3030
:::image type="content" source="./media/deploy-vscode/bicep-deploy-select-subscription.png" alt-text="Screenshot of Select subscription.":::
3131

32+
[!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
33+
3234
1. Select or create a resource group.
3335

3436
1. Select a parameter file or select **None** to enter the parameter values.

articles/azure-resource-manager/bicep/visual-studio-code.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create Bicep files by using Visual Studio Code
33
description: Describes how to create Bicep files by using Visual Studio Code
44
ms.topic: conceptual
5-
ms.date: 11/11/2022
5+
ms.date: 12/06/2022
66
---
77

88
# Create Bicep files by using Visual Studio Code
@@ -64,6 +64,8 @@ This command decompiles an ARM JSON template into a Bicep file, and places it in
6464

6565
You can deploy Bicep files directly from Visual Studio Code. Select **Deploy Bicep file** from the command palette or from the context menu. The extension prompts you to sign in Azure, select subscription, create/select resource group, and enter parameter values.
6666

67+
[!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
68+
6769
### Generate parameters file
6870

6971
This command creates a parameter file in the same folder as the Bicep file. The new parameter file name is `<bicep-file-name>.parameters.json`.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
author: mumian
3+
ms.service: azure-resource-manager
4+
ms.topic: include
5+
ms.date: 12/06/2022
6+
ms.author: jgao
7+
---
8+
9+
> [!NOTE]
10+
> The Bicep deploy command from within vscode uses the [Azure Account extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) for authentication. It doesn't use cloud profiles from [bicepconfig.json](./bicep-config.md#credential-precedence).

0 commit comments

Comments
 (0)