You need to ensure the module is loaded. Because this is part of the VS environment from that console window, it loads some different modules by default. You can resolve this by opening up your console in VS, and use
PS ~/> $path = (Get-Module -Name EntityFrameworkCore).Path
For me, this resolved to:
PS ~/> $path
C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.entityframeworkcore.tools\2.1.1\tools\EntityFrameworkCore.psm1
So you can then take that path and import it in a regular powershell window:
PS ~/> Import-Module -Name $path
But after looking at the folder (which annoyingly doesn't follow standards), it also has a module manifest file (.psd1), which is what you should import instead:
PS ~/> Set-Location -Path 'C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.entityframeworkcore.tools\2.1.1\tools'
PS /Program Files/dotnet/sdk/NuGetFallbackFolder/microsoft.entityframeworkcore.tools/2.1.1/tools/> Import-Module -Name EntityFrameworkCore.psd1
Footnote: this is how my VS install initializes its console:
Import-Module 'C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\ENTERPRISE\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\NUGET\Modules\NuGet\NuGet.psd1'
$__pc_args=@(); $input|%{$__pc_args+=$_}; & 'C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.entityframeworkcore.tools\2.1.1\tools\init.ps1' $__pc_args[0] $__pc_args[1] $__pc_args[2]; Remove-Variable __pc_args -Scope 0