Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Based on your description, the repeated increase outside the application’s working set warrants a worker/platform-level investigation. However, the graph alone does not identify a particular agent, maintenance task, or platform defect.
Is this known platform activity?
I couldn’t find a public Microsoft advisory confirming this specific West Europe pattern beginning November 10, 2026. App Service performs platform and operating-system maintenance, but that does not establish that your recurring eight-to-nine-hour resource increase is expected maintenance.
The identical outbound IP sets are consistent with shared deployment infrastructure, but do not indicate that the apps share a worker or identify the cause. Also, Basic plans already have compute dedicated to the plan; B1 is not the shared-compute hosting tier.
Resource Health showing Available does not establish that resource consumption is normal: its documented App Service checks focus on host/service availability, reachability, and content storage.
Can you identify the processes?
There is an important visibility limitation: SSH into a Linux App Service gives access to the application container, not the underlying host operating system. Consequently, top or ps there cannot provide a complete inventory of worker-host processes.
Since you have already used Linux Memory Drill Down, the next useful step is to preserve that evidence and open an Azure support request for host-level CPU and memory attribution during the recurring window. Include both plan/app resource IDs, worker instance IDs, exact UTC windows, diagnostic screenshots or exports, and a normal-period comparison.
For that comparison, use the plan’s CPU and memory metrics at one-minute granularity, split by instance, rather than relying only on hourly averages. Both metrics support this granularity and dimension. Ask support to identify the growing processes and distinguish process memory from other host memory consumption, then correlate the onset with platform changes.
Should you scale up or move?
B1 → B2 is a reasonable temporary capacity test if headroom is a concern, not a confirmed fix. B2 provides two cores and 3.5 GB RAM versus B1’s one core and 1.75 GB. I would test staging first and compare absolute consumption and application performance across the next nightly window—not just the lower percentage on a larger machine.
A move to another deployment unit is not a normal “Change plan” operation. Microsoft documents that existing plans cannot change webspaces, and supported app-to-plan moves are restricted to the same webspace. Do not assume that creating another plan or changing its resource group will move the existing workload to a different scale unit. Discuss relocation with support before undertaking a redeployment.
The public documentation establishes these diagnostic and mitigation limits, but it does not explain your November 10 onset; identifying the responsible host activity requires the resource-specific support investigation.