Lars Kemmann
My feedback
-
2,224 votes
Work is actively underway to add naked domain support with an automatic renewal flow to App Service Managed Certificates. There have been some snags getting the auto-renewal flow working. We understand these kinds of delays are frustrating, but rest assured the feature is being worked on and is coming in the future.
-Azure App Service Team
Lars Kemmann
supported this idea
·
-
3 votesLars Kemmann
shared this idea
·
-
403 votes
We have a sample for this use case here: https://github.com/azure-ad-b2c/samples/tree/master/policies/invite
Let us know what you think and if this fits your use case.
An error occurred while saving the comment An error occurred while saving the comment Lars Kemmann
commented
Can't you just port the AAD B2B invite & redemption logic over? That solves the multitenancy problem so elegantly!
Lars Kemmann
supported this idea
·
-
155 votes
Thank you for the feedback. We will look into this.
An error occurred while saving the comment Lars Kemmann
commented
Any update on this? It's been three years since the last update and this is still super-important for building cost-effective IoT solutions.
Lars Kemmann
supported this idea
·
An error occurred while saving the comment Lars Kemmann
commented
This should be done via support for the complex data types in Event Hubs' existing Avro-based Archive feature that was recently launched. That would enrich multiple data sources for ADF, not just Event Hubs, and it would also use an existing well-tested solution for egress from Event Hubs while bypassing the Event Hub egress quotas.
-
42 votes
Just since it’s been a while, I wanted to reconfirm that this is planned.
Lars Kemmann
supported this idea
·
-
138 votes
We are currently prioritizing Azure AD as and identity provider into B2C. We will review this request after that work is done. Keep the requests coming! /Jose Rojas
An error occurred while saving the comment Lars Kemmann
commented
So I've looked at this more and I believe the idea as Sven shared it is exactly what is needed. I found a StackOverflow post yesterday that seems to get halfway there -- the multi-tenant app is based on a "normal" AAD tenant, not in the B2C tenant, and the two are linked up via custom policy -- but it's a big step in the right direction.
https://stackoverflow.com/questions/48897555/multi-tenant-azure-ad-in-azure-ad-b2c
Now if we can just base the app in the B2C tenant and link those up (ideally with a clean Portal-based UX but at least with a how-to article) then we are all set! :)An error occurred while saving the comment Lars Kemmann
commented
Can't you just port the AAD B2B invite & redemption logic over? That solves the multitenancy problem so elegantly!
Lars Kemmann
supported this idea
·
-
315 votes
We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to aadb2cpreview@microsoft.com.
When you say “support for Microsoft Authenticator”, which feature are you referring to?
1. The ability to see the codes in the authenticator app
2. The ability to receive push notifications for MFAIf both, which do you prefer more?
Again, please email your feedback to aadb2cpreview@microsoft.com. Feel free to include more details about your scenarios/requirements!
Lars Kemmann
supported this idea
·
-
110 votes
An error occurred while saving the comment Lars Kemmann
commented
This would be a *killer* feature if you can make it work for real-time (IoT, etc.) SaaS ISVs who want to publish their Power BI datasets on AppSource and include real-time data in those datasets.
Lars Kemmann
supported this idea
·
-
2 votes
Thank you for your feedback and interest in Azure Bot Service. We are continually evaluating the list of the supported channel by Azure Bot Service. Please review https://docs.microsoft.com/en-us/azure/bot-service/bot-service-manage-channels?view=azure-bot-service-4.0
This topic is under review, and we will provide periodic updates.
Lars Kemmann
shared this idea
·
-
109 votes
Thank you all for sharing the feedback and upvoting for this feature. It is something being reviewed internally by the team and will be considered in the next wave of planning.
Lars Kemmann
supported this idea
·
-
143 votes11 comments · Azure Monitor-Application Insights » Service monitoring and diagnostics · Flag idea as inappropriate… · Admin →
Thanks for your feedback. We are working on prioritizing this work, and will post an update soon.
Lars Kemmann
supported this idea
·
-
125 votesunder review ·
AdminAzure Stream Analytics Team on UserVoice
(Product Manager, Microsoft Azure)
responded
we will consider this request.
Lars Kemmann
supported this idea
·
-
7 votesLars Kemmann
supported this idea
·
-
842 votesLars Kemmann
supported this idea
·
-
793 votes
Support for creating a container in ARM templates is now done. We have begun work to support Tables and Queues.
Here is a link to a sample template to create a container: https://azure.microsoft.com/en-us/resources/templates/101-storage-blob-container/
Lars Kemmann
supported this idea
·
-
371 votes
Currently, you can use “App Registration” blade in the Azure Portal (outside of the Azure AD B2C blades) to register an apps that define application permission and the register apps that use client credentials to request these. The caveat is that this is done using the same mechanism that you’d use in regular Azure AD.
Ideally we’d have a first class experience for this in the Azure AD B2C blades or at least have an Azure doc that walks you through the experience I just summarized, so I’m leaving this feature ask open.
It would be great if you guys can add comments with your feedback. What scenarios areyou trying to achieve? Does the approach above help you achieve what you want to achieve? Does the experience to do so work for you guys and if not, what would you like to see?
Lars Kemmann
supported this idea
·
-
163 votes
Thanks for the idea.
Lars Kemmann
supported this idea
·
-
331 votes
Thanks for your idea.
Lars Kemmann
supported this idea
·
-
25 votesLars Kemmann
supported this idea
·
-
67 votes
Thanks for reaching out. We hear you and we are working on it but will be delivering in CY18.
Thank you,
GuyLars Kemmann
supported this idea
·
Update? This is genuinely important. I need one place to go for customer identity, regardless of whether it's self-service sign-up or customer-managed (multi-tenant AAD).