Is it also possible to enable us to actually get a logger in the Startup? At some point we need to log more info during the startup and our only possibility is to create a logger manually by bypassing every previously added settings using the builder.

Is it also possible to enable us to actually get a logger in the Startup? At some point we need to log more info during the startup and our only possibility is to create a logger manually by bypassing every previously added settings using the builder.

If we try to get a `ILogger`, that raised this following exception:

> System.InvalidOperationException: 'Unable to resolve service for type 'Microsoft.Azure.WebJobs.Script.IFileLoggingStatusManager' while attempting to activate 'Microsoft.Azure.WebJobs.Script.Diagnostics.HostFileLoggerProvider'.'

I'm aware that during the `Configure` not all dependencies are already there and more could be added later on. But this statement doesn't solve what everybody is always asking: have logging in the startup.

This is what we need to do to "fix" this issue:
```csharp
var loggerFactory = LoggerFactory.Create(builder => builder.AddConsole());
logger = loggerFactory.CreateLogger();
```

_Originally posted by @pellea in https://github.com/Azure/azure-functions-host/issues/5782#issuecomment-627788704_

Start by reproducing the exception when resolving ILogger during Configure, then inspect how HostFileLoggerProvider depends on IFileLoggingStatusManager and how startup services are registered. Done means Startup can obtain a logger without manually creating a separate factory or bypassing previously configured settings.

Written by the indexing model from the issue text.