Christian Weiss
My feedback
-
6 votes1 comment · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
This is on our plan. Thanks for your feedback !
Christian Weiss
supported this idea
·
-
280 votes
Please tell us a bit more about scenarios you are trying to enable and how do you see this feature working.
Christian Weiss
supported this idea
·
-
259 votesChristian Weiss
supported this idea
·
-
222 votesChristian Weiss
supported this idea
·
-
1,736 votesChristian Weiss
supported this idea
·
-
35 votes
Great ask. Keep the votes coming. Nothing planned short term.
-
JeffChristian Weiss
supported this idea
·
-
151 votes
We have started the planning for this feature and hope to have a preview by the end of the calendar year. In the meantime, could you respond to aadb2cpreview@microsoft.com with the answers to the following questions:
- In which scenarios do you plan to force the user to change his/her password?
- What kind of information (if any) would you like to get back if the user goes through the reset flow?
- Do you currently or plan to track which users have reset their password?Christian Weiss
supported this idea
·
-
163 votes
Thank you. We will examine the experience of duplicate sign ups across Identity providers. Would performing this check by using the email address be sufficient?
BTW, Linking multiple provider accounts to one user is in our roadmap and we’ve already achieved it in preview…
We look forward to your feedback
/Jose Rojas
Christian Weiss
supported this idea
·
-
38 votes
Thanks for the feedback. We will take this under review, and report back.
Christian Weiss
supported this idea
·
-
1,985 votes73 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
Thanks for the suggestion. We recognise the strategic importance of DNSSEC and it is a key feature on our long-term backlog.
DNSSEC represents a very large engineering investment, and hence we have to prioritize carefully vs other work. The most customer data we can get supporting the need for DNSSEC support, the better prioritization decisions we can make. We appreciate your votes and your comments.
Christian Weiss
supported this idea
·
-
1,086 votes226 comments · Azure Active Directory » End user experiences · Flag idea as inappropriate… · Admin →
Folks,
Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).
First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.
Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this…
Christian Weiss
supported this idea
·
-
63 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 7191872
Christian Weiss
supported this idea
·
-
150 votes
Thanks for the suggestion. We are looking into this scenario for a future release. “PolyBase should allow escaping row, field and string delimiters in string fields” – 8826021.
Christian Weiss
supported this idea
·
-
27 votes
Sorry for the confusion, there was a regression during deployment in the Large Object support that caused a rollback of the functionality. We are actively working on getting a fix.
Christian Weiss
supported this idea
·
-
463 votes
Thank you for your feedback. I have discussed this in more detail with our team.
You are correct the workaround suggested to use .AsEnumerable().FirstOrDefault(). should not be a recommended work around. This way results in materializing all documents on the client first before getting the 1st document, which is not very efficient and the exact opposite of what you are trying to achieve.
Instead we recommend you use Take(1).AsEnumerable() and then .First() or .Single() or .FirstOrDefault() for Single() and First(). Take(1) is translated to SELECT TOP 1 and is processed server-side so more efficient than the previous suggestion and is what you are trying to achieve.
As to the original ask. The support for these operations can be done, but this work is not prioritized against the other work we want to deliver. I will move this back as unplanned but please note this is on our roadmap.
Thanks again…
Christian Weiss
supported this idea
·
-
384 votes
This support is planned for SQL DB Managed Instances:
Thanks
Christian Weiss
supported this idea
·
-
25 votesChristian Weiss
supported this idea
·
-
56 votes
This is very good feedback. Today we have separate datasources for what your quotas are (e.g. network, memory), and the metrics that we emit. Ideally, we could bring those two points together to give you a percentage of those metrics.
Also, once these are exposed, they will automatically be available for autoscale — already today you can use any exposed metric for scaling.
Christian Weiss
supported this idea
·
-
3 votesChristian Weiss
supported this idea
·
-
65 votesChristian Weiss
supported this idea
·
VNET integration should really be included in ALL plans - even Basic. We will not use API management until that's changed.