MVC aliases in Portal Projects

Working on a portal implementation in v10. Have a need to serve up static, extension-less files. We are doing authentication through Azure AD B2C and the pages that host the forms cannot have the injected form tag that is normally rendered through the portal.

I was hoping that by simply adding some controllers and views to the root CMS project, I could specify those controllers/action under the URLs tab of a page in the content tree. That didn't work out too well... anyway, I simply need to know if/how to use MVC routing in a Portal implementation. Any thoughts would be appreciated.