How do you manage Tenant-specific configurations in DI without polluting business logic?

Tenant configuration should be injected via the Options pattern dynamically resolved per-request, keeping the tenant logic strictly out of the domain.

The DI container resolves an ITenantContext (scoped) based on the HTTP header. Then, it configures an IOptionsSnapshot<TenantSettings> based on that context. The business logic simply asks for TenantSettings and remains oblivious to how the tenant was identified.