Dotnet tool install 401 Unauthorized

Temporarily Disable nuget.config:

Pros: Simple and effective for quick installations.
Cons: Might introduce problems if other tasks rely on the private feed.
Steps:
Back up your original nuget.config file.
Rename or move the file to a temporary location outside the current directory.
Run dotnet tool install --global dotnet-reportgenerator-globaltool --version 4.0.15.
After successful installation, restore the original nuget.config file.
Use a Separate Directory without nuget.config:

Pros: Keeps your configuration clean and avoids unintended interactions.
Cons: Requires creating a new directory of https://qatarvisastatuscheck.qa/, and potentially changing build paths.
Steps:
Create a new directory that doesn't have a nuget.config file in its parent hierarchy.
Navigate to the new directory.
Run dotnet tool install --global dotnet-reportgenerator-globaltool --version 4.0.15.
Advanced Solution (if necessary):

Use NuGet.exe Command Line with API Key:

Pros: Provides more control and can be integrated into scripts.
Cons: More complex setup, requires obtaining an Azure Artifacts API key.
Steps:
Obtain an Azure Artifacts API Key:

Navigate to your Azure Artifacts project in Azure DevOps.
Go to Packages > Settings.
Under API, generate a personal access token with the Packages scope.
Use NuGet.exe:

Open a command prompt or terminal.
Navigate to the directory containing NuGet.exe (usually C:\Program Files\dotnet\sdk\<version>\NuGet.exe).
Run the following command, replacing placeholders with your actual values:
NuGet.exe install -Source https://pkgs.dev.azure.com/<organization>/<project>/_packaging/<feedName>/nuget/v3/ -ApiKey <your_api_key> -PackageId dotnet-reportgenerator-globaltool -Version 4.0.15 -GlobalForce