WVD classic support lifecycle

Question

As much as we would like, we currently cannot start using the newer ARM-based WVD deployment as this is not yet available in EU. Law and compliance regulations restrict us from using the US as a geolocation for WVD. Unfortunately this means that we are now dependent on using the (now so-called) WVD Classic deployment.

However, sticking "Classic" to your products usually don't indicate a very long lifecycle remainder for that product. As we are now in the process of building several new Cloud Desktop solutions for our customers, we really need to know if WVD Classic is going to remain supported for the next couple of years or that it is going EOL any time soon. If not, we may have to go for another option and not use WVD. Please let me know, thanks!

Answer 1

@Tom Just for clarity, the component that is not available in the EU is the metadata service or DB. This contains information about your deployment and is true for WVD and WVD Classic.

There are now 22 gateway locations in Azure geos around the globe. The gateway services your traffic to your VM’s that you have placed in any Azure region.

The EU DB is expected somewhere in Q4CY2020 as per information from our backend team.

Hope it helps!!!

If the suggested response helped you resolve your issue, do click on "Mark as Answer" and "Up-Vote" for the answer that helped you for benefit of the community.