Scott Arbeit
My feedback
-
1,720 votes
Thank you for the feedback. We are investigating this feature request and I will update this status as we make progress.
Best,
JasonScott Arbeit
supported this idea
·
-
1,049 votes
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.
Scott Arbeit
supported this idea
·
-
12 votesScott Arbeit
supported this idea
·
-
99 votes
An error occurred while saving the comment Scott Arbeit
shared this idea
·
-
503 votesScott Arbeit
supported this idea
·
-
842 votesScott Arbeit
supported this idea
·
-
396 votesScott Arbeit
supported this idea
·
-
7 votesScott Arbeit
shared this idea
·
-
61 votes
We’ll work on this
Scott Arbeit
supported this idea
·
An error occurred while saving the comment Scott Arbeit
commented
I'm seeing this too, with almost any blade open. If I switch to another tab in IE, the CPU usage of the Azure Portal tab drops. So... yay for figuring out when the portal is the selected tab; and boo for running so much JavaScript that it sucks up double-digit CPU.
-
245 votes
AAD currently requires a strict directory scoping. We can investigate options if this is a popular request.
An error occurred while saving the comment Scott Arbeit
commented
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!
Scott Arbeit
supported this idea
·
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?