Closed boblangley closed 4 months ago
I think the workaround mentioned in https://github.com/Particular/NServiceBus.AzureFunctions.InProcess.ServiceBus/issues/549 would work here as well until this gets addressed
@andreasohlund I don't believe that workaround will work.
The Azure Service Bus transport public API only allows setting the token credential through the constructor or via a TransportExtensions extension method. The Worker model owns the usage of the constructor and as shown in this issue using configuration.AdvancedConfiguration.UseTransport(…)
with a properly configured transport doesn't appear to work.
Subscribed to this one, since we're really waiting for this feature in Azure Functions (isolated).
Also subscribing to this, much needed.
Btw there was an attempt for a pr: https://github.com/Particular/NServiceBus.AzureFunctions.InProcess.ServiceBus/pull/718
It seems like the fix is fairly simple. Is there a reason why managed identity is not supported by particular?
It seems like the only way is to fork the repo an build a custom artifact and use that, but that is just silly.
The PR was exactly that, an attempt that was unfortunately abandoned because of other priorities. I also don't have more details about that PR than that. We never really make promises about when we pick up or release features like this, but I can tell you that managed identity is very high on our radar for possibly Q1 2024.
We've been able to use Managed Identity with NServiceBus.AzureFunctions.Worker.ServiceBus version 4.0.0-rc.2. Not sure how exactly it all works, but I thought it might be worth mentioning here.
Hi Guys,
Any news on this subject?
Cheers.
Yes! It's actually queued up to be worked on soon! There will be movement on this coming soon
This will be shipped in 5.1.0
Description
Microsoft Entra ID authentication is now supported for Azure Functions using the isolated worker model.
Documentation
https://docs.particular.net/nservicebus/hosting/azure-functions-service-bus/#configuration-servicebus-connection