Is there ever a reason to explicitly Import-Module?

I was just reading the PowerShell Modules guide page and I noticed a line on the Import-Module section:

The following actions trigger automatic importing of a module, also known as "module auto-loading."

• Using a cmdlet in a command. For example, typing Get-ExecutionPolicy imports the Microsoft.PowerShell.Security module that contains the Get-ExecutionPolicy cmdlet.

So given that, why should we ever care about using Import-Module? Isn't it always taken care for us automatically? In what case would I need to explicitly write out Import-Module?

You have to use Import-Module in the following cases :

• The module file is not in a path included in $PSModule Path
• You have different modules with the same name but in different paths
• The module is already loaded and you want to reload it after making modifications to it. (with -Force)
• To import only specific cmdlets, functions or variables from that module (with the -Cmdlet, -Function, and -Variable parameters respectively)
• To prevent loading cmdlets or functions from the module that would overwrite the commands with the same name and are already loaded in the current session ( with -NoClobber )
• To add a prefix to the nouns of the cmdlets in this module ( with -Prefix)
• To import a module from a remote computer (with the -PSSession parameter )

The list is not totally exhaustive but these are the main use cases for the Import-Module cmdlet.