New-WebServiceProxy depends on a bunch of .NET Framework-specific APIs (notably client code in the System.Web.Services.Discovery namespace), that aren't available in newer versions of .NET - hence its absence from PowerShell 7. – Mathias R. Jessen

(I have found the invoke-webrequest cmdlet should be used {in my case atleast} in replacement for the now defunct new-webserviceproxy.)