Service Bus now supports Azure AD authentication in preview. To learn more, see: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-role-based-access-controlAnonymous shared this idea ·
We are looking for private preview customers who are interested in using Azure AD (single tenant only) or any other custom OIDC compliant identity providers in your built-in policies. If you are interested, please send an email specifying this specific request to firstname.lastname@example.org with your Azure AD B2C tenant name.
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
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?
Thank you for your feedback. Providing this functionality is on our backlog but there is no ETA we can share at this time. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
We are always looking to improve the speed we accomplish VIPSwap.
This work is on our backlog and currently under consideration. We will update here if this changes.
We understand this is a top customer ask and as such it is currently on our backlog to be prioritized. We will update when the status changes.
Changing this and clarifying. You can do this today with the Event Grid trigger (e.g. create an event grid trigger and then add subscriptions for each container in a storage account – or many storage accounts – and point to same function). That’s the way that works today and is planned to be the solution for this short term. However leaving this open as I think it was more general to have the Blob and not the Event Grid trigger do this. Keep the votes coming and comment on if Event Grid may not be enough.
Per the GitHub issue, this is not something we plan to do.
We are starting to look into the feasibility of this and the experience that people are looking for. If you are interested to provide feedback on how you’d like to see this implemented please comment here https://github.com/Azure/azure-functions-host/issues/4459
This remains unplanned – please keep the votes coming!
The below is still accurate, but updating to better reflect product backlog. Keep the votes coming.
No plans for this right now, but please keep the votes coming.
Moving this work item to unplanned, as it is clear that this request is no for a global throughput limit.
We do now offer the ability to limit your maximum instances in the Premium plan, which will allow you to avoid swamping downstream resources. https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan#plan-and-sku-settings
We prioritized that above a max call per X limit, because our only control to limit throughput is to outright deny some number of requests above a threshold.
Keep the feedback coming!
Azure Functions Team