3 votesDirk Boer shared this idea ·
this feature has been postponed as it wouldn’t be complete and might be revisited later if standards/supported features by CAs and browsers change (double wildcard certificates are not supported standard, resulting in no way to secure double wildcard domain)Dirk Boer commented
This is a really big blocker for SAAS applications with no simple workaround. According to this stackexchange https://serverfault.com/questions/104160/wildcard-ssl-certificate-for-second-level-subdomain it is actually working on modern browsers.
Any update on an ETA? Could this be months or years?
AAD currently requires a strict directory scoping. We can investigate options if this is a popular request.
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)Dirk Boer commented
Yeah, please copy paste this somewhere in your codebase:
if ( CurrentBill >= Account.SpendingLimit )
The lack of this feature is absolutely ridiculous. Usually I'm a big Microsoft and Azure fan, but this is completely unsellable. I can't get rid of the feeling that this was a deliberate trap to make some extra money by companies that are paying less attention.