How to deploy a Desktop Access 2010 app via Azure and RemoteApp?

Question

I currently sell an Access 2010 app that uses the 2010 Access Runtime for deployment on desktop PCs. I very much would like to make it available over the internet on PC/Mac/iPad using the Azure RemoteApp, if possible. The Access app has a number of supporting
files- it’s not just an Access accdb or accde file. For it to work correctly all the supporting files need to be in folders related to the main accde/accdb fie. Those files are a few other accde files, csv, pdf, and some folders.
Each of my clients (a company) may have 1-15 simultaneous users. On the Desktop Access version, I have a Front End accde installed on each workstation and a single Back End accdb data file installed on a shared drive. Each FE workstation is linked to the
single BE data file. I would need to replicate this somehow on an Azure VM (like perhaps have a designated folder for the BE data file that each user account’s FE is linked to?).
I created an Azure VM (server 2012 R2) and installed the Access Desktop App on it. I can access that full VM with RDP (and see the whole desktop, not just my Access app). What I’m trying to figure out is a way to do this with RemoteApp- can RemoteApp use
my Access 2010 app as an available ‘app’ or does the user need to see the whole VM desktop? 
As well, in my Azure portal the ‘RemoteApp’ option is grayed out ‘pending approval’ so I can’t test it. 
Any help figuring this out would be great. Thanks- 

Answer 1

N8827N
I ended up a great solution for this. I'm using 3 Windows Server 2012 R2 VMs to run it as a RemoteApp program. It's set up sort of like this:
VM 1: RD Broker
VM 2: Active Directory (where Users/Groups are created)
VM 3: AppServer (where the Access app is actually located and run on- the VM2/Active Directory 'talks' to the AppServer to create/validate users but all the action happens on VM3).
RemoteApp requires Windows Server 2012 so I don't think it'll work with Server 2008. The great thing about RemoteApp is it opens the Access 2010 Front End in a unique window, all on its own. The user doesn't need to see the Desktop of the server- they just
see the Access Navigation Form(s). 
In brief, on the VM3/AppServer I have a  unique folder for the backend Access data file and a User Account (created in the VM2 Active Directory) for each user with the frontend Access file in C/Users/Username/AppData.
RemoteApp- when the user logs in via the RemoteApp app- points to that specific user profile's frontend Access db in that location and opens it in its own window on their host computer. And since each FE is linked to a common BE data file everyone uses the
same data, just like in a regular LAN Server FE/BE setup. 
It required some changes in the Access app to deal with it- uploading images and files, emailing straight from the app, etc but it was worth it. I also had to pay a development company to set up the 2012 R2 Servers, as I didn't know the details of how to
do that myself. But I'm managing the setup, ongoing, and it's not so hard to do.
So now my customers can run the Access app on a PC, Mac, or iPad pretty much anywhere. Excellent way to extend an Access application..