Mihir Dilip

How about trying this? Note the scheme names "Bearer" and "ApiKey". ``` builder.Services.AddAuthentication(options => // this also fixes the double log { options.DefaultAuthenticateScheme = "BearerOrApiKey"; options.DefaultChallengeScheme = "BearerOrApiKey"; }) .AddJwtBearer("Bearer",...

In that case don't pass anything to `AddAuthentication` since you are using `[Authorize]` attribute with your preferred scheme name anyways.

Try referring to the [config on comment here](https://github.com/nkdAgility/azure-devops-migration-tools/issues/1217#issuecomment-1184222468)

Here is a working config, hope this helps.. update the collection urls and source/target project names. Enable the processor which you want to use and run it (assuming that you...

Try setting ProcessorEnrichers to null on your processor. ``` "Processors": [ { "$type": "TfsTeamSettingsProcessorOptions", "Enabled": true, "MigrateTeamSettings": true, "UpdateTeamSettings": true, "MigrateTeamCapacities": true, "PrefixProjectToNodes": false, "Teams": null, "ProcessorEnrichers": null, "SourceName": "TeamSettingsSource",...

I am closing this as the thread is no longer active.

I have just published version 7.0.0 where I have changed the level of this log from Information to Debug. I hope this helps.

Assuming that this is no longer a problem and closing this issue.