microsoft / vscode-azureresourcegroups

VS Code extension for managing Azure resources.
https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureresourcegroups
MIT License
54 stars 29 forks source link
azure vscode

Azure Resources for Visual Studio Code (Preview)

Version Installs Build Status

View and manage Azure resources directly from VS Code.

Resources explorer

Sign up today for your free Azure account and receive 12 months of free popular services, $200 free credit and 25+ always free services 👉 Start Free.

Move to built-in VS Code authentication

The Azure Resources extension now uses the built-in VS Code Microsoft authentication provider to authenticate with Azure, and no longer depends on the Azure Account extension. This move increases the reliability of Azure authentication, especially when using a proxy.

How to Sign In

Sign in by selecting the "Sign in to Azure..." item in the Azure Resources view.

Note: Sessions won't be migrated from Azure Account to the new built-in authentication. This means you will have to sign in once Azure Resources updates to v0.8.0.

Sign in

You can also sign in using the new "Azure: Sign In" command contributed by the Azure Resources extension. Note: make sure you don't mistake it for the old Azure Account "Azure: Sign In" command.

Sign in using command palette

How to Sign Out

Sign out in the Accounts menu located in the bottom left of your VS Code window.

Sign out with Accounts menu

Filter Subscriptions

You can filter the displayed subscriptions just as before, by selecting the Filter icon on any subscription. Previously filtered subscriptions will not be migrated automatically.

Filter subscriptions

The filtered subscriptions are stored in the new azureResourceGroups.selectedSubscriptions setting.

Sign In to a Specific Directory/Tenant

Use the new "Sign in to Directory" command to sign in to directories that cannot be automatically authenticated to on initial sign in. This is useful for directories/tenants that require MFA. Executing this command will show a menu with a list of unauthenticated directories. If the list is empty, then sessions exist for each directory already.

Using Sovereign Clouds

To connect to a sovereign cloud, set the microsoft-sovereign-cloud.environment setting.

Support for vscode.dev

The Azure Resources extension fully supports running on vscode.dev and github.dev. This means you can use the Azure Resources extension to manage your Azure resources directly from your browser! Note that this does not require the Azure Accounts extension and uses VS Code's built-in authentication provider.

Features

Resource and Workspace views

Use the Resources explorer to create and manage Azure resources. Use the Workspace explorer to create files and deploy.

Azure explorer

Grouping

Change the way resources are grouped to fit your workflow.

Grouping

Activity Log

View all of your recent activities and quickly access resources you've recently created in the Activity Log.

Activity Log

Create Resources

Create an Azure resource from your installed extensions directly in VS Code.

Create Resource

Azure Cloud Shell

Azure Cloud Shell instances can be started via the terminal view in VS Code. To begin, click the dropdown arrow in the terminal view and select from either Azure Cloud Shell (Bash) or Azure Cloud Shell (PowerShell).

VS Code terminal view with context menu

If this is your first time using the Cloud Shell, the following notification will appear prompting you to set it up.

"Must setup cloud shell" notification

The Cloud Shell will load in the terminal view once you've finished configuring it.

The Azure Cloud Shell in the terminal window

You may also upload files to Cloud Shell using the Azure: Upload to Cloud Shell command.

Azure Extensions

Install these extensions to enable additional resource-specific features.

Contributing

There are a couple of ways you can contribute to this repo:

Legal

Before we can accept your pull request you will need to sign a Contribution License Agreement. All you need to do is to submit a pull request, then the PR will get appropriately labelled (e.g. cla-required, cla-norequired, cla-signed, cla-already-signed). If you already signed the agreement we will continue with reviewing the PR, otherwise system will tell you how you can sign the CLA. Once you sign the CLA all future PR's will be labeled as cla-signed.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Telemetry

VS Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more. If you don’t wish to send usage data to Microsoft, you can set the telemetry.enableTelemetry setting to false. Learn more in our FAQ.

License

MIT