The technique hasn't changed substantially since Dynamics AX 2012. The key difference is that we will need to manually craft the binding. We will still need to create a C# project to consume the web service, and then use it as a reference within our Dynamics 365 for Operations project.
The example service is a weather service provided by WebserviceX.net (www.webservicex.net). There is no recommendation here; it was simply the first one in when I searched for weather web services. The aim is to create a recipe that you can use for your web services: the chosen service in this case isn't relevant.
When selecting a service to use, we must check the license terms and conditions, as not all are free to use; just because the license terms aren't enforced, it does not mean that it is free to use.
