0.9.0

In preparation of the Azure Account extension being deprecated at the end of the year, we've moved the Azure Cloud Shell feature to the Azure Resources extension. Apart from moving codebases, the feature is the same from a users perspective. Authentication for the Cloud Shell feature is now handled by the VS Code built-in Microsoft authentication provider, which means you may have to login upon first use of the migrated feature.

Additionally, we've fixed two longstanding Azure Cloud Shell bugs that caused issues launching the feature on Linux and macOS: #719 and #959.

Added

• [848] Migrate Azure Cloud Shell feature from the Azure Account extension

Fixed

• [855] Stop using --ms-enable-electron-run-as-node flag to fix launching Cloud Shell on macOS
• [854] Use process.execPath instead of process.argv0 to fix launching Cloud Shell on Linux

0.8.6

Added

• [777] Add Azure Web Pub Sub service to the resources view. See the new Azure Web PubSub extension for details.

0.8.5

Fixed

• [820] Fix bug that prevents resource groups from loading when there's a ghost resource
• [825] Throw a better error for any item that resolves as undefined

Engineering

• [829] Add listSubscriptions method to v1 Resource Groups API to support 4402
• [836] Add maintainCloudShellConnection command

0.8.4

Added

• [747] Add Azure Arc-enabled machines to the resources view. See the new Azure Arc-enabled machines extension for more details.

Fixed

• [811] Update walkthrough sign in command to use the new built-in authentication provider

0.8.3

Fixed

• Fix zip deploy failing with a "Number of entries expected in End Of Central Directory" error
• Fix sovereign cloud support

0.8.2

Fixed

• Fix zip deploy on sovereign clouds (Azure Functions and Azure App Service)

0.8.1

Fixed

• Fix support for sovereign clouds

Note: Make sure to set microsoft-sovereign-cloud.environment to the correct environment when using a sovereign cloud.

0.8.0

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.

What's new?

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.

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.

How to Sign Out

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

Filter Subscriptions

You can filter the displayed subscriptions just as before, by selecting the Filter icon on any subscription.

The filtered subscriptions are stored in the new azureResourceGroups.selectedSubscriptions setting. Previously filtered subscriptions will not be migrated automatically.

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.

Azure Account extension

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.

0.7.5

Fixed

• Do not depend on the Azure Account extension on VS Code for web.

0.7.4

Added

• Focus feature v2 by @alexweininger in #679

Fixed

• Fix compatibility issue in BranchDataItemCache by @alexweininger in #678