Skip to content

Commit aa10af0

Browse files
author
Jill Grant
authored
Merge pull request #290891 from mumian/1120-vscode-authentication
Update Visual Studio Code authentication method
2 parents b9d0d68 + 128b213 commit aa10af0

File tree

7 files changed

+9
-8
lines changed

7 files changed

+9
-8
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,14 @@ title: Deploy Bicep files with Visual Studio Code
33
description: Deploy Bicep files from Visual Studio Code.
44
ms.topic: how-to
55
ms.custom: devx-track-bicep
6-
ms.date: 03/20/2024
6+
ms.date: 12/03/2024
77
---
88

99
# Deploy Bicep files from Visual Studio Code
1010

1111
You can use [Visual Studio Code with the Bicep extension](./visual-studio-code.md#deploy-bicep-file) to deploy a Bicep file. You can deploy to any scope. This article shows deploying to a resource group.
1212

13-
From an opened Bicep file in VS Code, there are there ways you can find the command:
13+
From an opened Bicep file in VS Code, there are three ways you can find the command:
1414

1515
- Right-click the Bicep file name from the Explorer pane, not the one under **OPEN EDITORS**:
1616

@@ -24,9 +24,9 @@ From an opened Bicep file in VS Code, there are there ways you can find the comm
2424

2525
After you select the command, you follow the wizard to enter the values:
2626

27-
1. Sign in to Azure and select subscription.
27+
1. If you're not signed in, follow the instructions provided in the prompt to complete the sign-in process.
2828

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

3131
[!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
3232

8.79 KB
Loading
-65.1 KB
Loading

articles/azure-resource-manager/bicep/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919
- name: Quickstarts
2020
items:
2121
- name: Create Bicep templates - VS Code
22-
displayName: vscode
22+
displayName: vscode,vs code
2323
href: quickstart-create-bicep-use-visual-studio-code.md
2424
- name: Create Bicep templates - Visual Studio
2525
href: quickstart-create-bicep-use-visual-studio.md

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create Bicep files by using Visual Studio Code
33
description: Learn how to use Visual Studio Code to create Bicep files.
44
ms.topic: how-to
55
ms.custom: devx-track-bicep
6-
ms.date: 10/14/2024
6+
ms.date: 11/20/2024
77
---
88

99
# Create Bicep files by using Visual Studio Code

includes/resource-manager-vscode-authentication.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22
author: mumian
33
ms.service: azure-resource-manager
44
ms.topic: include
5-
ms.date: 01/10/2023
5+
ms.date: 12/02/2024
66
ms.author: jgao
77
---
88

99
> [!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](../articles/azure-resource-manager/bicep/bicep-config-modules.md#configure-profiles-and-credentials).
10+
> The Bicep deploy command in Visual Studio Code uses the new built-in [authentication API](https://code.visualstudio.com/api/references/vscode-api#authentication) for managing authentication. It doesn't use cloud profiles from [bicepconfig.json](../articles/azure-resource-manager/bicep/bicep-config-modules.md#configure-profiles-and-credentials).
11+
> To sign in to a custom cloud, select **Manage** > **Settings** > **Extension** > **Microsoft accounts** > **Microsoft Sovereign Cloud**. At this time, multiple signed-in accounts aren't supported.

0 commit comments

Comments
 (0)