How to maintain and update Azure Function Connector deployed via WEBSITE_RUN_FROM_PACKAGE?

Your migration aligns with Microsoft's current connector reference: the Azure Function-based Box connector is marked deprecated, and Box Events through the Codeless Connector Framework is its replacement. A newer solution version does not establish that the old package is receiving fixes.

WEBSITE_RUN_FROM_PACKAGE mounts a deployment artifact read-only; it is not a live connection to GitHub source. Repository edits do not deploy themselves. For an externally hosted package updated at the same address, Azure Functions documents restarting the app and synchronizing triggers. Disabling package mode is unnecessary.

For scheduled analytics rules created from templates, use Review and update, compare versions, and reapply customizations through Custom changes. Verify automation references afterwards; active rules are not automatically updated when templates change.

The specific old package's republishing history and historical maintenance commitments require confirmation from the Box solution maintainer. Deprecated status means you should not depend on continuing legacy fixes.