@microsoft/vscode-azext-azureauth 4.0.3 → 4.1.1

package/AzureFederatedCredentialsGuide.md

@@ -1,174 +1,174 @@
-# Setting up workflow identity federation with Azure DevOps
-
-This guide describes how to set up your Azure DevOps (ADO) and Azure environment to leverage [workflow identity federation](https://learn.microsoft.com/entra/workload-id/workload-identity-federation), enabling you to use
-`AzureDevOpsSubscriptionProvider` provided in this section. See the [README](README.md#azure-devops-subscription-provider) for more details.
-
-## 1. Create a new service principal
-
-Create a new service principal on which you will assign the necessary permissions. In this example, we use an app registration:
-
-1. Navigate to the [App Registrations](https://ms.portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) page on the Azure portal
-2. Click on `New Registration`
-
-    ![New Registration](guide-imgs/app_registration.jpg)
-
-3. Assign any name
-4. Make sure to select the first option for the account type (`Accounts in this organization directory only (Microsoft only - Single tenant)`)
-5. Leave the Redirect URI and Service Tree ID fields empty
-6. Click on `Register`
-
-    ![Register an application](guide-imgs/app_registration_2.jpg)
-
-## 2. Create a new Azure DevOps (ADO) Service Connection:
-
-Create a new ADO service connection under your organization's project. In this example, we create it under the DevDiv project:
-
- 1. Navigate to the [organization's (DevDiv) ADO page](https://devdiv.visualstudio.com/DevDiv)
- 2. Navigate to the settings page by clicking on the gear icon on the bottom left
- 3. Select the ["service connections"](https://devdiv.visualstudio.com/DevDiv/_settings/adminservices) blade from the panel on the left
-
-    ![Select service connection](guide-imgs/service_connection_1.jpg)
-
- 4. Create a new service connection by clicking on the `New service connection` button
-
-   ![Click on new service connection](guide-imgs/service_connection_2.jpg)
-
- 5. Select `Azure Resource Manager` as the type
- 6. Select `Workload Identity federation (manual)` for the authentication type
- 7. Provide a new name for your new service connection
- 8. Click on `Next`
- 9.  This will create a new draft service connection, with the `issuer` and `subject identifier` fields already filled in.
- 10. Leave this window open while you finish the next step, which will require those `issuer` and `subject identifier` fields, then you will return to this window to finish creating the service principal
-
-   ![Draft service connectoin screen](guide-imgs/service_connection_3.jpg)
-
-## 3. Create a federated credential:
-
-Create a new "federated credential" on your service principal to connect it to your new service connection:
-
- 1. Navigate back to the Azure Portal page for your service connection (app registration) from step 1
- 2. Navigate to the `Certificates & secrets` blade
- 3. Navigate to the `Federated credentials` tab
- 4. Click on the `Add credential` button
-
-   ![Add federated credential](guide-imgs/credential_1.jpg)
-
- 5. For the scenario, select `Other issuer`
- 6. For the `issuer` and `subject identifier` fields, fill in with the details of your draft service connection from the previous step
- 7. Select a new name for your new federated credential
-
-    ![Fill in issuer, subject identifier, and name fields](guide-imgs/credential_2.jpg)
-
- 8. Click on `Add`
-
-## 4. (Temporary but required) Grant your service principal reader role on the desired subscription:
-
-This step is not required for running your tests, but _is_ required to finish creating the service connection. This should be revoked after successful creation of the service connection and only necessary roles applied to the service principal.
-
- 1. On the Azure Portal, navigate to the page for the subscription you want the service principal to have access to.
- 2. Navigate to the `Access control (IAM)` blade
-
-    ![access control tab](guide-imgs/subscription_1.jpg)
-
- 3. Navigate to the `Roles` tab
- 4. Click on the `+ Add` button, and choose `Add role assignment`
-
-   ![add role](guide-imgs/subscription_2.jpg)
-
- 5. Choose `Reader` and click `Next`
- 6. Choose `User, group, or service principal`, then click on `+ Select members`
-
-   ![select members](guide-imgs/subscription_3.jpg)
-
- 7. Select your service principal from step 1
- 8. Click on `Review and assign`
-
-## 5. Finish creating your service connection:
-
-Finish creating the draft service connection you created in step 2.
-
- 1. Navigate back to your draft service connection from step 2
- 2. For Environment, select `Azure Cloud`
- 3. For Scope Level, choose `Subscription`
- 4. Under `Subscription Id`, and `Subscription Name`, write the subscription ID and name (must provide both) for the desired subscription
- 5. For `Service Principal Id`, provide the `Application (client) ID` of your app registration from step 1 (can be found in the `Overview` blade)
- 6. For the `Tenant ID`, provide the `Directory (tenant) ID` of your app registration from step 1 (can be found in `Overview` blade)
- 7. Click on `Verify and save`
-
-## 6. Revoke unnecessary read access and assign only necessary roles
-
-Revoke the `Reader` role on the subscription for the service connection after it is created. This is no longer necessary.
-
- 1. Navigate to `Access control (IAM)` blade.
- 2. Under the `Role assignments` tab, find the role assignment corresponding to the App registered on step 1
- 3. Click on `Remove` then `Yes`
- 4. You can then assign the required roles to specific resources only if required, instead of assigning `Reader` role to the entire subscription.
-
-## 7. Create a dummy Key Vault
-
-A dummy Key vault step is required to propagate the necessary environment variables in the context of the pipeline.
-
- 1. Create a new Key Vault resource in the subscription you want to test on
- 2. Give it a new name as appropriate. You can keep the default settings
-
-    ![Create key vault](guide-imgs/dummy_kv.jpg)
-
-## 8. Assign your service principal "key vault reader" role on the dummy Key Vault:
-
- 1. Navigate to `Access control (IAM)` blade on your newly created dummy key vault
-
-   ![access control tab](guide-imgs/subscription_1.jpg)
-
- 2. Navigate to the `Roles` tab
- 3. Click on the `+ Add` button, and choose `Add role assignment`
-
-   ![add role](guide-imgs/subscription_2.jpg)
-
- 4. Choose `Key Vault Reader` (**NOT** `Reader`) and click `Next`
- 5. Choose `User, group, or service principal`, then click on `+ Select members`
-
-   ![select members](guide-imgs/subscription_3.jpg)
-
- 6. Select your app registration from step 1
- 7. Click on `Review and assign`
-
-## 9. Add the dummy Key Vault step in the pipeline
-
-To ensure that the appropriate env variables are propagated in the context of running the pipeline, a dummy Key Vault step is required in that pipeline:
-
- 1. In the desired pipeline's `.yml` file, add a step as below. The `azureSubscription` field should correspond to the name of your service connection from step 2, while the `keyVaultName` field should correspond to the dummy key vault created in step 7:
-
-     ```yml
-      # This gives the TestServiceConnection service connection access to this pipeline.
-     - task: AzureKeyVault@1
-       displayName: 'Authorize TestServiceConnection service connection'
-       inputs:
-         azureSubscription: 'TestServiceConnection'
-         KeyVaultName: 'TestDummyKeyVault'
-     ```
-
- 2. In the step which runs your code (e.g., the npm test step), make sure that the `$(System.AccessToken)` variable is manually propagated as a `SYSTEM_ACCESSTOKEN` environment variable. All other required environment variables should be propagated automatically:
-
-     ```yml
-     - task: Npm@1
-       displayName: "Test"
-       inputs:
-         command: custom
-         customCommand: test
-      env:
-         SYSTEM_ACCESSTOKEN: $(System.AccessToken)
-        ```
-
-## 10. Pass the appropriate values to identify your service connection:
-
-The constructor for `AzureDevOpsSubscriptionProvider` expects three arguments in an initializer object in order to identify your service connection you setup in step 5.
-
-These are:
-
-- `serviceConnectionId`: The resource ID of the service connection created in step 2, which can be found on the `resourceId` field of the URL at the address bar, when viewing the service connection in the Azure DevOps portal
-- `domain`: The `Tenant ID` field of the service connection properties, which can be accessed by clicking "Edit" on the service connection page
-- `clientId`: The `Service Principal Id` field of the service connection properties, which can be accessed by clicking "Edit" on the service connection page
-
-  ![identifier values for service connection](guide-imgs/identifier_values.jpg)
-
-Make sure you pass an object containing these variables for the `new AzureDevOpsServiceProvider()` constructor. These values are _not_ secrets, so they can be set as environment variables, assigned as pipeline variables in ADO, accessed and assigned using an Azure Key Vault step, or even manually hardcoded in code (not recommended).
+# Setting up workflow identity federation with Azure DevOps
+
+This guide describes how to set up your Azure DevOps (ADO) and Azure environment to leverage [workflow identity federation](https://learn.microsoft.com/entra/workload-id/workload-identity-federation), enabling you to use
+`AzureDevOpsSubscriptionProvider` provided in this section. See the [README](README.md#azure-devops-subscription-provider) for more details.
+
+## 1. Create a new service principal
+
+Create a new service principal on which you will assign the necessary permissions. In this example, we use an app registration:
+
+1. Navigate to the [App Registrations](https://ms.portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) page on the Azure portal
+2. Click on `New Registration`
+
+    ![New Registration](guide-imgs/app_registration.jpg)
+
+3. Assign any name
+4. Make sure to select the first option for the account type (`Accounts in this organization directory only (Microsoft only - Single tenant)`)
+5. Leave the Redirect URI and Service Tree ID fields empty
+6. Click on `Register`
+
+    ![Register an application](guide-imgs/app_registration_2.jpg)
+
+## 2. Create a new Azure DevOps (ADO) Service Connection:
+
+Create a new ADO service connection under your organization's project. In this example, we create it under the DevDiv project:
+
+ 1. Navigate to the [organization's (DevDiv) ADO page](https://devdiv.visualstudio.com/DevDiv)
+ 2. Navigate to the settings page by clicking on the gear icon on the bottom left
+ 3. Select the ["service connections"](https://devdiv.visualstudio.com/DevDiv/_settings/adminservices) blade from the panel on the left
+
+    ![Select service connection](guide-imgs/service_connection_1.jpg)
+
+ 4. Create a new service connection by clicking on the `New service connection` button
+
+   ![Click on new service connection](guide-imgs/service_connection_2.jpg)
+
+ 5. Select `Azure Resource Manager` as the type
+ 6. Select `Workload Identity federation (manual)` for the authentication type
+ 7. Provide a new name for your new service connection
+ 8. Click on `Next`
+ 9.  This will create a new draft service connection, with the `issuer` and `subject identifier` fields already filled in.
+ 10. Leave this window open while you finish the next step, which will require those `issuer` and `subject identifier` fields, then you will return to this window to finish creating the service principal
+
+   ![Draft service connectoin screen](guide-imgs/service_connection_3.jpg)
+
+## 3. Create a federated credential:
+
+Create a new "federated credential" on your service principal to connect it to your new service connection:
+
+ 1. Navigate back to the Azure Portal page for your service connection (app registration) from step 1
+ 2. Navigate to the `Certificates & secrets` blade
+ 3. Navigate to the `Federated credentials` tab
+ 4. Click on the `Add credential` button
+
+   ![Add federated credential](guide-imgs/credential_1.jpg)
+
+ 5. For the scenario, select `Other issuer`
+ 6. For the `issuer` and `subject identifier` fields, fill in with the details of your draft service connection from the previous step
+ 7. Select a new name for your new federated credential
+
+    ![Fill in issuer, subject identifier, and name fields](guide-imgs/credential_2.jpg)
+
+ 8. Click on `Add`
+
+## 4. (Temporary but required) Grant your service principal reader role on the desired subscription:
+
+This step is not required for running your tests, but _is_ required to finish creating the service connection. This should be revoked after successful creation of the service connection and only necessary roles applied to the service principal.
+
+ 1. On the Azure Portal, navigate to the page for the subscription you want the service principal to have access to.
+ 2. Navigate to the `Access control (IAM)` blade
+
+    ![access control tab](guide-imgs/subscription_1.jpg)
+
+ 3. Navigate to the `Roles` tab
+ 4. Click on the `+ Add` button, and choose `Add role assignment`
+
+   ![add role](guide-imgs/subscription_2.jpg)
+
+ 5. Choose `Reader` and click `Next`
+ 6. Choose `User, group, or service principal`, then click on `+ Select members`
+
+   ![select members](guide-imgs/subscription_3.jpg)
+
+ 7. Select your service principal from step 1
+ 8. Click on `Review and assign`
+
+## 5. Finish creating your service connection:
+
+Finish creating the draft service connection you created in step 2.
+
+ 1. Navigate back to your draft service connection from step 2
+ 2. For Environment, select `Azure Cloud`
+ 3. For Scope Level, choose `Subscription`
+ 4. Under `Subscription Id`, and `Subscription Name`, write the subscription ID and name (must provide both) for the desired subscription
+ 5. For `Service Principal Id`, provide the `Application (client) ID` of your app registration from step 1 (can be found in the `Overview` blade)
+ 6. For the `Tenant ID`, provide the `Directory (tenant) ID` of your app registration from step 1 (can be found in `Overview` blade)
+ 7. Click on `Verify and save`
+
+## 6. Revoke unnecessary read access and assign only necessary roles
+
+Revoke the `Reader` role on the subscription for the service connection after it is created. This is no longer necessary.
+
+ 1. Navigate to `Access control (IAM)` blade.
+ 2. Under the `Role assignments` tab, find the role assignment corresponding to the App registered on step 1
+ 3. Click on `Remove` then `Yes`
+ 4. You can then assign the required roles to specific resources only if required, instead of assigning `Reader` role to the entire subscription.
+
+## 7. Create a dummy Key Vault
+
+A dummy Key vault step is required to propagate the necessary environment variables in the context of the pipeline.
+
+ 1. Create a new Key Vault resource in the subscription you want to test on
+ 2. Give it a new name as appropriate. You can keep the default settings
+
+    ![Create key vault](guide-imgs/dummy_kv.jpg)
+
+## 8. Assign your service principal "key vault reader" role on the dummy Key Vault:
+
+ 1. Navigate to `Access control (IAM)` blade on your newly created dummy key vault
+
+   ![access control tab](guide-imgs/subscription_1.jpg)
+
+ 2. Navigate to the `Roles` tab
+ 3. Click on the `+ Add` button, and choose `Add role assignment`
+
+   ![add role](guide-imgs/subscription_2.jpg)
+
+ 4. Choose `Key Vault Reader` (**NOT** `Reader`) and click `Next`
+ 5. Choose `User, group, or service principal`, then click on `+ Select members`
+
+   ![select members](guide-imgs/subscription_3.jpg)
+
+ 6. Select your app registration from step 1
+ 7. Click on `Review and assign`
+
+## 9. Add the dummy Key Vault step in the pipeline
+
+To ensure that the appropriate env variables are propagated in the context of running the pipeline, a dummy Key Vault step is required in that pipeline:
+
+ 1. In the desired pipeline's `.yml` file, add a step as below. The `azureSubscription` field should correspond to the name of your service connection from step 2, while the `keyVaultName` field should correspond to the dummy key vault created in step 7:
+
+     ```yml
+      # This gives the TestServiceConnection service connection access to this pipeline.
+     - task: AzureKeyVault@1
+       displayName: 'Authorize TestServiceConnection service connection'
+       inputs:
+         azureSubscription: 'TestServiceConnection'
+         KeyVaultName: 'TestDummyKeyVault'
+     ```
+
+ 2. In the step which runs your code (e.g., the npm test step), make sure that the `$(System.AccessToken)` variable is manually propagated as a `SYSTEM_ACCESSTOKEN` environment variable. All other required environment variables should be propagated automatically:
+
+     ```yml
+     - task: Npm@1
+       displayName: "Test"
+       inputs:
+         command: custom
+         customCommand: test
+      env:
+         SYSTEM_ACCESSTOKEN: $(System.AccessToken)
+        ```
+
+## 10. Pass the appropriate values to identify your service connection:
+
+The constructor for `AzureDevOpsSubscriptionProvider` expects three arguments in an initializer object in order to identify your service connection you setup in step 5.
+
+These are:
+
+- `serviceConnectionId`: The resource ID of the service connection created in step 2, which can be found on the `resourceId` field of the URL at the address bar, when viewing the service connection in the Azure DevOps portal
+- `domain`: The `Tenant ID` field of the service connection properties, which can be accessed by clicking "Edit" on the service connection page
+- `clientId`: The `Service Principal Id` field of the service connection properties, which can be accessed by clicking "Edit" on the service connection page
+
+  ![identifier values for service connection](guide-imgs/identifier_values.jpg)
+
+Make sure you pass an object containing these variables for the `new AzureDevOpsServiceProvider()` constructor. These values are _not_ secrets, so they can be set as environment variables, assigned as pipeline variables in ADO, accessed and assigned using an Azure Key Vault step, or even manually hardcoded in code (not recommended).

package/CHANGELOG.md

@@ -1,90 +1,98 @@
-# Change Log
-
-## 4.0.3 - 2024-12-20
-* [#1862](https://github.com/microsoft/vscode-azuretools/pull/1862) Display account name on duplicate tenant picks
-
-## 4.0.2 - 2024-12-19
-
-* [#1861](https://github.com/microsoft/vscode-azuretools/pull/1861) Remove unecessary if statement
-
-## 4.0.1 - 2024-12-17
-
-* [#1856](https://github.com/microsoft/vscode-azuretools/pull/1856) Fix tenantId undefined error
-
-## 4.0.0 - 2024-12-06
-
-### What's new
-Pass in a `vscode.LogOutputChannel` to the `VSCodeAzureSubscriptionProvider` constructor to enable logging. [#1851](https://github.com/microsoft/vscode-azuretools/pull/1851)
-
-`AzureSubscriptionProvider.getTenants()` now returns `AzureTenant[]` instead of `TenantIdDescription[]`. This is a breaking change for implementors of `AzureSubscriptionProvider`. [#1849](https://github.com/microsoft/vscode-azuretools/pull/1849)
-
-### All Changes
-* [#1849](https://github.com/microsoft/vscode-azuretools/pull/1849) Create `AzureTenant` interface which includes account property
-* [#1850](https://github.com/microsoft/vscode-azuretools/pull/1850) Clean up `isSignedIn` implementation
-* [#1851](https://github.com/microsoft/vscode-azuretools/pull/1851) Add logging to `VSCodeAzureSubscriptionProvider`
-
-## 3.1.0 - 2024-11-26
-
-* [#1827](https://github.com/microsoft/vscode-azuretools/pull/1827) Add more comprehensive support for multi-account scenarios
-* [#1815](https://github.com/microsoft/vscode-azuretools/issues/1815) Fix `VSCodeAzureSubscriptionProvider.getSubscriptions()` returning empty
-
-## 3.0.1 - 2024-11-19
-* [#1819](https://github.com/microsoft/vscode-azuretools/pull/1819) Add account parameter to `AzureSubscriptionProvider.isSignedIn()` function to fix a multi-account issue [#1809](https://github.com/microsoft/vscode-azuretools/issues/1809)
-* [#1822](https://github.com/microsoft/vscode-azuretools/pull/1822) Add check in `VSCodeAzureSubscriptionProvider.getTenants()` to fix a multi-account issue [#1809](https://github.com/microsoft/vscode-azuretools/issues/1809)
-
-## 3.0.0 - 2024-09-19
-* [#1789](https://github.com/microsoft/vscode-azuretools/pull/1789) Change `getTenants` to be compatible with the new Azure Resources tenants view. This also includes a possible breaking change where an optional parameter `account` which when passed in `getTenants` will return the tenants associated with that single account. Otherwise `getTenants` will return the tenants for all authenticated accounts.
-
-## 2.5.0 - 2024-08-06
-
-* Add `getSessionWithScopes` to get a session that has the proper scoping instead of always the default management plane
-
-## 2.4.1 - 2024-05-15
-
-* [#1729](https://github.com/microsoft/vscode-azuretools/pull/1729) Change AzureDevOpsSubscriptionProvider so that it accepts values as arguments
-
-## 2.4.0 - 2024-05-07
-
-* [#1723](https://github.com/microsoft/vscode-azuretools/pull/1723) Implementation fo AzureSub provider that leverages federated credentials
-
-## 2.1.0 - 2023-12-13
-
-* Use management endpoint for scope by default to fix deploying app service projects with sovereign clouds
-
-## 2.0.0 - 2023-11-20
-
-* Switches to use `@azure/arm-resources-subscriptions` instead of `@azure/arm-subscriptions`. Potentially a breaking change so I revved the major version.
-* Fixes an issue where the `endpoint` wasn't set for the subscription client, breaking sovereign clouds
-
-## 1.4.0 - 2023-11-03
-* [#1619](https://github.com/microsoft/vscode-azuretools/pull/1619) Make `getSession` synchronous to fix an issue that broke app service deployments
-
-## 1.3.0 - 2023-10-23
-
-* [#1610](https://github.com/microsoft/vscode-azuretools/pull/1610) Add `signInToTenant` command which facilitates signing in to a specific tenant.
-* [#1610](https://github.com/microsoft/vscode-azuretools/pull/1610) Add `getUnauthenticatedTenants` utility.
-
-## 1.2.2 - 2023-10-19
-
-* [#1608](https://github.com/microsoft/vscode-azuretools/pull/1608) Fix appending `.default` to tenant id scope which caused sign in to fail
-
-## 1.2.1 - 2023-09-26
-
-* [#1594](https://github.com/microsoft/vscode-azuretools/pull/1594) Fix getScopes always injecting the management scope, even if a scope for a different resource is specified
-* [#1597](https://github.com/microsoft/vscode-azuretools/pull/1597) Make `authentication.getSession` use scopes argument
-
-## 1.1.3 - 2023-09-14
-
-* [#1585](https://github.com/microsoft/vscode-azuretools/pull/1585) Check if tenant is signed in before listing subscriptions
-
-## 1.1.2 - 2023-07-26
-
-* [#1542](https://github.com/microsoft/vscode-azuretools/pull/1542) Fix Azure subscriptions are not returned in alphabetical order
-
-## 1.1.1 - 2023-07-26
-
-* [#1540](https://github.com/microsoft/vscode-azuretools/pull/1540) Ignore .default if it is passed as a scope
-
-## 1.0.0 - 2023-06-05
-
-Initial release
+# Change Log
+
+## 4.1.1 - 2025-02-03
+
+* Fix `VSCodeAzureSubscriptionProvider` implementation of `getSubscriptions` filtering returned subscriptions by `getSubscriptionFilters()` when the `filter` parameter is a `GetSubscriptionsFilter` object.
+
+## 4.1.0 - 2025-01-31
+
+* Add filtering `getSubscriptions` by a specific account and/or tenant.
+
+## 4.0.3 - 2024-12-20
+* [#1862](https://github.com/microsoft/vscode-azuretools/pull/1862) Display account name on duplicate tenant picks
+
+## 4.0.2 - 2024-12-19
+
+* [#1861](https://github.com/microsoft/vscode-azuretools/pull/1861) Remove unecessary if statement
+
+## 4.0.1 - 2024-12-17
+
+* [#1856](https://github.com/microsoft/vscode-azuretools/pull/1856) Fix tenantId undefined error
+
+## 4.0.0 - 2024-12-06
+
+### What's new
+Pass in a `vscode.LogOutputChannel` to the `VSCodeAzureSubscriptionProvider` constructor to enable logging. [#1851](https://github.com/microsoft/vscode-azuretools/pull/1851)
+
+`AzureSubscriptionProvider.getTenants()` now returns `AzureTenant[]` instead of `TenantIdDescription[]`. This is a breaking change for implementors of `AzureSubscriptionProvider`. [#1849](https://github.com/microsoft/vscode-azuretools/pull/1849)
+
+### All Changes
+* [#1849](https://github.com/microsoft/vscode-azuretools/pull/1849) Create `AzureTenant` interface which includes account property
+* [#1850](https://github.com/microsoft/vscode-azuretools/pull/1850) Clean up `isSignedIn` implementation
+* [#1851](https://github.com/microsoft/vscode-azuretools/pull/1851) Add logging to `VSCodeAzureSubscriptionProvider`
+
+## 3.1.0 - 2024-11-26
+
+* [#1827](https://github.com/microsoft/vscode-azuretools/pull/1827) Add more comprehensive support for multi-account scenarios
+* [#1815](https://github.com/microsoft/vscode-azuretools/issues/1815) Fix `VSCodeAzureSubscriptionProvider.getSubscriptions()` returning empty
+
+## 3.0.1 - 2024-11-19
+* [#1819](https://github.com/microsoft/vscode-azuretools/pull/1819) Add account parameter to `AzureSubscriptionProvider.isSignedIn()` function to fix a multi-account issue [#1809](https://github.com/microsoft/vscode-azuretools/issues/1809)
+* [#1822](https://github.com/microsoft/vscode-azuretools/pull/1822) Add check in `VSCodeAzureSubscriptionProvider.getTenants()` to fix a multi-account issue [#1809](https://github.com/microsoft/vscode-azuretools/issues/1809)
+
+## 3.0.0 - 2024-09-19
+* [#1789](https://github.com/microsoft/vscode-azuretools/pull/1789) Change `getTenants` to be compatible with the new Azure Resources tenants view. This also includes a possible breaking change where an optional parameter `account` which when passed in `getTenants` will return the tenants associated with that single account. Otherwise `getTenants` will return the tenants for all authenticated accounts.
+
+## 2.5.0 - 2024-08-06
+
+* Add `getSessionWithScopes` to get a session that has the proper scoping instead of always the default management plane
+
+## 2.4.1 - 2024-05-15
+
+* [#1729](https://github.com/microsoft/vscode-azuretools/pull/1729) Change AzureDevOpsSubscriptionProvider so that it accepts values as arguments
+
+## 2.4.0 - 2024-05-07
+
+* [#1723](https://github.com/microsoft/vscode-azuretools/pull/1723) Implementation fo AzureSub provider that leverages federated credentials
+
+## 2.1.0 - 2023-12-13
+
+* Use management endpoint for scope by default to fix deploying app service projects with sovereign clouds
+
+## 2.0.0 - 2023-11-20
+
+* Switches to use `@azure/arm-resources-subscriptions` instead of `@azure/arm-subscriptions`. Potentially a breaking change so I revved the major version.
+* Fixes an issue where the `endpoint` wasn't set for the subscription client, breaking sovereign clouds
+
+## 1.4.0 - 2023-11-03
+* [#1619](https://github.com/microsoft/vscode-azuretools/pull/1619) Make `getSession` synchronous to fix an issue that broke app service deployments
+
+## 1.3.0 - 2023-10-23
+
+* [#1610](https://github.com/microsoft/vscode-azuretools/pull/1610) Add `signInToTenant` command which facilitates signing in to a specific tenant.
+* [#1610](https://github.com/microsoft/vscode-azuretools/pull/1610) Add `getUnauthenticatedTenants` utility.
+
+## 1.2.2 - 2023-10-19
+
+* [#1608](https://github.com/microsoft/vscode-azuretools/pull/1608) Fix appending `.default` to tenant id scope which caused sign in to fail
+
+## 1.2.1 - 2023-09-26
+
+* [#1594](https://github.com/microsoft/vscode-azuretools/pull/1594) Fix getScopes always injecting the management scope, even if a scope for a different resource is specified
+* [#1597](https://github.com/microsoft/vscode-azuretools/pull/1597) Make `authentication.getSession` use scopes argument
+
+## 1.1.3 - 2023-09-14
+
+* [#1585](https://github.com/microsoft/vscode-azuretools/pull/1585) Check if tenant is signed in before listing subscriptions
+
+## 1.1.2 - 2023-07-26
+
+* [#1542](https://github.com/microsoft/vscode-azuretools/pull/1542) Fix Azure subscriptions are not returned in alphabetical order
+
+## 1.1.1 - 2023-07-26
+
+* [#1540](https://github.com/microsoft/vscode-azuretools/pull/1540) Ignore .default if it is passed as a scope
+
+## 1.0.0 - 2023-06-05
+
+Initial release

package/LICENSE.md

@@ -1,21 +1,21 @@
-    MIT License
-
-    Copyright (c) Microsoft Corporation. All rights reserved.
-
-    Permission is hereby granted, free of charge, to any person obtaining a copy
-    of this software and associated documentation files (the "Software"), to deal
-    in the Software without restriction, including without limitation the rights
-    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-    copies of the Software, and to permit persons to whom the Software is
-    furnished to do so, subject to the following conditions:
-
-    The above copyright notice and this permission notice shall be included in all
-    copies or substantial portions of the Software.
-
-    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-    SOFTWARE
+    MIT License
+
+    Copyright (c) Microsoft Corporation. All rights reserved.
+
+    Permission is hereby granted, free of charge, to any person obtaining a copy
+    of this software and associated documentation files (the "Software"), to deal
+    in the Software without restriction, including without limitation the rights
+    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+    copies of the Software, and to permit persons to whom the Software is
+    furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included in all
+    copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+    SOFTWARE