The change was for the designer, not the runtime We made sure you can now use the designer on a SQL Server database on azure for database first scenarios. To do that we ported a transient error recovery strategy as we use in the runtime to the driver foundation code
The changelog on the website lists the package/component the change is for as well, which states 'drivers' So for the runtime and thus your code, nothing changes as the changes are in the drivers, the runtime already worked OK on azure and will keep on doing so.