So two ways. The most popular way to do it is go ahead and have a site to site VPN between Azure and your local environment. That works fine unless you have a low latency requirement in your line of business applications. In that case, now we look at something called global file cache, which is a feature of Azure Net App files. What that does is it gives you global, and this is a big deal for our engineering customers, that gives you global file locking across huge files of all kinds of different types in one place. And it’s synchronized between your on-premise location and the Azure Cloud. So you essentially have two copies of that 150 meg AutoCAD file and its in both places. Global file cache keeps them in sync and it also locks it. So if you have a WVD station that grabs the Cloud version of the file but someone else is on-prem and wants to grab it, they won’t be able to because they’ll know it’s locked up here. It’s a simple thing but that’s how we get around the latency issue of having files on-prem and in the cloud. But it will still allow people to work with them simultaneously and that is a great solution.
But the easiest thing for people to do is just a VPN between the two and as long as you don’t have really low latency requirements that works fine.
- Can we have different Microsoft licenses for different employees?
- How many devices can I install Office apps on if I have a M365 business plan?
- Do you support persistent and non-persistent WVD?
- Can we move from a traditional Microsoft Client Server environment to Windows Server?
- Can we get rid of our on-premise domain controllers and move to Azure Domain Services?