In this Azure tutorial, we will discuss how to fix this error, which came while trying to install the MSOnline module in PowerShell in Azure.
Table of Contents
I was trying to install the MSOnline module in PowerShell. I got the above error. I was executing the below command to install the MSOnline module in PowerShell.
Install-Module -Name MSOnlineHere is the exact error that I got
PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider 'NuGet'. The package provider requires 'PackageManagement' and 'Provider' tags. Please
check if the specified package has the tags.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7468 char:21
… $null = PackageManagement\Install-PackageProvider -Name $script:N …
~~~~~~~~~~~~~
CategoryInfo : InvalidArgument: (Microsoft.Power…PackageProvider:InstallPackageProvider) [Install-PackageProvider], Exception
FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackageProviderYou can check out the screenshot below, where I executed the MSOnline PowerShell command and got the above error.

Solution
Now, Let’s try to fix it. To fix it, follow the below steps.
1. Open your Powershell ISE in Run as administrator mode.
2. Run the below line of command
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
3. Now install the NuGet package using the below command.
Install-PackageProvider -Name NuGet
As you can see above, the Nuget package was installed successfully without any issues.
4. Now, let’s try to install the MSOnline module in PowerShell. Use the below command to do so.
Install-Module -Name MSOnline
5. The below popup will appear. You can click on the Yes button.

You can see the module’s installation has started without any issues. Check out the screenshot below.

You may like the following Azure tutorials:
Wrapping Up
In this Azure tutorial, we discussed how to fix the error. No match was found for the specified search criteria for the provider ‘Nuget’. I hope it helped you to fix your issue.
I am Bijay, a Microsoft MVP (10 times) having more than 17 years of experience in the software industry. During my IT career, I got a chance to share my expertise in SharePoint and Microsoft Azure, like Azure VM, Azure Active Directory, Azure PowerShell, etc. I hope you will learn from these Azure tutorials. Read more

Thank you for sharing. I was hitting the exact same problem: the machine configuration blocked TLS 1.1 connections, and forcing TLS 1.2 allowed the connection. In my case I did not have to run that command from an elevated admin shell window.
Thank you. This is perfect and worked like a charm.
…in like Flint — Thanks ALOT!
Awesome. Just what did the trick for us non-PowerShell guys.