diff --git a/README.md b/README.md index a8465dfb..c3b39f71 100644 --- a/README.md +++ b/README.md @@ -22,6 +22,8 @@ winget install "Key Vault Explorer" --source msstore ### macOS and Linux Download from the [releases page](https://github.com/cricketthomas/AzureKeyVaultExplorer/releases). + +![Downloads](https://img.shields.io/github/downloads/cricketthomas/AzureKeyVaultExplorer/total)

Named 'Key Vault Explorer' in the Microsoft Store.

@@ -89,8 +91,8 @@ After downloading the `.exe`, Windows may block it (unless you got it from winge ## Azure CLI > [!NOTE] -> You can use a custom client ID that belongs to Microsoft Azure CLI. This is intended for testing only and is not recommended by the maintainers of this repository, as it may violate Microsoft’s Terms of Service. -> Doing so can bypass the need for an IT administrator to grant permissions to the application, effectively circumventing the standard consent process. Once done, click save in the settings page and restart the application. +> You can use a custom client ID that belongs to Microsoft Azure CLI `04b07795-8ddb-461a-bbee-02f9e1bf7b46`. This is intended for testing only and is not recommended by the maintainers of this repository, as it may violate Microsoft’s Terms of Service. +> Doing so can bypass the need for an IT administrator to grant permissions to the application, effectively circumventing the standard consent process. Navigate to the Ssttings page, check the "Custom Client ID" checkbox, add the aformentioned Clinet Id, click save, and restart the application. > See this article for more details on the well-known client ID. https://rakhesh.com/azure/well-known-client-ids/ image diff --git a/docs/CUSTOM-CLIENT-TENANT-ID.md b/docs/CUSTOM-CLIENT-TENANT-ID.md index b34af7ac..dfa222f6 100644 --- a/docs/CUSTOM-CLIENT-TENANT-ID.md +++ b/docs/CUSTOM-CLIENT-TENANT-ID.md @@ -1,5 +1,19 @@ ## Using your own Client ID / Application ID +### Easiest Option: + +### Azure CLI + +> [!NOTE] +> You can use a custom client ID that belongs to Microsoft Azure CLI `04b07795-8ddb-461a-bbee-02f9e1bf7b46`. This is intended for testing only and is not recommended by the maintainers of this repository, as it may violate Microsoft’s Terms of Service. +> Doing so can bypass the need for an IT Administrator to grant permissions to the application enabling a zero change setup in most tenants and is enterprise friendly. THis effectively circumventing the standard consent process. Navigate to the Ssttings page, check the "Custom Client ID" checkbox, add the aformentioned Clinet Id, click save, and restart the application. +> See this article for more details on the well-known client ID. https://rakhesh.com/azure/well-known-client-ids/ + +image + + +--- + This allows you to use your own enterprise application instead of the default one. Requires the checkbox to be selected and a valid Client ID. 1. Create an Enterprise application in your Azure AD / Entra tenant: diff --git a/docs/FIRST-TIME-SETUP.md b/docs/FIRST-TIME-SETUP.md index 349ccb84..cedca2bb 100644 --- a/docs/FIRST-TIME-SETUP.md +++ b/docs/FIRST-TIME-SETUP.md @@ -8,6 +8,12 @@ When running Key Vault Explorer for the first time, you may encounter an error l This means your Azure tenant global admin needs to grant consent. Have them open one of the following URLs in a browser: +**Azure CLI CLIENT ID:** +- This approach should require no intervention if Azure CLI is used by your organization. Please see the instructions here: +[Using your own Client ID / Tenant ID](CUSTOM-CLIENT-TENANT-ID.md/#azure-cli) + + + **Default Client ID:** ```