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.
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.
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 out in the Accounts menu located in the bottom left of your VS Code window.
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.
The filtered subscriptions are stored in the new azureResourceGroups.selectedSubscriptions setting.
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.
The Azure Account extension will be deprecated in the future. Azure Account is used by many partner extensions still, so this will be a slow process. Our team will develop a deprecation plan and a reasonable date.
Until the Azure Account extension is removed as a dependency on all the Azure extensions, it will still be installed. However, it's no longer used by the extensions so signing in using the old commands will not work with the Azure Resources extension. For example, the "Azure: Sign in with Device Code", "Azure: Sign In", and "Azure: Sign Out" commands are all Azure Account specific commands, and are no longer integrated with Azure Resources.
Also, the Azure Account status bar may appear if another extension still uses Azure Account for authentication. Just know that this status bar item is no longer connected to Azure Resources, and won't reflect the authentication state of our extensions.
- [#718] Migrate to Track 2 SDK
- [#721] Refactor Azure grouping
- [#707] Use the new shared authentication provider package
- [#742] Add
ArcEnabledServersresource toAzExtResourceTypeenum - [#735] Support icons next to create commands in quick pick
- Do not depend on the Azure Account extension on VS Code for web.
- Focus feature v2 by @alexweininger in microsoft#679
- Fix compatibility issue in
BranchDataItemCacheby @alexweininger in microsoft#678
- Support for Logic Apps by @ccastrotrejo in microsoft#670
- Fail to deploy the project by clicking "Deploy" button from the notification by @alexweininger in microsoft#664
- Disable resource group walkthrough by @esweet431 in microsoft#672
- Fix missing resource icons on Windows by @nturinski in #658
- Enable strict mode and update typings by @alexweininger in #656
- VS Code for the Web support. Manage all of your Azure resources in your browser! @nturinski in microsoft#611
- Refresh subscription instead of group by @alexweininger in microsoft#618
- Don't throw if resource group isn't found by @alexweininger in microsoft#622
- Throw a no resource found error if there are no resource groups by @nturinski in microsoft#638
- Fix createClient issue by @alexweininger in microsoft#642
- Change message of create resource group by @nturinski in microsoft#637
- Update azuretools packages for various fixes by @nturinski in microsoft#632
- Make Azure resource provider mockable by @alexweininger in microsoft#650
- Add API tests by @alexweininger in microsoft#563
Full Changelog: https://github.com/microsoft/vscode-azureresourcegroups/compare/v0.6.2...v0.7.0
- Prepare for Azure Spring Apps VS Code extension integration by @wangmingliang-ms in #605
- Support Azure Account extension versions < 0.10.0 #596 fixed by @alexweininger in #597
- Infinite prompts when running commands #598 fixed by @alexweininger in #599
- Update dependencies with
npm audit fixby @alexweininger in #593
We've made significant improvements and changes to the Azure Resources API, which is now on version 2.0.0. Find out more about the Azure Resources API v2 here.
- Azure Resources API v2 by @alexweininger, @bwateratmsft, and @philliphoff in #535
- Create package for consuming extension API by @alexweininger in #530
- Add Spring Apps icon by @alexweininger in #484
- Use Azure codicon by @alexweininger in #476
- Update minimum required version of VS Code to 1.66 by @alexweininger in #523
- Dedupe Azure resources by @alexweininger in #527
- Focus a group feature.
- Fix default app to deploy by @alexweininger in #586
- Bump json-schema from 0.2.3 to 0.4.0 by @dependabot in #384
- Bump markdown-it and vsce by @dependabot in #385
- Remove dependency on fs-extra. by @philliphoff in #410
- Bump loader-utils from 1.4.0 to 1.4.1 by @dependabot in #424
- Bump ansi-regex by @dependabot in #428
- Bump minimatch and mocha by @dependabot in #429
- Bump loader-utils from 1.4.1 to 1.4.2 by @dependabot in #433
- Bump decode-uri-component from 0.2.0 to 0.2.2 by @dependabot in #443
- Bump qs from 6.5.2 to 6.5.3 by @dependabot in #450
- Bump json5 from 1.0.1 to 1.0.2 by @dependabot in #480
- Use
@vscode/vsceinstead ofvsceby @alexweininger in #548
- Azure Container Apps extension view to the Resources explorer
- Minimum version of VS Code is now 1.65.0 #346
- When subscription or group is refreshed, refresh the children as well #339
- Resources are not re-resolved after installing extensions #280
- Fix displaying Logic Apps as Function Apps #332
- Unable to load resources when using Azure Stack #296
- Open walkthrough tree item to help view #321
- Make Resources and Workspace view visible by default #310
- Make location of "Edit Tags..." context menu item consistent #313
- Update @vscode/extension-telemetry to 0.6.2 #317
- Resources are not sorted alphabetically in the list when executing commands from command palette #299
- The confirmation message is inconsistent when deleting a resource group from context menu and command palette #308
- Cannot select multiple files and folders at once for an attached storage account #300
- Extra "select subscription" step when creating a resource group by right clicking a subscription #304
- Element is already registered error when expanding group tree items #264
- Update @vscode/extension-telemetry to 0.5.2 #290
- Error: Element is already registered when focusing/unfocusing groups #284
- Resources explorer to create and manage Azure resources.
- Workspace explorer to create and manage your local project files and deploy.
- View all of your recent activities and quickly access resources you've recently created in the new Activity Log panel
- Focus on a specific group in the Resources explorer
- Group resources by Type, Resource Group, ARM Tag, and Location in the Resources explorer
- "Get started with Azure in VS Code" walkthrough
- Minimum version of VS Code is now 1.57.0
- Azure view icon to match new Azure Portal
- Icons updated to match VS Code's theme. Install new product icon themes here
- Delete resource group confirmation includes number of resources that will be deleted
- "Help and Feedback" view
This extension will be depended on by other Azure extensions, so the following changes were made:
- "Resource Groups" view is now collapsed by default to reduce clutter
- Changed some naming from "Resource Groups" to "Resources" to be more generic
- Edit tags
- View, create, and delete Azure Resource Groups