This technique hasn't changed substantially since Dynamics AX 2012. The key difference is that we will need to manually craft the binding. We still need to create a C# project to consume the web service, and then use it as a reference within our F&O project.
The example service is a weather service provided by Open Weather (https://openweathermap.org/). There is no recommendation here. It was simply the first one I found 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 since not all of them are free to use. Just because the license terms aren't enforced doesn't mean that the service is free to use.
