We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.
We’ve put out a new version of the sign in policy called sign in v2. This is available through the new portal experience and we have rebranded policies as user flows. Please give this a try and give us feedback through this link: https://microsoft.qualtrics.com/jfe/form/SV_0Gu45RkBy2YR1kh
Seven months later... I'm writing a .NET Core app that's going to talk to Service Bus, and I do a search to see if there's a .NET Core implementation of the Service Bus SDK, and I find my own feedback. Any updates? Is the team working on it at least?
For applications that require cross document join, please consider the Gremlin API: https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet, which has primitives for joins, traversals, and other graph operations.
We are evaluating expanding the SQL grammar to support graph functionality, which will provide the ability to perform cross-document JOINs. Please upvote this item to help us prioritize this work.
We’ll work on this
AAD currently requires a strict directory scoping. We can investigate options if this is a popular request.
I'm not sure what the motivation was to go with the one-account-at-a-time view, but if that's absolutely necessary for some back-end reason that I don't understand, could we at least get to choose which account comes up by default? Right now I happen to be working inside of a different account than the one that the new code has chosen as my default, so the first thing I have to do every time I log in to the Portal is change my subscription. It's just two clicks, but, still... it's unnecessary, and I can't imagine how the Portal UX team thought this was an improvement. Thanks!