Forum Discussion
RDS serves
you can limit access to your users. the app would still be located on you internal web servers.
so the end result would be the same, with greater flexability.
If its a web app, you could use Azure AD application proxy and just expose the application via Azure.
no need for RDS if its a web based application.
Hi Kent,
Thank you for your response. My app is runing fine on my server but the problem is the internet browser in different companies. So all what I need is IE11 with SilverLight enabled and add one site as trusted site.
I get where you are coming from.
But paying RDS licensing, Server licensing, and RDS server hardware vs using Azure AD proxy or WEb application proxy, and inform the user of your apps requirements.
Consider using Scale sets for you RDS enviroment then. this will reduce Server cost during off peak times.
- I have to say that my major problem is that I cannot give customers and requirements. That's why I thought RDS would be the best option because I can set IE configurations and site according to the app's requirements.
Ok, then RDS would be you best option.
Would you be running the servers as vm's in azure ?
I have to say it is good solution but this web app was written by 3rd party and never been tested in public cloud, software provider will charge a lot to allow us to install this outside our server.
you can limit access to your users. the app would still be located on you internal web servers.
so the end result would be the same, with greater flexability.