Which way to go-advice needed

[guyinkalamazoo3]

I know this is a rather broad question, but here is my scenario and I have several different solutions. I developed an app that is in current production here at our facility using Power Apps. It has an on-prem SQL server database backend. We have just over 1,000 personnel who use it at least once on a yearly basis. Now that Power Apps has changed their licensing model and it sounds like we would have to add 1,000 Power App licenses at $7/month, that isn't going to happen. So in doing some research I have found the following:

1. I have signed up for an Azure test account and have seen where SQL in Azure would probably be much more cost effective then paying $7K per month for users who mostly wouldn't even use a power app on a monthly basis (the issue with Power Apps lies in the fact that we are using a data gateway for an on-prem database server).
2. I am a .Net programmer and can create either a classic Windows Form application or an ASP .Net Web application. The obvious pro with this is cost. We already have the systems in place for this. The con is that I am the only person here in this facility that knows programming. Can an ASP.Net app be served up in an iframe in SharePoint?
3. Use SharePoint online as the database (using lists) and program from there

Management does not want to pay the Power Apps licensing fees (and at least our "trial" period was extended to Jan 1, 2020) and they are very hesitant to have me build my own application whether it be a Windows form or and ASP web app due to that "getting hit by the bus" theory.

Has anyone hit a scenario like this and what would be your advice? I am leaning towards building the ASP.Net Web app and serving it up through SharePoint online, or just publishing it to an in-house IIS server.

Thanks


Brad Allison

Continue reading...