Our eventual goal is to connect every service in Azure to publish events, however, we haven’t started on Service Bus Standard integration yet.
We’re passing your feedback along to the Service Bus team, but as always make sure you let them know as well so they hear your voice!
Most use-cases are priced out by Premium, the only other option for using Logic App triggers is polling which causes Logic Apps to be billed for every connector as each poll considers the app as "evaluated" -- so many of my clients are stuck between two bad pricing options with no way out...we could really use this feature.
Just since it’s been a while, I wanted to reconfirm that this is planned.
Great ask. Keep the votes coming. Nothing planned short term.
We are still under consideration for this feature. In the meanwhile, could you use Azure CDN to accomplish this?
Currently, if you use Service Bus triggers for Logic Apps, the trigger uses a time-period polling mechanism to run. Unfortunately, this incurs charges for the entire logic app set of connectors with each poll as it considers this trigger as "evaluated". The only other, newer, option, is to use Event Grid triggers emitted from Service Bus to trigger the Logic App, but this is only available to the Premium SKU of Service Bus. This incurs nearly $10,000 in yearly cost. This presents two different, overly expensive options, for a simple task -- Service Bus triggering a logic app should not require polling and evaluation of all Logic App connectors. If Event Grid is the way forward, it should be available of non-Premium SKUs so it can be utilized by the customers who need it most. Customers who want quality architecture to combine messaging and serverless shouldn't be subjected to such extreme barriers of entry.
This is in progress for Azure CDN from Microsoft.
-Max G [MSFT]
From a consulting and solutioning perspective, the lack of this feature makes Azure a tough sell. Explaining to potential customers that you have to jump through hoops on almost all Azure services to setup SSL, which has become ubiquitous with the modern web, is challenging if not pitiful. Please, please, please, launch some sort of initiative to make SSL available and easily integrated across web-facing services. The "solution" of "oh you can use ssl but you have to upgrade plans / use a cdn / etc" makes everyone in the room cringe.
You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at email@example.com.
Please tell us a bit more about scenarios you are trying to enable and how do you see this feature working.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?