Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Hi @SimonY-1215
In Azure App Service, the “Current working directory” shown in Kudu is process-specific and dynamically set at runtime, not a fixed system path like C:\Windows\system32. The path you are seeing (C:\Program Files (x86)\SiteExtensions\ApplicationInsightsAgent\...\ExtensionManager) indicates that the active process is running from the Application Insights site extension, which defines its own working directory when it starts. This is expected behavior in App Service, where multiple components (Kudu, site extensions, your app) run as separate processes, each with its own working directory. This setting does not affect your application’s execution, as your app content is always hosted under D:\home\site\wwwroot, and Microsoft recommends using absolute paths or environment variables instead of relying on the current working directory. Additionally, this value cannot be manually reset to C:\Windows\system32 because it is controlled by the process startup context, not by App Service configuration.
https://learn.microsoft.com/en-us/azure/app-service/monitor-app-service?tabs=aspnetcore
https://learn.microsoft.com/en-us/azure/app-service/operating-system-functionality
https://learn.microsoft.com/en-us/azure/app-service/resources-kudu
Let me know if you have any further assistance needed.