Migration question: strategy for Scoped services

[LuisM000]

Hi!
We’re migrating a large Bot Framework solution (using TeamsActivityHandler) to the Microsoft 365 Agents SDK. Our code relies heavily on Scoped services across many layers.

As part of the migration, we’re switching to the new CloudAdapter, which enqueues tasks. I understand that HostedActivityService does not resolve IAgent within a scope, which could cause issues since it won’t share the same request scope.
However, we still need a safe way to use Scoped services per “turn.”

Questions:

1. What’s the recommended migration approach for solutions that rely heavily on Scoped services?
2. Will there be a “synchronous” adapter option (similar to Bot Framework) that processes inline, without using the background queue, to make migration smoother?

Thanks!

[tracyboehrer]

I see this and will need to consider the options.

[architectsapience]

@tracyboehrer using IServiceScopeFactory to create a new scope inside a given turn handler would be problematic?

eg. let's say we create this handler: OnActivity(ActivityTypes.Message, OnMessageAsync, rank: RouteRank.Last);

Within our handler OnMessageAsync, we create 'manually' the following scope and do whatever it takes with the scoped service:

using var scope = _serviceScopeFactory.CreateScope();
var myScopedService = scope.ServiceProvider.GetRequiredService();

What would be the pros and cons of this approach? Overall, would this be safe to use?

[EXT97937]

same problem here, any solution? @tracyboehrer??