Support Bring-Your-Own-App for AzureFunctions

[christopheranderson]

Scenario: While the auto-provisioned Azure Function App is great for basic use cases and getting started, being able to bring and manage your own app service apps will enable more complex applications without forcing users out of the functions portal UX.

Priority: Post-MVP

Open questions:

1. What's the best experience for users to bring their own apps, without added complexity to Azure Functions UX?
   • Potentially an Azure Portal action to "enable" the app for Azure Functions?
   • Maybe it is entirely transparent and all App Service Apps
   • Dedicated app type (kind = 'functions')

[davidebbo]

Relying on a 'kind' would I think make sense. The hard problems to solve are:

• When just going to the Functions portal, how does it know what site to use?
• Hopefully, the ARM API will let us efficiently list all functions in the subscription that have that kind
• Then I guess we could show a drop down. We're already going to have drop downs for Tenant and Sub.

[mathewc]

Our site extension takes over the www root. In the "bring your own", are you talking about a site with no content?

[davidebbo]

No, no change to that model. By bring your own, he means the ability to control the RG/ServicePlan/WebApp in advanced scenarios, instead of us always magically creating things. But whichever site we end up using will use the same model.

So that should have no bearing on your code :)

[christopheranderson]

Yeah, I don't have any particular care on what the gesture is, as long as there is one, to use an arbitrary app in an arbitrary app service plan which can be deployed by portal/ARM api.