A function app provides a hosting boundary and runtime configuration for functions. Creating that boundary is different from deploying and testing a handler. The application also needs appropriate identity, settings and dependencies for the event it will process.
The original intake tasks save runtime and app settings. They deliberately stop short of claiming that a handler ran. Think about repeated messages and stable business identifiers when designing the eventual implementation. A retry can be necessary after a failure, but it can also repeat an external side effect if the handler lacks an idempotency plan. The local account checks configuration and decisions; real execution requires a deployed handler and independent event tests.
Separate hosting configuration from handler deployment and behavior.