Troubleshooting .NET 6.0 Azure Function App with IronPdf on Azure

I’m encountering an issue with a .NET 6.0 (LTS) Azure Function App on Windows, using the elastic premium plan. My application runs locally but not on Azure. I’m following guidelines from IronSoftware on How to Run HTML to PDF with .NET on Azure? and insights from a related Stack Overflow post. Initially, I considered .NET 6.0 (Isolated), but reverted due to reported support issues.

Here’s where I’m at:

Local Development: The app runs locally on .NET 6.0 but had to copy the runtime to the bin directory. I’m unsure if this step is necessary for a publish build or in the Azure environment, since its for Azureite local storage.

Testing: The app works as expected locally.

Deployment: I’ve used a publish profile, disabled ‘run as package’, and added extensive logging. However, the app fails on Azure when running the code from the Ironsoft example.

failing here:

log.LogInformation("About to render pdf...");
ChromePdfRenderer renderer = new ChromePdfRenderer();
using var doc = renderer.RenderUrlAsPdf("https://www.google.com/");
log.LogInformation("finished rendering pdf...");

example code:

log.LogInformation("Entered PrintPdf API function...");
        IronPdf.Installation.LicenseKey = "MYCOMPANYKEY"; 
        IronPdf.Logging.Logger.EnableDebugging = false;
        IronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.Custom;
        IronPdf.Logging.Logger.CustomLogger = log;
        Installation.LinuxAndDockerDependenciesAutoConfig = false;
        Installation.ChromeGpuMode = IronPdf.Engines.Chrome.ChromeGpuModes.Disabled;
        try
        {
            log.LogInformation("About to render pdf...");
            ChromePdfRenderer renderer = new ChromePdfRenderer();
            using var doc = renderer.RenderUrlAsPdf("https://www.google.com/");
            log.LogInformation("finished rendering pdf...");
            //return new FileContentResult(doc.BinaryData, "application/pdf") { FileDownloadName = "google.pdf" };
        }
        catch (Exception e)
        {
            log.LogError(e, "Error while rendering pdf", e);
        }

Error Details:

It looks like it fails on the subprocess launch in the second to last trace, but hard exits without hitting the try catch.

Given this context, I have one question:

What could be causing the IronPdf.ChromePdfRenderer to fail on Azure, despite functioning locally?
Any insights or suggestions for troubleshooting this issue would be greatly appreciated.