Back to articles

Tag archive

#azurefunctions

O
Nov 13, 2026

Obfuscating an Azure Functions Isolated-Worker App Without Breaking Function Discovery

The .NET isolated worker finds your functions through a source-generated metadata provider that bakes each function''s entry point into the assembly as a literal string — "Namespace.Class.Method" — at compile time. Obfuscate after that and renaming moves the method out from under the string, so the Functions host loads your app and then cannot find a single function. This post explains exactly which names the isolated model resolves at runtime, how to keep-list the trigger methods and binding DTOs with Nebula.NET, and how to string-encrypt and virtualize the business logic that is the whole reason the function exists.

Nov 13, 20269 min read0 reactions0 comments