Managed Identity [5 of 8] | .NET on Azure for Beginners

[@ZeroPageX]

Cool! Any way to avoid the connection string to the SQL Azure database?

[@michelvosje]

I think the builder supports only 1 client. And the razor @injectable supports one service registration. So perhaps you could create your own client provider class for the clients and register the client in separate client provider instances. Now create a client provider interface for each client provider instance and let the client provider class implement those interfaces. Register the providers instance in the service collection using the interfaces.
Other ways could probably be to keep a registration by name inside the provider. And use the name to request a specific client. That would mean you won't need any interfaces and changes when adding clients.
Or you could create the client where needed.

[@Ukrainian_Tiger]

Thank you

[@nandm9654]

Can we use managed identity to create connection from an m365 service to azure service

[@CleverCottonMouth]

Where I can get advanced azure video tutorials?

[@LearnWithVarun]

If we have multiple storage accounts, then how we inject blob storage service with desired storage account reference?

[@lucasyang7726]

the storage url